DS-7708NI-I4/8P Reboot Loop (Hikvision)

yorkie · Apr 4, 2024

Hello,
I recently purchased from house clearance a Hikvision DS7708NI-I4/8P NVR for part of a potential system upgrade. The unit had been password locked but I resolved that with the XML file reset method sent from tech support.
The unit came without a HDD and so I installed a spare 2TB seagate surveillance which I had lying around - and in the menu structure of the NVR I started a full disk test which too a few hours but eventually came through as successful, and states something like 1.8G free space (which sounds about right when accounting for partioning etc). Whilst the NVR was on it would make a series of beeps at regular intervals - if considered as Morse Code, the beeps were "dash-dash-dash-dot-dot".

In one menu setting it required the system to be restarted and so I did this, and as usual when the system loaded after the Hikvision splash screen, the dialog box pops up asking for system language as normal and then a second box asking if the display resolution can be set to 1920x1080 - previously I have ignored this and carried on as 1024x768 (although once before I did try it and it went through a boot loop then came back to showing the language dialog box)... BUT this time I selected "Yes" to which the unit then restarted.

Now the NVR is stuck in a boot loop... it turns on and beeps then the screen goes blank for a bit, then the HIKVISION "the system is loading" splash screen is shown (the monitor at this point shows 1024x768 resolution). After this the screen goes blank and the monitor shows it is in 1920x1080 resolution - and it stays blank, then eventually there is a faint 'click' heard within the NVR and it restarts then the same thing repeates again...... and this is using a VGA monitor. If I use the HDMI output I get the splash screen as normal, but as soon as it should show the language dialog box then the screen goes blank and the message "UNSUPPORTED" is shown. I have tried using a flatscreen TV with the HDMI input - first time round it showed the HIKVISION splash screen in 1024x768 then it went blank for a couple of seconds and then showed the HIKVISION screen again in 1920x1080, then it went blank and hasn't shown anything since (won't even show the 1024x768 splash screen now - even if I connect a VGA monitor, that will show the 1024x768 screen but the HDMI won't).... I have tried this with the LAN connected, LAN disconnected, HDD data lead disconnected but powered, HDD data and power connected, HDD fully disconnected, and all variations in between - all the same result.

Hikvision tech support is as unhelpful as expected in this regard, with Ye Olde "we can't provide support to end users or of devices not bought through an authorised agent" type response.

There is no form of hard reset button on the motherboard, though I don't know if there are contacts on the board which would reset the system if shorted (but I don't want to go shorting random connections together for obvious reasons). There is an RS-232 D-SUB type connection on the back of the unit but no JST-ZH 4-pin header on the board.

Part of me is wondering whether to take out the motherboard battery - would that perform a hard reset back to factory default? I don't want to take it out if it won't perform a reset.

* Firmware version V4.61.020 *

Any help appreciated

--
PS, I have seen this thread
Hikvision - Clearing Passwords and/or Loading Firmware via TTL Serial
though I'm not particularly sharp with PUTTY so would likely need specific guidance right from the app initially loading up, if this is the necessary route to go down.

The unit was bought cheap so it's not a massive loss if no fix can be achieved, though I am on a tight budget so any loss is still a loss, but I am of the opinion that if something can be repaired to a working state then it should be done instead of throwing into landfill... Plus I am pretty PO'd about it going like this after it was working so would prefer to get it back to working again.

alastairstevenson · Apr 6, 2024

yorkie said:
Part of me is wondering whether to take out the motherboard battery - would that perform a hard reset back to factory default? I don't want to take it out if it won't perform a reset.

I'm pretty sure all that battery does is maintain the system clock when power is off.

yorkie said:
There is no form of hard reset button on the motherboard, though I don't know if there are contacts on the board which would reset the system if shorted (but I don't want to go shorting random connections together for obvious reasons).

None that I'm aware of for that model.

yorkie said:
There is an RS-232 D-SUB type connection on the back of the unit

This will provide access to the serial console.
You'll need a USB to RS-232 (not serial TTL) convertor, and a null modem cable, widely available on eBay.

