Search results

Does the NVR have network connection? Use serial and try to ping internal and external networks.

You should tell what was causing the issue and how you solved it, for other people.

Seems like setenv works, but saveenv does not. What does the serial output say when trying to saveenv? Is the command maybe not implemented? Try with "help" to list available commands and make sure saveenv is existant.

You set the boot args and it did not help? Because your printenv shows, it is not set.

You should can put all files to root directory (no subdirectories). If a usb-stick is attached to front-usb input, it will check if the specific update file is existant, if not, it will continue boot like normal. What does the serial output say? Also looking at your bootenv, bootarg and bootcmd...

l You put the files into the root director of fat32 formatted USB, put the stick into the front USB Slot and start the NVR. Watch serial output, if the updater can find the updatefile it is looking for and if it does not find the file, it will output, which file it was looking for.

Why not try to update via usb? Have you checked your boot enviroment and set serverip?

File should be the one attached

Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 No NAND device found!!! 0 MiB I haven't seen this in any one else's log. Maybe Nand faulty? Dunno... But uboot seems to work, maybe an SPI Flasher can help you aswell. Which command did you use for TFTP flash? It should go like this sf probe 0...

Why are flashing via tftp? Are there any problems with flashing via usb?

It is J1

I know, but it may now, coming from a new firmware. There is no risk anymore right? ;) I would just try once more, just out of curiosity.

with usb, like initially.

I think, usually the uboot will not be overwritten when flashing. But now since it is working you could try out to update via recovery ;)

Does it really have to be exactly for this NVR? I found this thread for the same chip "MX25L128XX" and same CPU (Hi3520D), someone posted a uboot dump. MBD6704T-EL поделитесь uboot & env, пожалуйста. : Восстановление и настройка • Форум по системам видеонаблюдения, безопасности, пожарным и...

Just out of interest, may i ask you how you did it? Can you refer to a howto maybe.

Serial does not say anthing?

If this is the one that should be flashed via recovery jdvr-recover-sw-nd6004-h1-2.0-128M.bin, maybe you should try sw-nd6004-h1-2.0-128M.bin first, the one with 1kb can be skipped i guess. But does it even matter? With a programmer "trial and error"-method can be applied i think.

So, everything is running? According to page two it should be this one http://subaccount.nvsip.com/UpLoadFiles/20180130/2018013020022828.zip

Sorry to hear, but don't blame me man :D. I told you to extract firmware first and leave the uboot untouched.

I don't know which file or even if you can just write one these files to SPI Flash storage. Since one of these files has exact size of 16777216 and that is exactly 16MB like the SPI Flash storage, it could be the file to flash. Following the tutorial from here Booting Linux kernel using U-Boot...

Why don't you try with JUpdate 0x1000000 0x80008000 if it successfully downloaded into memorry?

tftp is correct, you are right. If it is stored in 0x80008000 Did you try: tftp 0x80008000 firmware.bin JUpdate 0x1000000 0x80008000 ?

I think the filename is irrelevant, therefore you give the address where it is stored. Did you try: tftpboot 0x80008000 firmware.bin JUpdate 0x1000000 0x80008000 ? Do you have the correct firmware file with 16777216 bytes?

If you have tftpserver set up then use JUpdate, i think it may work like this: usage:JUpdate (filesize) (temp ram addr) Put firmware via TFTP to temp ram addr at 0x81000000: tftpboot 0x81000000 firmware.bin Filesize is 16777216 so it can be either 16777216 if it is supposed to be in decimal...

Post printenv please

Is still stuck at 2 Pin to finish or do you get blackscreen? It could be video output error, those last line may refer to a resolution issue. You could try on another monitor. If you hit enter button, after it stuck at boot, will it give you access to command line? And also post your new...

Your bootcmd is missing, that is why it is not booting anymore. Here is mine: First try by adding bootcmd only, i think the commands go like this: If that ain't enough try modifying bootargs aswell: If it is still not enough, add these lines aswell:

can you post "printenv" output?

Did you try to detach the PC TX ----> NVR RX cable while booting? While leaving following cables attached: PC GND ----> NVR GND PC RX -----> NVR TX