[Solved] XVR H.264 Firmware v4.02.r11.e82b0119: Seeking IP Recorder 8 Channels (NBD6808T-PL) Update

Hello!

I am looking for a firmware to IP recorder 8 Channels model unknown

Originally it was soft: firmware v4.02.r11.e82b0119.12001.130000.00000
The hardware version is: NBD6808T-PL

Attachments of the motherboard and the box in the attachments.

  DSC_10..JPG (1.48 MB)You must be logged in to download this attachment. DSC_10..JPG (955.47 kB)You must be logged in to download this attachment. DSC_10..JPG (966.35 kB)You must be logged in to download this attachment.

Do you need hardware software because the device does not start up? Because there is a password and you can not enter or just want to upgrade the software?
Anyway, so far, just what I found in the Annex.
As you can and you have the option to rip the current load in the event of WU

Only now from what the internet provides:

Quote:

There are several hardware versions of this recorder.
To determine the hardware version must be in „ Settings / Information / version ”
to find the line version „ System: V4.02.R11.YYYYYXXX.12001.130000.00000 »
In the block after V4.02.R11. there are 8 digits.
You must specify the last three digits of "XXX" in this block.
These three numbers indicate the hardware version of the device.
V4.02.R11.00000099 - 099 device version
V4.02.R11.00000083 - 083 device version
V4.02.R11.00000119 - 119 version of the device
V4.02.R11.00000121 - 121 hardware version

It would come out that you have a device version 119 only that under this version I find but the model NBD7808T-PL.
And your NBD6808T-PL seems to be under 099 .

Additionally, after marking the disc, you can deduce that HI3515 is sitting there, but with the firmware it could be concluded that there is HI3520.
You can not see it through the heat sink, but if you hooked up to UART, you can read more about it in the Terminal.

The radiator, like what is glued on the silicone, can be slightly heated and cut with a razor or with molybdenum wire. God forbid, do not tear for him, and worse, do not twist, turn everything with sensitivity. It is known after detaching anyway you have to attach it there to some thermo conductive double-sided tape.

This topic can be related to this thread on the eastern language forum

Send a photo of the recorder from the front of the housing. There is no information sticker under it.

Hello!

Thanks for the response. This is so: the recorder after "fw update" does not start; hangs on the start page with the "H.264 XVR" logo. The soft V4.02.R11.00000119 was used, i.e. the bad one.
The recorder responds to pings, and you can not log into it via telnet, via cms. Nmap shows that all ports are closed.

If you told me how to connect to UART, I would be grateful.

scss wrote:

Thanks for the response. This is so: the recorder after "fw update" does not start; hangs on the start page with the "H.264 XVR" logo. Was included soft V4.02.R11.00000119, or this bad.

So now you can check this 099.

scss wrote:

The registrar reacts to pings, and you can not log into it via telnet, via cms. Nmap shows that all ports are closed.

Check if this program detects the device.
SearchTool

Hello

gradek83 wrote:

So now you can check this 099.

Seems like that, but for now I have to revive my life somehow.

gradek83 wrote:

Check if this program detects the device.SearchTool

Unfortunately, it does not detect ...

Tak korzystając z okazji dodam tabelkę jak by ktoś w przyszłości szukał pod inny model rejestratora danej wersji oprogramowania sprzętowego.


Added after 9 [minutes]:

 

scss wrote:

If you told me how to connect to UART, I would be grateful.

Check on the device on which voltage you have between pin 1 and 2, this 1 is probably GND mass.

It's a white small socket with 4 pins, what do you got there with sometimes USB from the front panel?


I've searched and leaves that HI3520 is there

Hello.

Thank you very much for information.
Yes, this white connector is a usb on the front panel.
Between the points you showed is 3.3V - so I guess it's going to be an uart. Now, the question - which adapter do you recommend, ie which company and which?

Quote:

I've searched and leaves that there is, however, HI3520

You are great, I was sitting for 4 hours and I found nothing, no software, no info about this rej.

scss wrote:

Between the points you showed is 3.3V - so I guess it's going to be a uart. Now, the question - which adapter do you recommend, ie which company and which?

Yes I wanted to make sure it is sometimes not an additional USB port but as it is 3.3 it's probably UART
or GND | TXD | RXD.

I use the USB-RS232 / TTL ELS EM-USB-01 converter on the FT232RL chip.