yorkie said:
I'm not particularly sharp with PUTTY so would likely need specific guidance right from the app initially loading up

You'll be fine, and get plenty help here.
The serial console should show why it's rebooting, and allow recovery to be attempted.

yorkie · Apr 6, 2024

I do already have a USB-to-serial converter, but it's a male D-SUB because I'd got it for another piece of equipment... so I'll be getting one with a female end later today (and then with Royal Mail speed it'll probably be next saturday before it comes at the soonest!)

yorkie · Apr 9, 2024

alastairstevenson said:
You'll need a USB to RS-232 (not serial TTL) convertor, and a null modem cable, widely available on eBay.

The USB to RS-232 cable has arrived this morning (quicker than I expected, for once).

What would the null modem cable be needed for? The NVR is currently next to the PC which I'll be using for debugging, so wouldn't it simply be a case of using the USB to RS-232 cable to connect the PC to the NVR (with the null modem cable then unused)?

... if this USB to RS-232 cable is all that's required now, what would be the first steps in getting any form of dialogue using PUTTY?

alastairstevenson · Apr 9, 2024

yorkie said:
What would the null modem cable be needed for? The NVR is currently next to the PC which I'll be using for debugging, so wouldn't it simply be a case of using the USB to RS-232 cable to connect the PC to the NVR (with the null modem cable then unused)?

In the RS-232 serial comms standard there are 2 types of equipment - DTE (Data Terminal Equipment, eg a PC) and DCE (Data Communications Equipment, eg a modem). These are wired such that TX (Transmit Data) on the DTE connects to RX (Receive Data) on the DCE and vice versa. There are also various control signals, but we'll ignore these just now for simplicity.
The PC and NVR are usually the same RS-232 equipment type, therefore a 'null modem cable' is needed to ensure the signals are correctly connected.
You should also find that the gender does not match - unless your USB to RS-232 is already wired as a null modem device.
Was it advertised as such?

yorkie said:
what would be the first steps in getting any form of dialogue using PUTTY?

Connect the cables to the PC and NVR, in the PC start PuTTY selecting the COM port of the USB convertor, with the setting 115,200 baud, 8 bits no parity.
Power on the NVR and you should see the serial console as it boots up.
At some point you should see the reboot start.
In PuTTY, use the 'Copy all to clipboard' option in the top left menu which will allow all the text so far to be pasted in to Notepad or similar for inspection / editing / posting / record-keeping etc.
There should be clues as to what is causing the reboot.

yorkie · Apr 9, 2024

alastairstevenson said:
In the RS-232 serial comms standard there are 2 types of equipment - DTE (Data Terminal Equipment, eg a PC) and DCE (Data Communications Equipment, eg a modem). These are wired such that TX (Transmit Data) on the DTE connects to RX (Receive Data) on the DCE and vice versa. There are also various control signals, but we'll ignore these just now for simplicity.
The PC and NVR are usually the same RS-232 equipment type, therefore a 'null modem cable' is needed to ensure the signals are correctly connected.
You should also find that the gender does not match - unless your USB to RS-232 is already wired as a null modem device.
Was it advertised as such?

Right I see, so kinda similar to a LAN crossover cable, but with a few extras. The USB-RS232 converter I got didn't say specifically that it acts as a null modem, but the listing mentions "Support automatic handshake protocol" though I suspect that's a variation of plug and play.

alastairstevenson · Apr 9, 2024

The standard also includes the connectors, so if one of the USB converters cable end fits the NVR, well and good. But generally the null modern cable would be needed to match up the gender and the signals.

yorkie · Apr 9, 2024

alastairstevenson said:
The standard also includes the connectors, so if one of the USB converters cable end fits the NVR, well and good. But generally the null modern cable would be needed to match up the gender and the signals.

I ordered one so that the 9-pin end would be the right gender to fit into the NVR.... I suppose I can connect it up and see if any data comes through, if not then I'll get a null modem cable too

alastairstevenson · Apr 9, 2024

yorkie said:
I ordered one so that the 9-pin end would be the right gender to fit into the NVR.

