Open IP Camera Forum

End User => Firmware => Topic started by: Graham on February 02, 2014, 02:05:46 pm

Title: EASYN - error firmware
Post by: Graham on February 02, 2014, 02:05:46 pm
Hello together,

I am new here and new to the world of IP cams.
I bought a EASYN F-series IP Cam and heard that it is compatible with APM-J011 Firmware (same cams?). Since the original EASYN Firmware was not too well I downloaded it and flashed it. Obviously it was the wrong Firmware I downloaded or the cams are not compatible. When I log on the cams webinterface I get the message "error firmwar!". I found your community and thought you might able to tell me what to do. Do I have to upload a new firmware using a serial adapter like discribed in the one post here?

Thanks for your help
Graham
Title: Re: EASYN - error firmware
Post by: schufti on February 03, 2014, 01:10:42 am
You probably only updated the firmware but not the WebUI.
The EASYN WebUI checks for the firmware verison and gives the error you see if there is a mismatch.
Now you can try to update the WebUI according to the firmware via camfinder tool.

If this doesn't work you can try to access the update page directly. Then you can decide to either change the firmware back to EASYN or to change the WebUI to Apexis, too.

The url for the direct access of the update page is something like
http://ip.of.your.cam:port/maintance.htm
Title: Re: EASYN - error firmware
Post by: Graham on February 03, 2014, 02:12:04 pm
Thanks a lot Schufti, that is good news. I am not at home today but I will try tomorrow right after work. I hope it works!
Just one last question. My cam is marked with EasyN F-M166 and the commercial where I bought the cam says FS-613B-M166. I do not have a valid original EasyN Firmware. Do you know where to get it? I did not find anything on EasyN's website. Is the cam really compatible with the Apexis cam I mentioned? Maybe you know or you know some links where I could check that. I get the Apexis WebUI on the Apexis website?

Thanks a lot, I really appreciate your help.

Regards
Graham

P.S. which Web UI would I have to update to get my cam running with the Apexis Firmware? The MJ745?
Title: Re: EASYN - error firmware
Post by: schufti on February 04, 2014, 06:56:38 am
yes, EasyN removed the FW download from their website.
You can try to contact user celem, he had some (old) version
unfortunately I (re)moved my local fw collection.

p.s.: ??? the US EasyN offers foscam SW for download after registration ???
http://easynusa.com/firmware.html
Title: Re: EASYN - error firmware
Post by: Graham on February 04, 2014, 02:52:41 pm
Once more, thank you Schufti!
I registeres for the foscam software but I have no clue which one to pick for my camera. What is the difference to the other firmwares? Can you recommend it?
I will drop celem a PM as well.

Sorry for asking so much and thanks
Graham

