Open IP Camera Forum

General => General Discussion => Topic started by: steaky1212 on November 13, 2011, 10:09:47 am

Title: Camera not working
Post by: steaky1212 on November 13, 2011, 10:09:47 am
Hey,

So I guess the subject doesnt give much away, but hear me out.
I guess the camera is OEM, and I have no idea who the manufacturer is.

When the camera powers up the camera doesnt pan around as part of the power up sequence. There is a green LED on the front centre of the IR leds, that is also off. I cant talk to it over ethernet - but the ethernet lights do flash. The camera used to work, but one day it stopped.
I've soldered wires to J2 (rs232) and can terminal in.

I get the following printed out:
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 supported by Winbond
Copyright Winbond Limited 2001-2006. All Rights Reserved.
ERROR: Unknown data

Checking the image gives 0 checksum errors.
Typing Set -? returns Cant find bood loader information
ERROR: Data Abort @ pc=0x7F003100.

other stuff, cache is disabled, bootloader interface is MAC

Image: 0 name:BOOT INFO base:0x7F010000 isze:0x00000048 exec:0x7f010000 -f

Any ideas what is wrong?
Looking at the pyhsical PCB shows some (maybe) damage to pins 80-90 but my decent soldering iron is at work.

Thanks in advanced
Stephen
Title: Re: Camera not working
Post by: steaky1212 on November 13, 2011, 10:15:37 am
So some extra hunting around

Presuming those pins lead to the flash chip, then its not working as those pins are damamged, and cant load the stuff from flash

OR....
somehow the flash stuff got corrupted, and all I need to do it rewrite the flash stuff

thoughts
Title: Re: Camera not working
Post by: admin on November 13, 2011, 10:25:23 am
Definitely flash corrupt issue - thats what it says..

Quote
ERROR: Unknown data

Can try reflashing  something see if it can take, otherwise may be a write-off unless you feel up to resoldering smd mount flash and putting a new chip on..
Title: Re: Camera not working
Post by: steaky1212 on November 13, 2011, 10:58:35 am
Hey,

