bricked foscam fi9828p

X

xavier00

Getting the hang of it
Jul 31, 2016
103
1
i did a firmware update and some how it ended up bricked, called foscam and no help, i bougtit on ebay an the seller is no longer, i have the ttl cables, opened the cam an there are no f2 or f4 ports.i need if some one knows where to soldrer this cables to the serial ports so i can recover, please help!!'
 
Can you post a picture of the main board so we can have a guess?
And then when you've found the right connections, this might be useful: http://foscam.us/forum/fi9828p-v2-bricked-after-firmware-upgrade-t13566.html
But I suspect you may already have seen that ...

With a TTL Serial interface - you could easily probe the test points or connectors just using the RX input only, if you connect the GND lead, and watch what PuTTY or your favourite serial terminal shows when you power on the camera. Readable characters and you have found TX on the board.
Try settings 115,200 buad rate 8 bits no parity, no flow control.
 
Wow, that's a lot of test points on that board!
From another post:
"Take your USB to TTL serial convertor, attach the GND wire to any of the big corner holes that the mounting screws go in - or the metal plate they connect to if the board is still assembled.
Wrap the RX wire around a short needle and start up PuTTY or your favourite serial terminal program, with likely settings 115,200 baud rate, 8 bits no parity, no flow control.
With the camera powered off, poke the needle gently on to one of the pads marked TP around the big SoC chip in the middle.
Power on the camera and watch for readable text scrolling up in the terminal. It will likely finish with a '#' prompt, it might be static, it might still keep scrolling.
If nothing, power off, move to the next pad and power on again.
When you've got the right one, you need to get another hand to keep the Return key pressed on the keyboard.
Wrap the TX wire around another needle and whilst keeping the original needle in place, probe the pads marked TP and look for the one that generates new lines on the terminal screen. The return key will be sending data if it's kept pressed.
When you've found them - the hard task is then to fix the wires in place so you can make use of the access.
But be careful - don't short things out."

You do need, of course, to find out what serial port the Serial TTL convertor is using.
Click to expand...

Skip testing any TP that are labelled 'TP_somevoltage' such as TP_5V0
Maybe include the set of 4 connector pads next to the MicroSD slot, and maybe include the cluster of 4 pads (2 round, 2 square) middle right of the board.
 
finally my seller sent me instructions ad finally gained acces with teraterm and aparently its missing the bootloader , no where says bootloader or press key ,it keeps uncompressing linux files but starts over again
 
aparently its missing the bootloader
Click to expand...
The bootloader is fine - Linux is starting up.
If there was no bootloader, it would be truly dead, and it isn't.
There will likely be a firmware mismatch, or missing module or similar.
It's functional enough that recovery should be possible.

However:
But it's not possible to see anything useful with a couple of screenshots.
You need to capture the text as a logfile of a full startup, data not images.
You could send the logfile to the seller.
And you will need for comparison a 'known good example' to compare against to figure out the problem area.
By the way - I know nothing about how Foscam firmware works, don't consider me an expert on them.

*edit* Actually - those serial console instructions look pretty good - on the face of it, the recovery process is well documented.
To interrupt u-boot, it's usually Control-U as opposed to 'any key'
To interrupt Amboot it's usually 'keep Return pressed'
 
thanks a lot!! unfortunually the seller wont help any more or foscam, its like you are on your own, i would apreciate if some one could tellme how to figure this thing out!!! keeps looping with logs and there is no way to access bootloader! thanks again!!!!
 
