News:

Re-organized the forum to more cleanly delineate the development section, as the end user support side appears to have taken a life of its own!

Author Topic: "open video device error" does it mean my cam is dead??  (Read 12321 times)

August 17, 2011, 03:25:48 pm
Hi All!
My cam is a FOSCAM clone from DX - SKU 26358
Have not used it for about 3-4 months, plugged it yesterday and found it does not work. It just stood all that time on wardrobe powered off. Connected over RS232 and saw that it reboots after "open video device error". But from time to time (dozens power off/on) it just boots and work ok!  Search google and found nothing about this problem. Boot log is attached. HELP please!
Thanks, Vlad.

W90N745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Jun 19 2006
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:EE:11:22:33:44
        IP Address          : 192.168.1.157
        DHCP Client         : Enabled
        CACHE               : Enabled
        BL buffer base      : 0x00300000
        BL buffer size      : 0x00100000
        Baud Rate           : 115200
        USB Interface       : Enabled
        Serial Number       : 0x00000000


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) #1221 6~ 12TB 15 09:31:56 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, 287K 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-7F1703FF [VIRTUAL 7F0E0000-7F1703FF] (RO)
W19B320SB 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

Sash command shell (version 1.1.1)
/> no support
hub.c: connect-debounce failed, port 1 disabled
new USB device :807b3004-7e86c0
hub.c: new USB device 1, assigned address 2
usb.c: USB device not accepting new address=2 (error=-110)
new USB device :807b3004-7e86c0
hub.c: new USB device 1, assigned address 3
usb.c: USB device not accepting new address=3 (error=-110)
new USB device :807b3004-7e86c0
hub.c: new USB device 2, assigned address 4
VIA Networking Wireless LAN USB Driver Ver. 1.20.04
Copyright (c) 2004 VIA Networking Technologies, Inc.
vntwusb_init--->eth1 initial ok!
insmod VNTWUSB SUCESSFUL...
factory params zone not inited !
camera params zone not inited !
aw version is 11.14.2.17
factory video params zone not inited !
video params zone not inited !
dyndns status zone not inited !
aw not exist !
aw version is 0.0.0.0

Wait for auto-negotiation complete...OK
100MB - FULL
open video device error
myreboot

 

  • No avatar
  • *****
August 17, 2011, 03:54:13 pm
Hi,
it looks like your device has either alzheimers desease or someone has badly tampered with it...

it obviously lost all settings and the webui but not even one hickup in the kernel and romfs???
very unlikely....