Did the item description mention that it was wired as a null modem connector? (link?)
edit Though I see above that you said it didn't.

yorkie · Apr 9, 2024

alastairstevenson said:
Did the item description mention that it was wired as a null modem connector? (link?)
edit Though I see above that you said it didn't.

It's a CH340 type cable, if that means anything... hardware ID details being "VID_1A86&PID7523&REV_0254".... just been hunting for drivers to get it working.
I believe it's most likey a standard cable not a null modem one - if you're thinking the same thing then I'll order a null modem cable overnight

yorkie · Apr 9, 2024

alastairstevenson said:
Connect the cables to the PC and NVR, in the PC start PuTTY selecting the COM port of the USB convertor, with the setting 115,200 baud, 8 bits no parity.
Power on the NVR and you should see the serial console as it boots up.
At some point you should see the reboot start.
In PuTTY, use the 'Copy all to clipboard' option in the top left menu which will allow all the text so far to be pasted in to Notepad or similar for inspection / editing / posting / record-keeping etc.
There should be clues as to what is causing the reboot.

Right well I've given it a try with the current cable and got nowhere.
Windows Device Manager shows the cable as working properly under "Ports (COM & LPT)" with it's proper name "USB-SERIAL CH340" and shows it being on COM4.
Started PUTTY and set that to serial and with the required baud/bit/parity settings and got "unable to open connection to COM4. Unable to configure serial port". This error only comes up on some attempts, on others I click to open the connection and there's nothing, a bit like on an old webpage where the form handling script for a button is missing.

yorkie · Apr 15, 2024

alastairstevenson said:
Did the item description mention that it was wired as a null modem connector? (link?)
edit Though I see above that you said it didn't.

I have the Null Modem Cable and the USB-to-Serial (CH340) converter all plugged in to the NVR. Windows device manager shows the CH340 as plugged into COM5 (I changed it to a USB directly on the motherboard).
Open PuTTY, input the required settings under the "session" tab with the 'Serial' box checked, and still I get the error "Unable to configure serial port"

Looking around on other forums, stackoverflow, etc, this seems to be a fairly common problem with PuTTY in not recognising a serial converter even when all the drivers are installed and working.

As a comparison, I have opened up Tera Term and in the initial setup dialogue I selected 'Serial' for the connection, and immediately the dropdown menu box showed "USB-SERIAL CH340 (COM5)" - which suggests the converter is installed correctly. I'm sat here with a blank window now in Tera Term as I'm unaware of the commands required, and I assume it doesn't automatically fill in text from the NVR

alastairstevenson · Apr 16, 2024

If the serial interface is working correctly, you'll see lots of chat from the NVR when it's powered on without having to issue any commands.

yorkie · Apr 16, 2024

alastairstevenson said:
If the serial interface is working correctly, you'll see lots of chat from the NVR when it's powered on without having to issue any commands.

Right well I just had a sudden DING moment and tried a little alteration.... I have opened up the NVR case and unplugged the 5-pin lead that goes from the inside of the Serial port, turned it roud, and plugged it in the other way; then I have the USB-Serial converter plugged in directly without a Null Moden Cable and have FINALLY got some talkback from the device

Get ready for a data dump

here it comes

Code:

