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: EASYN - error firmware  (Read 65775 times)

  • No avatar
  • *****
June 01, 2014, 06:43:01 am
Hi,
I don't know extra PuTTY, so can't give any advice. I done it with XP Hyperterm.

Now with the big hurl (bi directionla communication working) overcome you could try kermit again. Regarding transfer protocols it should be the swiss-army-knife.

And if I remember correctly, there are x-modem and x-modem-1k so there might be a difference ....

  • No avatar
  • *
June 01, 2014, 07:23:35 am
Hi Schufti,

I got one step ahead while you posted. I am using TeraTerm and now it works. I flashed a firmware that was posted by carcamonia on page one of this thread. Sending linux.bin worked but when I tried to send romfs.bin I get another error. See below:

Code: [Select]
bootloader > fx 7 linux.bin 0x7f020000 0x8000 -acxz
Waiting for download
Press Ctrl-x to cancel ...
C
Flash programming ...
............
bootloader > ls
Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000038 exec:0x7F010000 -af
Image: 7 name:linux base:0x7F020000 size:0x000BFE5C exec:0x00008000 -acxz
Image: 7 name:linux.bin base:0x7F020000 size:0x000C0000 exec:0x00008000 -acxz

bootloader > fx 6 romfs.bin 0xf0e0000 0xf0e0000 -a
ERROR: Data corrupted, please check the free space of flash.

So I must have done something wrong I guess. I need to get rid of linux.bin right? Because I have two 7 in there. But when I use del 7 it deletes the other one first.

Graham
« Last Edit: June 01, 2014, 08:22:19 am by Graham »

  • No avatar
  • *
June 01, 2014, 10:18:13 am
*Edit*

Damn I switched to German. That is why edit my post.

I tried a few firmware versions but always just replaced 7 (and then tried to replace the rest). With some I could replace 7 but never 6 and 8. Do I have to replace boot as well? I did not dare so far. I guess I am still doing something wrong here. In some Firmware versions I tried it was hard to identify which is the linux, romfs and webui file. Maybe I am doing something wrong here?

Have a nice Sunday
Graham
« Last Edit: June 01, 2014, 10:47:31 am by Graham »

  • No avatar
  • *
June 01, 2014, 11:47:11 am
It is finally working.
I unzipped the bin files and zip them again and upload them after that and now it works. No clue why but finally!

Thanks for your help Schufti. I would not have made it without you!!!


  • No avatar
  • *****
June 01, 2014, 04:29:24 pm
Hi!

Ok, took us only 4 month to get all sorted out. Hopefully this thread will help others to get there faster.

But all is well that ends well  :)

schufti

P.S.: ich haette es auch in deutsch verstanden, aber den anderen haett es es weniger geholfen.

  • No avatar
  • *
June 02, 2014, 06:47:20 am
I am sure it will help others :-)
The four month were my fault. It took a long time till I finally got my serieral USB port and then my work did not let me spent any time on this. But finally it works.

Passt schon, bin ja des Englischen mächtig. Und so erreichte es eben mehr.

  • No avatar
  • *
June 02, 2014, 12:32:08 pm
I have one last question if it is ok.
The WLAN functionality of the cam is not working. May this be a result of the firmware I use? I will check the boot messages later to see what exactly happens but I was just wondering if the firmware versions might include different WLAN drivers?

Regards
Graham

