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

[KyleRiemen]

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.

 

[CA50]

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.

The earlier problem was because i have flashed the wrong firmware from NVR8.
After flashing with the correct one , the boot process works but it gets stuck here.

RAMDISK: gzip image found at block 0
update_logo 12
uncompression error
update_logo 13
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 144K
EXT2-fs (ram0): error: ext2_lookup: deleted inode referenced: 3371
EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #1673: : rec_len                                                                                                                                                              is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.                                                                                                                                                              See Linux Documentation/init.txt for guidance.
Backtrace:
[<c0036d50>] (dump_backtrace+0x0/0x110) from [<c04c1390>] (dump_stack+0x18/0x1c)
 r6:c0047c84 r5:c05edc90 r4:c05edc90 r3:60000013
[<c04c1378>] (dump_stack+0x0/0x1c) from [<c04c1408>] (panic+0x74/0x188)
[<c04c1394>] (panic+0x0/0x188) from [<c002c594>] (init_post+0xa8/0xd8)
 r3:c4427f18 r2:c387d800 r1:c06b9fa0 r0:c05623a4
 r7:00000013
[<c002c4ec>] (init_post+0x0/0xd8) from [<c0008494>] (kernel_init+0x124/0x12c)
 r4:c0025d2c r3:00000028
[<c0008370>] (kernel_init+0x0/0x12c) from [<c0047c84>] (do_exit+0x0/0x6d4)
 r5:c0008370 r4:00000000

Any input?

 

[CA50]

Latest update. Issue fixed. I am able to boot into my NVR.
Thank you all for your inputs.

 

[KyleRiemen]

Latest update. Issue fixed. I am able to boot into my NVR.
Thank you all for your inputs.

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

 

[CA50]

Sure, my blinking issue was because of corrupt EEPROM,
I solved by following these stesp
1. flashing EEPROM with the attached file using CH341 programmer
2. After restart, NVR hangs at boot logo and restart
3. Updated firmware normally using USB (new firmware link 20171012-狮安-NVR6-S-1G16M-v1.0.1.7246 - 尚维国际)

But till it cannot detect my IP cameras

 

[alastairstevenson]

Hey, well done, you got there!

But till it cannot detect my IP cameras

Is this an 'auto-detect' or have you manually entered the camera IP address, port etc?
Are you trying to use ONVIF as the method of connection?
Different ONVIF implementations have different 'ONVIF ports'.
If ONVIF, loads of info on the cameras can be obtained using ONVIF Device Manager from sourceforge.net

 

[CA50]

Hey, well done, you got there!


Is this an 'auto-detect' or have you manually entered the camera IP address, port etc?
Are you trying to use ONVIF as the method of connection?
Different ONVIF implementations have different 'ONVIF ports'.
If ONVIF, loads of info on the cameras can be obtained using ONVIF Device Manager from sourceforge.net

Auto detect: Wifi cams are not detected
Manual: (Device mode) : Not connected error
(ONVIF) : Not connected error

In the camera configuration, the ONVIF port is set as 8080, i am using the same.
Also i checked with ONVIF Device Manager and entered the correct URL, but no success

Here is the serial output

timeout happened in discovery...
proc_NS_Device,addr=http://192.168.3.105:8080/onvif/devices,ip=192.168.3.105
############NSDev_NewOnvif dev.serviceAddress[http://192.168.3.105:8080/onvif/devices]
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:237 GetCapabilities ret: 28, soap error: 0, errnum: 0, SOAP-ENV:Sender, No route to host
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:238 m_dev.serviceAddress: http://192.168.3.105:8080/onvif/devices
[/home/zsl/svn/st_svn/onvif-client-fb/functions/ovf_discovery.c]:1152 fault: No route to host, subcode: (null)
default onvif pass:admin 12345,manufacture=,dev=0x401a69c8
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:237 GetCapabilities ret: 28, soap error: 0, errnum: 0, SOAP-ENV:Sender, No route to host
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:238 m_dev.serviceAddress: http://192.168.3.105:8080/onvif/devices
[/home/zsl/svn/st_svn/onvif-client-fb/functions/ovf_discovery.c]:1152 fault: No route to host, subcode: (null)
onvif search :result=1,timeout=3000,parm=0
Push onvif:ip=192.168.3.105,N1761847488,bDestroy=1,ret=0
ch0 startRec,euStatus Error:1:1
getServerTime: soap error: 28, errnum: 113, SOAP-ENV:Sender, No route to host
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:237 GetCapabilities ret: 28, soap error: 0, errnum: 0, SOAP-ENV:Sender, No route to host
[/home/zsl/svn/st_svn/onvif-client-fb/nvc/OvfNvcDevice.cpp]:238 m_dev.serviceAddress: http://192.168.3.105:8080/onvif/devices
[/home/zsl/svn/st_svn/onvif-client-fb/functions/ovf_discovery.c]:1152 fault: No route to host, subcode: (null)
_Onvif_Connect, ch0, dev=0x401a69c8, acId=admin,pw=admin,ret=-11

 

[alastairstevenson]

Also i checked with ONVIF Device Manager and entered the correct URL, but no success

Normally, ODM does auto-discovery, for devices on the same IP network segment as the PC.
If it doesn't find it, that suggests a problem, either no ONVIF support, or a networking accessibility issue.

The camera is on WiFi?
If so, would it be feasible to temporarily connect it to the switch/router with an ethernet cable?