[   87.442538] libphy: 1:07 - Link is Down
[   90.442538] libphy: 1:07 - Link is Up - 1000/Full
Copy /nand/uImage to 0x42000000...      [DONE]
MAC:   <<removed>>
|NUL ethaddr| TFTP server not found
## Booting kernel from Legacy Image at 42000000 ...
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] need to Authorization
[    2.609095] init(1) called reboot syscall, cmd: 0x0.
[    6.562534] libphy: 1:07 - Link is Up - 1000/Full
[   53.002421] libphy: STMMAC FIXED MII:01 - Link is Up - 1000/Full
[   56.142584] libphy: 1:07 - Link is Up - 1000/Full
[   87.132543] libphy: 1:07 - Link is Down
[   91.132587] libphy: 1:07 - Link is Up - 1000/Full
[  156.363429] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. Call hikwdt notifie                                                         r chain!
[  156.371379]            CPU0       Inc        CPU1       Inc        CPU2                                                                Inc        CPU3       Inc
[  156.382128]  32:         1         1         0         0         0         0                                                                  0         0      GIC  HIK_WDT_INT
[  156.393570]  35:     12875      2890         0         0         0         0                                                                  0         0      GIC  timer4
[  156.404532]  36:         0         0         0         0     13390      2894                                                                  0         0      GIC  timer6
[  156.415549]  37:         0         0         0         0         0         0                                                                  0         0      GIC  RTC Alarm
[  156.426823]  38:         0         0         0         0         0         0                                                                  0         0      GIC  uart-pl011
[  156.438185]  43:        34         0         0         0         0         0                                                                  0         0      GIC  Hisilicon Dmac
[  156.449895]  49:         0         0         0         0         0         0                                                                  0         0      GIC  hik_ir
[  156.460858]  50:         0         0         0         0         0         0                                                                  0         0      GIC  hi_cipher_irq
[  156.472477]  52:         1         0         0         0         0         0                                                                  0         0      GIC  ohci_hcd:usb2
[  156.484099]  53:         0         0         0         0         0         0                                                                  0         0      GIC  ehci_hcd:usb1
[  156.495713]  55:         0         0         0         0         0         0                                                                 12         2      GIC  stmmaceth
[  156.506983]  56:        10         0         0         0         0         0                                                                118        37      GIC  stmmaceth
[  156.518248]  57:         0         0         0         0         0         0                                                                  0         0      GIC  stmmaceth
[  156.529519]  58:         0         0         0         0         0         0                                                                  0         0      GIC  stmmaceth
[  156.540793]  59:       292         0         0         0         0         0                                                                  0         0      GIC  ahci
[  156.551636]  60:         0         0         0         0         0         0                                                                  0         0      GIC  xhci-hcd:usb3
[  156.563219]  78:         0         0         0         0         0         0                                                                  0         0      GIC  IVE
[  156.573972]  79:      6676      2891         0         0         0         0                                                                  0         0      GIC  AIO Interrupt
[  156.585592]  80:         8         0         0         0         0         0                                                                  0         0      GIC  hi_tde_irq
[  156.596959]  94:         0         0         0         0         0         0                                                                  0         0      GIC  hi_iommu
[  156.608158] 105:         6         0         0         0         0         0                                                                  0         0      GIC  timer
[  156.619092] 107:         0         0     12404      2914         0         0                                                                  0         0      GIC  timer5
[  156.630107] 108:         0         0         0         0         0         0                                                              14188      2916      GIC  timer7
[  156.641074] 112:     10892      3468         0         0         0         0                                                                  0         0      GIC  VOU Interrupt
[  156.652705] 125:         1         0         0         0         0         0                                                                  0         0      GIC  mali.0
[  156.663726] 126:         1         0         0         0         0         0                                                                  0         0      GIC  mali.0
[  156.674747] 127:         1         0         0         0         0         0                                                                  0         0      GIC  mali.0
[  156.685733] total: 70910
[  156.688316] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. I'm so Sorry (>_<).                                                         ..
[  156.695723] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. last_feedwdt:429495                                                         0042(jiffies64:4294952932,timeout:25)


DDR Training Suc


U-Boot 2010.06-svn (Jun 26 2015 - 15:08:07)

