Debug action on G15 - General Help and Assistance on using CHDK stable releases - CHDK Forum  
« previous next »
Pages: [1]   Go Down

Debug action on G15

  • 6 Replies
  • 2214 Views
*

Offline buttim

  • *
  • 45
Debug action on G15
« on: 01 / October / 2013, 09:43:24 »
Advertisements
I'm bumping my head but can't find the way to trigger the "debug action" on my Powershot G15.
The menu help says Erase Alt +/-. I tried  to configure the Alt button to each and every different possibility but had no luck in finding the magical Erase Alt combination. Needless to say the camera does not have a +/- button.
Anybody can help?
Logged
*

Offline srsa_4c

  • ******
  • 4416
Re: Debug action on G15
« Reply #1 on: 01 / October / 2013, 10:27:50 »
Quote from: buttim on 01 / October / 2013, 09:43:24
I'm bumping my head but can't find the way to trigger the "debug action" on my Powershot G15.
The menu help says Erase Alt +/-. I tried  to configure the Alt button to each and every different possibility but had no luck in finding the magical Erase Alt combination. Needless to say the camera does not have a +/- button.
Anybody can help?
The keymap of the port is a bit incomplete. See platform/g15/kbd.c .
You could try to work out the missing buttons, especially KEY_ERASE. I think the KEY_DISPLAY alias should be removed from the map, as that button is the "DOWN" button.
To let CHDK know that the cam doesn't have a dedicated DISP button add
#undef  CAM_HAS_DISP_BUTTON
to the port's platform_camera.h
To visualize physw_status, uncomment the "debug keymap, KEYS_MASKx, SD_READONLY_FLAG, USB_MASK" block in core/gui_osd.c (search for the string).
Logged
*

Offline buttim

  • *
  • 45
Re: Debug action on G15
« Reply #2 on: 01 / October / 2013, 13:03:11 »
Thanks. I successfully located the unmapped buttons and added the defines.
I was also able to change the debug action shortcut to something useful.
Would you suggest posting the (quite simple) changes?
Logged
*

Offline srsa_4c

  • ******
  • 4416
Re: Debug action on G15
« Reply #3 on: 01 / October / 2013, 13:41:16 »
Quote from: buttim on 01 / October / 2013, 13:03:11
Would you suggest posting the (quite simple) changes?
Post the patch in this thread: http://chdk.setepontos.com/index.php?topic=650.0
Logged
*

Offline philmoz

  • *****
  • 3325
    • Photos
Re: Debug action on G15
« Reply #4 on: 01 / October / 2013, 15:58:53 »
Quote from: buttim on 01 / October / 2013, 13:03:11
Thanks. I successfully located the unmapped buttons and added the defines.
I was also able to change the debug action shortcut to something useful.
Would you suggest posting the (quite simple) changes?

Have a look at the G1X solution - it has the same button layout as the G15.
I used the METER button as DISP to avoid the conflict with DOWN.

The G15 has an ERASE button so I'm not sure why there would be a problem with the debug action.

Phil.
Logged
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 buttim

  • *
  • 45
Re: Debug action on G15
« Reply #5 on: 01 / October / 2013, 16:23:45 »
Other cameras define the KEY_METERING button so it seems more logical to put in the definition in kbd.c

Code: [Select]
static KeyMap keymap[] = {
    { 0, KEY_METERING     ,0x00000400 },
    ...
and add the following lines in platform_camera.h

Code: [Select]
#undef CAM_HAS_DISP_BUTTON
#define SHORTCUT_TOGGLE_RAW       KEY_METERING
« Last Edit: 01 / October / 2013, 17:13:53 by buttim »
Logged
*

Offline philmoz

  • *****
  • 3325
    • Photos
Re: Debug action on G15
« Reply #6 on: 01 / October / 2013, 18:07:56 »
Quote from: buttim on 01 / October / 2013, 16:23:45
Other cameras define the KEY_METERING button so it seems more logical to put in the definition in kbd.c

Code: [Select]
static KeyMap keymap[] = {
    { 0, KEY_METERING     ,0x00000400 },
    ...
and add the following lines in platform_camera.h

Code: [Select]
#undef CAM_HAS_DISP_BUTTON
#define SHORTCUT_TOGGLE_RAW       KEY_METERING

The problem is that DISP is wired to a number of functions in the code and it's easier to use CHDK if you have a dedicated button for it. It's on the list of things that need fixing.

Phil.
Logged
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)
Pages: [1]   Go Up
« previous next »
 

Related Topics