Here is the serial output

This is on the NVR, when trying the auto-discovery?
This has to be a clue of some sort, but I'm not sure what : SOAP-ENV:Sender, No route to host
How are the NVR and camera and PC IP addresses?
http://192.168.3.105:8080/onvif/devices
Does the WiFi run on a different, routed, segment?

 

[CA50]

Normally, ODM does auto-discovery, for devices on the same IP network segment as the PC.
If it doesn't find it, that suggests a problem, either no ONVIF support, or a networking accessibility issue.

The camera is on WiFi?
If so, would it be feasible to temporarily connect it to the switch/router with an ethernet cable?

I can see and have enabled ONVIF in the camera settings. Also i have enabled ONVIF in the NVR.
Both the NVR and IP camera are connected via the same router. I have connect the IP camera via LAN, then NVR can detect and display the image.
In case of wifi, the NVR cannot find it.

This is on the NVR, when trying the auto-discovery?

No, this was after i added the IP camera manually in ONVIF mode

This has to be a clue of some sort, but I'm not sure what : SOAP-ENV:Sender, No route to host
How are the NVR and camera and PC IP addresses?
http://192.168.3.105:8080/onvif/devices
Does the WiFi run on a different, routed, segment?

Can you please explain this, i didn't get the question.
Both the NVR and IP camera are on the same network via the same router

 

[KyleRiemen]

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

 

[alastairstevenson]

I have connect the IP camera via LAN, then NVR can detect and display the image.

That's interesting, and confirms that the configuration settings are good, and that the camera is compatible.
Presumably ODM would find the camera automatically when on the LAN as opposed to WiFi.

In case of wifi, the NVR cannot find it.

So it's a matter of finding out what's different about the WiFi.
Usually, it would just show as a different IP address, in the same network as the IP address when it's on the LAN.

Can you please explain this, i didn't get the question.
Both the NVR and IP camera are on the same network via the same router

But I wondered if you can list the IP addresses of the camera both when on the LAN and when on WiFi, and the IP address of the NVR.
Are the camera IP addresses configured as static values, or are you letting DHCP provide the configuration?

 

[CA50]

The problem was with my router. Changing it has fixed the IP Camera detection issue

 

[geopapai]

Hi everyone, I have this nvr with a firmware v04.02.r11.g3731118
It is 4ch for 1080p
And the cpu is Hi3520

Any firmware update to have more ch at 1080p?

Provided that you have the right model (there are variations). Your firmware does not seem to match the one below but...

Look up for this : 201603015-zhongxing-NVR8-V1.0.1.5927.zip
This works 100% for the OWSOO 4ch Hi3520 we mention above, will be converted to 8ch. Mine works as a charm.

Double check your model, I am not responsible for any bricks...

 

[alastairstevenson]

Any firmware update to have more ch at 1080p?

There are also a few Hi3520-based firmwares here to explore - with care : V4.02.R11 H.264/H.265 DVR/NVR Firmware Download

 

[alastairstevenson]

Nbd7804r-f

That's a Xiongmaitech board.
Firmware and details here : www.xiongmaitech.com/en/index.php/product/product-detail/4/183/243Nbd7804r-f

 

[alastairstevenson]

Can’t see what firmware is that compare to the one I have

You are right - I didn't check the firmware download on the link I posted, it looks like it's been disabled, discontinued product.

But there is some firmware here : 00000124（NBD7804R-F）
Version:V4.02.R11.00000124.1 or V4.02.R11.00000124.0

Would you think I can flash 8ch 1080p on this board?

No harm in trying, if the device isn't critical to you.
The Hi3520D can handle 8 x 1080P IP streams.

I did something similar recently on a Xiongmaitech board in a QVIS DVR, with newer firmware converted it to support ONVIF as well as the original 'IPC' XM protocol so it could support 3rd-party cameras.

 

[geopapai]

Provided that you have the right model (there are variations). Your firmware does not seem to match the one below but...

Look up for this : 201603015-zhongxing-NVR8-V1.0.1.5927.zip
This works 100% for the OWSOO 4ch Hi3520 we mention above, will be converted to 8ch. Mine works as a charm.

Double check your model, I am not responsible for any bricks...

The firmware I mention above does not match your board. its for 70xx versions. For 7804 I have nothing but check also this, it has a lot of models 资源下载 - 尚维国际

 

[andrewam]

Hi everybody,
I've an OWSOO 4ch NVR that's in a bootloop after a firmware upgrade.
The motherboard says "N3515-v1.2 20140715" and the original firmware was V1.0.1.4960. The CPU is a Hi3520 DRQCV200.
I've flashed the "20161110-欣伟浩-NVR4-V1.0.1.6964" and also tried "201603015-╓╨╨╘-NVR4-V1.0.1.5927" found on the Net, but both make the NVR to start and stop loading on the last two/three "notches".
I haven't found other firmwares nor I am sure of the motherboard (the N3515 written on it doesn't give good results on Google). I've searched also for the original firmware, but without success.
Please help me found a solution.
Thanks.

 

[dreamstar]

Can anybody tell where to get firmware:

201603015-zhongxing-NVR8-V1.0.1.5927.zip


Link from the first page of this thread is dead and google cannot help to find this file on the web. Thanks.

 

[arekwawa]

does anyone have the current version for OWSOO 4ch NVR?