Protected at offset:0,size:40000 Protection status:[0x22f]=>[0x22f].
Hit ctrl+u to stop autoboot:  0
timeout for link [4338]!
yaffs: Mounting /nand
Copy /nand/uImage to 0x42000000...      [DONE]
MAC:   <<removed>>
|NUL ethaddr| TFTP server not found
## Booting kernel from Legacy Image at 42000000 ...
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] need to Authorization
[    2.609205] init(1) called reboot syscall, cmd: 0x0.
[    6.562636] libphy: 1:07 - Link is Up - 1000/Full
[   53.062375] libphy: STMMAC FIXED MII:01 - Link is Up - 1000/Full
[   56.132657] libphy: 1:07 - Link is Up - 1000/Full
[   87.144139] libphy: 1:07 - Link is Down
[   91.142952] libphy: 1:07 - Link is Up - 1000/Full
[  159.223200] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. Call hikwdt notifier chain!
[  159.231151]            CPU0       Inc        CPU1       Inc        CPU2       Inc        CPU3       Inc
[  159.241899]  32:         1         1         0         0         0         0         0         0      GIC  HIK_WDT_INT
[  159.253365]  35:     14189      2778         0         0         0         0         0         0      GIC  timer4
[  159.264345]  36:         0         0         0         0     13644      2782         0         0      GIC  timer6
[  159.275367]  37:         0         0         0         0         0         0         0         0      GIC  RTC Alarm
[  159.286652]  38:         0         0         0         0         0         0         0         0      GIC  uart-pl011
[  159.298034]  43:        34         0         0         0         0         0         0         0      GIC  Hisilicon Dmac
[  159.309750]  49:         0         0         0         0         0         0         0         0      GIC  hik_ir
[  159.320731]  50:         0         0         0         0         0         0         0         0      GIC  hi_cipher_irq
[  159.332364]  52:         1         0         0         0         0         0         0         0      GIC  ohci_hcd:usb2
[  159.343988]  53:         0         0         0         0         0         0         0         0      GIC  ehci_hcd:usb1
[  159.355618]  55:         0         0         0         0         0         0        12         2      GIC  stmmaceth
[  159.366899]  56:         6         0         0         0         0         0       126        37      GIC  stmmaceth
[  159.378180]  57:         0         0         0         0         0         0         0         0      GIC  stmmaceth
[  159.389465]  58:         0         0         0         0         0         0         0         0      GIC  stmmaceth
[  159.400748]  59:       294         0         0         0         0         0         0         0      GIC  ahci
[  159.411601]  60:         0         0         0         0         0         0         0         0      GIC  xhci-hcd:usb3
[  159.423189]  78:         0         0         0         0         0         0         0         0      GIC  IVE
[  159.433957]  79:      6971      2779         0         0         0         0         0         0      GIC  AIO Interrupt
[  159.445587]  80:         8         0         0         0         0         0         0         0      GIC  hi_tde_irq
[  159.456970]  94:         0         0         0         0         0         0         0         0      GIC  hi_iommu
[  159.468185] 105:         6         0         0         0         0         0         0         0      GIC  timer
[  159.479129] 107:         0         0     13721      2803         0         0         0         0      GIC  timer5
[  159.490151] 108:         0         0         0         0         0         0     12006      2804      GIC  timer7
[  159.501125] 112:     11227      3334         0         0         0         0         0         0      GIC  VOU Interrupt
[  159.512759] 125:         1         0         0         0         0         0         0         0      GIC  mali.0
[  159.523779] 126:         1         0         0         0         0         0         0         0      GIC  mali.0
[  159.534810] 127:         1         0         0         0         0         0         0         0      GIC  mali.0
[  159.545791] total: 72249
[  159.548374] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. I'm so Sorry (>_<)...
[  159.555784] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. last_feedwdt:4294950440(jiffies64:4294953251,timeout:25)


DDR Training Suc


U-Boot 2010.06-svn (Jun 26 2015 - 15:08:07)

Protected at offset:0,size:40000 Protection status:[0x22f]=>[0x22f].
Hit ctrl+u to stop autoboot:  0
timeout for link [4430]!
yaffs: Mounting /nand
Copy /nand/uImage to 0x42000000...      [DONE]

alastairstevenson · Apr 17, 2024

Well done for getting there!

