is there a "generic" firmware available for Hi3535 based NVR? (owsoo branded)

[KyleRiemen]

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

 

[alastairstevenson]

Good news!
The system is running again. I did not believe it anymore ....

Excellent! That is a good result, well done.
In the 201603015-zhongxing-NVR4-V1.0.1.5927.zip file, the file "flash-sw-nd6004-h1-2.0-128M.bin" is not encoded and looks like it's intended to be used with a flash programmer. Is that the file that you used?

 

[Karsten]

Yes, I have taken exactly these file.
But how am I supposed to do the update?

 

[KyleRiemen]

with usb, like initially.

 

[Karsten]

With usb in the nvr updatesection didn't work! This was the heginning of my problems, See my first post.

 

[KyleRiemen]

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.

 

[miguelopez]

I need a rx-tx pin out. I have a bricked device after update. Is on j1 conector or j4 conector.? thanks

 

[KyleRiemen]

It is J1

 

[miguelopez]

When i try to upgrade a bin file this is the error.

TFTP from server 192.168.1.2; our IP address is 192.168.1.10
Download Filename 'uImage'.
Download to address: 0x80008000
Downloading: #########################

U-Boot 2010.06 (May 26 2014 - 14:41:35)

NAND: Check nand flash controller v504. found
hinfc504.c(1141): !!! BUG Driver does not support. Can't malloc memory for NAND driver

 

[miguelopez]

this is my boot log.

U-Boot 2010.06 (May 26 2014 - 14:41:35)

NAND: Check nand flash controller v504. found
Special NAND id table Version 1.36
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
0 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
Spi(cs1): Block:64KB Chip:16MB Name:"MX25L128XX"
In: serial
Out: serial
Err: serial
(Re)start USB search...
USB: scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
saveaddr: 82000000
PHY not link!
sf probe 0;sf read 0x86000000 0x60000 0x20000
16384 KiB hi_sfc at 0:0 is now current device

vo 0,picwh:800 0, addr=0, xywh:0 300 800 0
vo 2,picwh:800 0, addr=a0, xywh:0 288 720 0
setenv jpeg_addr 0x86000004
setenv jpeg_size 0x7a6f5b66
setenv vobuf 0x0
jpeg decoding ...
Invalid VOU buffer address 0x00000000
load jpeg err.
dev 0 opened!
16384 KiB hi_sfc at 0:0 is now current device


Wrong Image Format for bootm command
ERROR: can't get kernel image!

 

[KyleRiemen]

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

 

[miguelopez]

Yes tftp usb not reconiced any usb memory.

 

[miguelopez]

This is a usb update


NAND: Check nand flash controller v504. found
Special NAND id table Version 1.36
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
0 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
Spi(cs1): Block:64KB Chip:16MB Name:"MX25L128XX"
In: serial
Out: serial
Err: serial
(Re)start USB search...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... usb_stor_get_info->1406,blksz:512
1 Storage Device(s) found
Hit any key to stop autoboot: 0
saveaddr: 82000000
MAC: 00-00-23-34-45-66
JVUpd Start
OurPort: 3191
starting...
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 67, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 1947, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191

time out resend: 0
after resend data
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 67, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 67, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 17500, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 138, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191
packet not correct: des: 137, our: 3191

JVUpdTimeout When CMD_TRY
sf probe 0;sf read 0x86000000 0x60000 0x20000
16384 KiB hi_sfc at 0:0 is now current device

vo 0,picwh:800 0, addr=0, xywh:0 300 800 0
vo 2,picwh:800 0, addr=a0, xywh:0 288 720 0
setenv jpeg_addr 0x86000004
setenv jpeg_size 0x7a6f5b66
setenv vobuf 0x0
jpeg decoding ...
Invalid VOU buffer address 0x00000000
load jpeg err.
dev 0 opened!
16384 KiB hi_sfc at 0:0 is now current device

 

[KyleRiemen]

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
tftp 0x81000000 firmware.bin
sf erase 0x0 0x1000000
sf write 0x81000000 0x0 0x1000000

! use the correct firmware, mentioned by Karsten in #120

And also provide your uboot enviroment.

 

[miguelopez]

mi enviroment


hisilicon # printenv
bootdelay=1
baudrate=115200
ethaddr=00:00:23:34:45:66
ipaddr=192.168.1.10
serverip=192.168.1.2
netmask=255.255.254.0
bootfile="uImage"
bootcmd=showlogo;startvo 0 36 13;mw 0x200300b8 0x0ff0f0ff;sf probe 0;sf read 0x81000000 0x100000 0x380000;sf read 0x82000000 0x480000 0x280000;bootm 0x81000000 0x82000000
bootargs=mem=96M console=ttyAMA0,115200 root=0100 rootfstype=ext2 logo_addr=9FF00000 mtdparts=hi_sfc:1M(boot),3584K(kernel),2560K(rootfs),7M(APP),2M(config) pcimod=host logo_w=800
jpgLogoAddr=0x60000
jpgLogoLen=0x20000
jpgLogoW=800
jpgLogoHtenv=logo_addr 00000
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06 (May 26 2014 - 14:41:35)
jpeg_addr=0x86000004
jpeg_size=0x7a6f5b66
vobuf=0x0

 

[miguelopez]

I do you ftpf comand and device is dead dead. Not serial command and only buzzer .(

 

[Karsten]

I would like to share my experience.

I think the software transfer is the easiest with the CH341A programmer and SOP8 DIP8 test clip.
I spent a lot of time with the other methods.
You can read everything in the posts, it's really not hard.

The hardware you get cheap at the China-shops.

 

[miguelopez]

ok, i buy one in two week i recibe.

 

[miguelopez]

I recibe today ch341a programer. Whay program i need and last firmware for 16ch model.?

 

[KyleRiemen]

I recibe today ch341a programer. Whay program i need and last firmware for 16ch model.?

File should be the one attached