Menu
What's new

DC-2732F Bricked

G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
Camera is bricked and does not get the 192.0.0.64 address to reflash. I am able to get into uboot but do not have the process to rewrite a firmware and reload. Is the hardware broken or can it be recovered?

Sorry but i cannot remember what i previously did to get it to this state. This is a CN camera


U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0

Then stops


HKVS # help
The following commands are supported:
boot help bios diag
mtest dump erase go
exec ping r8 r16
r32 reset saveenv printenv
setenv show usbdl w8
w16 w32 tftpboot bootm
readoob killb crc nandread
nandwrite ups upm format
update upf upa upr
upk updateb ubi bapi

Use 'help' to get help on a specific command
HKVS #
 
Last edited:
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
Looks like i may have fixed it with an mimage file and the correct firmware
 
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,980
Reaction score
6,802
Location
Scotland
gazzam86 said:
Looks like i may have fixed it with an mimage file and the correct firmware
Click to expand...
Well done, a good result.
I was going to suggest the 'update' command that would tftp in the correct digicap.dav but that would fail if the mImage was damaged.
Did you get the mImage off the forum here?
 
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
Sure did! I thought this unit was destined for the bin.

That was my next step with brickfixv2 but was getting stuck booting into min-system mode. It would just pause after the reboot. Any ideas?
 
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,980
Reaction score
6,802
Location
Scotland
gazzam86 said:
That was my next step with brickfixv2 but was getting stuck booting into min-system mode.
Click to expand...
The brickfixV2 firmware when it executes, on the first power cycle after an installation, actually drops an mImage as the payload, then triggers a reboot into it.
When running the resultant min-system there are no web services, so it might appear a bit dead.
But it responds to SADP and shows the 4.0.8 firmware version, and accepts a telnet connection under admin/12345 on 192.0.0.64 IP address.
That's assuming that the bootloader environment variables ipaddr and serverip have not been modified away from their default values.

But I think what you are describing is that the mImage / min-system in brickfixV2 hangs on your camera when it boots into it.
I'm not sure why that would be, unless there would be a clue via the serial console while you go through the brickfixV2 normal install / execute steps.
 
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
[ INFO][MIN]TFTP: ####
[ INFO][MIN]TFTP: Download File [OK]
[ INFO][MIN]BURN: File size is 18558206 bytes (18123 KB)
[ INFO][MIN]BURN: Writing Flash
[ INFO][MIN]BURN: ..........................................................
[ INFO][MIN]BURN: Write Flash [OK]
***** UPDATE COMPLETE *****

#98

U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
|RCV UDP pack timeout|
Unknown command:null
nand booting ...
load kernel...
load ramdisk...
init started: BusyBox v1.19.3 (2016-05-23 16:23:55 CST)
starting pid 375, tty '': '/etc/init.d/rcS'
Starting udev: [ OK ]
UBI device number 1, total 189 LEBs (24385536 bytes, 23.3 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi1_0.
pri_iUpgSuccCnt:0x1, sec_iUpgSuccCnt:0x1
UBI device number 3, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi3_0.
Check dir /davinci ok! (0)
UBI device number 4, total 32 LEBs (4128768 bytes, 3.9 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
waiting for /dev/ubi4_0.
Check dir /config ok! (0)
diagnose_way = 15, repair_way = 1, interval = 30
route: ioctl 0x890c failed: No such process
mount: mounting none on /proc/bus/usb failed: No such file or directory
/dav
map_size = 0x300000
nr_item = 3
addr_offset = 0x0 filename = orccode.bin
addr_offset = 0x200000 filename = orcme.bin
addr_offset = 0x2a0000 filename = default_binary.bin
mmap returns 0x4031d000
loading ./orccode.bin...addr = 0x4031d000, size = 0x1a0a91
loading ./orcme.bin...addr = 0x4051d000, size = 0x3a4fc
loading ./default_binary.bin...addr = 0x405bd000, size = 0x40000
===============================
u_code version = 2016/4/6 3.0
===============================
Hello Hikvision! Enabling rollback ...
Enabled.
rm: can't remove '/dav/fixup_stage?.txt': No such file or directory
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot


U-Boot 1.3.4-30623 (Dec 6 2012 - 11:05:48)

ARM Clock: 480MHz
DDR Clock: 336MHz
Hit Ctrl+u to stop autoboot: 0
begin to enter mini system
 
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
Last edited:
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
So looks like i have gotten further. Would it be possible for mtdblock6 to be missing? the script seems to want to pull instead of pushing to the pc
 
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,980
Reaction score
6,802
Location
Scotland
gazzam86 said:
the script seems to want to pull instead of pushing to the pc
Click to expand...
Maybe it's in the Stage2 state.
You could either execute the commands manually - there are not that many, if you look at the script
cat /dav/fixup.sh
Or reset the state back to the beginning
rm /dav/fixup_stage?.txt
 
G

gazzam86

n3wb
Joined
Sep 29, 2017
Messages
10
Reaction score
1
Well that was fun! Managed to manually run the commands with a bit of stuffing around to get the files transferred. Now running a 5.4.5 full english and working perfectly on the 7608ni!! Thank you and much appreciated alastairstevenson
 
You must log in or register to reply here.
Top