This is a pic of the pins I was talking about
(http://i1228.photobucket.com/albums/ee459/steaky1212/blog/DSC05458.jpg)

I think I'm going to try resoldering these - or putting jumpers on. I dont fancy replacing a flash chip - but I've had to hand solder the ARM pitch at work - so thats not too daunting.
Presumably if those pins have been damaged then a new flash image wouldnt take anyway.

Stephen
Title: Re: Camera not working
Post by: schufti on November 13, 2011, 03:44:53 pm
hmmm, such hardware damage doesn't usually occur overnight ????

according to the datasheet (see filesection) this are address lines, so the symptoms are what one expects with this kind of error ...
Title: Re: Camera not working
Post by: steaky1212 on November 13, 2011, 04:34:42 pm
schufti,

I am as flumuxxed as you to be honest, and I have no idea how that came to be.
I should have a decent bit of luck soldering most of those back - i think one is a power rail and bends back underneither the device, so that may require a jumper.
I havent tried writing anything to the flash, so I guess if I fix those tracks then the thing should work fine - nothing a pit of flux and a bucket tip cant handle
Title: Re: Camera not working
Post by: steaky1212 on November 14, 2011, 09:06:12 am
So, I've resoldered those pins and I'm getting something different now.

Quote
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:F7:00:81:E4
        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 ...


ERROR: Prefetch Abort @ pc=0x7F007DE0
bootloader >

I am taking this to mean that part of it is working as the serial isnt set, and I get ERROR:Prefetch Abort @ pc=0x7f007DE0.
All of the pins looked soldered, but could it be the case that one actually isnt, and so always returns 0 (or shorted to power so 1).

What are your ideas?
Title: Re: Camera not working
Post by: steaky1212 on November 14, 2011, 11:05:43 am
*Update*
So I've just done LS and CHK,
LS reveals
Quote
Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000038 exec:0x7F010000 -af     
Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000048 exec:0x7F010000 -f     
Image: 7 name:linux base:0x7F020000 size:0x000BF7B0 exec:0x00008000 -acxz       
Image: 6 name:romfs base:0x7F0E0000 size:0x000F9800 exec:0x7F0E0000 -a

CHK reveals
Quote
ERROR: Image 7 checksum error found !                                           
Image check finished. 1 checksum error found.

Could this still be an incorrectly soldered pin, or is it more likely a dodgy flash? Is it possible to download the image and verify it and/or find another compatable image?
Title: Re: Camera not working
Post by: admin on November 14, 2011, 11:58:22 am
Either one of the higher address lines is borked on the board -> the flash chip (which is possible looking at your photo), or the flash needs reflashing.

You are getting there though.

Keep at it.

Suggest download a data sheet for the flash chip and check which lines are for the upper memory area access so you can buzz them out.

Title: Re: Camera not working
Post by: steaky1212 on November 14, 2011, 12:00:04 pm
admin,

That is exactly what I am thinking.
Using the "d" command I have got to this...
Quote
bootloader > d                                                                 
Displaying memory at 0xFFFF00                                                   
[00FFFF00] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF10] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF20] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF30] 55555555 55555555 - 0A7F0A64 30306630  UUUUUUUUd..0f00             
[00FFFF40] 0A303062 5555550A - 55555555 55555555  b00..UUUUUUUUUUU             
[00FFFF50] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF60] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF70] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFF80] 55555555 55555555 - 78300067 30303030  UUUUUUUUg.0x0000             
[00FFFF90] 30303030 55555500 - 55555555 55555555  0000.UUUUUUUUUUU             
[00FFFFA0] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFFB0] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFFC0] 55555555 55555555 - 55555555 55555555  UUUUUUUUUUUUUUUU             
[00FFFFD0] 55555555 0000000A - 00006020 00004D28  UUUU.....`..(M..             
[00FFFFE0] 00FFFF89 7F008CDF - 00000001 0000451C  ............E..             
[00FFFFF0] 00FFFF88 00000000 - 7F001A74 00FFFE74  ........t..t...             
                                                                               
bootloader > d                                                                 
Displaying memory at 0x1000000                                                 
[01000000] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[01000010] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[01000020] 00000000 0000791E - 00000000 00000000  .....y..........             
[01000030] 00000000 FFFFFFFF - 00000000 0000791D  .............y..             
[01000040] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[01000050] 00000000 E28DD0FC - 00000000 00005EF0  .............^..             
[01000060] 00000000 00006070 - 00000000 00082073  ....p`......s...             
[01000070] 00000000 00006325 - 00000000 0000451C  ....%c.......E..             
[01000080] 00000000 E92D4008 - 00000000 EB000FAB  .....@-.........             
[01000090] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000A0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000B0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000C0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000D0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000E0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
[010000F0] 00000000 55555555 - 00000000 55555555  ....UUUU....UUUU             
                                                                               
ERROR: Data Abort @ pc=0x7F000EB8                                       

I am guessing there is an open circuit somewhere
Title: Re: Camera not working
Post by: admin on November 14, 2011, 12:11:20 pm
Actually having actually seen the full photo now (jumped on a vpn) - thats the CPU, not the flash chip.
Still, looks like address line problem.

I'd just return the unit - its definitely a QC issue.
Contact the supplier, and arrange for another one.
Title: Re: Camera not working
Post by: schufti on November 14, 2011, 12:16:29 pm
Hi
AFAIK the regions you dumped are not flash
flash starts at 0x7F000000

I'm not sure where RAM is located in these devices.
Try finding out and do a fill and dump on page boundaries.

I wouldnt try flashing some new fw until it's granted there is no missing addressline, it could end in a destroyed bootloader .... so no "del ..." either
Title: Re: Camera not working
Post by: steaky1212 on November 15, 2011, 03:30:27 am
admin, the thing has been taken apart and it's already out of its warrenty - so I guess a return would be out of the question.

schufti, what do you mean by fill and dump of page boundaries.
Sorry but this is the lowest level I've worked with before (at least on a consumer item).

thank you both for your help though, it is extremely useful.

