ELPH300HS aka IXUS220HS - Porting Thread - page 39 - DryOS Development - CHDK Forum

ELPH300HS aka IXUS220HS - Porting Thread

  • 899 Replies
  • 406168 Views
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #380 on: 30 / November / 2011, 00:33:52 »
Advertisements
I can’t find any information about changes in CHDK for Ixus220.

What with manual mode, like extended range of shutter speeds, shutter priority, 1/1000s, EV comp, auto focus and others?

BTW Is it possible to block video exposure and solve limit of 10 minutes for hd movies?

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #381 on: 30 / November / 2011, 02:50:21 »
Comparing the 1.01c, 1.01d and 1.01e firmware dumps it looks like they are all compatible with the 1.01c CHDK version.

I have added 1.01d and 1.01e to the autobuild as copies of 1.01c.

Also fixed a couple of entries in stubs_min.S for the 1.01a and 1.01c versions.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline Sektor

  • *
  • 13
  • ixus220_elph300hs-101a
    • Grand Theft Media Press
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #382 on: 30 / November / 2011, 04:19:35 »
Thanks for this. Great job! I have v1.01A. I had never installed CHDK on any other cameras before.

edit: removed my feature request since it was off topic and I don't want it clogging search results
« Last Edit: 30 / November / 2011, 08:51:11 by Sektor »

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #383 on: 30 / November / 2011, 07:13:38 »
I'd love an option to automatically create a new file when the 4GB limit is reached and keep recording.
Scripts to do that have been posted several times on this forum.   Use the search box at the top of the page - this has been a popular request.   (hint :  video time limit)
« Last Edit: 30 / November / 2011, 07:46:12 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #384 on: 30 / November / 2011, 08:06:27 »
Here's the values I get on 1.01c going down the modes:

These values are all the same on 1.01a.

I should add that Auto is mode 32768

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #385 on: 30 / November / 2011, 08:25:40 »
I've been chasing the flicker problem - it's really bad in Auto mode, when the moving focus box clobbers the CHDK menu, but it's noticeable whenever Canon's OSD updates change. 

I've compared lib.c for various cameras and I've seen two flavors of vid_bitmap_refresh().  One flavor, used with the sx230hs, calls _LockAndRefresh() / _UnlockAndRefresh().  I notice our lib.c looks very very similar to that one, only we have _ScreenLock() / _ScreenUnlock() primitives instead.  But other cameras that use these - for instance, sx40hs, have an active_viewport_buffer in stubs_min.S, and a vid_get_viewport_live_fb function in lib.c. 

So I'm guessing we need to find active_viewport_buffer in memory, so we can enable double-buffered drawing for CHDK?

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #386 on: 30 / November / 2011, 09:46:41 »
I've compared lib.c for various cameras and I've seen two flavors of vid_bitmap_refresh().  One flavor, used with the sx230hs, calls _LockAndRefresh() / _UnlockAndRefresh().  I notice our lib.c looks very very similar to that one, only we have _ScreenLock() / _ScreenUnlock() primitives instead.  But other cameras that use these - for instance, sx40hs, have an active_viewport_buffer in stubs_min.S, and a vid_get_viewport_live_fb function in lib.c. 

Here's a simple hack I've used during the early part of porting a new camera.

Code: [Select]
extern unsigned int screen_width, screen_height, screen_size;
extern void draw_filled_rect( int, int, int, int, int );

void vid_bitmap_refresh()
{
draw_filled_rect(0, 0, screen_width, screen_height, 0x00) ;
}

Does that fix the problem ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #387 on: 30 / November / 2011, 10:05:42 »

Here's a simple hack I've used during the early part of porting a new camera.

Code: [Select]
extern unsigned int screen_width, screen_height, screen_size;
extern void draw_filled_rect( int, int, int, int, int );

void vid_bitmap_refresh()
{
draw_filled_rect(0, 0, screen_width, screen_height, 0x00) ;
}

Does that fix the problem ?

Doesn't seem to make a difference.


*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #388 on: 30 / November / 2011, 10:29:32 »
Here's the values I get on 1.01c going down the modes:

These values are all the same on 1.01a.

I should add that Auto is mode 32768

Thanks, guys!  :)

I can confirm the same values for 1.00c.

Attached you'll find new shooting.c file.

Update:
stubs_entry.S is now only complaining about three modemap entries:
// Mode 33320 in firmware but not in current modemap
// Mode 33322 in firmware but not in current modemap
// Mode 32792 in firmware but not in current modemap

If they are the same as in ELPH500 than these could be:
    { MODE_SCN_FACE_SELF_TIMER, 33320 },
    { MODE_SCN_WINK_SELF_TIMER, 33322 },
    { MODE_SCN_FIREWORK,        32792 },

Does that mean we could be able to use e.g. the WinkSelfTimer?
Modemaps are available in Firmware but we cannot activate them via standard Canon Firmware.

« Last Edit: 30 / November / 2011, 13:37:36 by tommi2water »

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #389 on: 30 / November / 2011, 10:48:58 »
    { MODE_SCN_FACE_SELF_TIMER, 33320 },
    { MODE_SCN_WINK_SELF_TIMER, 33322 },
    { MODE_SCN_FIREWORK,        32792 },

Does that mean we could be able to use e.g. the WinkSelfTimer?
Modemaps are available in Firmware but we cannot activate them via standard Canon Firmware.

I believe the ELPH300 combines face self timer and wink self timer into the "smart shutter" mode.

Odd that fireworks mode is missing.  It appears Canon must have taken it out, because it's in some documentation.

[Edit: fireworks mode may only be selectable automatically, if the camera detects fireworks.  landscape mode is gone too, but I've seen the camera put the landscape icon up during auto mode.]
« Last Edit: 30 / November / 2011, 10:51:26 by jstanley0 »

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal