SX60HS Porting - page 78 - DryOS Development - CHDK Forum

SX60HS Porting

  • 915 Replies
  • 212478 Views
Re: SX60HS Porting
« Reply #770 on: 16 / June / 2017, 15:42:26 »
Advertisements
SD card formatted several times.
 The card is missing CHDK.
 However, the clock from the CHDK application is sitting in the camera's memory.
 I can turn it on.
Shows time.
What to do with this ..
 Every older and newer CHDK application works the same. The CHDK menu can not be enabled..
Earlier, a few weeks earlier, CHDK worked well

Re: SX60HS Porting
« Reply #771 on: 16 / June / 2017, 15:47:32 »
@nico2008

Does the camera boot and operate normally when writelock on the SD card is disabled?
Is the SD card a single partition or multiple?

Re: SX60HS Porting
« Reply #772 on: 16 / June / 2017, 15:56:18 »
the camera works well. SD card is a single partition

Re: SX60HS Porting
« Reply #773 on: 16 / June / 2017, 16:08:24 »
If you load an older version of CHDK does everything work as it used to?

I think I'll try a completely fresh install on my camera and see if I have problems.  I've always just upgraded bit by bit. 

Can you take a picture of what you see when you try to boot chdk and post it?
Thanks for your effort. 


Re: SX60HS Porting
« Reply #774 on: 16 / June / 2017, 16:32:51 »
However, the clock from the CHDK application is sitting in the camera's memory.
If by some chance this is the clock you are seeing, it is not being produced by CHDK :
Ported :   A1200    SD940   G10    Powershot N    G16

*

Online reyalp

  • ******
  • 12112
Re: SX60HS Porting
« Reply #775 on: 16 / June / 2017, 16:33:22 »
SD card formatted several times.
 The card is missing CHDK.
 However, the clock from the CHDK application is sitting in the camera's memory.
 I can turn it on.
I don't really understand this. Maybe a picture would help.

If any part of CHDK appears after formatting, then the card wasn't really formatted, and CHDK is still running.

Have you checked that the playback button works normally when CHDK is not installed?

Don't forget what the H stands for.

Re: SX60HS Porting
« Reply #776 on: 16 / June / 2017, 22:21:56 »
@nico2008
I think I found the problem. There are several alternatives for the ALT key. I wiped my card and downloaded the installation package, and installed. The usual ALT key "Play" does not work as you say!  So I tried the alternatives, WIFI, VIDEO, ShortCut...
the ShortCut key appears to be the default.  This is the small button on top of the camera just to the left and rear of the jogdial behind the shutter. 
Once in Alt mode you can navigate to CHDK Settings/Alt mode button and change it to playback. 
Sorry for all the confusion!
I think I should find a way to make Play the default on fresh installs...its probably just the order of possibilities in platform_camera.h?


Edit: I've attached a CFG file that will set Play as the Alt button, copy it to the CHDK folder on the SD card
« Last Edit: 17 / June / 2017, 12:56:09 by 62ndidiot »

Re: SX60HS Porting
« Reply #777 on: 16 / June / 2017, 22:32:16 »
@reyalp, I think I should fix the default alt key problem for fresh installs asap.  Not sure of the procedure to update autobuild etc.  I suspect it's a very minor change so go ahead and make it for me if you prefer.  Let me know, thanks.


*

Online reyalp

  • ******
  • 12112
Re: SX60HS Porting
« Reply #778 on: 16 / June / 2017, 23:12:35 »
@reyalp, I think I should fix the default alt key problem for fresh installs asap.  Not sure of the procedure to update autobuild etc.  I suspect it's a very minor change so go ahead and make it for me if you prefer.  Let me know, thanks.
The default alt key appears to be playback in the port (it's first in CAM_ALT_BUTTON_OPTIONS), so I think you'll need to debug it. The most obvious way for this to happen would be if the bits were identified wrong in they keymap.

The autobuild updates whenever something is checked in.
Don't forget what the H stands for.

Re: SX60HS Porting
« Reply #779 on: 17 / June / 2017, 13:06:51 »
Quote
The default alt key appears to be playback in the port (it's first in CAM_ALT_BUTTON_OPTIONS), so I think you'll need to debug it. The most obvious way for this to happen would be if the bits were identified wrong in they keymap.
Yet, it works correctly, once selected. KEY_SHORTCUT is the same as KEY_PRINT in CHDK and I believe the mask is correct. See attached spreadsheet which calculates the mask. I'm wondering if I have one too many alternatives defined. Nope that does not fix it, still defines Shortcut.  Now I'll play with the order, and see if its always Shortcut

Edit: Seems to always be KEY_SHORTCUT  0x4000 independent of order and what comes first, KEY_PLAYBACK is 0x10000. Mask is 0x00056FFF which allows both of these to be seen as far as I can tell.

Code: [Select]
#define KEYS_MASK0 (0x00056fff)
//#define KEYS_MASK0 (0x00050fff)
#define KEYS_MASK1 (0x00000000)
#define KEYS_MASK2 (0x0000001e)

Code: [Select]
KeyMap keymap[] = {
    { 0, KEY_SHOOT_FULL      ,0x00040001 }, // Found @0xfc5cfb3c, levent 0x01
    { 0, KEY_SHOOT_HALF      ,0x00040000 }, // Found @0xfc5cfbc4, levent 0x00
    { 0, KEY_SHOOT_FULL_ONLY ,0x00000001 }, // Found @0xfc5cfb3c, levent 0x01
    { 0, KEY_VIDEO           ,0x00000008 }, // Found @0xfc5cfb54, levent 0x02
    { 0, KEY_MENU            ,0x00000010 }, // Found @0xfc5cfb5c, levent 0x14
    { 0, KEY_UP              ,0x00000020 }, // Found @0xfc5cfb64, levent 0x06
    { 0, KEY_DOWN            ,0x00000040 }, // Found @0xfc5cfb6c, levent 0x07
    { 0, KEY_RIGHT           ,0x00000080 }, // Found @0xfc5cfb74, levent 0x09
    { 0, KEY_LEFT            ,0x00000100 }, // Found @0xfc5cfb7c, levent 0x08
    { 0, KEY_SET             ,0x00000200 }, // Found @0xfc5cfb84, levent 0x0a
    { 0, KEY_ERASE           ,0x00000400 }, //found by testing
    { 0, KEY_WIFI            ,0x00002000 }, // found by testing
    { 0, KEY_FACE            ,0x00000800 },
    { 0, KEY_PRINT           ,0x00004000 },  // this is Shortcut
    { 0, KEY_FRAMING_ASSIST  ,0x00000002 },
    { 0, KEY_ZOOM_ASSIST     ,0x00000004 },
    { 0, KEY_PLAYBACK        ,0x00010000 }, // Found @0xfc5cfbb4, levent 0x101
//    { 0, KEY_POWER           ,0x00020000 }, // Found @0xfc5cfbbc, levent 0x100
    { 2, KEY_ZOOM_OUT        ,0x00000008 }, // full speed


Obviously, I am missing something that in hindsight will be "obvious".  :blink:
« Last Edit: 17 / June / 2017, 13:33:29 by 62ndidiot »

 

Related Topics