*UPDATE* I've tried buzzing out the address connections and everything seems to be there - though it is still early here so I'll give my brain a chance to settle down and try again later. Out of interest, reading http://wiki.openipcam.com/index.php/Test_Firmware_Installation (http://wiki.openipcam.com/index.php/Test_Firmware_Installation) seems to suggest I can load another firmware to a different part of the flash and get around my higher address line issues.
Also, unless I am mistaken this error "ERROR: Prefetch Abort @ pc=0x7F007DE0" points to a problem in the bootload code - as 0x7F007DE0 is in the "bootload" section of FLASH
Title: Re: Camera not working
Post by: schufti on November 15, 2011, 09:40:04 am
Hi,

having nonfunctional addresslines results in certain parts (size depending on which line failed) of the flash occuring twice in the memory window.

Consider the highest line of a 4MB chip being stuck on "L" then a write to 0x000100 will be ok and go to the lowest part of the flash, but you won't do this because your bootloader is located there.

A write to 0x200100 will unfortunately also go to 0x000100 and therefor ruin your bootloader with you not beeing aware of any wrong doing ....
Title: Re: Camera not working
Post by: steaky1212 on November 15, 2011, 11:23:35 am
schufti, is there any way of verifying the flash chip then - so reading parts of the flash chip and checking against what should be known values.

presumably reading 0x0000001 would not read correctly if a pin is held high, and 0xffffff would read incorrectly if held low? Also, using something similar to Kermit95 and capcam I can read every memory location, attempt to modify one location and see what else has been modified (purely in flash)

I have also tried loading the homebrew firmware directly into RAM, and that seems to be working fine - so I am fairly confident the issue is taking stuff from the Flash and not loading stuff onto the RAM.

*UPDATE*
webui.txt atteched
Title: Re: Camera not working
Post by: schufti on November 15, 2011, 02:45:04 pm
I'mm pretty sure that the bootloader is 99.9% the same on alldevices. So if you manage to dump the bootloader and then try to diff it wwith a known good dump, one can draw conclusions on the defunct pins from the emerging pattern of diff's. If there is no apparent pattern in the diffs, it is probably leftover random glitches from the moment of failure. If there are no diff's we unfortunately can't be sure there are no defects, yet. But maybe we could define a region where defects can be ruled out to affect the bootloader. Then we can try to flash there and verify.

At least we now know that the RAM area is not affected, so lower addresslines seem to be ok.
Title: Re: Camera not working
Post by: steaky1212 on November 15, 2011, 07:29:09 pm
So using camcap I have dumped from 0x7f000000 to 7F2B56FF.
Its quite a large file :P

Where can I find a decent bootloader, as I've only got the one camera here.
Title: Re: Camera not working
Post by: schufti on November 16, 2011, 03:22:42 pm
Hi,
the bl is only 64k from 0x7F000000 to 0x7F00FFFF

I have attached a dump (binary) from my cam. I compared the bl from a "4MB brand" (apexis) and a "2MB el cheapo" (wanscam), they are identical.

Maybe you want to upload your dump, but be aware that there may be sensible data in it (password, dyndns info, etc)?
Title: Re: Camera not working
Post by: steaky1212 on November 16, 2011, 04:50:58 pm
schufti. So that took longer than I'd hoped, but I managed to BIN my bootloader, and there are 0 differences between that one, and the one you posted.

The sensitive bits of info are held in the "settings" partition - so I can post my Linux and romfs files without issue right?
Title: Re: Camera not working
Post by: schufti on November 16, 2011, 04:58:10 pm
Hi

yes, the linux, romfs and webui parts are of interest.
the webui is located from 0x7F200000 until you see FF only

maybe we can see what parts are affected and keep the other.
but the double entry for image 0 makes me wonder ...
Title: Re: Camera not working
Post by: steaky1212 on November 16, 2011, 05:21:06 pm
Linux and romfs are here... http://www.sendspace.com/file/etxm9d (http://www.sendspace.com/file/etxm9d)
They are in txt format from kermit download, the *.hex following the jedit macro step, and finally in *.bin following hte HexBin step - just incase one step messed up.

I am a bit confused as to why I dont have a WebUI partition - especially given there was a web interface. And I am also a little perplexed by the 2 image 0's.
I've looked at the location 0x7f200000 and it does contain typical website stuff (ie admin.htm etc etc) - I wonder if it would be possible to split the hex for each page up, and recombine it into a working website. Presumabley it would be obvious if any characters are incorrect and so what address/data line has been messed up.

