SD1100/ixus 80 porting ....

whim

2044
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: SD1100/ixus 80 porting ....

« Reply #190 on: 30 / October / 2008, 05:24:49 »

Advertisements

@lunkwill

that's funny -- i just tried and it works

specs: - using firefox on WinXP + noscript (allowed scripts on setepontos.com = this forum)
- right clicked your link "Login" and chose open in new tab
- download dialog appears

i'm aware you're on linux, but maybe this helps ...

wim

PS attachment removed

edit: maybe cross site scripting problem ? you're on wiki -> click setepontos link w/ script -> bam ! CSS block ?

« Last Edit: 30 / October / 2008, 05:58:54 by whim »

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

Lunkwill

Re: SD1100/ixus 80 porting ....

« Reply #191 on: 30 / October / 2008, 05:34:02 »

Yes, this one worked---thanks a lot!

I had just noticed that the patch against the SVN that chr had attached to an earlier post worked as well, but the error is still there for the "official" link. Weird...
Anyway, now I got the binary to play around with and the patch against the SVN version, I'll see if I get the cross compiler set up today.

Logged

fe50

3139
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: SD1100/ixus 80 porting ....

« Reply #192 on: 30 / October / 2008, 05:49:44 »

@Lunkwill: the wikia link is working flawless here...

"Sorry, SMF was unable to connect to the database. ..." is a message from this board here... try it with an empty browser cache, normally Ctrl-F5 should also be enough...

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

Lunkwill

Re: SD1100/ixus 80 porting ....

« Reply #193 on: 30 / October / 2008, 06:19:49 »

@fe50: Indeed, reloading didn't do it but clearing the cache did, now it works. And so did patching the source, yay!

Logged

Lunkwill

Re: SD1100/ixus 80 porting ....

« Reply #194 on: 30 / October / 2008, 19:13:16 »

@alex_goe: How did you dump your FW? I tried udumper but am having the same problem as other people have reported here: a "No Image" and "Card Locked" display. Strangely enough, the ready-made CHDK boots fine from my 32 MB card (great job chr!)
I guess as it does work I could just use your FW dump but as my cam says "Version 1.0.1.0" in response to the ver.req file I figured I'd do it myself to be sure.

So meanwhile I've got the crosscompiling environment (arm-elf-gcc etc.) set up. Checked out SVN version 535, patched it, tried to compile. The first thing I stumbled upon was stuff like "OBJCOPY=arm-linux-gnu-objcopy" vs. "CC=arm-elf-gcc" in makefile.inc. Is there a particular reason for having two ARM compilers? One native compiler for tools, and one for ARM, right? I get quite a few errors less when I s/linux-gnu/elf/ ... it still gets stuck a bit further down with error messages about some instruction set stuff but I haven't really looked into those.

Logged

whim

2044
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: SD1100/ixus 80 porting ....

« Reply #195 on: 31 / October / 2008, 03:44:55 »

@lunkwill

about the udumper: you need an encoded diskboot.bin to dump NewDryOS cams... try it with this one A590IS porting...
(copy both empty.dum and diskboot.bin to an empty bootable card)

wim

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

Lunkwill

Re: SD1100/ixus 80 porting ....

« Reply #196 on: 01 / November / 2008, 11:11:49 »

Quote from: whim on 31 / October / 2008, 03:44:55

about the udumper: you need an encoded diskboot.bin to dump NewDryOS cams... try it with this one A590IS porting...

OK, lil step by lil step...
I tried this udumper and it didn't work. Behaved just like expected (you turn on the cam and nothing happens) but no matter how long I waited, empty.dum stayed empty. I zeroed out the whole card, formatted in cam, made it bootable and copied both files---still the same.
Now I got a little further by compiling nudumper myself and encoding it with chr's encoder. The result (attached) looks significantly different from the one included in the archive although the raw binary was also 176 bytes. This one behaves the same but now I get the "gaonisoy" signature, 0xe88000+4 bytes into the file. Which is almost at the end of the 16MB block so my dump is probably incomplete.
Comparing it to Alex's shows mine is GM1.01A while his is GM1.01B (strange, on an IXUS 75 the firmware version is reported exactly like this while mine says "1.0.1.0" in the display), though there are absolutely no differences apart from the version string in the part I dumped.
I'll go play with the addresses a little, but someone will have dumped 1.01A already and found out if its start address is the same, no?

diskboot.org (0.17 kB - downloaded 83 times.)

« Last Edit: 01 / November / 2008, 11:46:34 by Lunkwill »

Logged

Martor

Re: SD1100/ixus 80 porting ....

« Reply #197 on: 01 / November / 2008, 23:13:29 »

Thanks to all those who are making this possible!

Here is my feedback on the alpha version so far (running on 1.01A):

1) RAW files - Along with a few other people I have found that these get written to the memory card (along with a JPG), but the green blinking busy light stays on after taking a RAW shot. The camera doesn't actually "crash" until you try and switch modes or turn it off. It then needs a battery drop to sort it out.

2) If you take a photo and switch to PLAY mode, and then try and "zoom out" to view multiple shots, the cam crashes with the message "abort error : game over :" (I'm guessing that this is something to do with the key mapping problem...).

3) As per previous posts, battery consumption APPEARS to be higher with CHDK running, but is there a proper way to benchmark this?

I've also (foolishly?) tested a couple of UBASIC scripts off this site - Motion detection and time lapse, and both work suprisingly well.

Logged

whim

2044
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: SD1100/ixus 80 porting ....

« Reply #198 on: 02 / November / 2008, 04:28:16 »

@lunkwill

i have no explanation for this behaviour ... this is the exact same diskboot included in CardTricks 1.41, which
has been successfully used to dump A590, SX110, and ixus 870 ...
normally 'gaonisoy' should appear about 1 Mb into empty.dum (START_SECTOR = 2048)
maybe try chr's original udumper08 here universal dumper - one more idea
and read the linked topic for more info on udumper.
if that doesn't work either i would suggest trying it with another sd card ...

wim

PS about the version reporting: double check name: VER.REQ - as in 'version request'

« Last Edit: 02 / November / 2008, 04:58:15 by whim »

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

chr

138
IXUS 82 IS

Re: SD1100/ixus 80 porting ....

« Reply #199 on: 02 / November / 2008, 09:53:02 »

Quote from: Martor on 01 / November / 2008, 23:13:29

Thanks to all those who are making this possible!

Quote

Here is my feedback on the alpha version so far (running on 1.01A):

1) RAW files - Along with a few other people I have found that these get written to the memory card (along with a JPG), but the green blinking busy light stays on after taking a RAW shot. The camera doesn't actually "crash" until you try and switch modes or turn it off. It then needs a battery drop to sort it out.

This bug makes the filesystem "corrupt". Not serious but ...

Quote

2) If you take a photo and switch to PLAY mode, and then try and "zoom out" to view multiple shots, the cam crashes with the message "abort error : game over :" (I'm guessing that this is something to do with the key mapping problem...).

the cam becomes unstable. Run a filesystem check on the SD card, this bug should go away.
(Look debug/ROMLOG.txt I bed FS-Task crashed)

Quote

3) As per previous posts, battery consumption APPEARS to be higher with CHDK running, but is there a proper way to benchmark this?

There is a thread about this in the forum. The consumption is only +20mA. I recommand to have the flash disabled so it doesn't charge all the time while playing with chdk. Also note that the canon battery indicator stays at 100% while chdk batt indicator tells you the truth!

Logged