P.S.
Found a web UI that runs with my cam. Seems like everything works but I cannot move my cam using the buttons on the web UI. Just the button in the middle works where the cam does a ful circle.
Title: Re: EASYN - error firmware
Post by: schufti on February 05, 2014, 02:10:14 am
Hi,
I don't know why they link to the foscam fw and don't give any cross reference....
You could try the EasyN fw I attached. It is probably outdated but movement should work again ..
You can also try one of the attached WebUIs (one EasyN, one from me) to see if it is more to your liking.
(don't forget to unzip)
Title: Re: EASYN - error firmware
Post by: TheUberOverLord on February 06, 2014, 12:24:40 pm
Once more, thank you Schufti!
I registeres for the foscam software but I have no clue which one to pick for my camera. What is the difference to the other firmwares? Can you recommend it?
I will drop celem a PM as well.

Sorry for asking so much and thanks
Graham

P.S.
Found a web UI that runs with my cam. Seems like everything works but I cannot move my cam using the buttons on the web UI. Just the button in the middle works where the cam does a ful circle.

Please make sure your camera will support loading one of these Foscam MJPEG camera firmware versions. The table below should help you isolate what firmware versions MIGHT be compatible for your camera. If your camera cannot support using a Foscam MJPEG firmware version. Then you could wipe out important memory areas in your camera. You still might be able to recover your camera after doing so, by using a serial interface.

On the label for each camera. There will be a VNT or FR followed by the wireless Mac Address of the wireless daughterboard in the camera:

VNT wireless daughterboards only support 802.11 b,g
FR  wireless daughterboards support 802.11 b,g,n

Example System firmware map to Foscam MJPEG camera models by wireless daughter boards:

PT = Pan/Tilt

Code: [Select]
Type FR WiFi module                              Type VNT WiFi module
-------------------                              --------------------
Indoor PT cameras romfs_cmos_11_37_2_51          romfs_cmos_11_22_2_51
Indoor fixed cameras romfs_cmos_11_35_2_51       romfs_cmos_11_25_2_51
Outdoor waterproof cameras romfs_cmos_11_35_2_51 romfs_cmos_11_25_2_51
Outdoor PT cameras romfs_cmos_11_37_2_51         Never use VNT WiFi module

Note: The linux.zip file for each System firmware release. Example x.x.x.51, is common to ALL MJPEG camera models. The romfs file is unique to camera model type ("Indoor PT, Indoor Fixed, Outdoor 'fixed', Outdoor PT") and wireless daughter board in that camera model type.

I have ALL the firmware versions for ALL Foscam camera models. MJPEG, Old H.264 and currently being sold H.264 models. Including the linux.zip and romfs for ALL Foscam MJPEG camera models. Which can be used for serial interface recovery.

So worse case you could do a serial interface upgrade for the camera. IF it's compatible with Foscam MJPEG camera model firmware. The TTL Serial Interface needs to support 3V DC and can be a USB serial interface, like the one shown below. They can be found for under $2.00 U.S. ("Including shipping") on places like ebay.

(http://www.saveontelephonebills.com/camera/USBTTL3VDC.png)

All Foscam MJPEG camera models have a serial connector labeled J2. See below, for pin layouts and locations for Foscam MJPEG Outdoor ("Example 1") and Indoor ("Example 2") camera models. The pins RXD,TXD,GND are the same for both:

(http://www.saveontelephonebills.com/camera/J2Example1.png)

(http://www.saveontelephonebills.com/camera/J2Example2.png)

If you can still see your camera in the IP Camera Tool. Then you can simply reference the above table first two sets of firmware version numbers and download that firmware, from the Foscam firmware download page:

IP Camera Tool Download: http://foscam.us/downloads/IPCamera.exe

Foscam Firmware Downloads: http://www.foscam.com/down3.aspx

Then you can use the IP Camera Tool to install firmware normally, without the need to use serial interface recovery methods. By simply selecting the camera shown in the IP Camera Tool and then right-clicking on it and then choosing the upgrade firmware option.

You can first install only the system firmware before installing the Web UI firmware and use the below to verify that you can access the camera, prior to installing the Web UI via the IP Camera Tool:

Please do NOT use any leading http:// or www. when entering your camera and port information after you click on the link below

Simply enter: IPAddressForCamera:PorForCamera or DDNSForCamera:PortForCamera

http://www.saveontelephonebills.com/camera/YourCameraBIV25.htm

The above can be very helpful. Because it does not depend on any Web UI being in the camera. Since whatever Web UI firmware is currently in the camera, if any, may no longer match the system firmware, that's now in the camera. The above gives you a clean method to make sure that the system firmware now in the camera, is in fact functioning as it should be. Before taking any more time installing Web UI firmware, that won't work anyway, if the above fails. Allowing you to potentially install a different system firmware, if needed, first.

If your camera is accessible using the above. You can now use the IP Camera Tool to also install the Web UI firmware now, so that you can access the Standard Camera Interface by using the Cameras IP Address or DDNS and port for the camera from a browser.

The same method above, can be used when recovering a camera using the serial interface, prior to installing a matching Web UI firmware using the IP Camera Tool to do so, for the system firmware you used for the cameras serial recovery.

Don
Title: Re: EASYN - error firmware
Post by: Graham on February 06, 2014, 02:47:59 pm
Thanks a lot for the detailled instructions Don :-)
I really appreciate it.
Title: Re: EASYN - error firmware
Post by: Graham on February 06, 2014, 03:47:33 pm
Shit! Now I don#t see my cam in IP Camera tool.
I guees I am going back to zero
Not sure if I am smart enough to rescue it using the serial interfac.
Title: Re: EASYN - error firmware
Post by: TheUberOverLord on February 07, 2014, 03:30:15 pm
Shit! Now I don#t see my cam in IP Camera tool.
I guees I am going back to zero
Not sure if I am smart enough to rescue it using the serial interfac.
Sorry to hear that. The very first thing I said in my post was warning how you could harm your camera by installing the wrong firmware.

Don
Title: Re: EASYN - error firmware
Post by: TheUberOverLord on February 08, 2014, 02:42:27 am
I found a version of firmware for this camera on one of my systems. I can't tell what version it is. But it has both the system firmware and the WebUI firmware and it was downloaded by me on Oct 8, 2012 from somewhere.

Please see attached ("You must be logged in here to see the attachment"):

NOTE: Please use at your own risk since I am not sure where I got this from or if it works.

Don

Title: Re: EASYN - error firmware
Post by: carcamonia on February 08, 2014, 07:26:30 am
Es la ultima version EasyN_FS-613B-M1661 web ui  F-E-A1-A-A3
Title: Re: EASYN - error firmware
Post by: TheUberOverLord on February 08, 2014, 09:43:57 am
Es la ultima version EasyN_FS-613B-M1661 web ui  F-E-A1-A-A3
Translated: It's the latest version EasyN_FS-613B-M1661 web ui f-e - A-A1-A3.

Thanks. Good to know.

Don
Title: Re: EASYN - error firmware
Post by: carcamonia on February 08, 2014, 11:48:30 am
Después de muchos firmwares flasheos erroneos he tenido que reparar mi cámara muchas veces. En este enlace os dejo lo que para mí es la mejor combinación de archivos. Última versión para la EASYN F613 M136 con dos WEB ui.
La "FF-E-A1-A-A3(4.37.2.38).bin" es la original de EASYN y la "WEB UI COMPATIBLE EASYN 0.0.4.11.bin" es completamente compatible y funcional con nuestra cámara, además que incorpora muchas mejoras con respecto a la original. Está sacada de un firmware de Wanscam. El modo de instalación es el convencional por web. Espero haberles sido de ayuda. Saludos.

https://www.dropbox.com/s/1r96pm5n84rkkz7/F613%20M136%20EASYN%20LAST%2008-02-2014.rar
Title: Re: EASYN - error firmware
Post by: Graham on February 13, 2014, 06:49:19 am
Hey everybody,

I am very sorry for my late reply. I ordered a UART module and it is delay! So I can not flash my camera yet. Deleivery will be somewhen between 22. Feb and 17. March :-(((
I guess I ordered at the wrong place. I will keep you guys in the loop if it worked. I really appreciate your help.

Graham
Title: Re: EASYN - error firmware
Post by: Graham on February 22, 2014, 04:25:22 am
Hello everybody,

finally I have my USB to serial interface!!! Took forever to get here.
Just one question before I start rescuing my cam: Can I use the GPIO port of my cam as well to flash the latest firmware? Or do I have to solder some pins or cables on the board of my cam like shown in the picture above? I am not really good at soldering so I will ask a friend of mine to do that for me. That means I more delay until I can repair my cam ;-)

Thanks everybody (reall a great forum here)
Regards
Graham
Title: Re: EASYN - error firmware
Post by: schufti on February 24, 2014, 01:57:01 am
why do you complain about the delivery? it was the earliest date from the mentioned timespan.
unfortunately the necessary contacts are only available on the shown solderpoints ... maybe your friend can add some simple connector (like old soundcard-cd cable or ic-socket) to be more versatile
Title: Re: EASYN - error firmware
Post by: Graham on February 24, 2014, 03:11:42 am
Hi Schufti,

Quote
why do you complain about the delivery? it was the earliest date from the mentioned timespan.

Well yeah it sounded like I complain about the delivery. But to be honest I complain more about myself. I did not notice that the delivery takes that long when I ordered. So it was not the fault of the people I ordered from but my fault that I did not notice. But still it felt like it took forever :-)

OK then I will see what my friend can do. If I want to solder some pins I need to get them first as well.

Thanks again Schufti
Title: Re: EASYN - error firmware
Post by: schufti on February 26, 2014, 02:52:54 am
beware that the holes are in 2mm pitch not the common 2.54mm.
So it is practical to use a short cable, so you can use standard 2.54mm connectors and have it accessible from the outside when the cam is closed.
Title: Re: EASYN - error firmware
Post by: Graham on March 30, 2014, 05:30:52 am
Finally I have my cables hooked up to the cams board. I would start to flash the firmware according like it is described in this link http://www.neknek.net/ (http://www.neknek.net/). But I do not know which cable is what. Are there any descriptions about that?
Title: Re: EASYN - error firmware
Post by: Graham on March 30, 2014, 06:01:25 am
OK I just tried to find out which cable is 3,3V,TX,RX and GND from the picture neknek and Don posted and then I tried to connect. Crossing TX and RX like recommended in NekNek's instructions. When I cross RX and TX the data LED on my USB UART interface stays off. If i do not crosslink RX and TX then the data LED lights. When I open a Hyperterminal window and connect and then turn on the cam nothing happens. I think I should get some response like discribed in NekNek's instructions. Does anybody have another link with instructions maybe?

Does that mean my cam is lost when nothing appears in HyperTerminal?

Thanks in Advance everybody.

Graham
Title: Re: EASYN - error firmware
Post by: schufti on March 31, 2014, 01:48:22 am
Hi,
maybe you could give us a link to your adapter, this would make things easier.
Generally you only need gnd, rx, tx you shouldn't connect the 3.3V.
Finding gnd should be easy, it is usually the square pad and the black cable.

To check if your adapter / hyperterm setup are at all working, you could connect rx to tx (on the adapter, not the cam) this should then echo each character you type in hyperterm (or PuTTY which I prefer)

after this being positive we can look at connecting the cam.
Does the cam just sit there or does it show some signs of initialisation ?
Title: Re: EASYN - error firmware
Post by: Graham on March 31, 2014, 02:48:32 pm
Hi Schufti,

well my USB to TTL Adapter looks exactly like the one Don posted in his post. There is no brand or anything printed on it. It is hooked up to my COM6.

So used Putty to connect to it with the option serial and Speed 115200. When I directly connect TX and RX on my adapter and connect with putty I can type something and when I hit enter the curser jumps right at the beginning of the line. What I typed in stays in the same line. When I do not directly connect RX and TX I cannot type into the putty window.

Does that help in some way?

Thanks for your help

Graham

P.S. your nick sounds German ;-)
Title: Re: EASYN - error firmware
Post by: schufti on April 01, 2014, 06:55:57 am
Hi,
yes that tells us that your setup of the adapter and PuTTY is working ok.
So we can concentrate on the connection cam-adapter.

If the adapter has markings on the pins, try just connecting gnd-pin to the square pad on the cam and Rx-pin to the 2nd or 3rd after the square one and see if you get any (garbled) output in PuTTY on either pin. You could try the same with the Tx-pin. At one of the four combinations there should be output on the screen.

yes, I am german speaking.
Title: Re: EASYN - error firmware
Post by: Graham on April 02, 2014, 03:12:20 pm
Great that worked. I made it to the point where I can get some garbled output in PuTTY with just two cable connected. I guess that is good news. What to do now? Is the output encrypted?

Danke für die Hilfe :-)

Graham
Title: Re: EASYN - error firmware
Post by: schufti on April 03, 2014, 02:24:56 am
Hi,
if the output is garbled, then there are 2 possibilities:

a) simple one: wrong baudrate selected in PuTTY
can't remember what is used, try anything between 115200 and 9600

b) complex: connections are not correct still:
  check if the square pad is really gnd (e.g. ohm meter to gnd of power). check if connected pin of adapter is really gnd.
  if this was correct it can only be a) if not, restart previous procedure with new gnd connection.

