Menu
What's new

Pulling my hair out trying to RE-upgrade a 2732 to 5.3.0

G

gm85

n3wb
Joined
Aug 29, 2014
Messages
5
Reaction score
0
Hey Everyone

I have a Hikvision DS-2CD2732F-IS that's a couple years old.

This is a CN camera. When I purchased the camera it came with 5.1.5. I applied the CBX region fix (before the MTD5-6 mod was well-known), so the camera is set to Region 1.

Since that time, I upgraded the camera to 5.2.5 > 5.3.0 > 5.4.0 and everything was sucessful.

Back in the fall, the camera began to lock up because of a mapped NFS drive failing.
I didn't realize it was the drive at the time, so I reverted the camera back to 5.2.5 (using the 5.4.0 > 5.3.0 and 5.3.0 > 5.2.5 downgrade firmwares)


Fast forward to today.

I have spent countless hours trying to get the camera back to 5.3.0.
Every time I attempt to flash the firmware (through the web or TFTP), the camera reboots, stays on 192.0.0.64, with no accessibility through Web or SADP.
Only TFTP and Telnet are accessible. To get the camera working again, I have to reflash the "5.3.0 > 5.2.5 firmware" back onto the camera.

I've tried using EN firmwares
I've tried CN firmwares
I've tried firmwares converted using HikTools
I've tried uploading firmwares through the Web
I've tried uploading firmwares through TFTP

Anything related to 5.3.0 I can't get to work.

The only firmware that I've had success with is the "5.3.0 to 5.2.5 firmware" which gets the camera back into a usable state.

I attached screenshots of the MTD5 and MTD6 blocks showing Region 1, as well as the output from the prtHardInfo command
mtd5.PNG

mtd6.PNG
prtHardInfo.PNG

If I apply a 5.3.0 firmware and telnet into the device, I attached a screenshot showing the response I get. The device returns with an "login: can't chdir to home directory '/root/'"
telnet.PNG

Does anybody know what I could look at to see what's preventing the device from updating to 5.3.0? As mentioned I previously had success running 5.3.0 and 5.4.0 on this camera, as well as an identical camera I have at work.

Thanks!
 
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,989
Reaction score
6,810
Location
Scotland
gm85 said:
"login: can't chdir to home directory '/root/'"
Click to expand...
That's not a real error - just a bit of careless oversight profile or initrun.sh, I forget which.
gm85 said:
Does anybody know what I could look at to see what's preventing the device from updating to 5.3.0?
Click to expand...
The reason for that problem updating should show in the console log during the attempted upgrade.
I'd speculate that the original update to the 5.4.0 firmware has swapped out the 'recovery partition' of mtdblock8 that holds the 'min-system' kernel and the 'update' program with a newer version that has more restrictions.

