I have a DH-NVR5216-4KS2 that I bought back in 2017 from Andy, along with 8 x Dahua IPC cameras of various types.
All cameras are on the IPC-HX5X3X-Rhea_MultiLang_PN_Stream3_V2.800.0000013.0.R.191202 firmware (so latest, I believe).
I decided to update the NVR to the DH_NVR5XXX-4KS2_MultiLang_V4.001.0000003.2.R.201010 firmware (it was on: DH_NVR5XXX-4KS2_Eng_V3.215.0000000.3.R.20171211, so a little behind latest V3.216....)
Anyway, during the update clearly something went wrong and I ended up in the loop of V4 screen showing up & then rebooting...
I bought a USB to RS232 cable (I had a 3.3v / 5v USB to serial, but the NVR5216 clearly needed the full volts of RS232 to communicate) and then swapped TX/RX and got it showing up in Putty.
I managed to reflash using TFTP to DH_NVR5XXX-4KS2_MultiLang_V4.001.0000003.2.R.201010 firmware and it came up again just fine. It then appeared to be showing a bunch of error messages in the console when booting (things like using slave due to errors), so I used the web interface to roll it back to DH_NVR5XXX-4KS2_MultiLang_V3.216.0000006.0.R.20190223 and then after rebooting successfully under V3.216...6, used the web interface to upgrade to V4.001...3 again, which this time worked. Most of the error messages had by now gone away.
The console now shows the following when booting up (everything seems to be working OK):
Should I be worried by the 'err/failed' lines in the middle of this?
All cameras are on the IPC-HX5X3X-Rhea_MultiLang_PN_Stream3_V2.800.0000013.0.R.191202 firmware (so latest, I believe).
I decided to update the NVR to the DH_NVR5XXX-4KS2_MultiLang_V4.001.0000003.2.R.201010 firmware (it was on: DH_NVR5XXX-4KS2_Eng_V3.215.0000000.3.R.20171211, so a little behind latest V3.216....)
Anyway, during the update clearly something went wrong and I ended up in the loop of V4 screen showing up & then rebooting...
I bought a USB to RS232 cable (I had a 3.3v / 5v USB to serial, but the NVR5216 clearly needed the full volts of RS232 to communicate) and then swapped TX/RX and got it showing up in Putty.
I managed to reflash using TFTP to DH_NVR5XXX-4KS2_MultiLang_V4.001.0000003.2.R.201010 firmware and it came up again just fine. It then appeared to be showing a bunch of error messages in the console when booting (things like using slave due to errors), so I used the web interface to roll it back to DH_NVR5XXX-4KS2_MultiLang_V3.216.0000006.0.R.20190223 and then after rebooting successfully under V3.216...6, used the web interface to upgrade to V4.001...3 again, which this time worked. Most of the error messages had by now gone away.
The console now shows the following when booting up (everything seems to be working OK):
Code:
Spi(cs1) ID: 0xEF 0x40 0x13 0x00 0x00 0x00
Special NAND id table Version 1.36
Nand ID: 0xEF 0xF1 0x80 0x95 0x00 0x00 0x00 0x00
stmmac_init,568,0x70431,3
MAC: 00-00-23-34-45-66
U-Boot 2010.06-svn4783 (Jun 22 2020 - 22:18:37)
In: serial
Out: serial
Err: serial
ver is not set set and save it
squashfs use gzip
SCU: load slave image OK
spi env sysbackup=0
Read backup misc byte ... no env and backup env tc !!!
ok!
index 109 len 22
Erasing Nand...
Writing to Nand... done
restore backup to env!
GpioI2cMcuRecvAck 114 err
__FUNCTION__ = GpioI2cReadByteMcu, __LINE__ = 244
GpioI2cReadByteMcu faield
[is2uProduct] get failed
PRODUCT:1U
stmmac_init,692,0x70431,3
Hit any key to stop autoboot: 0
stmmac_init,692,0x70431,3
stmmac_init,692,0x70431,3
NET_autoLipDetect timeout
stmmac_init,692,0x70431,3
ARP Retry count exceeded; starting again
## Booting kernel from Legacy Image at 42000000 ...
Image Name: Linux-3.10.0_hi3536
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3000104 Bytes = 2.9 MiB
Load Address: 40008000
Entry Point: 40008000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Should I be worried by the 'err/failed' lines in the middle of this?