EDIT
Code: [Select]
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) #1453 Ò» 12ÔÂ 6 08:30:46 CST 2010
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: 14320KB available (1481K code, 299K 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-7F1EBFFF [VIRTUAL 7F0E0000-7F1EBFFF] (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.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

Sash command shell (version 1.1.1)
/> no support
hub.c: connect-debounce failed, port 1 disabled
new USB device :80fb4004-fed740
hub.c: new USB device 1, assigned address 2
usb.c: USB device 2 (vend/prod 0x148f/0x3070) is not claimed by any active driver.
new USB device :80fb4204-fed740
hub.c: new USB device 2, assigned address 3
probing sonix288 usb camera ...
dvm camera registered as video0
p1[7]:1,j 3,config->bNumInterfaces:4
usbaudio: device 3 audiocontrol interface 2 has 1 input and 0 output AudioStreaming interfaces
usbaudio: valid input sample rate 16000
usbaudio: device 3 interface 3 altsetting 1: format 0x00000010 sratelo 16000 sratehi 16000 attributes 0x01
usbaudio: valid input sample rate 48000
usbaudio: device 3 interface 3 altsetting 2: format 0x00000010 sratelo 48000 sratehi 48000 attributes 0x01
usbaudio: registered dsp 14,35
usbaudio: warning: found 1 of 0 logical channels.
usbaudio: assuming the channel found is the master channel (got a Philips camera?). Should be fine.
usbaudio: registered mixer 14,32
usb_audio_parsecontrol: usb_audio_state at 00ff3ba0
sw version is 4.22.2.36
aw version is 0.0.0.0

Wait for auto-negotiation complete...OK
100MB - FULL
video0 opened
1
1
1
1
1
1
unknown command
do_zoom_stop: write error 5
__pthread_initial_thread_bos:440000
manage pid:14
2
2
2
2
2
2
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
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
[26]
Jan  1 00:00:13 1970 dhcpcd[26]: infinite IP address lease time. Exiting

ntpc adjust ok
bonjour callback: service registered

Here are the boot messages. I think WLAN should be working right?
« Last Edit: June 02, 2014, 12:36:48 pm by Graham »

  • No avatar
  • *****
June 03, 2014, 01:52:42 am
don't know. can't find explicit statement from a driver.
Unfortunately the chinese plug in different wifi boards w/o changing the product number.
If you browse the forum you will find several threads about lost wifi after fw "upgrade" and tiresome search for the correct kernel.

to make shure which drivers are on your cam you can connect with the serial console and at the shell prompt enter: ls /sys/modules/ this should give you a list of all available drivers (at least on a standard linux system)

  • No avatar
  • *
June 08, 2014, 10:04:28 am
Hi Schufti,

unfortunately there is no folder called /sys. Strange!

Code: [Select]
/> ls -al
drwxr-xr-x  1 0        0              32  Jan 01 1970  .
drwxr-xr-x  1 0        0              32  Jan 01 1970  ..
drwxr-xr-x  1 0        0              32  Jan 01 1970  bin
drwxr-xr-x  1 0        0              32  Jan 01 1970  dev
drwxr-xr-x  1 0        0               0  Jan 01 1970  etc
drwxr-xr-x  1 0        0               0  Jan 01 1970  flash
drwxr-xr-x  1 0        0               0  Jan 01 1970  home
dr-xr-xr-x 24 0        0               0  Jan 01 1970  proc
drwxr-xr-x  1 0        0               0  Jan 01 1970  swap
drwxr-xr-x  1 0        0               0  Jan 01 1970  tmp
drwxr-xr-x  1 0        0               0  Jan 01 1970  usr
drwxr-xr-x  1 0        0              32  Jan 01 1970  var

So I guess I need to do try an error.

I should have that Apexis Firmware that I flashed on the cam right when I bought it. There WLAN was working properly. Would that help if I find it?
Btw I like your web interface. Good job!
« Last Edit: June 09, 2014, 08:43:38 am by Graham »

  • No avatar
  • *
June 09, 2014, 08:44:54 am
I just flashed the old Apexis FW. It seems to work with your web UI, but still WLAN does not work. I don't get that to be honest. Maybe I fried my WLAN adapter? I needed to unmount it when I attached to cables to plug on my serial adapter to my cam.
« Last Edit: June 09, 2014, 08:51:45 am by Graham »

  • No avatar
  • *
June 09, 2014, 04:46:50 pm
Very interesting. Now I flashed back the Apexis Firmware again and added the Web UI I used with it and loaded my old settings. When I do that the cam connects with my WLAN even that I do not see my WLAN on the Web UI WLAN settings when I hit the scan button (but my SSID is broadcasted in my Router's WLAN settings). So WLAN works but I cannot connect to the Web UI interface by simply typing in the IP adress of the web cam in my browser. If I use IP Camera Tool, then it works?!?!?!


  • No avatar
  • *****
June 10, 2014, 02:06:01 am
hmmm, maybe if you are located in europe ... are you using ch 12 or 13 ?
the fw can't handle these channels well, the chinese only know FCC if anything...

  • No avatar
  • *
June 13, 2014, 06:44:14 am
Hi Schufti,

I am using ch 8 so it should work I guess.

I will see if WLAN works with the EasyN Firmware I have as well and I maybe just did not see the SSID or the scanning did not work. After that I will check why UI is not working over WLAN (Which is really strang I think).