Another Foscam FI8908W Clone Firmware Exploration

I need to hook it up and take a look, its disconnected from the serial cable now.

Thanks

Seems to be only when a network lead connected it has the spinning freeze issue...

It boots up OK when you have network lead out.

As soon as you plug it in this happens.

MAC Line-on...

Wait for auto-negotiation complete...OK
100MB - FULL
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0
down wire eth
MAC Line-off...
sh: allocation of 118 pages failed!
Allocation of length 482353 from process 34 failed
Buffer memory:        0kB
Cache memory:     1132kB
Active: 0, inactive: 283, free: 99
Free pages:      99 (396kB), %5 frag, %0 slack
Free blks:        5 min=1 max=92 avg=19
Used blks:        6 min=1 max=1474 avg=324
Unable to allocate RAM for process text/data, errno 12

Then it reboots and this happens.  With network lead in it does the freeze at each reboot

W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Au
g 19 2009
Memory Size is 0x800000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:

MAC Address         : 00:60:6E:80:3F:10
IP Address          : 0.0.0.0
DHCP Client         : Enabled
CACHE               : Enabled
BL buffer base      : 0x00300000
BL buffer size      : 0x00100000
Baud Rate           : -1
USB Interface       : Disabled
Serial Number       : 0xFFFFFFFF


For help on the available commands type 'h'

Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #2020    3   27 11:05:03 CST 2013
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0 rw
Calibrating delay loop... 39.83 BogoMIPS
Memory: 8MB = 8MB total
Memory: 6416KB available (1399K code, 192K data, 40K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
PTZ Driver has been installed successfully.
Winbond W90N745 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80100 (irq = 10) is a W90N7451
I2C Bus Driver has been installed successfully.
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 7F0E0000-7F1E17FF [VIRTUAL 7F0E0000-7F1E17FF] (RO)
W19B320SB Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
i2c write io
i2s audio write failed
i2s audio probe 0
Winbond Audio Driver v1.0 Initialization successfully.
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 15
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
rtusb init rt2870 --->
usb.c: registered new driver rt2870
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: -t
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh

Sash command shell by maverick (version 1.1.1)
no support
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :807cee04-7e8740
hub.c: new USB device 1, assigned address 2
detect_sensor: mi360
dvm cmos successfully initialized
dvm camera registered as video0
new USB device :807b3204-7e8740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x160a/0x3184) is not claimed by any active driver.
params length is 5428
sw version is 11.22.2.51
aw version is 2.4.8.14

Wait for auto-negotiation complete...OK
100MB - FULL
eth1: unknown interface: Unknown error 19
eth1: unknown interface: Unknown error 19
video0 opened
1
1
1
1
1
1
set resolution 5
set brightness 80
set contrast 4
set sharpness 3
set mode 0
unknown command
do_zoom_stop: read error 5
do_focus_stop: read error 5
__pthread_initial_thread_bos:470000
manage pid:18
set speed 8000 0
set channels 1 0
set fmt 432 0
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
2
2
2
2
2
2
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0

This is a clean boot with no network lead connected.

The spinning starts after the auto negotiation and ethernet errors.  The scanning accross all axis then completes.



W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x800000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:

MAC Address         : 00:60:6E:80:3F:10
IP Address          : 0.0.0.0
DHCP Client         : Enabled
CACHE               : Enabled
BL buffer base      : 0x00300000
BL buffer size      : 0x00100000
Baud Rate           : -1
USB Interface       : Disabled
Serial Number       : 0xFFFFFFFF


For help on the available commands type 'h'

Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...



W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x800000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:

MAC Address         : 00:60:6E:80:3F:10
IP Address          : 0.0.0.0
DHCP Client         : Enabled
CACHE               : Enabled
BL buffer base      : 0x00300000
BL buffer size      : 0x00100000
Baud Rate           : -1
USB Interface       : Disabled
Serial Number       : 0xFFFFFFFF