With the telnet facility still open after the failed update, you should be able to manually trigger an update to 5.3.0 and capture the kernel log of the process.
This should be possible with either the Hikvision tftp updater, or a standard tftp server such as : TFTPD32 : an opensource IPv6 ready TFTP server/service for windows : TFTP server
From what I recall (my spare Hiks are out on loan so I don't have one to hand to check) you can trigger an update at the shell prompt with either / both
update
or just
tftp
assuming the IP addresses of the server is OK.
 
G

gm85

n3wb
Joined
Aug 29, 2014
Messages
5
Reaction score
0
Thanks for the response alastairstevenson

I attempted the upgrade again today and was able to capture the logs:

This was the /proc/kmsg while the camera was upgrading 5.2.5 > 5.3.0 (before it rebooted)
Code: 
<5>[48772.529673] UBI: attaching mtd14 to ubi2
<5>[48772.529717] UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>[48772.529741] UBI: logical eraseblock size:    129024 bytes
<5>[48772.529760] UBI: smallest flash I/O unit:    2048
<5>[48772.529777] UBI: sub-page size:              512
<5>[48772.529797] UBI: VID header offset:          512 (aligned 512)
<5>[48772.529816] UBI: data offset:                2048
<5>[48772.642218] UBI: max. sequence number:       156
<5>[48772.682140] UBI: attached mtd14 to ubi2
<5>[48772.682190] UBI: MTD device name:            "app_sec"
<5>[48772.682216] UBI: MTD device size:            24 MiB
<5>[48772.682235] UBI: number of good PEBs:        192
<5>[48772.682252] UBI: number of bad PEBs:         0
<5>[48772.682268] UBI: number of corrupted PEBs:   0
<5>[48772.682285] UBI: max. allowed volumes:       128
<5>[48772.682303] UBI: wear-leveling threshold:    4096
<5>[48772.682321] UBI: number of internal volumes: 1
<5>[48772.682339] UBI: number of user volumes:     1
<5>[48772.682357] UBI: available PEBs:             0
<5>[48772.682374] UBI: total number of reserved PEBs: 192
<5>[48772.682393] UBI: number of PEBs reserved for bad PEB handling: 2
<5>[48772.682416] UBI: max/mean erase counter: 55/43
<5>[48772.682433] UBI: image sequence number:  1519995641
<5>[48772.695678] UBI: background thread "ubi_bgt2d" started, PID 2843
<5>[48774.970096] UBIFS: mounted UBI device 2, volume 0, name "app_sec"
<5>[48774.970143] UBIFS: file system size:   22837248 bytes (22302 KiB, 21 MiB,                                                         177 LEBs)
<5>[48774.970178] UBIFS: journal size:       1161216 bytes (1134 KiB, 1 MiB, 9 L                                                        EBs)
<5>[48774.970205] UBIFS: media format:       w4/r0 (latest is w4/r0)
<5>[48774.970224] UBIFS: default compressor: lzo
<5>[48774.970245] UBIFS: reserved for root:  1078659 bytes (1053 KiB)
<5>[48895.635483] UBIFS: un-mount UBI device 2, volume 0
<5>[48895.911880] UBI: mtd14 is detached from ubi2
After the 5.3.0 upgrade, I checked the /proc/kmsg file:
Code: 
<5>Linux version 2.6.38.8 (wangqian@ipcteam2) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) )
<5>#42 PREEMPT Thu Apr 3 13:10:04 CST 2014
<4>CPU: ARMv6-compatible processor [4117b365] revision 5 (ARMv6TEJ), cr=00c5387f
<4>CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
<4>Machine: Coconut
<4>Ignoring unrecognised tag 0x44000426
<4>Memory policy: ECC disabled, Data cache writeback
<6>Ambarella: AHB       = 0x60000000[0xf0000000],0x01000000 0
<6>Ambarella: APB       = 0x70000000[0xf1000000],0x01000000 0
<6>Ambarella: PPM       = 0xc0000000[0xe0000000],0x00200000 9
<6>Ambarella: BSB       = 0xc8c00000[0xe8c00000],0x00400000 9
<6>Ambarella: DSP       = 0xc9000000[0xe9000000],0x07000000 9
<6>Ambarella: HAL       = 0xc00a0000[0xfee00000],0x0000e708 9
<7>On node 0 totalpages: 25344
<7>free_area_init_node: node 0, pgdat c0493be8, node_mem_map c04b3000
<7>  Normal zone: 198 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 25146 pages, LIFO batch:7
<4>bootmem_init: high_memory = 0xc8a00000
<7>pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>pcpu-alloc: [0] 0
<4>Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 25146
<5>Kernel command line: console=ttyS0 dbg=0 IP=192.0.0.64 MASK=255.255.255.0 GW=0.0.0.0 SERVER=192.0.0.128 video=amb0fb:720x480,720x480,1,0
<6>PID hash table entries: 512 (order: -1, 2048 bytes)
<6>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 99MB = 99MB total
<5>Memory: 91512k/91512k available, 9864k reserved, 0K highmem
<5>Virtual kernel memory layout:
<5>    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
<5>    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
<5>    DMA     : 0xfe600000 - 0xfee00000   (   8 MB)
<5>    vmalloc : 0xc9000000 - 0xe0000000   ( 368 MB)
<5>    lowmem  : 0xc0000000 - 0xc8a00000   ( 138 MB)
<5>    modules : 0xbf000000 - 0xc0000000   (  16 MB)
<5>      .init : 0xc0008000 - 0xc022c000   (2192 kB)
<5>      .text : 0xc022c000 - 0xc0476000   (2344 kB)
<5>      .data : 0xc0476000 - 0xc04942a0   ( 121 kB)
<6>Preemptable hierarchical RCU implementation.
<6>     RCU-based detection of stalled CPUs is disabled.
<6>     Verbose stalled-CPUs detection is disabled.
<6>NR_IRQS:224
<6>sched_clock: 32 bits at 72MHz, resolution 13ns, wraps every 59652ms
<2>sched_clock: wrong multiply/shift: 1864135111>>27 vs calculated 3728270222>>28
<2>sched_clock: fix multiply/shift to avoid scheduler hiccups
<4>Console: colour dummy device 80x30
<6>console [ttyS0] enabled
<6>Calibrating delay loop... 351.43 BogoMIPS (lpj=1757184)
<6>pid_max: default: 32768 minimum: 301
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<6>Ambarella Coconut:
<6>     chip id:                5100
<6>     board type:             3
<6>     board revision:         10
<6>     chip name:              a5m
<6>     HAL version:            176869
<6>     reference clock:        24000000
<6>     system configuration:   0x177804ea
<6>     boot type:              0x00000002
<6>     hif type:               0x00000000
<4>bio: create slab <bio-0> at 0
<6>ambarella-spi ambarella-spi.0: ambarella SPI Controller 0 created
<5>ambarella-i2c ambarella-i2c.0: Ambarella Media Processor I2C adapter[i2c-0] probed!
<5>ambarella-i2c ambarella-i2c.1: Ambarella Media Processor I2C adapter[i2c-1] probed!
<6>i2c i2c-0: Added multiplexed i2c bus 2
<6>ambarella-i2cmux ambarella-i2cmux.0: mux on ambarella-i2c adapter
<6>Switching to clocksource ambarella-cs-timer
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP established hash table entries: 4096 (order: 3, 32768 bytes)
<6>TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>TCP reno registered
<6>UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>NET: Registered protocol family 1
<6>Unpacking initramfs...
<0>Initramfs unpacking failed: junk in compressed archive
<6>Freeing initrd memory: 4096K
<0>[ kernel version:  svn-69900 ]
<4>mmc0 power register success!
<4>mmc1 power register success!
<1>use default reserved area information!
<6>reboot times :10
<6>msgmni has been set to 186
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>ambarella-uart.0: ttyS0 at MMIO 0x70005000 (irq = 9) is a ambuart
<6>NAND device: Manufacturer ID: 0x98, Chip ID: 0xd1 (Toshiba NAND 128MiB 3,3V 8-bit)
<4>ambarella_nand_config_flash: 0x02e00140, 0x02c00140
<7>Bad block table found at page 65472, version 0x01
<7>Bad block table found at page 65408, version 0x01
<6>ambarella-nand ambarella-nand: ambarella_nand_probe: Partition infomation found!
<5>Creating 18 MTD partitions on "ambnand":
<5>0x000000000000-0x000000020000 : "bst"
<5>0x000000020000-0x000000120000 : "ptb"
<5>0x000000120000-0x000000220000 : "bld"
<5>0x000000220000-0x000000320000 : "hal"
<5>0x000000320000-0x000000420000 : "ano_ptb"
<5>0x000000420000-0x0000004a0000 : "env"
<5>0x0000004a0000-0x000000520000 : "param"
<5>0x000000520000-0x000000620000 : "dpt"
<5>0x000000620000-0x000001020000 : "rcvy"
<5>0x000001020000-0x000001820000 : "krn_pri"
<5>0x000001820000-0x000002020000 : "krn_sec"
<5>0x000002020000-0x000002420000 : "rmd_pri"
<5>0x000002420000-0x000002820000 : "rmd_sec"
<5>0x000002820000-0x000004020000 : "app_pri"
<5>0x000004020000-0x000005820000 : "app_sec"
<5>0x000005820000-0x000005c20000 : "cfg_pri"
<5>0x000005c20000-0x000006020000 : "cfg_sec"
<5>0x000006020000-0x000007020000 : "dbg"
<6>Ambarella MII Bus: probed
<5>ambarella-eth ambarella-eth.0: MAC Address[44:19:b6:5b:45:88].
<6>mousedev: PS/2 mouse device common for all mice
<6>ambarella-rtc ambarella-rtc: rtc core: registered ambarella-rtc as rtc0
<6>i2c /dev entries driver
<5>ambarella-wdt ambarella-wdt: Ambarella Media Processor Watch Dog Timer[ambarella-wdt].
<6>TCP cubic registered
<6>NET: Registered protocol family 17
<6>ambarella-rtc ambarella-rtc: setting system clock to 2017-03-28 09:01:55 UTC (1490691715)
<6>Freeing init memory: 2192K
<5>net eth0: Could not find default PHY in 9.
<5>net eth0: Try PHY[9] whose id is 0x00008201!
<5>UBI: attaching mtd13 to ubi1
<5>UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>UBI: logical eraseblock size:    129024 bytes
<5>UBI: smallest flash I/O unit:    2048
<5>UBI: sub-page size:              512
<5>UBI: VID header offset:          512 (aligned 512)
<5>UBI: data offset:                2048
<5>UBI: max. sequence number:       345
<5>UBI: attached mtd13 to ubi1
<5>UBI: MTD device name:            "app_pri"
<5>UBI: MTD device size:            24 MiB
<5>UBI: number of good PEBs:        192
<5>UBI: number of bad PEBs:         0
<5>UBI: number of corrupted PEBs:   0
<5>UBI: max. allowed volumes:       128
<5>UBI: wear-leveling threshold:    4096
<5>UBI: number of internal volumes: 1
<5>UBI: number of user volumes:     1
<5>UBI: available PEBs:             0
<5>UBI: total number of reserved PEBs: 192
<5>UBI: number of PEBs reserved for bad PEB handling: 2
<5>UBI: max/mean erase counter: 63/52
<5>UBI: image sequence number:  855221409
<5>UBI: background thread "ubi_bgt1d" started, PID 321
<5>UBIFS: recovery needed
<5>UBIFS: recovery completed
<5>UBIFS: mounted UBI device 1, volume 0, name "app_pri"
<5>UBIFS: file system size:   22837248 bytes (22302 KiB, 21 MiB, 177 LEBs)
<5>UBIFS: journal size:       1161216 bytes (1134 KiB, 1 MiB, 9 LEBs)
<5>UBIFS: media format:       w4/r0 (latest is w4/r0)
<5>UBIFS: default compressor: lzo
<5>UBIFS: reserved for root:  1078659 bytes (1053 KiB)
<5>UBI: attaching mtd14 to ubi2
<5>UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>UBI: logical eraseblock size:    129024 bytes
<5>UBI: smallest flash I/O unit:    2048
<5>UBI: sub-page size:              512
<5>UBI: VID header offset:          512 (aligned 512)
<5>UBI: data offset:                2048
<5>UBI: max. sequence number:       285
<5>UBI: attached mtd14 to ubi2
<5>UBI: MTD device name:            "app_sec"
<5>UBI: MTD device size:            24 MiB
<5>UBI: number of good PEBs:        192
<5>UBI: number of bad PEBs:         0
<5>UBI: number of corrupted PEBs:   0
<5>UBI: max. allowed volumes:       128
<5>UBI: wear-leveling threshold:    4096
<5>UBI: number of internal volumes: 1
<5>UBI: number of user volumes:     1
<5>UBI: available PEBs:             0
<5>UBI: total number of reserved PEBs: 192
<5>UBI: number of PEBs reserved for bad PEB handling: 2
<5>UBI: max/mean erase counter: 55/44
<5>UBI: image sequence number:  1519995641
<5>UBI: background thread "ubi_bgt2d" started, PID 332
<6>PHY: 0:09 - Link is Up - 100/Full
<5>UBIFS: mounted UBI device 2, volume 0, name "app_sec"
<5>UBIFS: file system size:   22837248 bytes (22302 KiB, 21 MiB, 177 LEBs)
<5>UBIFS: journal size:       1161216 bytes (1134 KiB, 1 MiB, 9 LEBs)
<5>UBIFS: media format:       w4/r0 (latest is w4/r0)
<5>UBIFS: default compressor: lzo
<5>UBIFS: reserved for root:  1078659 bytes (1053 KiB)
<5>UBI: attaching mtd15 to ubi3
<5>UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>UBI: logical eraseblock size:    129024 bytes
<5>UBI: smallest flash I/O unit:    2048
<5>UBI: sub-page size:              512
<5>UBI: VID header offset:          512 (aligned 512)
<5>UBI: data offset:                2048
<5>UBI: max. sequence number:       92
<5>UBI: attached mtd15 to ubi3
<5>UBI: MTD device name:            "cfg_pri"
<5>UBI: MTD device size:            4 MiB
<5>UBI: number of good PEBs:        32
<5>UBI: number of bad PEBs:         0
<5>UBI: number of corrupted PEBs:   0
<5>UBI: max. allowed volumes:       128
<5>UBI: wear-leveling threshold:    4096
<5>UBI: number of internal volumes: 1
<5>UBI: number of user volumes:     1
<5>UBI: available PEBs:             0
<5>UBI: total number of reserved PEBs: 32
<5>UBI: number of PEBs reserved for bad PEB handling: 2
<5>UBI: max/mean erase counter: 112/108
<5>UBI: image sequence number:  1744608342
<5>UBI: background thread "ubi_bgt3d" started, PID 343
<5>UBIFS: recovery needed
<5>UBIFS: recovery completed
<5>UBIFS: mounted UBI device 3, volume 0, name "cfg_pri"
<5>UBIFS: file system size:   2193408 bytes (2142 KiB, 2 MiB, 17 LEBs)
<5>UBIFS: journal size:       1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
<5>UBIFS: media format:       w4/r0 (latest is w4/r0)
<5>UBIFS: default compressor: lzo
<5>UBIFS: reserved for root:  103599 bytes (101 KiB)
<5>UBI: attaching mtd16 to ubi4
<5>UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>UBI: logical eraseblock size:    129024 bytes
<5>UBI: smallest flash I/O unit:    2048
<5>UBI: sub-page size:              512
<5>UBI: VID header offset:          512 (aligned 512)
<5>UBI: data offset:                2048
<5>UBI: max. sequence number:       95
<5>UBI: attached mtd16 to ubi4
<5>UBI: MTD device name:            "cfg_sec"
<5>UBI: MTD device size:            4 MiB
<5>UBI: number of good PEBs:        32
<5>UBI: number of bad PEBs:         0
<5>UBI: number of corrupted PEBs:   0
<5>UBI: max. allowed volumes:       128
<5>UBI: wear-leveling threshold:    4096
<5>UBI: number of internal volumes: 1
<5>UBI: number of user volumes:     1
<5>UBI: available PEBs:             0
<5>UBI: total number of reserved PEBs: 32
<5>UBI: number of PEBs reserved for bad PEB handling: 2
<5>UBI: max/mean erase counter: 114/111
<5>UBI: image sequence number:  1077105010
<5>UBI: background thread "ubi_bgt4d" started, PID 354
<5>UBIFS: recovery needed
<5>UBIFS: recovery completed
<5>UBIFS: mounted UBI device 4, volume 0, name "cfg_sec"
<5>UBIFS: file system size:   2193408 bytes (2142 KiB, 2 MiB, 17 LEBs)
<5>UBIFS: journal size:       1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
<5>UBIFS: media format:       w4/r0 (latest is w4/r0)
<5>UBIFS: default compressor: lzo
<5>UBIFS: reserved for root:  103599 bytes (101 KiB)
I took your advice and attempted to re-upload from telnet, however I was unable to find the arguments associated with the update command:
Code: 
#update
[ INFO][MIN]TFTP: TFTP from server
[ INFO][MIN]TFTP: Filename: 'digicap.dav'
[ INFO][MIN]TFTP: Download File [FAIL] error: tftp.
!!!!! UPDATE FAIL !!!!!

