dx2

Unfortunately no solution yet.

Bad news, right? Any chance to replace the chip? Any idea which one is it? I loved very much this DVR because of its 16 inputs of audio and 16in/4out alarm contacts.

In order to avoid a very long post, I attached the log as text document. It begins with boot, stopping boot to update firmware, changing IP address of TFTP server in order to be found by DVR, loading firmware, resume booting, restart. After restart is new full, non-interrupted booting loop. Lines starting with several equal "=====" characters are my intervention points with explanations or only explanations of the booting process. Thank you for your support, Daniel boot_update_log.zip

It doesn't work with 192.0.0.128. It requires 192.168.1.15. I set up the TFTP initially with 192.0.0.128 but as you see it didn't load anything, waiting with "T". After I send the command "update" it responded with "TFTP from server 192.168.1.15; our IP address is 192.168.1.64", so I figured out TFTP needs to be 192.168.1.15. I changed TFTP server to 192.168.1.15 and it started to load at second attempt, with "#". DRAM: 256 MB numonyx flash devid:0x227e id3:0x2221 id4:0x2200 ARM Clock : 364MHz DDR Clock : 310MHz Hit ctrl+u to stop autoboot: 0 HKVS # update TFTP from server 192.168.1.15; our IP address is 192.168.1.64 Filename 'digicap.dav'. Load address: 0x81200000 Loading: T T T T T T T T Abort HKVS # update TFTP from server 192.168.1.15; our IP address is 192.168.1.64 Filename 'digicap.dav'. Load address: 0x81200000 Loading: ##################################### How should I reboot it? By poweroff (hardware) or by some command? I sent the command bootd. As in my previous tryout, the update did nothing. It still restarts. Yes, it did the update: ...... #### done Bytes transferred = 10000988 (989a5c hex) jffs2: add update file(uImage)...(1569292B->1580004B)done. jffs2: add update file(rootfs.img)...(714721B->722692B)done. jffs2: add update file(720.422)...(829440B->75324B)done. jffs2: add update file(ds8062_fpga.rbf)...(269846B->231764B)done. jffs2: add update file(initrun.sh)...(459B->396B)done. jffs2: add update file(preAllocMem)...(4704B->2388B)done. jffs2: add update file(waitAllocMem)...(3232B->1556B)done. jffs2: add update file(guirc.tar.gz)...(5072087B->5145416B)done. jffs2: add update file(webs.tar.gz)...(1536747B->1563068B)done. Un-Protect Flash space Un-Protected 122 sectors erase Flash space Erase Operation Completed. Erased 122 sectors Writing jffs2 to Flash.../done Re-Protect Flash space Protected 122 sectors HKVS # HKVS # bootd ### JFFS2 loading 'uImage' to 0x80700000 jffs2: scanning filesystem . done. ### JFFS2 load complete: 1569292 bytes loaded to 0x80700000 ## Booting image at 80700000 ... Image Name: Linux-2.6.10_mvl401-davinci_evm Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1569228 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... It goes exactly like before. Rebooting after the lines count = 0 visig=0 vi is ok (gxy)-- ----->ky6467 bufparam bufaddr=0x85743c00,yuvH=576,yuvW=704 (lkt)------>ky6467 bufparam audio addr[0]=0x8586cc80,addr[1]=0x8586d1a4,addr[2]=0x8586d6c8 The read of ISCSI_VERSION_FILE is 2.0-869 # I updated it again, with no luck either this time. The file digicap.dav used is from http://www.hikvisioneurope.com/portal/index.php?dir=Product%20Firmware/Recorder/Z%20Phased-out/DS-73xx%2081xx-S/V3.2/digicap(8100,7300,7200_v3.2_eu_Build110726).zip In the readme.txt shows: Firmware version: V3.2_Build110726 Based on:V3.1.0 build101227 Language:Multi-language ____________________________________________________________________________ Compatible Models: 7208HVI-S£¬7216HVI-S 7300HI-S£¬7300HFI-S, 8100HCI-S,8100HDI-S,8100HFI-S It's the wrong firmware file? It's the wrong command after loading firmware? It needs updating the bootloader also? What do you think?