if you can now read bootloader messages, the "other" adapter-pin (Tx/Rx) goes most likely to the unused pad of the 2 middle ones.

During boot-up the bootloader should react on input if all is correct.

you then may follow the "Firmware Recovery - method #2" thread
Title: Re: EASYN - error firmware
Post by: Graham on April 13, 2014, 02:14:28 pm
Hi,

I tried several things now and still do not get a readable output. I think I did not select GND correctly. I need to get a ohm meter to find out I guess. The connections I tried was 9600, 19200, 38400, 57600 and 115200. Those are the only possible ones righ? Or did I miss something?

Thanks
Graham
Title: Re: EASYN - error firmware
Post by: schufti on April 14, 2014, 02:55:23 am
yes, that covers all reasonable baudrates.

BUT I see I made a mistake in my post from 31.3./1.4., GND is not the square pad!
The pictures are correct, GND most likely is the 3rd. I mixed this up with some other gadget I'm currently working on, sorry.

So if it is really a "clone" then chances are extremly high they didn't change the pinout or baudrate and the way forward would be to try again with 115200 baud, connect TxD to the 1st (square) pad, RxD to the 2nd and gnd to the 3rd, do not connect the 4th. Try and see if there is any output. If not just swap RxD and TxD.
Title: Re: EASYN - error firmware
Post by: Graham on May 01, 2014, 11:45:08 am
Hi Schufti.