For such games and not only I can recommend a small programmer EZP2010 plus for this Adapter 1.8V and SO8 clip (Buying all-way attention, where is the shipping is cheap, it's probably CHINA and you have almost a month to wait it is worth remembering)

Witam!

Przepraszam za brak odzewu, lecz czekałem na konwerterek. Dziś się podłączyłem pod uart, oto efekt:

U-Boot 2010.06-svn1041 (May 02 2018 - 20:21:35)

Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x17 0xC2 0x20 0x17
Spi(cs1): Block:64KB Chip:8MB Name:"MX25L6406E"
CONFIG_CLOSE_SPI_8PIN_4IO = n.
at hifmc100_setTB() mid:0xc2,chipsize:0x800000
at xm_get_macronix_type() cr:0x0.
all blocks is unlocked.
envcrc 0xb4d82d77
ENV_SIZE = 0xfffc
In: serial
Out: serial
Err: serial
USB: scanning bus for devices... 1 USB Device(s) found
0 Storage Device(s) found
i:0, No usb storage device found!
Press CTRL-C to abort autoboot in 0 seconds8192 KiB hi_sfc at 0:0 is now current device
CFG_BOOT_ADDR:0x0
0ff:0x84000000
### /UbootLogo UbootLogoload complete: 51931 bytes loaded to 0x8e800000
jpeg decoding ...


decode success!!!!
decode jpeg success.
decode jpeg!
at do_jpgd() .
srcAddr 0x82000000, dstAddr 0x82000000
find_squashfs_file: name bin, start_block 0, offset 1284, type 1
find_squashfs_file: name boot, start_block 0, offset 1376, type 1
read inode: name boot, sb 0, of 1376, type 1
find_squashfs_file: name zImage.img, start_block 0, offset 1316, type 2
read inode: name zImage.img, sb 0, of 1316, type 2
### FS load complete: 1613452 bytes loaded to 0x82000000
## Booting kernel from Legacy Image at 82000000 ...
Image Name: linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1613388 Bytes = 1.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I na tym się zatrzymuje.
Teraz jaki fw mu wgrć aby go ruszyć? Macie jakieś pomysły co dalej z tym zrobić?

Find the pendrive so the best 2GB and format it in fat32 and copy the files unpacked from the attachment loosely on it and put in the recorder and run do not know if the update will start if not then we will be combining further.

Hello!

I did as you wrote, unfortunately without any effects. USB sees but the update does not go. It comes to the moment of loading linux and hangs. I tried to force an update from the usbboot command, but I get a message about the lack of USB:
.....
.....

"USB: scanning bus for devices ... 2 USB Device (s) found
usb_stor_get_info-> 1406 blksz: 512
1 Storage Device (s) found
device name usb!
Interface: USB
  Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 400
            Type: Removable Hard Disk
            Capacity: 1912.0 MB = 1.8 GB (3915776 x 512)
Partition 1: Filesystem: FAT32 "NO NAME"
reading auconfig.txt
auconfig.txt not found
AuConfig_parse failed, name: usb
Press CTRL-C is abort autoboot in 0 secondshisilicon #

hisilicon # usbboot

** No boot device **
hisilicon # usbboot "

Greetings.

I wrote to technical support for help maybe Chinese will write back. For me in my other recorder but the same chipset is the AutoUpdate file which I copy to the data carrier I plug it into the recorder and run the update automatically installs.

Hello!

Thank you for your response. But did you specifically format the usb? Is it just the format on fat 32 and you have copied the files after being zipped?

The fat32 format is not ordinary without any special additions, it copies the file directly in bulk, and everything starts to be done when starting from the machine. This is how I wonder if sometimes such a Chinese file does not have to deal with this type of problems after uploading the wrong firmware.
I unpacked SimpGeneral_General_NBD6808T-PL_V4.02.R11.20140723_NT.bin

So try to unpack these files for copy and check how it will not move something Chinese people can advise.

And how do you run the recorder, press CTRL-C and enter the hisilicon #
enter there: printenv
And send the result.
__________________
OK, it should work, please download the file AUTO UPDATE.rar from the attachment, unpack the contents and copy to the data carrier and plug in to the disabled recorder under USB. Turn on the recorder and check if the update will start on the screen. The recorder should automatically restart, remember to remove the media so as not to loop the update.

If it does not move, I have one more way.

Hello!

Thank you very much for your help.
I apologize for the delayed reply, but business matters have not allowed me to take care of nvr before.

There is half progress. Namely, after unpacking files from AUTO UPDATE.zip to usb, nvr started from this usb, read usb, started the update, but at some point I get a message saying: "No need to upgrade the same version". Amazingly, there is no difference if I upload the image NBD6808T-PL_V4.02.R11.20140723_NT.bin (ie 00000019 ...) or NBD7808T-PL_V4.02.R11.Nat.OnvifC.20171121_UL.bin (ie 00000199) ) I always have the message "No need upgrade ...". After this message, colored test strips appear on the monitor and remain so.


