Bricked DS-KH6350-WTE1

tnpet2

n3wb
Joined
Sep 25, 2023
Messages
2
Reaction score
2
Location
's-Hertogenbosch
Hi all,

I updated my DS-KH6350-WTE1 to firmware 2.20 true iVMS 4200 and since then it isn't booting up anymore.
I tried to restore it with the tftp tool with no luck.
I also tried to do the restore with interrupting the booting proces with no luck either.
I can write down the "192.0.0.64" and "192.0.0.128" address and after that the "y" butt it repeats the same questions to putt in the ip adres again, again and again...

See the following logs (from the serial port) when I boot the device normally (I can ping it on the default adres 192.0.0.64).
Any help would be appreciated.

MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMOFB
MLE
RBE
SPL Nor Load!
SPL Nor flash boot!
Secure boot enable
Secure verify ok
LzmaDecode start
LzmaDecode end(0)


U-Boot 2017.09-svn560893 (Mar 10 2023 - 15:37:12 +0800)

DRAM: 128 MiB
MMC: dwmmc@10300000: 0
*** Warning - bad CRC, using default environment

In: uart@0x18400000
Out: uart@0x18400000
Err: uart@0x18400000

Current Mode: Release.
SA Version: svn561153
Net: eth0: ethernet@1b800000
### CRAMFS load complete: 8965 bytes loaded to 0x40000000
Hit any key to stop autoboot: 0
### CRAMFS load complete: 2299080 bytes loaded to 0x40008000
### CRAMFS load complete: 728683 bytes loaded to 0x41000000
### CRAMFS load complete: 22378 bytes loaded to 0x41800000
### CRAMFS load complete: 824 bytes loaded to 0x41810000
Signature verification uImage OK.
Signature verification ramdisk.gz OK.
## Booting kernel from Legacy Image at 40008120 ...
Image Name: Linux-4.9.138
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2298728 Bytes = 2.2 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 41000120 ...
Image Name: ramdisk_0.2.7_CPL-HZV-AVI-GEN-74
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 728331 Bytes = 711.3 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 41800000
Booting using the fdt blob at 0x41800000
Loading Kernel Image ... OK
Loading Ramdisk to 45f4e000, end 45fffd0b ... OK
reserving fdt memory region: addr=41800000 size=6000
Loading Device Tree to 45f45000, end 45f4dfff ... OK

Starting kernel ...

init started: BusyBox v1.31.1 (2021-11-26 11:39:17 CST)
Starting mdev: [ OK ]
mntpath decompress
len decompress 0
chmod: loadko.sh: Read-only file system
mmz_start: 0x46000000, mmz_size: 32M
show logo Fri Jan 9 11:49:10 UTC 1970
---not show logo
start decompress Fri Jan 9 11:49:10 UTC 1970
rm: can't remove '/home/app/app.tar.lzma': No such file or directory
tar: unexpected EOF
tar: short read
rm: can't remove '/home/app/vistalk.tar.lzma': No such file or directory
rm: can't remove '/home/app/misc.tar.lzma': No such file or directory
rm: can't remove '/home/app/audio.tar.lzma': No such file or directory
end decompress Fri Jan 9 11:49:16 UTC 1970
cp: can't stat '/home/app/cam_default.xml': No such file or directory
rm: can't remove '/home/app/cam_default.xml': No such file or directory
/home/hik/start.sh: line 148: /home/app/hicore: not found


BusyBox v1.31.1 (2021-11-26 11:39:17 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

BusyBox v1.2.1 Protect Shell (psh svn339403) Build Time: Apr 28 2021:16:10:56
Enter 'help' for a list system commands.

Random number is:1920343449
# help
Support Commands:
getHardInfo help Debug
sandbox
#
___

MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMOFB
MLE
RBE
SPL Nor Load!
SPL Nor flash boot!
Secure boot enable
Secure verify ok
LzmaDecode start
LzmaDecode end(0)


U-Boot 2017.09-svn560893 (Mar 10 2023 - 15:37:12 +0800)

DRAM: 128 MiB
MMC: dwmmc@10300000: 0
*** Warning - bad CRC, using default environment

In: uart@0x18400000
Out: uart@0x18400000
Err: uart@0x18400000

Current Mode: Release.
SA Version: svn561153
Net: eth0: ethernet@1b800000
### CRAMFS load complete: 8965 bytes loaded to 0x40000000
Hit any key 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. *
***

Now press [u/U] key to upgrade software:u
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
Please input ip address of device:
 

Attachments

trempa92

Pulling my weight
Joined
Mar 26, 2020
Messages
784
Reaction score
247
Location
Croatia,Zagreb
when prompted to confirm, type b and enter. It will give you ability to type cmds.

set ipaddr 192.0.0.64
set serverip 192.0.0.128
update

or

setenv ';ipaddr 192.0.0.64'
savenv
setenv ';serverip 192.0.0.128'
saveenv
setenv ';update'


perhaps it is already on default ip just type

printenv to confirm or setenv ';printenv'

then just update
Hope it helps
 

tnpet2

n3wb
Joined
Sep 25, 2023
Messages
2
Reaction score
2
Location
's-Hertogenbosch
when prompted to confirm, type b and enter. It will give you ability to type cmds.

set ipaddr 192.0.0.64
set serverip 192.0.0.128
update

or

setenv ';ipaddr 192.0.0.64'
savenv
setenv ';serverip 192.0.0.128'
saveenv
setenv ';update'


perhaps it is already on default ip just type

printenv to confirm or setenv ';printenv'

then just update
Hope it helps
Hi, you're the man :)!
I was able to update the device with the option "b"!!

I already was getting a headache from it hahaha...
 
Joined
Oct 31, 2023
Messages
7
Reaction score
1
Location
Italia
Hi all I've the same problem can you help me?
the tool tftp don't not discover the ds-kh6350 how can I solve it?
@trempa92


[2023-10-31 23:48:35] TFTP server [192.0.0.128] initialized
[2023-10-31 23:49:54] TFTP server [192.0.0.128] initialized


and the ping to 192.0.0.64 it's ok but the the tool does not discovery anywere ....
 
Last edited:

trempa92

Pulling my weight
Joined
Mar 26, 2020
Messages
784
Reaction score
247
Location
Croatia,Zagreb
Do you have cable to connect to debug port of device? 4pin

If not, then i cant help you :/
 

rafy

n3wb
Joined
Nov 16, 2023
Messages
1
Reaction score
0
Location
Zagreb, Croatia
Can somebody explain how to interrupt the boot process? I connected the unit over debug port, and using putty.
 
Top