I don't have any hdd mounted at this time in the DVR. Is this a problem? Thank you.

The available commands are: HKVS # help ? - alias for 'help' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory cmp - memory compare cp - memory copy crc32 - checksum calculation format - format nand except bootloader area fsinfo - print information about filesystems fsload - load binary file from a filesystem image go - start application at address 'addr' help - print online help ls - list files in a directory (default /) md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nand - NAND sub-system nboot - boot from NAND device ping - send ICMP ECHO_REQUEST to network host pready - set panel to ready printenv- print environment variables reset - Perform RESET of the CPU saveenv - save environment variables to persistent storage setenv - set environment variables tftpboot- boot image via network using TFTP protocol update - update digicap.dav updateb - update uboot(u-boot.bin) to nor updatebl- update ubl(ubl_646x.bin) to nand updatefs- update filesystem(davinci.img) to nand updatek - update kernel(uImage) to nand updates - serial update kernel or filesys HKVS #

Thank you. It seems that I cannot stop the boot process using ctrl+u as suggested. I'm using an ATEN US-232A adapter on a Win7 laptop, using 115200, 8N1, without flow control. As terminal, I'm using Putty in serial mode. I'm doing something wrong? Daniel Later Edit: Flow control should be hardware RTS/CTS. I ended up with different options. I tried tftpboot which showed me it is trying to load from server 192.168.1.15, dvr having address 192.168.1.64. I changed the TFTP server address to 192.168.1.15 and tried again. This time it downloaded the digicap.dav. After that I used command update. After it returned prompter again, I used bootd command. DVR restarted and the "restart" problem did not dissapear (it's the same problem). I saw at one time it tried to load from TFTP server "uImage". Any other thoughts/advices? Thank you.

Thank you for confirming my guessing. I'll try to find the proper commands to do it.

Hello there, I started to search for this problem in December 2014 when I manualy rebooted my DVR. Since then it does not start anymore, looping with"loading, please wait..." and then rebooting again. My model is DS-8116HDI-S, european version. Original firmware (since I didn't update it) is ."V3.1.0_100605" as written on the unit label. I tried the solution with TFTP server, but it didn't work (it does not try to load the firmware from the PC). I used a Windows 7 machine and a Windows XP one, none of them working. Windows firewall disabled, Bitdefender firewall disabled. I then tried to connect it via serial port and got the following: " U-Boot 1.2.0 (Nov 19 2009 - 16:28:58) DRAM: 256 MB numonyx flash devid:0x227e id3:0x2221 id4:0x2200 ARM Clock : 364MHz DDR Clock : 310MHz Hit ctrl+u to stop autoboot: 0 ### JFFS2 loading 'uImage' to 0x80700000 jffs2: scanning filesystem . done. ### JFFS2 load complete: 1569292 bytes loaded to 0x80700000 ## Booting image at 80700000 ... Image Name: Linux-2.6.10_mvl401-davinci_evm Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1569228 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. BusyBox v1.2.1 (2009.08.25-02:50+0000) Built-in shell (ash) Enter 'help' for a list of davinci system commands. a lot of lines here... chan 14 sub net buffer virtAddr = 0x49894000 phyAddr = 0x81b60000 chan 15 rec buffer virtAddr = 0x498b4000 phyAddr = 0x8d680000 chan 15 net buffer virtAddr = 0x49a34000 phyAddr = 0x81d00000 chan 15 sub net buffer virtAddr = 0x49ab4000 phyAddr = 0x81d80000 mapbuf0: len=1572864,offset=84000000 mapbuf1: len=1572864,offset=84180000 mapbuf2: len=1572864,offset=84300000 count = 0 visig=0 vi is ok (gxy)-- ----->ky6467 bufparam bufaddr=0x85743c00,yuvH=576,yuvW=704 (lkt)------>ky6467 bufparam audio addr[0]=0x8586cc80,addr[1]=0x8586d1a4,addr[2]=0x8586d6c8 The read of ISCSI_VERSION_FILE is 2.0-869 # " This is the last line of log. It then begins from the top. What can I do to fix it? Thank you, Daniel