iDS-7208HUHI-M2/S problem after upgrade.

nikc0

n3wb
Joined
Oct 17, 2022
Messages
4
Reaction score
0
Location
Poland
Hi, today i upgrade software in recorder and after this he's bricked. I try to update it with putty but it do nothing. I try update this manual with command "tftpboot digicap.dav" but also had no effect.




This program will upgrade software.
***
  • ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY! *
  • Don't reset machine,or anything that interrupt it. *
  • The upgrade process must finish in 10 minutes! *
  • If this program fails,machine might be unusable, *
  • and you will need to reflash again. *
  • If you find this too risky,power off machine now. *
***

Now press [u/U] key to upgrade software: u
File system error,please upgrade by TFTP

Please input ip address of device: 192.0.0.64
Please input ip address of upgrade server: 192.0.0.128
Confirm?(y/n): y
Loading file 'uImage' to addr 0x02000000...
Done
Verifying RSA ... OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.9.44
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5866513 Bytes = 5.6 MiB
Load Address: 00008000
Entry Point: 00008000
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 4.385769] init(1) called reboot syscall, cmd: 0x0.
Thu Jan 1 00:00:04 UTC 1970

[ 5.377081] Restarting system. (task: insmod, PID:135)
SPI NAND
Flash ID read done
Normal Boot
[SECURE_INF]: Platform:0x20180a BuildTime:0x5e8f07de

[SECURE_INF]: [SECURE] <<< Check secure boot enable >>>

[SECURE_INF]: <<< Secure Boot >>>

[SECURE_INF]: loader ready to boot

Enter Loader
WATCHDOG RESTART
0
Version 0.3.8
done
DDR1 1800 2Gb
Uncompress from 0x100000 to 0x0, size 296096


U-Boot 2016.07-svn37416 (Apr 09 2020 - 19:32:18 +0800)

pwm read 5, set duty = 20
Hit ctrl+u to stop autoboot: 0
Loading file 'uImage' to addr 0x02000000...
Done
Verifying RSA ... OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.9.44
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5866513 Bytes = 5.6 MiB
Load Address: 00008000
Entry Point: 00008000
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 4.375511] init(1) called reboot syscall, cmd: 0x0.
Thu Jan 1 00:00:04 UTC 1970

[ 5.361357] Restarting system. (task: insmod, PID:135)
SPI NAND
Flash ID read done
Normal Boot
[SECURE_INF]: Platform:0x20180a BuildTime:0x5e8f07de

[SECURE_INF]: [SECURE] <<< Check secure boot enable >>>

[SECURE_INF]: <<< Secure Boot >>>

[SECURE_INF]: loader ready to boot

Enter Loader
WATCHDOG RESTART
0
Version 0.3.8
done
DDR1 1800 2Gb
Uncompress from 0x100000 to 0x0, size 296096


U-Boot 2016.07-svn37416 (Apr 09 2020 - 19:32:18 +0800)

pwm read 5, set duty = 20
Hit ctrl+u to stop autoboot: 0
Loading file 'uImage' to addr 0x02000000...
Done
Verifying RSA ... OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.9.44
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5866513 Bytes = 5.6 MiB
Load Address: 00008000
Entry Point: 00008000
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 4.375480] init(1) called reboot syscall, cmd: 0x0.
Thu Jan 1 00:00:04 UTC 1970
uuuu
u[ 5.366653] Restarting system. (task: insmod, PID:136)
SPI NAND
Flash ID read done
Normal Boot
[SECURE_INF]: Platform:0x20180a BuildTime:0x5e8f07de

[SECURE_INF]: [SECURE] <<< Check secure boot enable >>>

[SECURE_INF]: <<< Secure Boot >>>

[SECURE_INF]: loader ready to boot

Enter Loader
WATCHDOG RESTART
0
Version 0.3.8
done
DDR1 1800 2Gb
Uncompress from 0x100000 to 0x0, size 296096


U-Boot 2016.07-svn37416 (Apr 09 2020 - 19:32:18 +0800)

pwm read 5, set duty = 20
Hit ctrl+u to stop autoboot: 0

This program will upgrade software.
***
  • ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY! *
  • Don't reset machine,or anything that interrupt it. *
  • The upgrade process must finish in 10 minutes! *
  • If this program fails,machine might be unusable, *
  • and you will need to reflash again. *
  • If you find this too risky,power off machine now. *
***
 

ludshed

Getting comfortable
Joined
Sep 14, 2022
Messages
650
Reaction score
821
Location
Us
Your ip addresses don’t look logical; 192.0.0.64? By default that should be 192.168.0.64 for hik.
 

nikc0

n3wb
Joined
Oct 17, 2022
Messages
4
Reaction score
0
Location
Poland
I change recorder ip to my local network : 192.168.1.64 and server ip 192.168.1.128 . Logs are this same
 
Top