G11 porting - page 43 - DryOS Development - CHDK Forum

G11 porting

  • 530 Replies
Re: G11 porting
« Reply #420 on: 17 / March / 2010, 07:16:52 »
I never used "CameraVersion" to get the firmware version until now, i only know the "Firmware info" method in the wiki (http://chdk.wikia.com/wiki/G11). But if "CameraVersion" works correct, it looks like you have a very old firmware version: 1.00A
You can simply try if one of the allready available g11 chdk ports is working for your camera/fw-version. If none of the ports work, and your camera freezes, shuts down or does not start at all, dont worry, simply remove the battery and the set sd-card switch back to R/W and your g11 is back to normal, because chdk does not change/overwrites the original canon firmware. It is only copied from sd-card to RAM and runs directly out of the RAM.

If no of the available ports works, then i think another port for 1.00A is needed. For that case, it is necessary to get a dump of your 1.00A firmware. For this, use the modified udumper (you can find the link in the chdk g11 wiki) and upload the fw dump please.

Yeah, my G11 is from like immediately after it came out. It arrived in late November.

I'll confirm my version number using the ver.req method and then give F, J, and K a go.

Thank you! :)
« Last Edit: 17 / March / 2010, 07:19:36 by Viper007Bond »


Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #421 on: 17 / March / 2010, 07:59:24 »
Okay, if you really have 1.00A on your camera, i think it is enough to test the "closest" firmware version port 1.00F. The chance that the newer ones are working on 1.00A is very, very small (allmost 0% ;) ).

Please make also a dump of your 1.00A fw version, it is needed anyway for a dedicated 1.00A port, if 1.00F is not working.
For this, e.g use cardtricks under windows: Use the "NewDryOs" Button to create a udumper sd-card, an then replace the diskboot.bin on the sd-card with this one: http://chdk.setepontos.com/index.php/topic,4647.msg46175.html#msg46175. Then run the sd-card on the G11. Finally use the "strings" button to check if you have got a non-zero dump file on the sd-card and then use the "Clean" button to create a cleaned up version of the dump file.
« Last Edit: 17 / March / 2010, 08:10:47 by ERR99 »

Re: G11 porting
« Reply #422 on: 17 / March / 2010, 09:02:32 »
I am running the 1.00L diskboot.bin and I am getting a crash (camera turns off) when running the Time-Lapse Lua script from the SDM common files.  I tried following the instructions for a "save ROMLOG.txt file" but the options was no in the debug parameters menu.

Anyways, the script runs until the shutter is about to open and the camera shuts off.

If I can be of any more help, please let me know.

Thanks for all the great work!!!!

Re: G11 porting
« Reply #423 on: 17 / March / 2010, 09:32:38 »
Welcome !

There are no Lua scripts in the SDM Common_files.zip.

I guess you are using CHDK as there is no SDM 1.00L  version yet.

The SDM time_lapse.bas will not work with CHDK.

Re: G11 porting
« Reply #424 on: 17 / March / 2010, 16:38:58 »
Opps.  Yea time-lapse.bas.  Sorry, I saw all the other Lua scripts and "[admin: avoid swearing please]-u-me-d" that it was Lua as well.  While I am not directly interested in 3D with a Canon, I AM interested in time-lapse.

Can a more basic functioning script be written to support time-lapse photography?


Re: G11 porting
« Reply #425 on: 18 / March / 2010, 05:50:59 »
The SDM time_lapse.bas is a very powerful script, but you will have to wait until the 1.00L version is available before you can try that.

A lot of CHDK users use this script :-



Offline fe50

  • ******
  • 3147
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: G11 porting
« Reply #426 on: 18 / March / 2010, 07:39:10 »
I AM interested in time-lapse.
You may also be interested in these Lua scripts for CHDK:

* http://chdk.wikia.com/wiki/LUA#Minimalistic_Intervalometer (Minimalistic Intervalometer)
* http://chdk.wikia.com/wiki/LUA#yet_another_accurate_intervalometer (yet another accurate intervalometer)
* http://chdk.wikia.com/wiki/User:Fe50#double_intervalometer (my double intervalometer)


Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #427 on: 18 / March / 2010, 16:44:05 »
So, what say the testers? Is the 1.00L port working well enough to integrate/add the port to the SVN so it can be part of the autobuild?
Or are there any serious problems left?  ::)


Offline KaLi

  • *
  • 21
  • G11 CHDK, FinePix Real 3d W1, 2*A460 SDM, S50, S40
Re: G11 porting
« Reply #428 on: 20 / March / 2010, 06:52:32 »
I have some kind of feature request for the G11...

In "Quick Shot" mode, the CHDK display enhancements overlay the Canon "quick settings" menu... it would be a good idea, if the chdks display enhancements would be fully deactivated, when the camera is set to "Quick Shot". As it is now, "Quick Shot" is rather useless, when chdk is booted.

Any comments?
any bad photo is much better than any photo not shot...

Re: G11 porting
« Reply #429 on: 20 / March / 2010, 07:11:28 »
Sorry I have not responded earlier, but I have been playing with my G11 and my time lapse script!!!

I have not tried all the functions for the 1.00L, but the ones I have tried seem to work.  I don't know about other versions, but the chdk menu seems to disappear a LOT on my camera.  I know it was an issue but it makes it REAL hard to use as I have to keep rotating the dial back and forth to keep the menu up sometimes.

Also it seems that I have to press the "Alt" button a few times to bring up the chdk menu--again it could be related to the menu not displaying (or displaying and disappearing).

Other than that, of the fuctions I have tried, they have worked--temp, icon locations, scripts, reversi ect.  I have not used any overrides other than the superfine jpg options.

So, my recomendation is YES it is ready for integration to the SVN.  I will keep testing functions as I learn about them and report any thing I find.

Again, THANKS for all the hard work ERR99.  I know how much (or at least have a good idea) how much effort and work you and Microfunguy have put into this project and a lot of it goes un or underappriciated.


Related Topics