Given the bootloader was correct, what assumptions can I make about the state of the address/data lines. I am afraid I havent quite figured out how the address line stuff works (a 4meg chip would have 2C0000 data locations, and so would need to be addressed with 22 address lines, and return the data over 8 lines). I guess that a working bootload would suggest then that the lower 12 lines are working fine.
And I am getting even more confused as the S29GL032N90TFI04 only has 20 address lines so sohlud only be able to go to FFFFF
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 03:39:16 am
Hi,
the webui partition is allways "hidden" in pristine cams as it is nothing relevant to the bootloader.

there is allready a little tool for extracting/packing the webui image, just search for fostar.

the flash size is in megabit. so a "32Mb" device (S29GL032N90TFI04) can be 4M * 8bit or 1M * 32bit  therefor needing only a quarter of addresslines. This one is in between with 2M*16bit (==0x1FFFFF or 2097151dec or 111111111111111111111 for the highest "word"), needing 21 lines (A0-A20).

I'll have a look at the files soon(ish). The color and layout of the pcb look familiar, I'm sure I have seen this pcb in one of the boards/blogs. Maybe we can determin the manufacturer.


P.S.: ok, I had a look at your files:

a) your hex-bin conversion didn't work ...
b) the linux dump is flawed. There is a big "empty" part starting [7F030040] here.
   @ 7F03FFE0 there is a BOOT INFO image footer, allthough according to the screenshot it should be at a different address.
c) the wrong data in this area would explain why the checksum of the linux file (it is actually a zipped kernel) is incorrect., but surprisingly also the size does not fit. The dump is larger than the stated compressed size in the zip-header ok, my hex math ...
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 05:00:34 am
So I've taken another picture, this time of the full board.
(http://i1228.photobucket.com/albums/ee459/steaky1212/blog/DSC05468.jpg)

Of course, I forgot it was a 16bit flash. So briefly looking through the hex dump of the firmware, I have obtained values including 00 and FF, so I can conclude that the 16 data lines, and the lower 10 address lines are free from defects.
If after extracting the website everthing looks in order then I can conclude that my higher address lines are also fine, and that it was simply the flash that became corrupted - and it would be relatively safe to attempt an alternative flash.
Saying that, I would probably load the attempted alt flash into RAM first, just to make sure it was working.
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 06:57:06 am
a) see my P.S. to my last post

b) is it possible that someone poked through the mounting hole at the bottom of the cam?
or the screw touched the traces? or some lightning induced small sparks from the screw to the traces?

please post the full dump from the beginning of the webui 0x7F200000 to 0x7F3FFFFF (.txt and .hex) if possible.
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 07:24:56 am
schufti, good catch on that linux dump. I am just dumping the webui now.

So I guess the fact that there is boot info at 0x7f010000 and 0x7f030000 is bad, and also not recoverable if that is the actual case - as a pin problem would cause more occurances of repeating data.

It is entirely possible that someone/something poked through, but it seems strange as the camera was in use at the time, and mounted up. And I cant remember it being stormy. Obviously there was some damage to the region of the ARM corresponding to pins A14-16 but I dont know how that arose.

Unfortunately, I am at work atm, and so cant get access to JEdit to HEXify the data. I will post the TXT now, but the HEX will have to wait another 6 hours.

*UPDATE*
webui.txt attached
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 08:29:39 am
Hi,

the unexpected 2nd "boot info" is located 0x7f03 0000 to 0x7f03 ffff
but originaly it certainly was flashed to 0x7f01 0000 to 0x7f01 ffff

