ip camera brick after firmware wrong

[vasycara]

I have a Wanscam ip camera, after loading with bad firmware the ip camera is dead
It does not appear in my network, it does not respond to ping
If I use a serial console interface with Putty I see this


U-Boot 2010.06 (May 23 2014 - 08:55:45)

NAND: Special Nand id table Version 1.35
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
0 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
Spi(cs1): Block:64KB Chip:16MB Name:"MX25L128XX"
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
16384 KiB hi_sfc at 0:0 is now current device

## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.0.8
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2521708 Bytes = 2.4 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.0.8 (root@localhost.localdomain) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+uclibc_0.9.32.1+eabi+linuxpthread)) ) #3 Fri May 23 17:16:42 HKT 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: hi3518
Memory policy: ECC disabled, Data cache writeback
AXI bus clock 220000000.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40640
Kernel command line: mem=160M console=ttyAMA0,115200 root=/dev/mtdblock2 rootfstype=jffs2 mtdparts=hi_sfc:512K(boot),2560K(kernel),13M(rootfs)
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 160MB = 160MB total
Memory: 157592k/157592k available, 6248k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xca800000 - 0xfe000000 ( 824 MB)
lowmem : 0xc0000000 - 0xca000000 ( 160 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0021000 ( 100 kB)
.text : 0xc0021000 - 0xc046d000 (4400 kB)
.data : 0xc046e000 - 0xc048bd40 ( 120 kB)
.bss : 0xc048bd64 - 0xc049eeb0 ( 77 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:32 nr_irqs:32 32
sched_clock: 32 bits at 110MHz, resolution 9ns, wraps every 39045ms
Console: colour dummy device 80x30
Calibrating delay loop... 218.72 BogoMIPS (lpj=1093632)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Serial: AMBA PL011 UART driver
uart:0: ttyAMA0 at MMIO 0x20080000 (irq = 5) is a PL011 rev2
console [ttyAMA0] enabled
uart:1: ttyAMA1 at MMIO 0x20090000 (irq = 5) is a PL011 rev2
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource timer1
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 307
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
Spi id table Version 1.22
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
SPI FLASH start_up_mode is 3 Bytes
Spi(cs1):
Block:64KB
Chip:16MB
Name:"MX25L128XX"
spi size: 16MB
chip num: 1
3 cmdlinepart partitions found on MTD device hi_sfc
Creating 3 MTD partitions on "hi_sfc":
0x000000000000-0x000000080000 : "boot"
0x000000080000-0x000000300000 : "kernel"
0x000000300000-0x000001000000 : "rootfs"
Fixed MDIO Bus: probed
himii: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
hiusb-ehci hiusb-ehci.0: HIUSB EHCI
hiusb-ehci hiusb-ehci.0: new USB bus registered, assigned bus number 1
hiusb-ehci hiusb-ehci.0: irq 15, io mem 0x100b0000
hiusb-ehci hiusb-ehci.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
hiusb-ohci hiusb-ohci.0: HIUSB OHCI
hiusb-ohci hiusb-ohci.0: new USB bus registered, assigned bus number 2
hiusb-ohci hiusb-ohci.0: irq 16, io mem 0x100a0000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 10
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
registered taskstats version 1
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
¦usb 1-1: new high speed USB device number 2 using hiusb-ehci
VFS: Mounted root (jffs2 filesystem) on device 31:2.
Freeing init memory: 100K

_ _ _ _ _ _ _ _ _ _ _ _
\ _ _ _ _ _ ___
/ /__/ \ |_/
/ __ / - _ ___
/ / / / / /
_ _ _ / / / \/ \_ __
___\\___

[RCS]: /etc/init.d/S00devs
[RCS]: /etc/init.d/S01udev
udevd (396): /proc/396/oom_adj is deprecated, please use /proc/396/oom_score_adj instead.
[RCS]: /etc/init.d/S80network
ADDRCONF(NETDEV_UP): eth0: link is not ready
sd
sd
/lib/libhichip.so
/lib/libAPILib.so
/lib/libNetLib.so
mtutil7601Usta: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/mtutil7601Usta.ko': invalid module format
mt7601Usta: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/mt7601Usta.ko': invalid module format
mtnet7601Usta: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/mtnet7601Usta.ko': invalid module format
extalarm: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/extalarm.ko': invalid module format
wdt: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/wdt.ko': invalid module format
encript: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '

(none) login: insmod: can't insert '/mnt/mtd/ipc/modules/encript.ko': invalid module format
relay: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/relay.ko': invalid module format
reset: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/reset.ko': invalid module format
hi_rtc: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/hi_rtc.ko': invalid module format
rled: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/rled.ko': invalid module format
ircut: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/ircut.ko': invalid module format
saradc: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/saradc.ko': invalid module format
rs485: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/rs485.ko': invalid module format
light: version magic '3.4.35 mod_unload ARMv5 p2v8 ' should be '3.0.8 mod_unload ARMv5 '
insmod: can't insert '/mnt/mtd/ipc/modules/light.ko': invalid module format
mmz_start: 0x8c000000, mmz_size: 64M


U-Boot 2010.06 (May 23 2014 - 08:55:45)

NAND: Special Nand id table Version 1.35
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
0 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
Spi(cs1): Block:64KB Chip:16MB Name:"MX25L128XX"
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
hisilicon # lp
Unknown command 'lp' - try 'help'
hisilicon # help
? - alias for 'help'
base - print or set address offset
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
getinfo - print hardware information
go - start application at address 'addr'
help - print command description/usage
loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modifyA
usbboot - boot from USB device
version - print monitor version
hisilicon #
hisilicon #
hisilicon #
hisilicon #
hisilicon #
hisilicon #
hisilicon #

I have a good firmware that the camera worked with, but I don't know how to load this firmware through the uart interface.
Any ideas are welcome.

 

[vasycara]

Seems to have net addresses :



U-Boot 2010.06 (May 23 2014 - 08:55:45)

NAND: Special Nand id table Version 1.35
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
0 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x18 0xC2 0x20 0x18
Spi(cs1): Block:64KB Chip:16MB Name:"MX25L128XX"
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
hisilicon # help
Unknown command 'help' - try 'help'
hisilicon # help
? - alias for 'help'
base - print or set address offset
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
getinfo - print hardware information
go - start application at address 'addr'
help - print command description/usage
loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
tftp - tftp - download or upload image via network using TFTP protocol
usb - USB sub-system
usbboot - boot from USB device
version - print monitor version
hisilicon #
hisilicon #
hisilicon # printenv
bootdelay=1
baudrate=115200
bootfile="uImage"
phyaddru=0
phyaddrd=1
mdio_intf=rmii
ethaddr=00:0a:bc:ef:82:25
filesize=25F000
fileaddr=82000000
netmask=255.255.255.0
bootargs=mem=160M console=ttyAMA0,115200 root=/dev/mtdblock2 rootfstype=jffs2 mtdparts=hi_sfc:512K(boot),2560K(kernel),13M(rootfs)
bootcmd=sf probe 0;sf read 0x82000000 0x80000 0x280000;bootm 0x82000000
ipaddr=192.168.8.88
serverip=192.168.8.8
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06 (May 23 2014 - 08:55:45)

Environment size: 503/262140 bytes
hisilicon #

 

[wittaj]

Ouch, you just learned a hard lesson...

I have nothing to offer you other than to use this thread as a learning opportunity to future people that come here looking for a firmware update...

You really need to be asking yourself why are you updating? If it is just for grins and giggles or OCD behavior to be running the latest firmware, think twice.

A common theme around here is don't fix what ain't broke. If the unit is working and meets your needs, in many instances an update breaks what you had working and provides you with something you didn't need or bricks the camera. In most instances, updates are simply security vulnerability patches (usually years after the breach was found), but since we do not give our cameras internet access, the update is useless to us.

Here are issues I have seen people report here where they were upgrading just for the sake of upgrading:

• A Dahua Z12E that someone updated and then constantly reboots comes to mind,
• The Dahua 49225 PTZ that loses autotracking with an update come to mind,
• A Hikvision ANPR camera losing half the FPS and loses the ability to read US plates - those are big deals to have happen.
• A Hikvision camera that the user lost ability to control the LED light function at night.
• Countless other instances where the camera simply bricked and became useless.
• Countless examples where the camera went into Chinese.

Don't do it unless it is fixing a problem you are experiencing or adds a feature you really need.

Further, it is best to obtain any firmware updates from the vendor you purchased it from so that you do not run into issues. Any firmware you find here or elsewhere is obviously proceed at your own risk. We have many threads here where someone tried an update with a firmware they found on the internet and bricked their unit.

Many units being sold are Chinese hacked units that will either brick or go into Chinese upon updating. Some vendors will be upfront and tell consumers that as part of their website, but many do not or the consumer forgets...here is one such example....

 

[vasycara]

With this command ip camera responds to ping, and appears in my network. I can upload files with tftp but I don't know what to upload, I have a good firmware that ip camera has worked with before.

hisilicon # ping 192.168.8.88
Hisilicon ETH net controler
MAC: 00-0A-BC-EF-82-25
UP_PORT : phy status change : LINK=DOWN : DUPLEX=FULL : SPEED=100M
UP_PORT : phy status change : LINK=UP : DUPLEX=FULL : SPEED=100M

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again