#update 192.0.0.128
[ INFO][MIN]TFTP: TFTP from server
[ INFO][MIN]TFTP: Filename: 'digicap.dav'
[ INFO][MIN]TFTP: Download File [FAIL] error: tftp.
!!!!! UPDATE FAIL !!!!!

# upgrade
[ERROR][MIN]BURN: open failed
If the issue is related to the mtdblock8, I wonder if that partition is identical among all hikvision cameras.
As mentioned I also have another 2732 flashed with 5.4.0. I wonder if I would have success copying ALL the mtdblock partitions (aside from 5 and 6) from that camera to this one.

EDIT: Scratch that last idea.... Forgot that since 5.4.0 is flashed on the other camera, I can't get shell access to it.
 
Last edited:
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,989
Reaction score
6,810
Location
Scotland
gm85 said:
After the 5.3.0 upgrade, I checked the /proc/kmsg file:
Click to expand...
That's just the log of the 'min-system' kernel startup - check out the old Linux version at the start of it - ">Linux version 2.6.38.8"
gm85 said:
This was the /proc/kmsg while the camera was upgrading 5.2.5 > 5.3.0 (before it rebooted)
Click to expand...
I don't think the update program writes it's output there, there is nothing showing.

What may be good would be to see what the update program has to say in terms of errors while attempting the update.
To do this, it looks like you need to setenv and savenv some needed environment variables. Use printenv to see what they are currently.
You can set the camera "ipaddr" conveniently to match your LAN, and the "serverip" to match the PC the tftp server is running on. I'm using this one : TFTPD32 : an opensource IPv6 ready TFTP server/service for windows : TFTP server