for me this looks like there has been a problem with (at least) A16 (if my maths don't fool me again) stuck high or connected with A15.
this might have happened on the first boot with damged traces:
The BL couldn't find the bootinfo, so it flahed a new one that ended up in the middle of the linux image.
It has exactly the size of the "empty part" with the few "random bytes" in the beginning beeing the restored "bootinfo" (recognizeable via missing MAC address)

Since the bootlog shows a valid MAC now, I think this fault is fixed. The dump of the webui will hopefully be positive proof...

I'll try to verify the rom-fs part later today
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 08:39:42 am
Hi,

So the camera borked itself then. By trying to fix the missing boot_info it actually wrote into the linux partition. AWESOME!

Given there is no way of recovering the lost uCLinux, do I have to keep trying every uCLinux,romfs and webui until I get one that works?

p.s can I try to read what?
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 09:06:31 am
p.s can I try to read what?

unfortunately I'm not able to mount the romfs ... didn't find anything obvious yet.
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 12:15:29 pm
I dont know whats happened now, because my BOOT_INFO region (0x7f010000) contains just FF's. But when I LS then bootinfo has base 0x7f010000.
And when it boots up I get "ERROR: Unknown data" instead of the variables.
This is so frustrating
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 01:00:38 pm
Hi,
maybe some of the new contacts got loose...

the bootinfo consists mostly of FFs only some 48h bytes on the beginning and the footer 32h bytes at the end.

Another good message: I got the romfs mounted, it is o.k.
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 01:23:08 pm
Awesome news about the romfs.... i guess.
I have to admit, I know nothing about linux.
If hte romfs and webui are good, and the only issue was that the boot_info was put on top of some linux stuff - what is the likelihood that I can find a compatable linux dump?

plus, Im going to try and buzz out the pins again, but cant to any soldering until tomorrow now.
Title: Re: Camera not working
Post by: schufti on November 17, 2011, 02:46:48 pm
Hi,

good news again. The webui is ok as well. It is branded as "Storage options"

It definitely is a rebranded EasyN webcam, most likely a FS-613x-xxx for which we have firmware in the files section. I'd start with the newest (don't care it is for the ir-cut model) and flash the linux.zip (don't unzip!) if it boots ok, reflash the fw and webui via webui.

Storage Options don't offer fw on their webpage, but the usermanual shows
fw: 4.22.2.32  webui: 4.5.3.44

files in file section are fw: 4.22.2.36  webui: 4.5.3.45
Title: Re: Camera not working
Post by: steaky1212 on November 17, 2011, 04:39:58 pm
do I need to flash both the romfs.img and linux.zip files
Title: Re: Camera not working
Post by: schufti on November 18, 2011, 01:28:55 am
hi,

for a start the linux.zip should be enough. after flashing the 2nd "boot info" image shuold be gone.
to have the latest fw fitting th elinux.zip you could later on flash the romfs.img via serial or the full fw via webui.
Title: Re: Camera not working
Post by: steaky1212 on November 18, 2011, 05:30:11 am
I've got some good news of my own - I downloaded the easyN camera firmware linux.zip and romfs.img, and sent the extracted linux.bin to 0x8000 (sdram) - and that seems to have worked in that the green light was flashing on the front, and it resolved an IP address.
For some reason it didnt use our DHCP server, and so I've yet to verify the actual full functionality but it definitely seems promising.

Now on to the bad news, I still cant get the BOOT_INFO region to work again. As far as I can tell the pins have full connectivity - but when the camera boots it brings up the "ERROR: Unknown data", and it seems to freeze when unzipping image 7 (instead of just failing as it did before).
Also, when I use hte "set" command it freezes too.

Do you think it is worth trying the program the flash with the linux.zip - and conceed defeat on the BOOT_INFO?
The camera doesnt seem to think that the BOOT_INFO is missing, as although it is full with FF's, the one on 0x7f030000 is currently still there, and it appears in the "LS" as appearing in 0x7f010000
My assumption is that the presence of the BOOT_INFO in the wrong location is causing all sorts of issues.
Title: Re: Camera not working
Post by: schufti on November 18, 2011, 06:09:24 am
hmm, I would try "del 0" to clear the boot info area and have the BL build a new one.

at boot it should bring sth like:
Code: [Select]
WARNING: Image 0 was not found. Try to create one ....Image 0 created If this doesn't take, nothing else will I'm afraid...

If it does, either flash back your bootinfo from the dump
Code: [Select]
fx 0 "BOOT INFO" 0x7F010000 0x7F010000 -for use
Code: [Select]
set -mac0 [MAC] to recover MAC etc.
Title: Re: Camera not working
Post by: steaky1212 on November 18, 2011, 06:36:09 am
I tried the "del 0" and it says it deletes it - but then typing in LS lists it again, and when it reboots it doesnt say anything about rebuilding.
Title: Re: Camera not working
Post by: schufti on November 18, 2011, 09:25:08 am
ok, so it finds the 2nd one. So

a) try to del 0 again.

