S100 porting thread - page 15 - DryOS Development - CHDK Forum

S100 porting thread

  • 287 Replies
  • 138898 Views
*

Offline c10ud

  • ***
  • 245
Re: S100 porting thread
« Reply #140 on: 18 / July / 2012, 16:43:19 »
Advertisements
Hello, I did the original port but I'm currently very busy..

I don't exclude that in future I could try porting 101b too but in general what waterwingz said stands correct. (and I'd add that once you have a camera ported, another firmware version isn't very difficult).

Re: S100 porting thread
« Reply #141 on: 19 / July / 2012, 06:50:36 »
Hello c10ud, thanks for bringing CHDK to the S100. I just purchased an S100, and to my disappointment, it is firmware 1.01B.

I will gladly help beta test 1.01B, and thanks a million for all your help and effort.

Kind regards,

Re: S100 porting thread
« Reply #142 on: 19 / July / 2012, 08:25:30 »
same issue...waterwingz...wher can we get the "A" version of firmware. I've searched the canon site, but they only post the latest

Re: S100 porting thread
« Reply #143 on: 19 / July / 2012, 08:31:49 »
same issue...waterwingz...wher can we get the "A" version of firmware. I've searched the canon site, but they only post the latest
Basically,  you can't.  Canon does not typically provide firmware updates unless there is a major bug.  And without their update,  you can't change your camera's firmware version.  Sorry.

Ported :   A1200    SD940   G10    Powershot N    G16

Re: S100 porting thread
« Reply #144 on: 19 / July / 2012, 08:35:46 »
worth the try...I'll post results later today

Re: S100 porting thread
« Reply #145 on: 19 / July / 2012, 08:36:27 »
sorry...I meant I'll try the version "A" CHDK

Re: S100 porting thread
« Reply #146 on: 19 / July / 2012, 13:27:04 »
S100 "A" does not appear to work with firmware version "B"

The camera actually hangs up with card locked and battery has to be removed to get camera to start with card unlocked

Verified boot sector was in place with HDHacker. Made disk bootable with EOS card and CHDK files were unzipped directly to SD card, not copied

Re: S100 porting thread
« Reply #147 on: 19 / July / 2012, 15:12:48 »
The camera actually hangs up with card locked and battery has to be removed to get camera to start with card unlocked

I can confirm the same behavior when attempting to use the "s100-101a CHDK firmware" on my S100 (FW: 1.01b).

*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: S100 porting thread
« Reply #148 on: 19 / July / 2012, 15:53:20 »
101a and 101b are different firmware. grep from German forum found the differences and compiles a running 101b version.

http://forum.chdk-treff.de/viewtopic.php?p=26046#p26046

Code: [Select]
    $ diff -r 101a 101b
    diff -r 101a/boot.c 101b/boot.c
    150c150
    < "    LDR     R0, =0xFF64BE6C \n"
    ---
    > "    LDR     R0, =0xFF64BECC \n"
    158c158
    < "    LDR     R1, =0x195D34 \n"
    ---
    > "    LDR     R1, =0x195D34 \n"
    Only in 101b: boot.c~
    Binary files 101a/boot.o and 101b/boot.o differ
    Only in 101b: copybin.sh
    Only in 101b: dumpelf.sh
    Binary files 101a/libplatformsub.a and 101b/libplatformsub.a differ
    Only in 101b: primary.asmdump
    Binary files 101a/PRIMARY.BIN and 101b/PRIMARY.BIN differ
    Only in 101b: primary.elf
    Only in 101b: stubs_entry.diff
    diff -r 101a/stubs_entry.S 101b/stubs_entry.S
    6c6
    < //   Firmware Ver GM1.01A
    ---
    > //   Firmware Ver GM1.01B
    22c22
    < // Firmware modemap table found @ff09cf84 -> ff099208 -> ff205770 -> ff3877c4 -> ff626550
    ---
    > // Firmware modemap table found @ff09cf84 -> ff099208 -> ff205770 -> ff3877c4 -> ff6265b0
    28,29c28,29
    < //DEF(levent_table                            ,0xff5905cc) // Found @0xff5905cc,          stubs_min = 0xff5905cc (0xff5905cc)
    < //DEF(FlashParamsTable                        ,0xff6267b4) // Found @0xff6267b4,          stubs_min = 0xff6267b4 (0xff6267b4)
    ---
    > //DEF(levent_table                            ,0xff59062c) // Found @0xff59062c,          stubs_min = 0xff59062c (0xff59062c)
    > //DEF(FlashParamsTable                        ,0xff626814) // Found @0xff626814,          stubs_min = 0xff626814 (0xff626814)
    106c106
    < NSTUB(ExecuteEventProcedure                   ,0xff08d868) //  1
    ---
    > NSTUB(ExecuteEventProcedure                   ,0xff08d868) //  2
    Binary files 101a/stubs_min.o and 101b/stubs_min.o differ
    diff -r 101a/stubs_min.S 101b/stubs_min.S
    5,6c5,6
    < DEF(levent_table                            ,0xff5905cc) // Found @0xff5905cc,          stubs_min = 0xff5905cc (0xff5905cc)
    < DEF(FlashParamsTable                        ,0xff6267b4) // Found @0xff6267b4,          stubs_min = 0xff6267b4 (0xff6267b4)
    ---
    > DEF(levent_table                            ,0xff59062c) // Found @0xff5905cc,          stubs_min = 0xff5905cc (0xff5905cc)
    > DEF(FlashParamsTable                        ,0xff626814) // Found @0xff6267b4,          stubs_min = 0xff6267b4 (0xff6267b4)
    Only in 101b: stubs_min.S~
    Only in 101a: .svn
    Only in 101b: t

Maybe he provides a complete patch file for the svn. I asked him.

msl
CHDK-DE:  CHDK-DE links

Re: S100 porting thread
« Reply #149 on: 19 / July / 2012, 16:54:25 »
Thanks..I guess there is hope

I am really new at this...the code you posted is what or goes where???

 

Related Topics


SimplePortal © 2008-2014, SimplePortal