yorkie said:
[HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. I'm so Sorry (>_<).

I'm speculating that the reboot is caused by a hardware fault.
It looks like the watchdog timer (wdt) has expired and forced a reboot.

wdt is a hardware timer that needs to be periodically 'fed' (re-initiallised) by CPU activity.
If it runs down, it indicates a CPU (there are multiple cores in this model) has stalled or is stuck in a loop and a reboot is required.

It should be easy enough to test if a firmware re-flash would change anything, in case a corruption is causing a program loop.
Try interrupting the bootloader (Control-U till it repeats, power on the NVR) and there will be either an update menu, or bootloader commands.

yorkie · Apr 17, 2024

alastairstevenson said:
It should be easy enough to test if a firmware re-flash would change anything, in case a corruption is causing a program loop.
Try interrupting the bootloader (Control-U till it repeats, power on the NVR) and there will be either an update menu, or bootloader commands.

It has gone straight to an update action.

Code:

This program will upgrade software.
*******************************************************
*  ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY!     *
*  Don't reset machine,or anything that interrupt it. *
*  The upgrade process must finish in 10 minutes!     *
*  If this program fails,machine might be unusable,   *
*  and you will need to reflash again.                *
*  If you find this too risky,power off machine now.  *
*******************************************************

Now press [u/U] key to upgrade software: u
File system error,please upgrade by TFTP

Please input ip address of device: <<removed>>
Please input ip address of upgrade server:

Presumably the "upgrade server" would refer to the PC which I'm currently on, and not a remote server...?

At the moment however I don't have an upgrade file for this. I assume I have to download firmware from here

https://www.hikvisioneurope.com/uk/portal/?dir=portal/Product%20Firmware/Hikvision/04%20Back%20Ends/NVR/01%20I%20Series%20%5B76%2077%2096%20NI-I%5D

- however I am unsure what version of the software the unit is currently running, and I suspect going straight to the latest update won't work.

Or does this line in the bootlog suggest the current version the NVR is running:

Code:

U-Boot 2010.06-svn (Jun 26 2015 - 15:08:07)

... I've just noticed the log actually states "file system error, please upgrade by TFTP" so is there another step to this?

alastairstevenson · Apr 17, 2024

yorkie said:
Presumably the "upgrade server" would refer to the PC which I'm currently on, and not a remote server...?

Yes, the PC on your LAN that must be running a standard tftp server, not the Hikvision tftp updater which has a 32MB filesize limit.
The one from Phiippe Jounin usually works OK.

Tftpd32: an opensource free firewall friendly dhcp, syslog sntp and tftp server/service for windows, tftp client

A free tftp and dhcp server for windows, freeware tftp server

pjo2.github.io

yorkie said:
At the moment however I don't have an upgrade file for this. I assume I have to download firmware from here

There can be issues in updating from the V3.x firmware to the V4.x firmware if the V3.x firmware isn't new enough - so in the absence of knowing the current version, it would be prudent to attempt the newest V3,x version before trying for a V4.x version.
If it already has the V4.x version, the downgrade block will simply reject it.
A bigger selection including V3.x versions is here :

https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/02%20%20NVR/00%20%20Product%20Firmware/04%20I-series/%5B76%2077%2096%20NI-I%5D

Good luck! Though I suspect the firmware update may not fix the problem, bust easy enough to try..

yorkie · Apr 18, 2024

alastairstevenson said:
Good luck! Though I suspect the firmware update may not fix the problem, bust easy enough to try..

Turns out I had made a note of the firmware when I first got the NVR - 4.61.020....
I have tried flashing that version back onto the NVR, it went through OK but still got the same reboot loop.

I have then tried flashing firmware 4.61.025 onto it... again, the update went through fine but it is still going through the reboot loop.

logs:-

Code:

This program will upgrade software.
*******************************************************
*  ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY!     *
*  Don't reset machine,or anything that interrupt it. *
*  The upgrade process must finish in 10 minutes!     *
*  If this program fails,machine might be unusable,   *
*  and you will need to reflash again.                *
*  If you find this too risky,power off machine now.  *
*******************************************************

Now press [u/U] key to upgrade software: u
File system error,please upgrade by TFTP

Please input ip address of device: <<removed>>
Please input ip address of upgrade server: <<removed>>
Confirm?(y/n): y
timeout for link [4999]!
MAC:   <<removed>>
TFTP from server <<removed>>; our IP address is <<removed>>
Download Filename 'digicap.dav'.
Download to address: 0x40008000
Downloading: #################################################
done
Bytes transferred = 63845196 (3ce334c hex)
headEx checkSum ok !
uImage checkSum ok !
start.sh checkSum ok !
sys_app.tar.lzma checkSum ok !
gui_res.tar.gz checkSum ok !
webs.tar.lzma checkSum ok !
i18n.tar.lzma checkSum ok !
RSA checkSum ok !
new_10.bin checkSum ok !
fac_check.bin checkSum ok !
start to erase nand flash partition 0  start: 0x200000 end: 0x6200000 len: 0x6000000 ...
Erasing at 0x61e0000 -- 100% complete.
--- OK!
start to erase nand flash partition 1  start: 0x6200000 end: 0xC200000 len: 0x6000000 ...
Erasing at 0xc1e0000 -- 100% complete.
--- OK!

start to write files to partition 0...
yaffs: Mounting /nand
11-1.  write /nand/headEx len: 1024
11-2.  write /nand/uImage len: 10484976
11-3.  write /nand/start.sh len: 19600
11-4.  write /nand/sys_app.tar.lzma len: 30187472
11-5.  write /nand/gui_res.tar.gz len: 13734024
11-6.  write /nand/webs.tar.lzma len: 7811056
11-7.  write /nand/i18n.tar.lzma len: 1603856
11-8.  write /nand/RSA len: 24
11-9.  write /nand/new_10.bin len: 808
11-10.  write /nand/fac_check.bin len: 872
11-11.  write flag file /nand/version.bin len: 4
update partition 0 success!
save exit: isCheckpointed 1

start to write files to partition 1...
yaffs: Mounting /nand
11-1.  write /nand/headEx len: 1024
11-2.  write /nand/uImage len: 10484976
11-3.  write /nand/start.sh len: 19600
11-4.  write /nand/sys_app.tar.lzma len: 30187472
11-5.  write /nand/gui_res.tar.gz len: 13734024
11-6.  write /nand/webs.tar.lzma len: 7811056
11-7.  write /nand/i18n.tar.lzma len: 1603856
11-8.  write /nand/RSA len: 24
11-9.  write /nand/new_10.bin len: 808
11-10.  write /nand/fac_check.bin len: 872
11-11.  write flag file /nand/version.bin len: 4
update partition 1 success!
save exit: isCheckpointed 1
Press ENTER key to reboot
resetting ...


DDR Training Suc


U-Boot 2010.06-svn (Jun 26 2015 - 15:08:07)

Protected at offset:0,size:40000 Protection status:[0x22c]=>[0x2af].
Hit ctrl+u to stop autoboot:  0
timeout for link [4406]!
yaffs: Mounting /nand
yaffs: restored from checkpoint
Copy /nand/uImage to 0x42000000...      [DONE]
MAC:   28-57-BE-89-41-B4
|NUL ethaddr| TFTP server not found
## Booting kernel from Legacy Image at 42000000 ...
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] need to Authorization
[    2.609229] init(1) called reboot syscall, cmd: 0x0.
[    6.562636] libphy: 1:07 - Link is Up - 1000/Full
[   65.802724] libphy: STMMAC FIXED MII:01 - Link is Up - 1000/Full
[   68.262692] libphy: 1:07 - Link is Up - 1000/Full
[  100.142640] libphy: 1:07 - Link is Down
[  103.202659] libphy: 1:07 - Link is Up - 1000/Full
[  171.163522] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. Call hikwdt notifier chain!
[  171.171473]            CPU0       Inc        CPU1       Inc        CPU2       Inc        CPU3       Inc
[  171.182219]  32:         1         1         0         0         0         0         0         0      GIC  HIK_WDT_INT
[  171.193678]  35:     13088      2892         0         0         0         0         0         0      GIC  timer4
[  171.204650]  36:         0         0         0         0     16145      2896         0         0      GIC  timer6
[  171.215671]  37:         0         0         0         0         0         0         0         0      GIC  RTC Alarm
[  171.226950]  38:         0         0         0         0         0         0         0         0      GIC  uart-pl011
[  171.238317]  43:        34         0         0         0         0         0         0         0      GIC  Hisilicon Dmac
[  171.250032]  49:         0         0         0         0         0         0         0         0      GIC  hik_ir
[  171.261011]  50:         0         0         0         0         0         0         0         0      GIC  hi_cipher_irq
[  171.272643]  52:         1         0         0         0         0         0         0         0      GIC  ohci_hcd:usb2
[  171.284265]  53:         0         0         0         0         0         0         0         0      GIC  ehci_hcd:usb1
[  171.295893]  55:         0         0         0         0         0         0        12         2      GIC  stmmaceth
[  171.307173]  56:         9         0         0         0         0         0       103        22      GIC  stmmaceth
[  171.318461]  57:         0         0         0         0         0         0         0         0      GIC  stmmaceth
[  171.329744]  58:         0         0         0         0         0         0         0         0      GIC  stmmaceth
[  171.341023]  59:       292         0         0         0         0         0         0         0      GIC  ahci
[  171.351874]  60:        16         0         0         0         0         0         0         0      GIC  xhci-hcd:usb3
[  171.363454]  78:         0         0         0         0         0         0         0         0      GIC  IVE
[  171.374219]  79:      6905      2892         0         0         0         0         0         0      GIC  AIO Interrupt
[  171.385853]  80:         8         0         0         0         0         0         0         0      GIC  hi_tde_irq
[  171.397230]  94:         0         0         0         0         0         0         0         0      GIC  hi_iommu
[  171.408429] 105:         6         0         0         0         0         0         0         0      GIC  timer
[  171.419369] 107:         0         0     13525      2917         0         0         0         0      GIC  timer5
[  171.430389] 108:         0         0         0         0         0         0     15120      2918      GIC  timer7
[  171.441359] 112:     11162      3471         0         0         0         0         0         0      GIC  VOU Interrupt
[  171.452989] 125:         1         0         0         0         0         0         0         0      GIC  mali.0
[  171.464008] 126:         1         0         0         0         0         0         0         0      GIC  mali.0
[  171.475028] 127:         1         0         0         0         0         0         0         0      GIC  mali.0
[  171.486008] total: 76430
[  171.488592] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. I'm so Sorry (>_<)...
[  171.496001] [HKBSP][hik_wdt hik_wdt.1]hik-wdt:hikwdt_isr. last_feedwdt:4294951520(jiffies64:4294954412,timeout:25)