The first thing you need to do is get access to u-boot.
With the camera powered on, start the terminal program on the PC.
If the camera is in a boot loop, as you suggest, just check that you are getting recognisable characters scrolling up the screen.
Press return or use Control-C a few times and see if it affects anything on the screen.
If it does - that's good, you can send characters.
If not - it may be that the camera is not responding to input, or it may be that your TX connection is not correct.
(If it's easy to change the connections, you could connect the RX and TX from the USB to TTL serial together and check that any characters you type just get echoed.)
So far so good - you have access to the serial console.

Now power off the camera.
Keep Control-U pressed on the keyboard and power up the camera.
You should be able to interrupt u-boot.
If that doesn't work, keep Return pressed as you power up.
Check for any text that says 'Press any key to interrupt u-boot' or similar.

After you have interrupted u-boot, you should be able to follow the instructions in the link you referenced earlier.
Good luck!
 
U-Boot 2010.06 (Jul 21 2014 - 00:36:52)


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
Auto-update from TFTP: trying update file 'recover_image.bin'
Hisilicon ETH net controler
MAC: 00-00-23-34-45-66
Up/Down PhY not link.-
Can't load update file, aborting auto-update
Hit any key to stop autoboot: 1  0
16384 KiB hi_sfc at 0:0 is now current device


## Starting application at 0x82000000 ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.0.8 (root@ubuntu) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+
uclibc_0.9.32.1+eabi+linuxpthread)) ) #29 Sun Jul 13 23:18:12 PDT 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 200000000.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 48768
Kernel command line: mem=192M console=ttyAMA0,115200 mtdparts=hi_sfc:1M(boot),4M
(kernel),11M(jffs2)
PID hash table entries: 1024 (order: 0, 4096 bytes)-
Dentry cache hash table entr
ies: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 192MB = 192MB total
Memory: 183892k/183892k available, 12716k reserved, 0K highmem
Virtual kernel memory layout:-
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xcc800000 - 0xfe000000 ( 792 MB)
lowmem : 0xc0000000 - 0xcc000000 ( 192 mB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0627000 (6268 kB)
.text : 0xc0627000 - 0xc0a80000 (4452 kB)
.data : 0xc0a80000 - 0xc0a9c4a0 ( 114 kB)
.bss : 0xc0a9c4c4 - 0xc0aafc4c ( 78 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 100MHz, resolution 10ns, wraps every 42949ms
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
ScSI subsystem initialized
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.
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 359
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
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
brd: module loaded
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: 0x16777216
chip num: 1
3 cmdlinepart partitions found on MTD device hi_sfc
Creating 3 MTD partitions on "hi_sfc":
0x000000000000-0x000000100000 : "boot"
0x000000100000-0x000000500000 : "kernel"
0x000000500000-0x000001000000 : "jffs2"
Fixed MDIO Bus: probed
himii: probed-
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: 1E:45:DF:94:F0:BC
PPP generic driver version 2.4.2
SlIP: version 0.8.4-NeT3.019-nEWTtY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
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
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
registered taskstats version 1
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)-
øFreeing init memory: 62
68K
mount: mounting tmpfs on /dev failed: Invalid argument


_ _ _ _ _ _ _ _ _ _ _ _
\ _ _ _ _ _ __
/ /__/ \ |_/-
/ __ / - _ __* / / / / / /
_ _ _ _/ / / \_/ \_ ______
___________\___\__________________


[RCS]: /etc/init.d/S00devs
mknod: /dev/console: File exists
mknod: /dev/ttyAMA0: File exists
mknod: /dev/ttyaMA1: File exists
mknod: /dev/ttyS000: file exists
usb 1-1: new high speed USB device number 2 using hiusb-ehci
[RCS]: /etc/init.d/S01udev
udevd (437): /proc/437/oom_adj is deprecated, please use /proc/437/oom_score_adj
instead.
[RCS]: /etc/init.d/S80network
IP: 192.168.233.233
BOOTP:
GATEWAY: 192.168.233.1
NEtMASK: 255.255.255.0-
HOsTNAmE: -
nETDeV: eth0-
AUtOCOnF:
[RCS]: /etc/init.d/S90init
==== Your model name is FI9828P V2 SENSOR=6 WIFI=2 LANGUAGE=2 MoDELvERSiON=11 Mo
DELnUM=50 ====*==== Your input model name is FI9828P V2 ====
mem=190160
Hisilicon Media Memory Zone Manager
hi3518_base: module license 'Proprietary' taints kernel.*Disabling lock debugging due to kernel taint
Hisilicon UMAP device driver interface: v3.00
pa:8c000000, va:cc9c0000
load sys.ko for Hi3518...OK!
load viu.ko for Hi3518...oK!
ISP Mod init!
load vpss.ko ....OK!
load venc.ko for Hi3518...OK!
load group.ko for Hi3518...OK!
load chnl.ko for Hi3518...OK!
load h264e.ko for Hi3518...OK!
load jpege.ko for Hi3518...OK!
load rc.ko for Hi3518...OK!
load region.ko ....OK!
load vda.ko ....OK!
hi_i2c init is ok!
sha204 [sha204_init ,291]: sha204 driver init successful!-
==== Your input Sensor
type is 6 ====
*** Board tools : ver0.0.1_20120501 ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20030030: 0x00000000 --> 0x00000005 *[ENd]
acodec inited!
insert audio
==== Your input Wifi type is 2 ====
rtusb init rtusbSTA --->
*
=== pAd = cce6a000, size = 860440 ===-


<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x8
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x4-
RTmP_CoM_IoctlHandle():pAd->BulkOu
tEpAddr=0x5*RTMp_COm_IoctlHandle():pAd->BulkOutEpAddr=0x6
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x7
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x9
NvM is EFuSE*Endpoint(8) is for In-band Command*Endpoint(4) is for WMM0 AC0
Endpoint(5) is for WMM0 AC1
Endpoint(6) is for WMM0 AC2
Endpoint(7) is for WMM0 AC3
Endpoint(9) is for WMM1 AC0
Endpoint(84) is for Data-In
Endpoint(85) is for Command Rsp
usbcore: registered new interface driver rtusbSTA
ptz_init start ptz_state[3],HorPos[0],VerPos[0]
setup ptz gpio success
setup zoom gpio success
ptz_init end ptz_state[3],HorPos[0],VerPos[0],flag[0]
Hisilicon Watchdog Timer: 0.01 initialized. default_margin=5 sec (nowayout= 0, n
odeamon= 0)
mkdir: can't create directory '/mnt/mtd/app/modules': File exists
mkdir: can't create directory '/mnt/mtd/app/modules/extdrv': File exists
tar: can't open '/mnt/mtd/app/patch/patch.tar.xz': No such file or directory
set rtc time to system time
Auto login as root ...
(none) login: killall: devMng: no process killed
killall: codec: no process killed-
killall: UDTMediaServer: no process killed
killall: webService: no process killed
killall: storage: no process killed
killall: FirmwareUpgrade: no process killed
killall: RtspServer: no process killed
killall: NVTService: no process killed




U-Boot 2010.06 (Jul 21 2014 - 00:36:52)


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
Auto-update from TFTP: trying update file 'recover_image.bin'
Hisilicon ETH net controler
MaC: 00-00-23-34-45-66
Up/Down PHY not link.
Can't load update file, aborting auto-update
Hit any key to stop autoboot: 1 ( 0
16384 KiB hi_sfc at 0:0 is now current device-


## Starting application at 0x82000000 ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.0.8 (root@ubuntu) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+
uclibc_0.9.32.1+eabi+linuxpthread)) ) #29 Sun Jul 13 23:18:12 PDT 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 200000000.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 48768
Kernel command line: mem=192M console=ttyAMA0,115200 mtdparts=hi_sfc:1M(boot),4M
(kernel),11M(jffs2)
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: 192MB = 192MB total
Memory: 183892k/183892k available, 12716k reserved, 0K highmem*Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xcc800000 - 0xfe000000 ( 792 MB)
lowmem : 0xc0000000 - 0xcc000000 ( 192 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0627000 (6268 kB)
.text : 0xc0627000 - 0xc0a80000 (4452 kB)
.data : 0xc0a80000 - 0xc0a9c4a0 ( 114 kB)
.bss : 0xc0a9c4c4 - 0xc0aafc4c ( 78 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 100MHz, resolution 10ns, wraps every 42949ms
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-
SCSI subsystem initialized
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.
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JfFS2 version 2.2. (NaND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 359
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
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
brd: module loaded
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: 0x16777216
chip num: 1
3 cmdlinepart partitions found on MTD device hi_sfc*Creating 3 mTD partitions on "hi_sfc":
0x000000000000-0x000000100000 : "boot"
0x000000100000-0x000000500000 : "kernel"
0x000000500000-0x000001000000 : "jffs2"
Fixed MDIO Bus: probed
himii: probed
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: A2:58:32:02:70:98
PpP generic driver version 2.4.2
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
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 registe
red, 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
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
registered taskstats version 1
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
øFreeing init memory: 6268K
mount: mounting tmpfs on /dev failed: Invalid argument


_ _ _ _ _ _ _ _ _ _ _ _
\ _ _ _ _ _ ___
/ /__/ \ |_/
/ __ / - _ ___
/ / / / / /
_ _ _ _/ / / \_/ \_ ______
___________\___\__________________


[RCS]: /etc/init.d/S00devs
mknod: /dev/console: File exists
mknod: /dev/ttyaMA0: File exists
mknod: /dev/ttyAMA1: File exists
mknod: /dev/ttyS000: File exists
usb 1-1: new high speed USB device number 2 using hiusb-ehci
[rCS]: /etc/init.d/S01udev
udevd (437): /proc/437/oom_adj is deprecated, please use /proc/437/oom_score_adj
instead.
[RCS]: /etc/init.d/S80network
IP: 192.168.233.233-
BOOtP: -
GaTEWaY: 192.168.233.1
NETMASK: 255.255.255.0
HOSTNAME:
NETDEV: eth0
AUTOCONF:
[RCS]: /etc/init.d/S90init
==== Your model name is FI9828P V2 SEnSOR=6 WiFI=2 LAnGUAgE=2 MODELVERSION=11 MO
DELNUM=50 ====
==== Your input model name is FI9828P V2 ====
mem=190160
Hisilicon Media Memory Zone Manager
hi3518_base: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
Hisilicon UMAP device driver interface: v3.00
pa:8c000000, va:cc9c0000
load sys.ko for Hi3518...OK!
load viu.ko for Hi3518...OK!
ISP Mod init!
load vpss.ko ....OK!
load venc.ko for Hi3518...OK!-
load group.ko for Hi3518...OK!
load chnl.ko for Hi3518...OK!
load h264e.ko for Hi3518...OK!
load jpege.ko for Hi3518...OK!
load rc.ko for Hi3518...OK!
load region.ko ....OK!
load vda.ko ....OK!
hi_i2c init is ok!
sha204 [sha204_init ,291]: sha204 driver init successful!
==== Your input Sensor type is 6 ====
*** Board tools : ver0.0.1_20120501 ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20030030: 0x00000000 --> 0x00000005
[END]
acodec inited!
insert audio
==== Your input Wifi type is 2 ====
rtusb init rtusbStA --->




=== pAd = cce6a000, size = 860440 ===


<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x8*RTMp_COm_IoctlHandle():pAd->BulkOutEpAddr=0x4
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x5
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x6
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x7
RTMP_COM_IoctlHandle():pAd->BulkOutEpAddr=0x9
NVM is EFUSE
Endpoint(8) is for In-band Command
Endpoint(4) is for WMM0 AC0
Endpoint(5) is for WMM0 AC1
Endpoint(6) is for WMM0 AC2
Endpoint(7) is for WMM0 AC3
Endpoint(9) is for WMM1 AC0
Endpoint(84) is for Data-In*Endpoint(85) is for Command Rsp
usbcore: registered new interface driver rtusbSTA
ptz_init start ptz_state[3],HorPos[0],VerPos[0]
setup ptz gpio success
setup zoom gpio success
ptz_init end ptz_state[3],HorPos[0],VerPos[0],flag[0]
Hisilicon Watchdog Timer: 0.01 initialized. default_margin=5 sec (nowayout= 0, n
odeamon= 0)
mkdir: can't create directory '/mnt/mtd/app/modules': File exists
mkdir: can't create directory '/mnt/mtd/app/modules/extdrv': File exists
tar: can't open '/mnt/mtd/app/patch/patch.tar.xz': No such file or directory
set rtc time to system time
Auto login as root ...
(none) login: killall: devMng: no process killed
killall: codec: no process killed
killall: UDTMediaServer: no process killed
killall: webService: no process killed
killall: storage: no process killed
killall: FirmwareUpgrade: no process killed
killall: RtspServer: no process killed
killall: NVTService: no process killed
*
U-Boot 2010.06 (Jul 21 2014 - 00:36:52)
-
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
Auto-update from TFTP: trying update file 'recover_image.bin'
Hisilicon ETH net controler
MAC: 00-00-23-34-45-66
Up/Down PHY not link.
Can't load update file, aborting auto-update
Hit any key to stop autoboot: 1  0
16384 KiB hi_sfc at 0:0 is now current device


## Starting application at 0x82000000 ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.0.8 (root@ubuntu) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+
uclibc_0.9.32.1+eabi+linuxpthread)) ) #29 Sun Jul 13 23:18:12 PDT 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 200000000.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 48768
Kernel command line: mem=192M console=ttyAMA0,115200 mtdparts=hisfc:1M(boot),4M(
kernel),11M(jffs2)
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: 192MB = 19
2MB total
Memory: 183892k/183892k available, 12716k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
dMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xcc800000 - 0xfe000000 ( 792 MB)
lowmem : 0xc0000000 - 0xcc000000 ( 192 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0627000 (6268 kB)
.text : 0xc0627000 - 0xc0a80000 (4452 kB)
.data : 0xc0a80000 - 0xc0a9c4a0 ( 114 kB)
.bss : 0xc0a9c4c4 - 0xc0aafc4c ( 78 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 100MHz, resolution 10ns, wraps every 42949ms
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
SCSI subsystem initialized
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.
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse i

- - - Updated - - -

cant stop it,keeps looping
 
It's easier on the eye for all of us if you use the code (#) tags in Advanced to paste it into ... you could edit the post and do that.
All the logfile shows is that the camera boots pretty well then resets.

You do need to get into u-boot so that the firmware can be flashed with the correct version.
The log suggests it's any key, such as space bar etc:
Hit any key to stop autoboot: 1 0
Click to expand...
But your TTL serial convertor has to be sending data from it's TX output to the camera RX input, or nothing will happen.
Did you use my suggestions in post #10
 
it generates text but leeps scrolling and wont stop, took the cable out and did not generate imput back in yes but wont stop
 
took the cable out and did not generate imput back in yes but wont stop
Click to expand...
I'm sorry, but I don't know what you mean by this.

it generates text but leeps scrolling and wont stop
Click to expand...
Do you mean by this that when you type something at the keyboard, such as keeping a letter pressed so the keyboard auto-repeats, you can see the letter in the scrolling text?
If yes, that is good.

Now power off the camera.
Keep return pressed and power on the camera.
Check for the text that says 'Press any key to interrupt u-boot' or similar.
It will pause for a second or 2 at this point.
Quickly press the spacebar or Control-U
You should be able to stop u-boot if your serial TTL convertor is sending data OK.
 
wont stop when it begins , if i press any key on screen i can see the input, but it just skips and keeps trying to boot, then after failed firmware update, it begins again in a loop non stop, when i press a key i can see on the screen the caracters but it wont stop the boot
 
if i press any key on screen i can see the input, but it just skips and keeps trying to boot
Click to expand...
Well, that does confirm that you are transmitting characters to the device.
Strange that you can't interrupt it in the usual way - unless Foscam have changed the way the bootloader usually works.

A quick Google search suggests this may vary between different Foscam cameras.
Your log did show 'press any key'
Here is one result:
press the ESC button located in the new window prior to the 3 second timeout to remain in the bootloader.
Click to expand...
I've usually used Return for Amboot, and Control-U for u-boot

Have you tried experimenting with different characters?
 
it reads,,,, hit any key to stop auto boot 0 /no countdown, its set to 0 and maybe thats why it wont interrupt
 
Hmmm... when I saw the zero I assumed it was because the countdown had taken place.
I'm afraid I don't know how you get out of that, if the countdown has been set to zero and therefore disabled.
Bummer.
 
You must log in or register to reply here.
Top Bottom