August 17, 2011, 04:28:05 pm
Sorry, forged to say, after I've discovered that my cam is in "open video device error" reboot loop I've tried to flash it with FI8908W recovery (fx 7 linux_4Mx16Bit_new.zip 0x7f020000 0x8000 -acxz, fx 6 romfs_cmos_11_14_2_17.img 0x7f0e0000 0x7f0e0000 -a) in hope it will be detected by IP Cam Tools and I can flash full firmware. Sadly but it did not help.. still "open video device error" and reboot.. =(

  • No avatar
  • *****
August 19, 2011, 01:31:16 am
Hi,

maybe more forensic methods can help to recover your original fw.

can you remember how your webui looked like? (see here for examples)
can you remember what versions the fw/webui had?
can you give details about the factory ddns?

all these details can help to distinguish your "brand"

another step would be to flash the openip-cam fw. It has drivers for lots of video devices and chances are high it would detect your chip and see if it is broken or just a rare species.

December 11, 2012, 01:50:11 pm
Hi, I have a PT Cam from Shenzhen CiBoer Technology Co., Ltd., like CB-541W (http://www.ciboer.com/products.asp?smallclassid=1&bigclassid=1), but without wifi. It is now on a booting loop "open video device error", I tried a lot of firmware but no luck, maybe you know what is the correct one? thanks in advance

  • ***
December 11, 2012, 06:11:28 pm
Hi, I have a PT Cam from Shenzhen CiBoer Technology Co., Ltd., like CB-541W (http://www.ciboer.com/products.asp?smallclassid=1&bigclassid=1), but without wifi. It is now on a booting loop "open video device error", I tried a lot of firmware but no luck, maybe you know what is the correct one? thanks in advance

When you say "like CB-541W". Not sure what that means? What makes you think that? Hopefully, more than just the picture and/or only the specifications for the camera, at that web site?

Do you have the original System and Web UI firmware files besides just the firmware presently in the camera?

Have you tried to contact the person you purchased the camera from and asked for the firmware?

Have you tried to contact Shenzhen CiBoer Technology Co., Ltd. to ask them for the firmware?

While many times the generic System firmware can work, in some ways, with these types of cameras. Some use different camera modules ("Which also maybe causing your current error with your camera and the current System firmware"), and the picture and video quality, could be impacted, if you use other System firmware. I have had this happen with cheaply made camera clones when trying other system firmware in them.

Usually, it's not as bad if you are simply trying other Web UI firmware or if you have the original System and Web UI firmware, to fall back on, if needed.

By using the wrong System firmware, or shall I say a very different System firmware than the camera expects to see, it's much more likely to brick your camera. Of course there are some recovery methods, if you are willing to take that chance, that may or may not work without the need to open up the camera, using and adding a USB interface.

If you decide to NOT try the other methods suggested above first or can't get anywhere trying.

Here is the most generic version of both System and Web UI firmware that I am aware of for the camera you made reference to above, which has the features of a FI8908W Foscam camera:

http://www.ciboer.com/products-info.asp?pid=23

If you use these files, please understand, that you use them at your own risk. This firmware contains logic for WiFi ("Specifically 802.11b/g only"), which you state your camera does not support ("Yet the camera you reference as "like", does support WiFi"). I have no idea of how or what will happen when using the firmware below, with a camera that does not support WiFi. The files contained in the attached .zip are:

System Firmware: lr_cmos_0_37_2_47.bin
Web UI Firmware: 0.2.9.12.bin

Don
« Last Edit: December 11, 2012, 11:35:02 pm by TheUberOverLord »

December 11, 2012, 11:48:57 pm
Hi, I have a PT Cam from Shenzhen CiBoer Technology Co., Ltd., like CB-541W (http://www.ciboer.com/products.asp?smallclassid=1&bigclassid=1), but without wifi. It is now on a booting loop "open video device error", I tried a lot of firmware but no luck, maybe you know what is the correct one? thanks in advance

When you say "like CB-541W". Not sure what that means? What makes you think that? Hopefully, more than just the picture and/or only the specifications for the camera, at that web site?

Do you have the original System and Web UI firmware files besides just the firmware presently in the camera?

Have you tried to contact the person you purchased the camera from and asked for the firmware?

Have you tried to contact Shenzhen CiBoer Technology Co., Ltd. to ask them for the firmware?

While many times the generic System firmware can work, in some ways, with these types of cameras. Some use different camera modules ("Which also maybe causing your current error with your camera and the current System firmware"), and the picture and video quality, could be impacted, if you use other System firmware. I have had this happen with cheaply made camera clones when trying other system firmware in them.

Usually, it's not as bad if you are simply trying other Web UI firmware or if you have the original System and Web UI firmware, to fall back on, if needed.

By using the wrong System firmware, or shall I say a very different System firmware than the camera expects to see, it's much more likely to brick your camera. Of course there are some recovery methods, if you are willing to take that chance, that may or may not work without the need to open up the camera, using and adding a USB interface.

If you decide to NOT try the other methods suggested above first or can't get anywhere trying.

Here is the most generic version of both System and Web UI firmware that I am aware of for the camera you made reference to above, which has the features of a FI8908W Foscam camera:

http://www.ciboer.com/products-info.asp?pid=23

If you use these files, please understand, that you use them at your own risk. The files contained in the attached .zip are:

System Firmware: lr_cmos_0_37_2_47.bin
Web UI Firmware: 0.2.9.12.bin

Don


Hi Don, thanks for the reply. English is not my first language, sorry, I ' ll try to answer your questions:

Quote
When you say "like CB-541W". Not sure what that means? What makes you think that? Hopefully, more than just the picture and/or only the specifications for the camera, at that web site?

I bought the cam from someone on an auction, it came with his unbranded box (image 1) but with a paper inside (image 2) from Shenzhen CiBoer Technology Co., Ltd. There is  the model CB-541W in his page, so I´m assuming is that model.

image 1:


image 2:



Quote
Do you have the original System and Web UI firmware files besides just the firmware presently in the camera?



No, sorry, it came in not working state. I think someone tried to change the firmware and he bricked it.


Quote
Have you tried to contact the person you purchased the camera from and asked for the firmware?


Yes, but he doesn´t have it.


Quote
Have you tried to contact Shenzhen CiBoer Technology Co., Ltd to ask them for the firmware?


Yes, I sent e-mail to support@ciboer.com, but they didn't reply yet.

I´m using serial recovery metod documented for Lloyd E. Sponenburgh, using different linux and romfs files with no luck.

I don´t know how to use the files you suggested via serial connection, do you have the corresponding linux and romfs files?

Here are some pictures from the cam:








  • ***
December 12, 2012, 12:23:40 am
You are very welcome.

Yes, I see no WiFi board on the main PCB board, where there would be a secondary smaller board for WiFi.

There is a utility here, that can split the system firmware in my .zip file, into a romfs and a Linux.zip file, known as Fostarn.

More here: http://www.openipcam.com/forum/index.php/topic,101.0.html

Don
« Last Edit: December 12, 2012, 12:26:32 am by TheUberOverLord »

December 12, 2012, 12:59:55 am
You are very welcome.

Yes, I see no WiFi board on the main PCB board, where there would be a secondary smaller board for WiFi.

There is a utility here, that can split the system firmware in my .zip file, into a romfs and a Linux.zip file, known as Fostarn.

More here: http://www.openipcam.com/forum/index.php/topic,101.0.html

Don

Thanks Don!, I unpacked the firmware you suggested, but it don't work, same error. Here is the log:

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:B8:00:00:36:A6

   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) #1699 ËÄ 3ÔÂ 8 07:58:22 CST 2012

Processor: Winbond W90N745 revision 1

Architecture: W90N745

On node 0 totalpages: 4096

zone(0): 0 pages.

zone(1): 4096 pages.

zone(2): 0 pages.

Kernel command line: root=/dev/rom0 rw

Calibrating delay loop... 39.83 BogoMIPS

Memory: 16MB = 16MB total

Memory: 14612KB available (1283K code, 206K data, 40K init)

Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)

Inode cache hash table entries: 1024 (order: 1, 8192 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: 4096 (order: 2, 16384 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-7F1DC7FF [VIRTUAL 7F0E0000-7F1DC7FF] (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

rtusb init --->

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 1024 bind 2048)

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)
/> params length is 5428
sw version is 0.37.2.47
aw not exist !
aw version is 0.0.0.0


Wait for auto-negotiation complete...ResetPhyChip Failed

open video device error
myreboot



  • No avatar
  • *****
December 12, 2012, 05:05:06 am
just to think about it: I had one cam with the same symptoms and it showed to be the cables to the camera board. They have been pretty tight and the permanent back and forth movement broke two of them.

December 12, 2012, 07:42:20 pm
just to think about it: I had one cam with the same symptoms and it showed to be the cables to the camera board. They have been pretty tight and the permanent back and forth movement broke two of them.

Thanks schufti, I will test cable continuity later

December 12, 2012, 08:03:08 pm
You are very welcome.

Yes, I see no WiFi board on the main PCB board, where there would be a secondary smaller board for WiFi.

There is a utility here, that can split the system firmware in my .zip file, into a romfs and a Linux.zip file, known as Fostarn.

More here: http://www.openipcam.com/forum/index.php/topic,101.0.html

Don

Don, I'm using this command to load firmware:

FX 7 linux 0x7f020000 0x00008000 -acxz

FX 6 romfs 0x7f0E0000 0x7f0E0000 -a

when I try to load webui using "FX 8 webui 0x7f180000 0x7f180000 -a" I received an error (I don´t remember it exactly, but it was for space), it could be an error in memory address?

  • ***
December 12, 2012, 09:49:35 pm
You are very welcome.

Yes, I see no WiFi board on the main PCB board, where there would be a secondary smaller board for WiFi.

There is a utility here, that can split the system firmware in my .zip file, into a romfs and a Linux.zip file, known as Fostarn.

More here: http://www.openipcam.com/forum/index.php/topic,101.0.html

Don

Don, I'm using this command to load firmware:

FX 7 linux 0x7f020000 0x00008000 -acxz

FX 6 romfs 0x7f0E0000 0x7f0E0000 -a

when I try to load webui using "FX 8 webui 0x7f180000 0x7f180000 -a" I received an error (I don´t remember it exactly, but it was for space), it could be an error in memory address?

Not sure, seems right from this thread. Maybe others here, might have ideas and suggestions?

http://www.openipcam.com/forum/index.php/topic,39.60.html

Don
« Last Edit: December 12, 2012, 10:49:14 pm by TheUberOverLord »

  • No avatar
  • *****
December 19, 2012, 05:56:37 am
factory params zone not inited !
camera params zone not inited !
aw version is 11.14.2.17
factory video params zone not inited !
video params zone not inited !
dyndns status zone not inited !


Your factory settings area is empty / borked / overwritten.

you need to reset it so it has correct settings.
I'd need to dump that area for you to save, as the default camera stuff is pretty crap at resetting that area - basically the code is buggy, and doesn't reset it correctly.

Thats this area here
0x7f1f0000 - 0x7f1fffff (although it might be at a different offset dependent on flash size eg 4M or 2M).


Suggest get someone else with similar hardware to dump that area, and then you can upload that dump to that area.

Make sure you do a raw flash, and don't include the headers when you write it from the uboot.



January 27, 2013, 01:44:08 pm
Hello all!
I'm new here so let me first say you are a goldmine of information lol :)

Anyway, I also have a clone cam (ipcam_pt_v3.2a), where the camera stopped working. The 1117 regulator fried and took a few other small components with it. The cam module is otherwise ok, if I could change such small SMD parts. Since its a shame to use the motherboard as a paperweight, I am trying to either bring it back to life trying to change to another camera module. I would need some info as if this is a usb module or is it any other protocol that is attached to the motherboard. If looking at the wires, it could be usb interface with some extra power lines or something, but not quite sure. If it is possible, then I would probably need the kernel drivers included in the rom, to make it work. Can anyone please point me to the proper packing/unpacking tools for this cam ? If such exists of course. :) If there is no way to revive the vison properties, is there a chance to disable this boot dependency ? The hardware itself can still be used for some other projects, as it packs some pretty decent parts.

Thanks!
Best,
Dee