Powershot A3100 - Porting thread - page 6 - DryOS Development - CHDK Forum

Powershot A3100 - Porting thread

  • 139 Replies
  • 64719 Views
Re: Powershot A3100 - Porting thread
« Reply #50 on: 12 / November / 2012, 19:39:02 »
Advertisements
New release that fixes Alt key problem;

(updated links)
src: https://www.box.com/s/j4jbnt48hpc1iljvl0kk
Package for A3100/A3150 firmware 100b (untested): https://www.box.com/s/e75ewnmcd8ur4zkjse0w
Package for A3100/A3150 firmware 100d: https://www.box.com/s/onh14frtirntfx2hatdi

Any feedback is welcome!

Camera depending notes:

- The version for fw 100b is an pre-alpha version, it has not been tested at all, be the first!

+ dual partition boot for cards >4GB tested and works
+ Raw works, including DNG, Dark frame substraction enable/disable
+ Overrides work
+ Extra long exposures >64s work
+ Video settings work
+ Zoom in video works
+ scripting (lua) works
+ Simple USB remote shutter works

Default Alt key is 'Face/Print'
Install using the Bootable_SD_Card_Method

This built is based on the port of the A3000 (boot, capt_seq, loader) and the port of the A490 (movie_rec, keyboard routines)

History of changes
- cosmetic changes to the colors used by chdk
- fixed another bug in kbd.c preventing alt mode on formatted card
- fixed free space indicator on lcd
- fixed af scan during video
- added user configurable Alt button (and removed some bugs in kbd.c)
- Blind port for fw 100b
- Cosmetic changes improving the readability of chdk menu
« Last Edit: 13 / November / 2012, 19:26:00 by casrap »

*

Offline ahull

  • *****
  • 634
Re: Powershot A3100 - Porting thread
« Reply #51 on: 13 / November / 2012, 06:27:20 »
Thanks for that update casrap, it seems to have done the trick.

I should get a chance to run some of the test scripts on my A3150 Build 100d later today, but I can now load up the menus.

*

Offline ahull

  • *****
  • 634
Re: Powershot A3100 - Porting thread
« Reply #52 on: 13 / November / 2012, 09:34:43 »
First impressions are that it is stable on the A3150, I ran setmode.lua, which fails on one test (Set mode P) log is attached.

Lua Lib tests pass. (LLIBTST.LUA)
RomLog dumper works (and rather worryingly there was a romlog to dump, but its from 2010, so no worries there)
drawtest.lua works (colours are a little odd, but we can blame Canon for that  :blink:).
hdr script works
motion detection script works
inervalometer works.
DNG Raw shooting works, badpixel creation works. File is readable in RawTherapee, looks *very* good  :D
« Last Edit: 13 / November / 2012, 09:55:30 by ahull »

Re: Powershot A3100 - Porting thread
« Reply #53 on: 13 / November / 2012, 09:48:32 »
According to the firmware the mode maps are the same for the a3100 and the a3150. On the a3100 the test passes. Can you try again with parameter 'mode change delay' set to 3000?

<edit> or turn the flash off in P mode, i think that is causing the fail (charging the flash takes a lot of time).
<edit2> but then you will get an error on another mode that uses the flash.
You can also try to start the script from record mode while P is selected.
« Last Edit: 13 / November / 2012, 10:14:53 by casrap »


Re: Powershot A3100 - Porting thread
« Reply #54 on: 13 / November / 2012, 10:22:36 »
About the odd colors; if you go to the Alt menu->chdk settings->color settings->draw palette you can see what colors are available. While in record mode they look nice (be it without any red), but in play mode they are terrible (no red and no blue). The default selection is at least readable in both modes, but not very pleasant to look at.
It will not be easy to find a better color selection for both modes :(

Re: Powershot A3100 - Porting thread
« Reply #55 on: 13 / November / 2012, 10:33:30 »
It will not be easy to find a better color selection for both modes :(
You will probably want to implement the customized palette code for this camera. 

Grep for #define CAM_LOAD_CUSTOM_COLORS 1  (the A1200 implements it for example).
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline ahull

  • *****
  • 634
Re: Powershot A3100 - Porting thread
« Reply #56 on: 13 / November / 2012, 10:47:47 »
According to the firmware the mode maps are the same for the a3100 and the a3150. On the a3100 the test passes. Can you try again with parameter 'mode change delay' set to 3000?

<edit> or turn the flash off in P mode, i think that is causing the fail (charging the flash takes a lot of time).
<edit2> but then you will get an error on another mode that uses the flash.
You can also try to start the script from record mode while P is selected.

OK, switching off the flash did the trick. Test passes. Thanks.

Re: Powershot A3100 - Porting thread
« Reply #57 on: 13 / November / 2012, 11:01:37 »
Quote
You will probably want to implement the customized palette code for this camera. 

Grep for #define CAM_LOAD_CUSTOM_COLORS 1  (the A1200 implements it for example).
Already working on better colors, but the cam misses the palette functions that are present in newer cameras.


Re: Powershot A3100 - Porting thread
« Reply #58 on: 13 / November / 2012, 11:27:05 »
OK, switching off the flash did the trick. Test passes. Thanks.

Great, thanks for the test. It seems the cameras are identical.

*

Offline ahull

  • *****
  • 634
Re: Powershot A3100 - Porting thread
« Reply #59 on: 13 / November / 2012, 12:05:26 »
OK, switching off the flash did the trick. Test passes. Thanks.

Great, thanks for the test. It seems the cameras are identical.

I thought they had to be pretty similar since they have the same P-ID, hence my earlier comment "Note: the Powershot A3150 IS has the same P-ID (31f1) as the A3100 IS, ... " when I dumped the ROM.  (http://chdk.wikia.com/wiki/A3100IS)

Looks like a bit of re-badging by the Canon marketing team.

I have attached a rather boring HDR image taken using this A3150 ver 1.00D just to prove it all works.  :D
« Last Edit: 13 / November / 2012, 12:12:00 by ahull »

 

Related Topics