Below I paste a screenshot of UART can be useful to someone:


1. The result of the printenv command

hisilicon # printenv
bootcmd = sf probe 0; sf read 84000000 770000 10000; logoload 84000000; decjpg; sf read 82000000 30000 400000; squashfsload 82000000; bootm 0x82000000
BootDelay = 1
baudrate = 115200
BootFile = "uImage"
restore = 1
da = mw.b 0x82000000 ff 1000000; tftp 0x82000000 u-boot.bin.img; sf probe 0; flwrite
du = mw.b 0x82000000 ff 1000000; tftp 0x82000000 user-x.cramfs.img; sf probe 0; flwrite
dr = mw.b 0x82000000 ff 1000000; tftp 0x82000000 romfs-x.cramfs.img; sf probe 0; flwrite
dw = mw.b 0x82000000 ff 1000000; tftp 0x82000000 web-x.cramfs.img; sf probe 0; flwrite
dl = mw.b 0x82000000 ff 1000000; tftp 0x82000000 logo-x.cramfs.img; sf probe 0; flwrite
dc = mw.b 0x82000000 ff 1000000; tftp 0x82000000 custom-x.cramfs.img; sf probe 0; flwrite
up = mw.b 0x82000000 ff 1000000; tftp 0x82000000 update.img; sf probe 0; flwrite
tk = mw.b 0x82000000 ff 1000000; tftp 0x82000000 zImage.img; bootm 0x82000000
dd = mw.b 0x82000000 ff 1000000; tftp 0x82000000 mtd-x.jffs2.img; sf probe 0; flwrite
ipaddr = 192.168.1.10
serverip = 192.168.1.1
netmask 255.255.255.0 =
gatewayip = 192.168.0.1
ethaddr = 00: 0b: 3f: 00: 00: 01
bootargs = mem = 132M console = ttyAMA0,115200 root = 1f01 rootfstype = squashfs mtdparts = hi_sfc: 192K (boot), 1984K (romfs), 3776K (usr), 1664K (custom), 64K (logo), 512K (mtd)
appSystemLanguage = Angielski
appVideoStandard = PAL
serial = stdin
serial = stdout
stderr = serial
verify n =
ver = U-Boot 2010.06-svn1041 (May 02 2018 - 20:21:35)

Environment size: 1344/65532 bytes

-------------------------------------------------- ---------------------


2. During upgradue:
U-Boot 2010.06-svn1041 (May 02 2018 - 20:21:35)

Check spi flash controller v350 ... Found
Spi (cs1) ID: 0xC2 0x20 0x17 0xC2 0x20 0x17
Spi (cs1): Block: 64KB Chip: 8MB Name: "MX25L6406E"
CONFIG_CLOSE_SPI_8PIN_4IO = n.
at hifmc100_setTB () mid: 0xc2, chipsize: 0x800000 & lt; NO & gt;
at xm_get_macronix_type () cr: 0x0.
all blocks is unlocked.
envcrc 0xb4d82d77
ENV_SIZE = 0xfffc
In: serial
Out: serial
Err: serial
USB: scanning bus for devices ... 3 USB Device (s) found
usb_stor_get_info- & gt; 1406 blksz: 512
1 Storage Device (s) found
device name usb!
Interface: USB
  Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 400
            Type: Removable Hard Disk
            Capacity: 1912.0 MB = 1.8 GB (3915776 x 512)
Partition 1: Filesystem: FAT32 "NO NAME"
reading auconfig.txt
auconfig.txt found
at AuConfig_print ():
i: 0, eCfgType: 2, name: update.img
at AuConfig_process ():
i: 0, eCfgType: 2, name: update.img
reading update.img
.................................................. ..............................
8192 KiB hi_sfc at 0: 0 is now current device
unlock all block.
hisfc350_set_bp_level () NOTES: old_level [0x0] = level [0x0]
all blocks is unlocked.
PACK_ID OK
at __do_flwrite() argc:1, image name:linux.
Programing start at: 0x005d0000
Programing end at: 0x00770000

## Checking Image at 0x82000040 ...
Header CRC Checking ... OK
Image Name: linux
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 1703936 Bytes = 1.6 MiB
Load Address: 005d0000
Entry Point: 00770000
Programing len: 0x001a0000
Data CRC Checking ... OK
No need to upgrade the same version.
PACK_ID OK
at __do_flwrite() argc:1, image name:linux.
Programing start at: 0x00770000
Programing end at: 0x00780000