I finally have everything running! I am following the tutorial you quoted but I simplay can not find any working link to download Kermit. Can you help me out? Maybe I am simply to dumb to download from the webpage but I think the linke there is dead.

Thanks for your help
Graham
Title: Re: EASYN - error firmware
Post by: Graham on May 01, 2014, 11:59:41 am
I found Kermit on a different website now. But I can not really use it. I guess I need to configure it like I configured Putty before to get a connection, right?
Well I cannot do that because Kermit just accepts connection on COM port 1 to 4 and my serial adapter is on COM 6. Can I change that somehow?

EDIT:
So I have the script now. There was some problems with my browser. But I still do not have Kermit or the wrong Kermit version I think. Trying to fix that too.
Title: Re: EASYN - error firmware
Post by: Graham on May 08, 2014, 04:32:41 pm
I am still struggeling with Kermit. I can not get the correct version or maybe I do have the correct version and cannot get it to run. Are there any alternatives?

I feel dumb but my Kermit version opens but no Alt-X works and if I try to load the scripts, error messages come up. I think because of the com port issue.
Title: Re: EASYN - error firmware
Post by: schufti on May 13, 2014, 01:21:39 am
HI,
I can remember similar problems. Can't remember the details at the moment but will look into it as soon as I have some spare time. Can remember that there was someone who wrote a simple software to do the same thing but I couldn't get this to work either. Maybe you're lucky...
Title: Re: EASYN - error firmware
Post by: Graham on May 26, 2014, 04:36:37 am
Hi Schufti,