For help on the available commands type 'h'

Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #2020    3   27 11:05:03 CST 2013
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0 rw
Calibrating delay loop... 39.83 BogoMIPS
Memory: 8MB = 8MB total
Memory: 6416KB available (1399K code, 192K data, 40K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
PTZ Driver has been installed successfully.
Winbond W90N745 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80100 (irq = 10) is a W90N7451
I2C Bus Driver has been installed successfully.
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 7F0E0000-7F1E17FF [VIRTUAL 7F0E0000-7F1E17FF] (RO)
W19B320SB Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
i2c write io
i2s audio write failed
i2s audio probe 0
Winbond Audio Driver v1.0 Initialization successfully.
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 15
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
rtusb init rt2870 --->
usb.c: registered new driver rt2870
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: -t
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh

Sash command shell by maverick (version 1.1.1)
no support
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :807cee04-7e8740
hub.c: new USB device 1, assigned address 2
detect_sensor: mi360
dvm cmos successfully initialized
dvm camera registered as video0
new USB device :807b3204-7e8740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x160a/0x3184) is not claimed by any active driver.
params length is 5428
sw version is 11.22.2.51
aw version is 2.4.8.14

Wait for auto-negotiation complete...ResetPhyChip Failed
eth1: unknown interface: Unknown error 19
eth1: unknown interface: Unknown error 19



W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x800000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:

MAC Address         : 00:60:6E:80:3F:10
IP Address          : 0.0.0.0
DHCP Client         : Enabled
CACHE               : Enabled
BL buffer base      : 0x00300000
BL buffer size      : 0x00100000
Baud Rate           : -1
USB Interface       : Disabled
Serial Number       : 0xFFFFFFFF


For help on the available commands type 'h'

Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #2020    3   27 11:05:03 CST 2013
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0 rw
Calibrating delay loop... 39.83 BogoMIPS
Memory: 8MB = 8MB total
Memory: 6416KB available (1399K code, 192K data, 40K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
PTZ Driver has been installed successfully.
Winbond W90N745 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80100 (irq = 10) is a W90N7451
I2C Bus Driver has been installed successfully.
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 7F0E0000-7F1E17FF [VIRTUAL 7F0E0000-7F1E17FF] (RO)
W19B320SB Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
i2c write io
i2s audio write failed
i2s audio probe 0
Winbond Audio Driver v1.0 Initialization successfully.
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 15
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
rtusb init rt2870 --->
usb.c: registered new driver rt2870
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: -t
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh

Sash command shell by maverick (version 1.1.1)
no support
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :807cee04-7e8740
hub.c: new USB device 1, assigned address 2
detect_sensor: mi360
dvm cmos successfully initialized
dvm camera registered as video0
new USB device :807b3204-7e8740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x160a/0x3184) is not claimed by any active driver.
params length is 5428
sw version is 11.22.2.51
aw version is 2.4.8.14

Wait for auto-negotiation complete...ResetPhyChip Failed
eth1: unknown interface: Unknown error 19
eth1: unknown interface: Unknown error 19
video0 opened
1
1
1
1
1
1
set resolution 5
set brightness 80
set contrast 4
set sharpness 3
set mode 0
unknown command
do_zoom_stop: read error 5
do_focus_stop: read error 5
__pthread_initial_thread_bos:470000
manage pid:18
set speed 8000 0
set channels 1 0
set fmt 432 0
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
bonjour callback: service registered
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
armed !!!!!!
start alarm video 2480
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
motion detect alarm !!!!!!
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
_i2c_write: write i2c error
_i2c_write: write i2c error
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip
ntpc.c: can not resolve ntpserver(time.nist.gov)'s ip

Do you have a spare Ethernet cable you can try to see if that current cable is bad?

Or use the current Ethernet Cable with another device to see if that device can connect to the Router/AP using the same cable?

Don

Yeh tried 2 different cables now, same deal

Yeh tried 2 different cables now, same deal

Was the Ethernet connection working with the x.37 firmware version?

