SX60HS Porting - page 80 - DryOS Development - CHDK Forum

SX60HS Porting

  • 915 Replies
  • 204464 Views
Re: SX60HS Porting
« Reply #790 on: 17 / June / 2017, 19:18:57 »
Advertisements
The shortcut key on the SX60HS is difficult to access and use IMO. It is recessed and requires a careful touch and it is not intuitively obvious what it's function is without reading the manual (at least to someone like me).    Recent documentation always talks about the Play key as Alt. It does not readily occur to users of this port to try the shortcut key as ALT...it is a bug which should be fixable in a completely backwardly compatible manner...in fact I could probably force it to work correctly by hacking some Sx60 code, but I'd rather not.

Maybe @nico2008 has an opinion?
:)

Re: SX60HS Porting
« Reply #791 on: 17 / June / 2017, 19:27:52 »
Thanks for the help .. the CCHDK4.CFG (1.2 kB)  file has helped. When there is a clock on the display, then press PLAY to turn ALT on. Works correctly . Screen shot of SX 60 hs (f) with CHDK :)
« Last Edit: 17 / June / 2017, 19:33:26 by nico2008 »

*

Offline reyalp

  • ******
  • 11923
Re: SX60HS Porting
« Reply #792 on: 17 / June / 2017, 19:42:59 »
Thanks for the help .. the CCHDK4.CFG (1.2 kB)  file has helped. When there is a clock on the display, then press PLAY to turn ALT on. Works correctly . Screen shot of SX 60 hs (f) with CHDK :)
This clock is part of the original Canon firmware, and not connected to CHDK. You should not need to activate the clock to use CHDK.

Normally, the clock is shown when you hold down FUNC SET. There's no need to do this to access CHDK.
Don't forget what the H stands for.

Re: SX60HS Porting
« Reply #793 on: 17 / June / 2017, 19:44:01 »
Thanks @nico2008! Your testing uncovered a bug in CHDK!


Re: SX60HS Porting
« Reply #794 on: 17 / June / 2017, 19:59:37 »
Here is a link to the latest zip's for SX60HS (100b,c,f)

Edit: the original files in this link had ShortCut as the default ALT key, I've added versions that default to PLAY (but they do not have the option to use ShortCut, your choice)

https://goo.gl/adBB59

If you've already downloaded from
this post on May 13, 2017 and things are working ok for you, no need to download again, this only allows for the firmware to default to using PLAY as the ALT-KEY in CHDK if none is previously defined.

Re: SX60HS Porting
« Reply #795 on: 18 / June / 2017, 05:44:43 »
I, too, thank you for your help :)

Re: SX60HS Porting
« Reply #796 on: 18 / June / 2017, 10:54:10 »
I'll look into fixing this, but it needs some thought to ensure that people who load an older build don't end up with no alt key defined.

tl;dr: the SX60hs is the only camera that will "break"

I did some grepping and spreadsheet merging today to figure this out.

There are 142 cameras that I looked at (sx270/sx275 removed) based on my latest svn update.  Of those cameras, 91 have a KEY_PRINT definition in their keymap and 89 cameras have CAM_ADJUSTABLE_ALT_BUTTON defined. Only 48 have both and so might be "at risk".

I combined things in the shreadsheet - looking through platform/kdb.c & platform/platform_camera.h as required.

And I was only able to find one camera actually "at risk" - the sx60hs.

At risk means :
  • KEY_PRINT is defined in the keymap
  • CAM_ADJUSTABLE_ALT_BUTTON is defined
  • KEY_PRINT is not the first element in CAM_ALT_BUTTON_OPTIONS

I eliminated cases where KEY_PRINT was aliased in the keymap with other keys (typically KEY_PLAYBACK - see A1200 for an example) and cases where the camera has a shortcut key but the port calls that KEY_PRINT.

Conclusion : fixing this so that if CAM_ALT_BUTTON_OPTIONS is defined then its first element goes into CONF_INFO rather than KEY_PRINT will not change the behavior of any current port.
« Last Edit: 18 / June / 2017, 10:56:49 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX60HS Porting
« Reply #797 on: 19 / June / 2017, 17:32:07 »
Greetings!

I am new to the forum and a first time user of CHDK.

I have successfully prepared my SD card:

Card: Sandisk SDHC 8GB ( FAT32)

Software: OS = Windows 7 x64. ACID.jar (non-elevated) to download and STICK.jar (elevated) to prepare card. JAR files were executed with jPortable.

CHDK files: Trunk CHDK\sx60hs-100b ( Cam bought on 29-Sep-2014, INDIA/ASIA )

Awesome! Thanks to everyone involved.  :)


Re: SX60HS Porting
« Reply #798 on: 20 / June / 2017, 00:36:57 »
Welcome to CHDK!  I hope you find many useful and interesting ways to use this software.

Re: SX60HS Porting
« Reply #799 on: 28 / June / 2017, 17:38:25 »
Testing HOTSHOE override.  Described here:

https://chdk.setepontos.com/index.php?topic=9969.msg133586#msg133586

First watched in kbd.c for which bit gets set when something is inserted in the shoe:

Code: [Select]
00018040: StartRedirectUART
00018050: Printf
00018100: UI:LogicalEvent:0x00001184:adr:0,Para:0
00018190: UI:VTMLock
00018190: UI:VTMUnLock
00021490: kb: 00077fff 20808830 1480043e
00021500: kb: 00077fff 20808830 1480043e
00021510: kb: 00077fff 20808830 1480043e
00021510: UI:Button:0x000010B5:MountExtFlash
Evidently HOTSHOE_IDX = 2 and HOTSHOE_FLAG = 0x00000800
because the middle word defaults to 0x20808030 (when idle)
I see there are apparently two possible settings for the CAM_HOTSHOE_OVERRIDE 1 or 2 ?

Test exposure in CHDK short exp to 1/2000
Camera setting to 1/100
Camera respects CHDK setting even when the hotshoe is occupied.

Not sure if this means I can ignore the setting for now. @waterwingz?

 

 

Related Topics