I am still struggeling with the software. Can you remember what software you finally used to get it to work?
Could I simply copy and paste the script in putty to make the commands from the script work?

Graham
Title: Re: EASYN - error firmware
Post by: schufti on May 27, 2014, 02:43:47 am
Hi Graham,
sorry for the delay in your work but just now I realised you don't need kermit at all. You don't want to download anything from your cam, you want to upload ... what can be done with PuTTY or Hyperterm etc as long as the sw provides x-modem protocol

You should capture a boot log in PuTTY first so we can see in which state your camera is exactly.

To flash the required part of fw use this as guidline
http://www.openipcam.com/forum/index.php/topic,39.msg1644.html#msg1644
Title: Re: EASYN - error firmware
Post by: Graham on May 29, 2014, 04:42:44 am
Hi Schufti,

no need to be sorry. I did not have much time to work on my cam lately anyway and you are helping me, so thank you in advance for any assistance.

Good new that I do not need Kermit. When I boot my cam and I press ESC when it is asking me to in order to enter debug mode, this what comes up (I think the same comes up when I don't press ESC during boot sequence).

Code: [Select]
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         : XX:XX:XX:XX:XX:XX
        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 .
ache 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) #1460 ▒▒ 12▒▒ 7 23:30:28 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: 14616KB available (1278K 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: 700000-6FFFFF [VIRTUAL 700000-6FFFFF] (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)
Blkmem: bad access: block=0, count=2 (pos=400, len=0)
end_request: I/O error, dev 1f:00 (Blkmem), sector 0
romfs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 1f:00

I edited the MAC adress. This Kernel panic does not sound good right? But to be honest I have no clue what it means. I made it to the bootloader before when I tried to follow recover method #2 post. No clue why it is not working right now. It is not receiving my ESC command I guess.

Happy father's day and thanks for your help.
Graham
Title: Re: EASYN - error firmware
Post by: schufti on May 29, 2014, 07:15:47 am
ok,
the kernel seems to boot up fine but cannot find the root file system.
So you should try to flash the rootfs (romfs.img or whatever it is named in the fw you use) next, it should then boot up to the point where it complains about no gui found ...
The timing for the esc key is somewhat crucial. but it could also bee that the terminal sw that you use needs any handshake disabled so it won't wait for a "go" before transmitting keystrokes. you can check this by just connecting rx/tx pins on your cable when cam is disconnected, your keystrokes should then show on the screen
Title: Re: EASYN - error firmware
Post by: Graham on May 29, 2014, 09:59:20 am
Hi Schufti,

I am using putty with these settings:
Speed: 115200 baud
data bits: 8
stop bits: 1
Parity: none
Flow Control: none

is flow control what you mean by handshake?
When I just connect RX and TX and then open putty (with no power on my cam) I do not see what I type in my putty windows. I tried at two different computers, both with the same results. Is it possible that one if my cables or soldered points are defect? I know that I was able to get into debug mode already a few days earlier.