I am wondering if your "Clone" is using a different Ethernet adapter interface that works with x.37 but not this .22 version. This would mean you might need to choose one firmware version of the other. One with working wireless and one with working Ethernet. Assuming that you configured your wireless prior to changing firmware versions.

I will PM you the x.37 recovery instructions and see if it boots with it.

Don

Hi all.

First of all sorry my bad English.

So, i have a Neo CoolCam Nip-02 Oam (http://en.szneo.com/en/products/show.php?id=142).
I want to flash rom and firmware via uart. I open Hyperterminal and i can connect the camera, press ESC and i'm in the boot loader. I type del 6 and del 7 and everything works fine. In the next step i send and flashing rom.img and linux.zip :

fx 7 linux.zip 0x7f020000 0x8000 -acxz
fx 6 rom.img 0x7f0e0000 0x7f0e0000 -a

I send the boot command and the camera reboot. This step the camera unzip the linux.zip and I always get this message "open video device error ... myreboot". I try a lot of rom and a lot of firmware. Please help me, anybody can link me a good rom and a good firmware ? Thanks

Hi,

Ive upgraded as per the files you sent me and im now at 11.37.2.51 and 2.4.8.14

Camera is stable now i dont get no freeze when booting with network lead in but the wifi is still not working....

When I press scan nothing is found and when i configure manually it does not connect.

here is the output from boot

W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x800000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:

MAC Address         : 00:60:6E:80:3F:10
IP Address          : 0.0.0.0
DHCP Client         : Enabled
CACHE               : Enabled
BL buffer base      : 0x00300000
BL buffer size      : 0x00100000
Baud Rate           : -1
USB Interface       : Disabled
Serial Number       : 0xFFFFFFFF


For help on the available commands type 'h'

Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #2020    3   27 11:05:03 CST 2013
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0 rw
Calibrating delay loop... 39.83 BogoMIPS
Memory: 8MB = 8MB total
Memory: 6416KB available (1399K code, 192K data, 40K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
PTZ Driver has been installed successfully.
Winbond W90N745 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options enabled
ttyS00 at 0xfff80100 (irq = 10) is a W90N7451
I2C Bus Driver has been installed successfully.
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 7F0E0000-7F1E17FF [VIRTUAL 7F0E0000-7F1E17FF] (RO)
W19B320SB Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
i2c write io
i2s audio write failed
i2s audio probe 0
Winbond Audio Driver v1.0 Initialization successfully.
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 15
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
rtusb init rt2870 --->
usb.c: registered new driver rt2870
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: -t
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh

Sash command shell by maverick (version 1.1.1)
no support
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :807cee04-7e8740
hub.c: new USB device 1, assigned address 2
detect_sensor: mi360
dvm cmos successfully initialized
dvm camera registered as video0
new USB device :807b3204-7e8740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x160a/0x3184) is not claimed by any active driver.
params length is 5428
sw version is 11.37.2.51
aw version is 2.4.8.14

Wait for auto-negotiation complete...OK
100MB - FULL
eth1: unknown interface: Unknown error 19
eth1: unknown interface: Unknown error 19
video0 opened
1
1
1
1
1
1
set resolution 5
set brightness 80
set contrast 4
set sharpness 3
set mode 0
unknown command
_i2c_write: write i2c error
_i2c_write: write i2c error
do_zoom_stop: read error 5
do_focus_stop: read error 5
__pthread_initial_thread_bos:470000
manage pid:18
set speed 8000 0
set channels 1 0
set fmt 432 0
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
2
2
2
2
2
2
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0
ntpc adjust ok
armed !!!!!!
start alarm video 2359
motion detect alarm !!!!!!
_i2c_write: write i2c error
_i2c_write: write i2c error
do_file: can not find file favicon.ico
start monitor video 9869
stop monitor video
motion detect alarm !!!!!!
process_HTTP_REQ: can not recv total http head
process_HTTP_REQ: can not recv total http head

Based on your results. It appears.

a. The WiFi daughter board in your IP Camera used for wireless communications. Is not the same brand/model, which is used in Foscam MJPEG based IP Cameras.

b. There is some hardware issue with the WiFi Daughter board in your camera.

Can you capture a serial boot with your IP Camera not having a Ethernet hardwired connection and post that text here. It might help to determine if any WiFi initialization problems are taking place or give some insight into what your issue is.

Don

Hi Don,
Thanks for such a thorough post.  I think I found the clone cam but figured I'd pass it by you and others to make sure:
http://www.ebay.com/itm/Sricam-Wireless-WiFi-IP-Camera-PT-Record-Audio-Smartphone-Android-iPhone-View-/171214170640?pt=LH_DefaultDomain_0&hash=item27dd28ea10

For about half price (40.00), that seems like a great deal.

I would love to start tweaking on the foscam f/w since I think they missed a few useful APIs.  But, I'll continue that on the foscam forum.
In the meantime, I'd like to try some of these cams just for fun.  So far, I'm having a tough time finding pics from all angles.

Actually I think this is more like it since it has the 4 alarm pin outputs.
http://www.ebay.com/itm/New-Wireless-WiFi-IP-Security-Camera-Monitor-IR-LED-Webcam-Night-Vision-Network-/111720121533?pt=LH_DefaultDomain_0&hash=item1a0309c4bd

Hi Don,
Thanks for such a thorough post.  I think I found the clone cam but figured I'd pass it by you and others to make sure:
http://www.ebay.com/itm/Sricam-Wireless-WiFi-IP-Camera-PT-Record-Audio-Smartphone-Android-iPhone-View-/171214170640?pt=LH_DefaultDomain_0&hash=item27dd28ea10

For about half price (40.00), that seems like a great deal.

I would love to start tweaking on the foscam f/w since I think they missed a few useful APIs.  But, I'll continue that on the foscam forum.
In the meantime, I'd like to try some of these cams just for fun.  So far, I'm having a tough time finding pics from all angles.

Hello. You are very welcome.

It's tough to look at the outside of a Network IP Camera and try to determine if it's compatible with the firmware shown here.

The only true way is to open the camera up and see if it looks like you can create a serial connection with it and see if it has some of the same values at the same hex locations shown here.

If it does not. Please don't try to update the firmware using these methods. Because you will most likely eternally brick your Network IP Camera by potentially stepping on important factory default memory locations like the Network IP Cameras Serial Number, MAC Address and/or DDNS. Which can cause the Network IP Camera to never be able to perform a successful startup process ("Boot") afterwards.

As far as doing the same for Foscam Network IP Cameras. Currently I don't have the liberty of providing that information because I am a moderator in the Foscam.us forum and am under and have NDA's ("Non Disclosure Agreements") with Foscam.

That all said. There are other ways to create your own custom front ends to many different Network IP Cameras. Which don't require the opening of a Network IP Camera and don't require the risk of bricking a Network IP Camera, by needing to install custom firmware.

Here are 40 different live Network IP Camera demonstrations using custom Interfaces without requiring custom firmware. You can try any and all of the current 40 examples shown below.

Please click on the image or link below to see the entire list of the 40 different live Network IP Camera demonstrations using my current Interfaces, to choose from:



http://107.170.59.150

Note: The above list has a language translation list box to automatically translate the list from English to over 90 different languages.

Over the years. I have come to determine that having the obligation to always update custom firmware to match a Network IP Cameras manufacturers latest firmware releases, becomes very burdensome vs. leaving the firmware updates to the manufactures and instead trying to create custom Interfaces to those Network IP Cameras that work with any Internet browser capable devices which are running on any Operating Systems and using any browsers. From Computers to Tablets to Phones and TV's. Without requiring special custom firmware to use those Interfaces. 

Don

Hi Don,
I just messaged you on skype (as V Schwartz)....
I'm going through the NDA process w/ foscam now.  I also asked a really specific functionality question there which would be the only reason I'd start hacking on f/w.  And, I agree it's unstable and a pain to keep it up to date.