News:

Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at http://www.computersolutions.cn/blog

Author Topic: neasy ipcam reboot all the time  (Read 6378 times)

July 10, 2012, 12:00:03 pm
i have an easyn ipcam fs-613a-m136
i coonect my cam with jtag and i get this messege



 W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on May 11 2010
Memory Size is 0x1000000 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:A8:F8:00:94:52
        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) #1162 Áù 12ÔÂ 1
2 17:13:00 CST 2009
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: 6248KB available (1470K code, 286K 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 en
abled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options e
nabled
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-7F16FBFF [VIRTUAL 7F0E0000-7F16FBFF] (RO)
S29GL032N Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
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

 _____     ____    _    ____
|__  /   _|  _ \  / \  / ___|
  / / | | | | | |/ _ \ \___ \
 / /| |_| | |_| / ___ \ ___) |
     |___/|____/_/   \_\____/
ZD1211B - version 2.24.0.0
usb.c: registered new driver zd1211b
main_usb.c: VIA Networking Wireless LAN USB Driver 1.20.04
usb.c: registered new driver vntwusb
usb.c: registered new driver rt73
dvm usb cam driver 0.0.0.0 by Maverick Gao in 2006-8-12
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: /bin/init
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
no support

Sash command shell (version 1.1.1)
/> aw version is 4.11.2.15
aw not exist !
aw version is 0.0.0.0

Wait for auto-negotiation complete...ÿÿResetPhyChip Failed
open video device error
myreboot



the problem that i cant go to debug mode
any one tell me what to do
« Last Edit: July 10, 2012, 12:04:57 pm by aboisam »

  • No avatar
  • *****
July 11, 2012, 07:03:15 am
1) You have connected a serial connection, not JTAG.

2) Your device is having issues talking to the Camera CCD/CMOS ->


open video device error


That means it couldn't talk to the camera inside the top part.

I do see that the driver did load though  -

dvm usb cam driver 0.0.0.0 by Maverick Gao in 2006-8-12
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

Suggest power off for a few minutes, and give it a retry.
Have you done anything like install other firmware on there?


Assuming you haven't, and it still doesn't want to play, then possibly the CCD is broken, or you've perhaps plugged the video into the wrong port.


Looking at the board, there are 3 port connectors on the left side, 2 ports on the right.

The USB connection for the Camera (with the multicolor cable) goes into the first of the 3 connectors. (this is the one closest to the usb wifi daughterboard).
The connection for the Audio, motors goes into the middle connector.
The GPIO sensor is the 3 pin one closest to the network.


If you have taken the camera apart (and it sounds like you have), then ensure that those ones haven't been plugged into the wrong connectors.


July 11, 2012, 08:08:10 am
thanks for replay

i have upgrade my firmeware to another and i try to get it back to the old one

so now what sould i do

  • *****
July 11, 2012, 10:08:18 am
Did you read the title of the FIRMWARE section? "Note that firmware is closely tied to what hardware is in your camera. Suggest that you backup your current firmware prior to testing what firmware is compatible with your specific camera hardware!"

If you did not backup the existing firmware prior to installing new firmware, then your camera may be unrecoverable toast.

While there is no guarantee that it is fully compatible with your camera, there is a copy of some original firmware for your model in the FILES section. You now have nothing to lose by installing it.

July 11, 2012, 02:49:13 pm
the problem now is not to find out the right firmware but how to install it in the cam while the cam reboot all the time
i try to press esc to come into bootloader but it will not
i need the right way please and thanks
« Last Edit: July 11, 2012, 02:54:05 pm by aboisam »

  • *****
July 11, 2012, 02:57:39 pm
Are you saying that your camera fails to enter debug mode when you enter ESC during the early part of the boot process?

July 11, 2012, 03:09:57 pm
yes what did i do wrong

  • *****
July 11, 2012, 03:26:44 pm
If you cannot enter debug mode by entering ESC during the early part of the boot process, then I know of no way to recover via the serial port. At this point your only choice may be in-circuit programming hardware, which is outside the scope of this website.

What did you do? Somehow you have no sh. Maybe you loaded the fs to the wrong location - who knows.

  • No avatar
  • *****
July 11, 2012, 04:24:19 pm
sometimes when ESC is not accepted it shows that either the connection is faulty or the terminal program is not supporting operation without handshake lines (or relevant option wasn't found).

first try to just connect tx and rx pin of the cable to the PC (without connecting to the cam), then every pressed key should appear on the screen.

If this isn't ok, try another terminal software (for linux I suggest minicom, for windows PuTTY).
If it still isn't ok, check the cable.

If the test above is ok, recheck the pinout of the connector to the cam.

btw, you have to be really quick to press ESC ..

  • *****
July 11, 2012, 06:41:49 pm
Schufti - good catch - he has provided no information to indicate the the Tx of his serial port is functional.