ELPH300HS aka IXUS220HS - Porting Thread - page 24 - DryOS Development - CHDK Forum
supplierdeeply

ELPH300HS aka IXUS220HS - Porting Thread

  • 899 Replies
  • 399389 Views
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #230 on: 26 / November / 2011, 10:42:41 »
Advertisements
So I copied the CHDK folder on the card and got into the ALT menu and tried out some stuff.

The shutter speed override didn't work for me either.

I did play around with stuff like the live histogram, the OSD layout editor, the filebrowser and loaded the text editor script, which seemed to work quite okay.
What's with the flicker? That's the most annoying thing at this point :P

After that my battery died so I have to wait for it to charge now.

Great work guys! I'm really happy seeing CHDK running on my camera! :)

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #231 on: 26 / November / 2011, 10:46:11 »
btw: I only used CHDK-PT the way to save instruction sequences and load them into Notepad++ for comparison with my boot.c code. Maybe CHDK-PT has much more power to do some work for you? Waterwingz will know more about CHDK-PT usage.

Once you have a ported version of the firmware,  CHDK-PT can help with a port to a different firmwared in three ways:
  • you can use it as a dissassembler that outputs each line in a format that can be directly compiled by gcc (the compiler used in the CHDK build chain).
  • you can use it to automatically translate the addresses in your stubs_entry_2.S file (although you should look at the resulting code to make sure it makes sense).  Use the Stubs button in the Convert box.
  • you can use it to extract the source for all the routines from boot.c,  movie_rec.c and capt_seq.c for the firmware of a different  firmware model.  This does all the address translation for you - no funny bugs for accidentally missing one address.  Use the Address List button in the Convert box.
Sometime people have trouble with the Address List concept. Let me know if you are interested and I will create an example list file for this camera.
« Last Edit: 26 / November / 2011, 10:54:40 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #232 on: 26 / November / 2011, 10:50:21 »
The shutter speed override didn't work for me either.
This is to be expected. Most shooting related functions will not work until the code in capt_seq.c has been completed.  Likewise, the ability to mechanically zoom in movie mode will not work until the code in movie_rec.c has been completed.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #233 on: 26 / November / 2011, 11:09:13 »
Of course you would have figured it out, too! But why not saving some time.  ;)

Why did I provide my current status also to other firmware like 1.01a and 1.01c? I know that some people are out there which own cameras with these firmware versions. These people should take this software as starting point for their investigations

Oh, don't get me wrong.  I agree wholeheartedly with that sentiment.  This isn't a race.  I just missed that breakthrough, but I'm sure I'll have other opportunities!


*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #234 on: 26 / November / 2011, 11:18:16 »
Oh, don't get me wrong.  I agree wholeheartedly with that sentiment.  This isn't a race.  I just missed that breakthrough, but I'm sure I'll have other opportunities!

I didn't!  :)

btw: I think I found capt_seq_task() stuff at address FF882920 in each of 1.00c/1.01a/1.01c firmwares.  :)

Code: [Select]
void __attribute__((naked,noinline)) capt_seq_task() {
// FF882920

asm volatile (

"STMFD SP!, {R3-R9,LR}\n"
"LDR R5, =0x3D48C\n"
"LDR R7, =0x2E28\n"
"MOV R6, #0\n"

"loc_FF074F2C:\n"
"LDR R0, [R7,#4]\n"
"MOV R2, #0\n"
"MOV R1, SP\n"
"BL sub_FF83B5B4\n"
"TST R0, #1\n"
"BEQ loc_FF88295C\n"
"LDR R1, =0x476\n"
"LDR R0, =0xFF882448\n" // aSsshoottask_c at 0xFF882448
"BL _DebugAssert\n"
"BL _ExitTask\n"
"LDMFD SP!, {R3-R9,PC}\n"

Maybe someone else would like to take over capt_seq.c file and work on this?


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #235 on: 26 / November / 2011, 12:00:51 »
why does the battery drain so quickly while running chdk?

*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #236 on: 26 / November / 2011, 12:14:17 »
why does the battery drain so quickly while running chdk?

Maybe the Battery Max/Min voltage setting is wrong?

Look at the photo from jstanley (http://chdk.setepontos.com/index.php?topic=6341.msg76596#msg76596). Canon battery icon shows "Battery Full" and CHDK battery information shows only 47%. Maybe it's only a settings issue.

Interesting thread on battery power: http://chdk.setepontos.com/index.php?topic=379.0

Which version are you using? I'm still interested in feedback from 1.01c firmware users.  :)
« Last Edit: 26 / November / 2011, 12:19:32 by tommi2water »

*

Offline sush

  • *
  • 29
  • ixus220 300hs firmware 1.01c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #237 on: 26 / November / 2011, 12:16:34 »
Excellent work, Tommi!!   I will download and try it out.


*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #238 on: 26 / November / 2011, 12:17:44 »
Excellent work, Tommi!!   I will download and try it out.

I will cross my fingers that it works an 1.01c as well! :)

*

Offline sush

  • *
  • 29
  • ixus220 300hs firmware 1.01c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #239 on: 26 / November / 2011, 12:23:06 »
fantastic!  :)  chdk screen comes up but I have not tried much else yet. 

Edit - works in autoboot mode too!
« Last Edit: 26 / November / 2011, 12:24:52 by sush »

 

Related Topics