Hi all,
A few weeks ago, I installed some DS-2CD2347G3-LIS2UY/SL 2.8 cams.
I've also installed the latest HiTools which marked 2 cams with 'update-available' which I did ... \*/ unfortunately 2 cameras ended up bricked real badly.
Tried the reset button, while running wireshark to look for bootP / tft / .. activity but no success.
managed to fix a UART serial connection via the Molex 1.25mm connector (pin 1,2,3 ) and managed to have a psh shell where i could see that during boottime, the U-bootloader was still loaded intact, but once the kernel started to load, it failed to load some required modules hence couldn't load/find initrun.sh script. so it stalled in the BusyBox v3.0.0 protected shell (/bin/psh) - because of that, some diagnostic davinci commands becom also unusable.
dmsg tells me that the kernel itselfs load correctly, and busy box partially, it breaks after partition and runtime initialisation.
Interupting the bootloader (<ctrl + u> during boottime) gave me some options to restore ethernet / ip connectivity which allows me to initiate a tftp-session to download digicap.dav. but unfortunatly, still no success.
because of the previous runtime errors, I think that restoring the correct digicap.dav won't un-brick it as of the 'broken' runtime image.
Next step was trying to hard factory reset; this can be done via tfpt by issuing the 'upf' command in the boot menue.
But here I stranded; it looks for a file "mImage_h13u" , which I don't have and cannot find on the Hikvision portal.
anybody here who was before facing this issue and found some solution/workeround ?
many thx
200OK
A few weeks ago, I installed some DS-2CD2347G3-LIS2UY/SL 2.8 cams.
I've also installed the latest HiTools which marked 2 cams with 'update-available' which I did ... \*/ unfortunately 2 cameras ended up bricked real badly.
- no usable ip connectivity anymore
- and endless bootloop.
Tried the reset button, while running wireshark to look for bootP / tft / .. activity but no success.
managed to fix a UART serial connection via the Molex 1.25mm connector (pin 1,2,3 ) and managed to have a psh shell where i could see that during boottime, the U-bootloader was still loaded intact, but once the kernel started to load, it failed to load some required modules hence couldn't load/find initrun.sh script. so it stalled in the BusyBox v3.0.0 protected shell (/bin/psh) - because of that, some diagnostic davinci commands becom also unusable.
dmsg tells me that the kernel itselfs load correctly, and busy box partially, it breaks after partition and runtime initialisation.
Interupting the bootloader (<ctrl + u> during boottime) gave me some options to restore ethernet / ip connectivity which allows me to initiate a tftp-session to download digicap.dav. but unfortunatly, still no success.
because of the previous runtime errors, I think that restoring the correct digicap.dav won't un-brick it as of the 'broken' runtime image.
Next step was trying to hard factory reset; this can be done via tfpt by issuing the 'upf' command in the boot menue.
But here I stranded; it looks for a file "mImage_h13u" , which I don't have and cannot find on the Hikvision portal.
anybody here who was before facing this issue and found some solution/workeround ?
many thx
200OK