SX30 IS porting thread - page 7 - General Discussion and Assistance - CHDK Forum
supplierdeeply

SX30 IS porting thread

  • 115 Replies
  • 58053 Views
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX30 IS porting thread
« Reply #60 on: 09 / December / 2010, 05:04:18 »
Advertisements
I think this is ready to release as a beta - what's the recommended way to make it available?
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)

Re: SX30 IS porting thread
« Reply #61 on: 09 / December / 2010, 05:33:14 »
Does the capture task jump to wait_until_button_released ?

If so, how did you find-out where to insert it in the caprure code, it will help Waldo with the S95 ?

David

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX30 IS porting thread
« Reply #62 on: 09 / December / 2010, 06:17:48 »
Does the capture task jump to wait_until_button_released ?

If so, how did you find-out where to insert it in the caprure code, it will help Waldo with the S95 ?

David

No I'm not calling that function (yet).
The SX30 capture code seems a bit different from the other cameras I was using as reference (SX20 & S95).
I found a place to call 'capt_seq_hook_raw_here' by trial and error - have not tried to call 'wait_until_remote_button_is_released' or 'capt_seq_hook_set_nr' yet.

Regards,
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)

Re: SX30 IS porting thread
« Reply #63 on: 09 / December / 2010, 06:24:24 »
If you display the disassembly in IDA graph view you should be able to see LOTS of message-handling branches for the capture code.

You need to find the one where the image is actually captured and then where in that branch you can pause it just before capture (but after screen blanking and preflash).


Deavid


*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX30 IS porting thread
« Reply #64 on: 10 / December / 2010, 07:27:12 »
If you display the disassembly in IDA graph view you should be able to see LOTS of message-handling branches for the capture code.

You need to find the one where the image is actually captured and then where in that branch you can pause it just before capture (but after screen blanking and preflash).


Deavid

I managed to find a place where the 'wait_until_remote_button_is_released' seems to work ok - again it was by trial and error in the capture code, although I had already found where the pre-flash fired so I knew roughly where to start.

Back to my previous question - any recommendations on the best method to publish the beta version?

Regards,
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 whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: SX30 IS porting thread
« Reply #65 on: 10 / December / 2010, 08:21:56 »
Hi,
Long standing member mariush wrote (here)
Quote
As I said some time ago, if there's a need for someone to host chdk related stuff like this forum, I have a dedicated server with plenty of resources available and I'm willing to host it for as long as needed...
his site is here: http://savedonthe.net/

Or use the cloud: Google Code, or box.net

hth,

wim

PS Of course there is no "best" way - just use whatever works best for you   :D
« Last Edit: 10 / December / 2010, 08:25:56 by whim »

Re: SX30 IS porting thread
« Reply #66 on: 10 / December / 2010, 08:46:03 »
Phil,

I was following your progress and I am interested in trying the beta. When you post it, can you specify what features are ready to test and what things are you looking for?

Thanks for your work.

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX30 IS porting thread
« Reply #67 on: 11 / December / 2010, 00:13:29 »
Beta posted to Google Code.
New topic created under CHDK Releases with release notes and links:
http://chdk.setepontos.com/index.php?topic=5900.0
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)


Re: SX30 IS porting thread (vid_bitmap_refresh)
« Reply #68 on: 11 / December / 2010, 23:54:37 »
philmoz :   Did you ever find a solution to the issues with vid_bitmap_refresh() that we discussed in http://chdk.setepontos.com/index.php?topic=5789.0 ?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX30 IS porting thread
« Reply #69 on: 12 / December / 2010, 03:12:24 »
philmoz :   Did you ever find a solution to the issues with vid_bitmap_refresh() that we discussed in http://chdk.setepontos.com/index.php?topic=5789.0 ?


I was able to find the functions and variables that got it working reasonably well as below - CHDK screen gets erased sometimes; but a keypress brings it back. I found similar code in the firmware dump.

Code: [Select]
extern void _LockAndRefresh(); // wrapper function for screen lock
extern void _UnlockAndRefresh(); // wrapper function for screen unlock

_LockAndRefresh();

//enabled_refresh_physical_screen=1;
full_screen_refresh |= 3; //found in ScreenUnlock underneath a CameraLog.c call sub_FFA02598

_UnlockAndRefresh();

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)

 

Related Topics