## Checking Image at 0x821a0080 ...
Header CRC Checking ... OK
Image Name: linux
Image Type: ARM Linux Standalone Program (gzip compressed)
Data Size: 16384 Bytes = 16 KiB
Load Address: 00770000
Entry Point: 00780000
Programing len: 0x00004000
Data CRC Checking ... OK
No need to upgrade the same version.
PACK_ID OK
at __do_flwrite() argc:1, image name:linux.
Programing start at: 0x00030000
Programing end at: 0x00220000

## Checking Image at 0x821a40c0 ...
Header CRC Checking ... OK
Image Name: linux
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 2015232 Bytes = 1.9 MiB
Load Address: 00030000
Entry Point: 00220000
Programing len: 0x001ec000
Data CRC Checking ... OK
No need to upgrade the same version.
PACK_ID OK
at __do_flwrite() argc:1, image name:linux.
Programing start at: 0x00220000
Programing end at: 0x005d0000

## Checking Image at 0x82390100 ...
Header CRC Checking ... OK
Image Name: linux
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 3559424 Bytes = 3.4 MiB
Load Address: 00220000
Entry Point: 005d0000
Programing len: 0x00365000
Data CRC Checking ... OK
No need to upgrade the same version.
Press CTRL-C to abort autoboot in 0 seconds8192 KiB hi_sfc at 0:0 is now current

device
CFG_BOOT_ADDR:0x0
0ff:0x84000000
can't find jpg corresponding entry
0ff:0x84000000
can't find jpg corresponding entry
### /UbootLogo LOAD ERROR !
jpeg decoding ...

addr:0x808549d4,size:755193,logoaddr:0x8e800000,:ff,ff
load jpeg err.
srcAddr 0x82000000, dstAddr 0x82000000
find_squashfs_file: name bin, start_block 0, offset 1284, type 1
find_squashfs_file: name boot, start_block 0, offset 1376, type 1
read inode: name boot, sb 0, of 1376, type 1
find_squashfs_file: name zImage.img, start_block 0, offset 1316, type 2
read inode: name zImage.img, sb 0, of 1316, type 2
### FS load complete: 1613452 bytes loaded to 0x82000000
## Booting kernel from Legacy Image at 82000000 ...
Image Name: linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1613388 Bytes = 1.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Pozdrawiam.

Check if it will also say "No need to upgrade the same version" or something else.

Hello!

There is success! After booting from USB with uploaded files from auto update2.rar nvr has updated. During startup the following message appears:

 "Mac confict. This is the default MAC will stop cloud service, MAC: 00: 0b: 3f: 00: 00: 01".

 And here is the problem, does not see the image from the cameras, the network can be set up, I can also get to it through the LAN.
The software version that is in NVR is: V4.02.R11.00000119.

And via the web if you are logged in you have access to the update window?
How can you see it or you can upload V4.02.R11.00000099
If I do not move, I will send you other versions, maybe I will catch one.

TXT files with info are in Russian if windows will see bushes use notepad ++ For me, Cyrillic shows.

scss wrote:

Originally it was soft: firmware v4.02.r11.e82b0119.12001.130000.00000

So if originally it was probably after uploading V4.02.R11.00000099 again will be what it was so after despite the hardware NBD6808T-EN comes out that the firmware is coming 119

But you have to check it out.


00031099 NBD6808T-PL (Old)

00031119 NBD7808T-PL (New)

Hello!

NVR saved. Everything works as it should, ie recording, playing, setting, etc. The soft on which it worked was: V4.02.R11.C7422119. On the others I had an error with the MAC address or a message about incompatibility of the equipment with the soft.
The only thing missing is: there is no notification of alarm states via a smartphone and there is no online update. The rest ok. I just do not have these options on the menu, which is a shame, because it would be useful.

Thanks a colleague gradek83. The topic can be closed.

scss wrote:

V4.02.R11.C7422119

Write exactly which * .bin file you have uploaded and theoretically you can close it if you do not want, for example, a root password by connecting to a telnet.

Hello!

The * .bin file on which this went:
ShiAn_ShiAnZW_NBD7808T-PL_V4.02.R11.OnvifC.20160805.bin

Hello!

After uploading this fw: ShiAn_ShiAnZW_NBD7808T-PL_V4.02.R11.OnvifC.20160805.bin
the recorder works as it should.