DDR Training Suc


U-Boot 2010.06-svn (Jun 26 2015 - 15:08:07)

Protected at offset:0,size:40000 Protection status:[0x22f]=>[0x22f].
Hit ctrl+u to stop autoboot:  0

alastairstevenson · Apr 18, 2024

yorkie said:
the update went through fine but it is still going through the reboot loop.

Yes, the same error triggering the reboot.
My guess is it's a hardware fault, unfortunately.

yorkie · Apr 19, 2024

alastairstevenson said:
Yes, the same error triggering the reboot.
My guess is it's a hardware fault, unfortunately.

well thanks for helping up to this point anyway.
If it had been doing this loop right from the outset then it would have been easier to write it off, but because it had originally started up and got to the grid screen (complete with a password reset) it's annoying for it to now be pretty much dead

... if there's nothing else that can be done for it then I might see if I can sell the PSU off for £20 and get my money back (lol)

Search

DS-7708NI-I4/8P Reboot Loop (Hikvision)

yorkie

n3wb

alastairstevenson

yorkie

n3wb

yorkie

n3wb

alastairstevenson

yorkie

n3wb

alastairstevenson

yorkie

n3wb

alastairstevenson

yorkie

n3wb

yorkie

n3wb

yorkie

n3wb

alastairstevenson

yorkie

n3wb

alastairstevenson

yorkie

n3wb

alastairstevenson

Tftpd32: an opensource free firewall friendly dhcp, syslog sntp and tftp server/service for windows, tftp client

yorkie

n3wb

alastairstevenson

yorkie

n3wb