SD1100/ixus 80 porting ....

  • 360 Replies
  • 87306 Views
*

Offline chr

  • ***
  • 138
  • IXUS 82 IS
SD1100/ixus 80 porting ....
« on: 30 / July / 2008, 18:31:24 »
Advertisements
cam:
SD1100IS - CHDK Wiki

Dump is here:
[DOWNLOAD LINKS] Firmware dumps available

latest chdk release:
SD1100/ixus 80 porting ....

Quote
ps: another big todo is to rewrite the diskboot.bin decoding procedure in C. I'm still hacking on that ...
This is done ;)
[REQ]Adding new cameras, applying patches into trunk (with source code prepared)
(this is included in the source patch, look in tools/dancingbits)


« Last Edit: 05 / November / 2008, 21:00:13 by chr »

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: SD1100/ixus 80 porting ....
« Reply #1 on: 30 / July / 2008, 19:45:47 »
I looked in the disassembly and all addresses are wrong.

Something wrong here, my output is
Code: [Select]
NSTUB(strcat, 0xff892020)
// Best match: 56%
NSTUB(strchr, 0xff8920a8)
NSTUB(strcmp, 0xff81d8a4)
// ERROR: strcpy is not found!
NSTUB(strlen, 0xff81d8e8)
NSTUB(strncmp, 0xff89205c)
// Best match: 52%
NSTUB(strncpy, 0xff81d868)
// Best match: 75%
NSTUB(strrchr, 0xff89220c)
NSTUB(strtol, 0xff82e3cc)

In all, search result is not too good.

*

Offline chr

  • ***
  • 138
  • IXUS 82 IS
Re: SD1100/ixus 80 porting ....
« Reply #2 on: 31 / July / 2008, 00:09:47 »
Code: [Select]
...
// ERROR: strcpy is not found!
NSTUB(strlen, 0xff81d8e8)
...
LOL?

I can find strcpy at 0xff81d88c just by staring at the hexdump!

strlen looks ok.

But I have no clue where strn* are ... how does that guess mechanic  script work?!


*

Offline chr

  • ***
  • 138
  • IXUS 82 IS
Re: SD1100/ixus 80 porting ....
« Reply #3 on: 31 / July / 2008, 20:50:12 »
Mh, don't know what went wrong but today I got stubs_entry.S.err and stubs_not_found_names.err.
They look quite logic ...

k, now I have something to continue.


Re: SD1100/ixus 80 porting ....
« Reply #4 on: 06 / August / 2008, 08:15:35 »
just bought me a ixus 80 IS myself .. if there is anything i can do to help lemme know
i'm new to CHDK but this seems like one hell of a project.

Hope u guys get it ported soon ^^

*

Offline chr

  • ***
  • 138
  • IXUS 82 IS
Re: SD1100/ixus 80 porting ....
« Reply #5 on: 07 / August / 2008, 10:38:55 »
just bought me a ixus 80 IS myself .. if there is anything i can do to help lemme know
i'm new to CHDK but this seems like one hell of a project.

Hope u guys get it ported soon ^^

Hi tracer!

Actually it looks like I'm the only owner of a SD1100 on this planet who is also a hacker ;)

For me it's a matter of time and passion.


Re: SD1100/ixus 80 porting ....
« Reply #6 on: 07 / August / 2008, 10:53:43 »
lol..

well i only have experience with java programming and i have no clue in what language ( asm? ) chdk is made.. but if any gruntwork.. or tests on the SD1100 ( ixus 80 ) are needed i'd be happy to help :)

cant wait to start shooting in RAW and use that MD :)

*

Offline will

  • *
  • 26
  • IXUS 80IS fw 1.01a
Re: SD1100/ixus 80 porting ....
« Reply #7 on: 07 / August / 2008, 19:17:35 »
chr, thanks for all your efforts thus far, it's much appreciated by all. Like tracer, i'm a programmer too (but C# rather than Java).

I'd be more than happy to help any way I can. I've got an IXUS 80 IS too, which I don't mind using to help test out/load stuff onto.

tracer: Looking at the Wiki, CHDK is written in C. Although the wiki also mentions assembler knowledge is required to add new camera support to CHDK. Hrmm...


*

Offline chr

  • ***
  • 138
  • IXUS 82 IS
Re: SD1100/ixus 80 porting ....
« Reply #8 on: 07 / August / 2008, 21:52:03 »
stubs_entry.S is done.

So lets see what's todo:

I'm actually lurking through stubs_entry_2.S ... from top to bottom.

We also need to rewrite this part to c (or any other language) so we have a handy tool to "decode" the diskboot.bin to make it work in latest cams:
decode.s - 0.00MB


Re: SD1100/ixus 80 porting ....
« Reply #9 on: 08 / August / 2008, 12:20:18 »
i'm trying to figure out how to actually port chdk and since u allready dumped the firmware it seems rather "easy" ?

correct me if i'm wrong but all we gotta do is find some specific routines in the firmware ( IDA? ) and enter the addresses in the source code?

 

Related Topics