D10 porting thread - page 10 - DryOS Development - CHDK Forum supplierdeeply

D10 porting thread

  • 131 Replies
  • 60457 Views
Re: D10 porting thread
« Reply #90 on: 09 / February / 2011, 16:34:53 »
Advertisements
Thanks, reyalp. I think I graduated from "clueless newbie" to "just plain newbie." I got the software installed, and it boots into CHDK, so perhaps it just works. I'll start playing with the software. If you do want a firmware dump, let me know and I'll try to find time to do it. I was a programmer, but am not sure I have the time to do this right now.

*

Offline reyalp

  • ******
  • 13432
Re: D10 porting thread
« Reply #91 on: 09 / February / 2011, 16:47:39 »
Thanks, reyalp. I think I graduated from "clueless newbie" to "just plain newbie." I got the software installed, and it boots into CHDK, so perhaps it just works. I'll start playing with the software. If you do want a firmware dump, let me know and I'll try to find time to do it. I was a programmer, but am not sure I have the time to do this right now.
If the 100a build boots and works, it should be fine, we can just make a copy of 100a to 100b in the autobuild. There's very small chance that some entry points are different, but AFAIK this has never happened on any of the previous versions that are able to share CHDK builds.

Having a dump for future reference might be useful, but it's not urgent.
Don't forget what the H stands for.

Re: D10 porting thread
« Reply #92 on: 25 / February / 2011, 05:09:33 »
Thanks for the great progress on the beta firmware!
My 100A D10 boots and runs CHDK, but:
a) there's continuous redraw flicker between the CHDK text & icons, and the D10's displayed items.  It's better in Program mode (smaller icon), and after turning off all D10 display (except for the "P", of course).  Are other people experiencing this?

b) the CHDK text and menus all appear as dark blue.  Is this usual?  Is it easily changeable?

c) After running Ultra Intervalometer several times, and taking about 20 photos, the D10 no longer powers up completely - it crashes(immediately shuts off after powerup) unless I un-write-protect the SD card.  This may have something to do with the script parameters saved by CHDK, and that I have scripting set to autostart. 

d) Assuming that (c) can be fixed or worked around, is it possible to turn off and leave off the LCD display in the D10?  For tripod-mounted intervalometry, there's no need for the display at all.

e) Is it possible to disable focusing, or lock focusing?  There's no need for it during interval shooting.
Thanks again.

*

Offline reyalp

  • ******
  • 13432
Re: D10 porting thread
« Reply #93 on: 25 / February / 2011, 21:53:11 »
Thanks for the great progress on the beta firmware!
My 100A D10 boots and runs CHDK, but:
a) there's continuous redraw flicker between the CHDK text & icons, and the D10's displayed items.  It's better in Program mode (smaller icon), and after turning off all D10 display (except for the "P", of course).  Are other people experiencing this?
If I've understood your description correctly, this is normal. CHDK display and canon display don't play well together. I suggest adjusting CHDK settings in playback mode where possible.

Quote
b) the CHDK text and menus all appear as dark blue.  Is this usual?  Is it easily changeable?
Menu colors can be adjusted in "visual settings" in the chdk menu, however, the color of a specific item will change depending on what the canon firmware does with the palette. Not much we can do about this.

On my camera, in playback mode the menus are white, in record mode they start medium gray, unless you go to auto mode, then they turn blue. I'll take a look into this and see if I can find a better color for the menu.

I also noticed "draw palette" crashed... another thing to look into.
Quote
c) After running Ultra Intervalometer several times, and taking about 20 photos, the D10 no longer powers up completely - it crashes(immediately shuts off after powerup) unless I un-write-protect the SD card.  This may have something to do with the script parameters saved by CHDK, and that I have scripting set to autostart. 
You mean you have script autostart set ? Removing your CHDK/CCHDK.CFG (using a card reader) will disable this setting and reset the selected script. This should allow the camera to boot.

If you can narrow down what triggers this, it would be very helpful.

A ROMLOG may also provide information, I've attached a build you can use to do this. It will be more useful to me to have a ROMLOG from a crash with this build, because I have the corresponding debug files.

You can try placing the diskboot.bin from this build on your card before removing the CCHDK.CFG, and try to boot. If it crashes, remove the CCHDK.CFG, boot CHDK, then get the ROMLOG.

Use romlog.lua to get the ROMLOG. See http://chdk.wikia.com/wiki/Lua/Scripts:Standard/Test/Romlog
Quote
d) Assuming that (c) can be fixed or worked around, is it possible to turn off and leave off the LCD display in the D10?  For tripod-mounted intervalometry, there's no need for the display at all.
Not sure about this. You can set the screen off timeout very short.

