The NVR uses RS-232 on the DB9 connector on the back panel - not serial TTL.I've got a USB to TTL adapter that I have hooked up a few different ways to the 5 pin connector on the board which goes to the RS-232 plug on the outside of the box (don't have that type of cable handy.
There are several different combinations of hooking the wires up in which Putty will display the bootup sequence but no matter how the ground, Tx and Rx to the board, I am unable to stop the bootloader or get characters to display at any point.
Thank you so much for your reply!The NVR uses RS-232 on the DB9 connector on the back panel - not serial TTL.
The signal levels are quite different between the 2 standards.
RS-232 is bipolar 3 to 15V
Serial TTL is unipolar at 3.3V.
You will need an RS-232 interface, such as a USB-based adaptor version, configured as a null modem connection.
With that you will be able to fully interact with the NVR.
When you hit Control-U, there will be an update dialogue that will allow you to install the same firmware version as you have already applied.
The difference will be an implicit 'reset to defaults' that will clear the mangled configuration database that's the cause of the corrupted admin credentials.
You will need a tftp server such as the Jounin one - Hikvision's tftp updater doesn't handle files larger than 32MB.
Unfortunately, I read the memo at us.hikvision.com after updating firmware. How it wasn't as clear at www.hikvision.com/en, I don't know.
Ok, so i'm able to interact with the NVR now but cannot figure out how to configure Tftpd64 correctly. I've read lots of posts and no one seems to talk about how to set it up. I've got the firmware file in the Tftpd64 folder, that folder is set as current director, server interface is set to 192.168.1.128 (NVR is at 192.168.1.2 according to SADP) and all i'm seeing in putty are a bunch ofI'll post an update tomorrow afternoon!
T is for timeout.server interface is set to 192.168.1.128 (NVR is at 192.168.1.2 according to SADP) and all i'm seeing in putty are a bunch of
T T T T T ...... followed by retry count exceeded; starting again.
Windows Firewall/Defender is disabled.Another possibility - some AV products have network access protection that may prevent the NVR from accessing the PC.
If so - temporarily disable the Windows firewall, so inbound access isn't blocked, and any AV that's running.
Tried that and same result, T T T T TAs a long shot - also try the tftpd32.
Some members have reported problems when using the tftp64.
Yes, that's all that's needed, and IP addresses in the same range.I literally just need to have the .dav file in the Ttftpd64/32 directory and run the program, correct?