This example should give some idea of what's needed, but there may be differences as this is a Chinese 3335
The firmware in digicap.dav isn't right for this camera - though the error isn't helpful.

Code: 
▒


U-Boot 2010.06-128034 (May 14 2015 - 19:28:38)

NAND:  128 MiB
Hit Ctrl+u to stop autoboot:  0
HKVS #
HKVS # printenv
bootcmd=loadk;bootm
bootdelay=3
baudrate=115200
bootfile="uImage"
init=/bin/sh
filesize=300000
fileaddr=80007FC0
netmask=255.255.255.0
ipaddr=192.168.1.65
bootargs=console=ttyAMA0,115200 init=/bin/sh rootfs=0x82000000 rootfstype=initrd
serverip=192.168.1.99
stdin=serial
stdout=serial
stderr=serial
verify=n
ethaddr=c4:2f:90:44:2a:c6
mdio_intf=mii
phy_addr=3
ver=U-Boot 2010.06-128034 (May 14 2015 - 19:28:38)

Environment size: 410/262140 bytes
HKVS # update
ETH0: PHY(phyaddr=3, mii) link UP: DUPLEX=FULL : SPEED=100M
MAC:   C4-2F-90-44-2A-C6
TFTP from server 192.168.1.99; our IP address is 192.168.1.65
Download Filename 'digicap.dav'.
Download to address: 0x82000000
Downloading: #################################################
done
Bytes transferred = 18002940 (112b3fc hex)
error: digicap package error!!!
HKVS #
 
G

gm85

n3wb
Joined
Aug 29, 2014
Messages
5
Reaction score
0
Well I tried round 2. Re-Flashed, 5.3.0 and rebooted

Attempted to use the "Update" command, but it was not accepting the argument variables. Took a look and found out the "Update" command is actually a shell script that launches the "tftp" and "upgrade" commands.

So, I ran the commands (contained in the script) manually:
Code: 
#  tftp -g -r digicap.dav  -l /digicap.dav 192.0.0.128
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
# upgrade /digicap.dav
[ INFO][MIN]BURN: File size is 21613690 bytes (21107 KB)
[ INFO][MIN]BURN: Writing Flash
[ INFO][MIN]BURN: ............................................................
#
So it downloaded and wrote the digicap.dav file, but no errors were returned. Rebooted and was in the same situation as before.

I might see if I can manually extract the mtdblocks from my office cam (running 5.4.0)... possibly using console access
 
You must log in or register to reply here.
Top