If you require the camera to be waterproof, plugging in the A/V adapter will turn off the display, but this doesn't save much power.
Quote
e) Is it possible to disable focusing, or lock focusing?  There's no need for it during interval shooting.
Thanks again.
If your subject is distant, just use the 'focus at infinity' mode. If it's closer, you can use af lock (described in the canon manual), or manual focus. You should also be able to use CHDK subject distance override, but I think in autofocus mode the camera will do the AF scan anyway. I'm also not sure SD override is working properly.

FWIW, On many cameras, manual focus mode consumes noticeably more power than AF. I haven't tested on D10.
Don't forget what the H stands for.


Re: D10 porting thread
« Reply #94 on: 27 / February / 2011, 02:10:52 »
After deleting CCHDK.CFG, it boots normally, but then it is recreated, and stops booting again.
After deleting again, "Script autostart" powers up as off, and I turned off "Save parameters", but after power cycling, the D10 still stops booting until I delete CCHDK.CFG again.

Finally (after deleting again) I tried "Reset options to defaults", and now the camera boots correctly. 

Is the firmware you posted here d10-1067-reyalp-test.zip suitable for further testing, or should I revert to the autobuild version?
Attached find the ROMLOG.LOG and CCHDK.CFG which triggers the non-boot(as well as the post "reset options" version which allows boot).

*

Offline reyalp

  • ******
  • 13432
Re: D10 porting thread
« Reply #95 on: 27 / February / 2011, 02:54:05 »
After deleting CCHDK.CFG, it boots normally, but then it is recreated, and stops booting again.
After deleting again, "Script autostart" powers up as off, and I turned off "Save parameters", but after power cycling, the D10 still stops booting until I delete CCHDK.CFG again.

Finally (after deleting again) I tried "Reset options to defaults", and now the camera boots correctly. 
This is strange, camera creating new cchdk.cfg should be the same as reset to defaults. You didn't change any other settings after the first boot ?

Are you starting the camera with the play button or power button ? If the power button, are you using a short press or long press (long will start directly in record mode).
Quote
Is the firmware you posted here d10-1067-reyalp-test.zip suitable for further testing, or should I revert to the autobuild version?
It's pretty much the same as the autobuild except that it has lua native calls enabled (allows you to run romlog), and has games disabled to save memory.
Quote
Attached find the ROMLOG.LOG and CCHDK.CFG which triggers the non-boot(as well as the post "reset options" version which allows boot).
Thanks. The stacktrace is a bit odd, I only see the start of spytask in there, not sure what that means. Whatever it is going on is quite early in the startup process.
Don't forget what the H stands for.

Re: D10 porting thread
« Reply #96 on: 27 / February / 2011, 03:53:05 »
Quote
This is strange, camera creating new cchdk.cfg should be the same as reset to defaults. You didn't change any other settings after the first boot ?
I had only changed a few items in the CHDK menus: scripting and the script parameters.  After testing, I changed the script to autostart, and that's when all the trouble started.

Quote
Are you starting the camera with the play button or power button ? If the power button, are you using a short press or long press (long will start directly in record mode).
Both press durations result in a non-boot.  The short press begins to show play mode, but boot stops.  Long press begins to show record mode, but then the screen goes black in a non-boot.

It now seems that after "reset options", changing ANY CHDK menu items, resulting in creation of CCHDK.CFG, results in a non-boot at next powerup, with either short or long powerbutton press, with either the latest autobuild or your custom build.

I don't know if this matters, but the flash card I'm using is 1GB, with 20MB free.

*

Offline reyalp

  • ******
  • 13432
Re: D10 porting thread
« Reply #97 on: 27 / February / 2011, 04:12:41 »
Sounds like starting method isn't a factor.

20 MB free ? Is the rest all image files ? The number of files on the card can have a significant effect, both on free RAM and startup time.

Can you start chdk, go to "miscellaneous stuff" -> "show memory info" and report the results ?

It would be good to know if the problem happens with an empty card. I'd try removing the files first, and if that doesn't resolve it, format.

If either of those does resolve it, you can try copying the files back to see if the problem re-appears.
Don't forget what the H stands for.


Re: D10 porting thread
« Reply #98 on: 27 / February / 2011, 17:28:13 »
Can you start chdk, go to "miscellaneous stuff" -> "show memory info" and report the results ?
Memory Info
Free Memory: 366608 bytes
CHDK size:    276756 bytes
loaded at: 0x146A2C


*

Offline reyalp

  • ******
  • 13432
Re: D10 porting thread
« Reply #99 on: 27 / February / 2011, 17:44:26 »
Can you start chdk, go to "miscellaneous stuff" -> "show memory info" and report the results ?
Memory Info
Free Memory: 366608 bytes
That's with the full card, correct ? If so, looks like free memory is not our problem.

Can you tell me approximately how many images are in the DCIM/* directories ?
Don't forget what the H stands for.

 

Related Topics