Thanks once more

Graham
Title: Re: EASYN - error firmware
Post by: schufti on May 29, 2014, 11:27:44 am
no, what I ment was connect Rx with Tx on the cable and not to the camera ...
then what you type and transmit should directly be received and displayed on your PC

and yes, handshake == flow control and the settings look ok.

I remember that this "esc" press was somehow time critical.
just start hammering the "esc" key before you power up your cam and see what happens. to many "esc" won't harm your cam  ;)
Title: Re: EASYN - error firmware
Post by: Graham on May 29, 2014, 01:29:00 pm
Hi Schufti,

got it now, sorry. So when I do that (connect TX and RX from my serial adapter) then I do get an echo on in putty of what I type. So that seems to work. But pressing ESC multiple times during booting of the cam does not work. I tried that already. Still not in debug mode :-(

So a broken soldering point or cable is not an option?

Thanks
Graham
Title: Re: EASYN - error firmware
Post by: schufti on May 29, 2014, 02:58:32 pm
try using a different terminal sw. Try hyperterm for a start.
worst case would be that the serial input of your cam somehow got fried ...
Title: Re: EASYN - error firmware
Post by: Graham on May 30, 2014, 02:47:32 am
I tried putty on two computers but not a different hyperterminal program. I will do that. Do you have any recommondations? I just know the old hyperterminal from Win XP. Will see if I get my old XP computer to run.

I have the strong feeling that I fried the serial input of my cam :-( But I will try another Hyperterminal program.

Title: Re: EASYN - error firmware
Post by: schufti on May 30, 2014, 03:31:27 am
ok, i got my cam down from the attic and the timing isn't that critical. as long as you press ESC when the dots are printed ist is ok. Even if you press and hold ESC when powering up the camera it is working. tested it with PuTTY ...

As now the receiving is working, I doubt a wrong pinout, but just to be sure: the 3 pads starting with the square one are used, the 3rd being gnd ...
Title: Re: EASYN - error firmware
Post by: Graham on May 30, 2014, 02:07:49 pm
Thanks for getting your stuff out.
I took a couple of pictures from my setup as well. Need to find a host where I can upload them (I don't have any web space at the moment).

My setup looks close to yours and my third pin is GND as well. Just like it is shown in your picture.
I also used my old XP computer and hyperterminal, but the same result. :-(

Thanks again
Graham

EDIT:
just looked at your pic closely again! I switched a cord and marked it wrong. It works now :-)
Thanks so much! I will try to flash the cam again tomorrow morning! Thank you so much!
Title: Re: EASYN - error firmware
Post by: Graham on May 31, 2014, 04:41:20 am
Good morning Schufti,

thanks again for yesterdays help.
Now I am at the point that putty is waiting for my XMODEM SEND to send the file over to the cam (at least I think putty does). On the putty output screen I get lots of Cs ;-)
If I remember it correctly I need to initiate the xmodem send from my command window right? But I have no clue what command to use.

Thanks again
Graham
Title: Re: EASYN - error firmware
Post by: Graham on May 31, 2014, 02:53:00 pm
I am trying to do it with ExtraPutty now. It has an optional Menu item that allows you pretty easily to initialize and Xmodem send of a file. But when I do that, the "C" that are printed on the screen by putty stop and nothing else happens. When I hit enter, I get back to the prompt. An ls -all shows that nothing was written on the cam yet. Anything I am doing wrong? Sorry that I causing so many unconveniences.

Graham
Title: Re: EASYN - error firmware
Post by: schufti on 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 ....
Title: Re: EASYN - error firmware
Post by: Graham on 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
Title: Re: EASYN - error firmware
Post by: Graham on 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
Title: Re: EASYN - error firmware
Post by: Graham on 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!!!

Title: Re: EASYN - error firmware
Post by: schufti on 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.
Title: Re: EASYN - error firmware
Post by: Graham on 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.
Title: Re: EASYN - error firmware
Post by: Graham on 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?
Title: Re: EASYN - error firmware
Post by: schufti on 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)
Title: Re: EASYN - error firmware
Post by: Graham on 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!
Title: Re: EASYN - error firmware
Post by: Graham on 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.
Title: Re: EASYN - error firmware
Post by: Graham on 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?!?!?!

Title: Re: EASYN - error firmware
Post by: schufti on 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...
Title: Re: EASYN - error firmware
Post by: Graham on 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).