or if this doesn't help

b) "go for gold" and flash the linux.zip
this will clear the 2nd bootinfo for good and maybe solve your mainproblem too.

Maybe we are to cautious and the BL is protected in the flash (possible, but not mandatory)
Title: Re: Camera not working
Post by: steaky1212 on November 18, 2011, 12:07:04 pm
So I took the plunge and flashed linux.zip and romfs.img,
now I am getting the write i2c error.

progress at least
Title: Re: Camera not working
Post by: schufti on November 18, 2011, 05:31:08 pm
so it's booting, loading and decompressing the kernel and firing up linux without hickup.

then the dreaded  i2c writing error?

There are several possibilities to try:

if not done allready reflash the old bootinfo

reflash the old romfs (attaced). Since the error comes from the camera binary that resides in the romfs this may be a solution...

allthough I'm pretty sure the 613B fw should be ok for your cam. The webui was exactly the version from the Storage Options userguide: 4.5.3.44, so I don't doubt the fw would have been the 4.22.2.32 perfectly fitting the 613B fw schema, you could try the 613A fw (attaced)

email Storage Options for the orig. fw
Title: Re: Camera not working
Post by: steaky1212 on November 18, 2011, 06:18:57 pm
schufti - I've just emailed storage options for orignal firmware - so we'll see how helpful they plan on being.
I cant remember which of the EasyN files worked as I tried them all - I will try them all again.
Just to clarify, did you mean the ones in /files/Firmware/EASYN IR FS613B-M1661/, or /files/Firmware/EasyNP/split/

I started working my way down the all the firmwares, and the one from hootoo "works" but it doesnt allow me my old DDNS stuff - so I'll keep trying.

I dont think I've thanked you enough
Title: Re: Camera not working
Post by: schufti on November 18, 2011, 06:36:33 pm
hi,

the ddns stuff is in the romfs. So if the linux.zip from hootoo works for you, try combining it with your original romfs. For a start keep your old webui or at max use the newer one from EasyN.

!!! Don't use EasyN webui with non EasyN romfs !!! (EasyN webui checks for romfs version and will bail out if not starting with 4.x.x.x)

The /files/Firmware/EasyNP/split/ are the old ones for 613A (which I think are not good for your cam)

The /files/Firmware/EASYN IR FS613B-M1661/ are the new ones for 613B but don't use the "unknown" which are kind of fake.
Title: Re: Camera not working
Post by: steaky1212 on November 18, 2011, 06:45:01 pm
so Iv'e used the linux.zip from the 613a_linux_romfs.zip and the romfs.bin and webui.bin from the stor_opi.zip .....

and the thing booted up fine. but the website isnt working :(
It shows a pink screen and 404 not found, with the serial terminal saying "do_file: can not find file index.hml"
Title: Re: Camera not working
Post by: schufti on November 19, 2011, 04:56:09 am
hmmm, that's interesting. how did you flash the webui?

it's a 4MB device, with the original (4MB) romfs and the webui at the correct address (usually there is a different error message in the console window if the webui is at the wrong address)
the hootoo fw is also for 4MB devices and did work ... so maybe try the hootoo linux with the orig romfs and webui or .... combinations galore.

is one of the cam identifying programms able to detect the cam?
then try to flash the webui with it.

wich linux.zip / romfs gave you the i2c errors?
Title: Re: Camera not working
Post by: steaky1212 on November 22, 2011, 04:19:02 am
schufti - So unfortunatly as the camera was actually my father-in-laws I never got the opportunity to fully complete the fix back to factory condition.
I had used HooToo's uCLinux, and my original romfs.bin and webui.bin files to build up a semi-working camera. He could use StorageOptions' custom controller software to view the video stream and control the pan/tilt, and was not too bothered by the lack of a web interface.
I was not entirely happy with the solution, but it got him what he wanted. I let him know that if he missed the web interface or the DDNS stuff then I would try again - so we'll just see how that goes on.

many thanks again for all your help - I really couldnt have done it without you.
steaky
www.steaky.co.uk (http://www.steaky.co.uk)