A800 Porting Thread - page 8 - DryOS Development - CHDK Forum  

A800 Porting Thread

  • 277 Replies
  • 101460 Views
Re: A800 Porting Thread
« Reply #70 on: 04 / February / 2012, 19:30:34 »
Advertisements
nrflag: stubs_entry.S contains it.
tests: it seems ok. On: after initial capture time it remains busy for the same amount of time defined for exposure (5 s). Off busy for much less time. Auto,in my test, as Off.
Thanks, again,Phill.
I will do some more tests, and then post a compatible new trunk version.

Re: A800 Porting Thread
« Reply #71 on: 06 / February / 2012, 10:47:44 »
I will do some more tests, and then post a compatible new trunk version.

Sounds good, thanks mlands!  I've got a few different projects I'm tinkering with but I'll keep an eye out for this new version and I'll try and do some testing on it :)

Re: A800 Porting Thread
« Reply #72 on: 08 / February / 2012, 15:19:24 »
Hi,
  rand and srand for a800 are not identified automatically neither could I find them. I checked in reference ports (a495 and ixus220) they are next to references to eyefi card in the first and to the string InspirationPlayController.c in the 2nd (and both doesn`t exist in A800 firmware - a800 seems compatible with eyefi cards). I have also tried to identify the caller, but  with no success. Where are they used ? Any suggestion to find them?

Version for trunk1650
PS:
A) When installing this new version trunk, I suggest to delete chdk/CCHDK.CFG in the card. When I installed  it without doing this, the  camera behaved strangely. After deleting that file, it functions normally (saving and reading the new  configuration file).
B)for compiling
1)Add in ./camera.csv
   a800,100c,,,
2)Add in include/modelist.h
  MODE_BLUR_REDUCTION   ,   // A800
4)  Modify core\gui.c about line 1991:
#if defined (CAMERA_s90) || defined (CAMERA_s95) || defined (CAMERA_g12) || defined (CAMERA_a3000) || defined (CAMERA_a800)

Re: A800 Porting Thread
« Reply #73 on: 08 / February / 2012, 20:13:56 »
Version for trunk1650
Took the liberty of converting this into a patch file and submitting for inclusion in the svn :

http://chdk.setepontos.com/index.php?topic=650.msg81174#msg81174

Hope that's okay - these attachments in the forum have a history of getting "lost" after a while so getting things into the svn is safer.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: A800 Porting Thread
« Reply #74 on: 08 / February / 2012, 21:41:57 »
Thanks for the new version!  Tests run using 1.1.0-1650 full.

When starting up (either with power button or with play button) the logo shows up as expected, but it only lasts for less than a second so I can't really read it, normally it would still on the screen until I pushed a button.

Histogram seems to work just fine, I can't get Zebra to show up (might be because the menu for that is tweaked and I don't have the parameters set to where it would show up, but with it just turned on and left to defaults and focusing in on various white things I can't get it to show up.)

The llibtst.lua test seems to run just fine, but setmode.lua errors and gives this in the log file:

a800 100c CHDK 1.1.0-1650 Feb  8 2012 15:13:17 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  300ms OK
TRY                    P   2 |                 AUTO   1 32768 STL  370ms CHANGE FAIL req   2 got   1
TRY            VIDEO_STD   9 |                 AUTO   1 32768 STL  280ms CHANGE FAIL req   9 got   1
TRY        SCN_KIDS_PETS  33 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  33 got   1
TRY         SCN_PORTRAIT  41 |                 AUTO   1 32768 STL  280ms CHANGE FAIL req  41 got   1
TRY           SCN_SUNSET  55 |                 AUTO   1 32768 STL  350ms CHANGE FAIL req  55 got   1
TRY     SCN_LONG_SHUTTER  60 |                 AUTO   1 32768 STL  330ms CHANGE FAIL req  60 got   1
TRY         SCN_LOWLIGHT  64 |                 AUTO   1 32768 STL  310ms CHANGE FAIL req  64 got   1
TRY  SCN_FACE_SELF_TIMER  78 |                 AUTO   1 32768 STL  310ms CHANGE FAIL req  78 got   1
TRY          SUPER_VIVID  83 |                 AUTO   1 32768 STL  270ms CHANGE FAIL req  83 got   1
TRY        POSTER_EFFECT  84 |                 AUTO   1 32768 STL  310ms CHANGE FAIL req  84 got   1
TRY                BEACH  87 |                 AUTO   1 32768 STL  270ms CHANGE FAIL req  87 got   1
TRY              FOLIAGE  88 |                 AUTO   1 32768 STL  280ms CHANGE FAIL req  88 got   1
TRY                 SNOW  89 |                 AUTO   1 32768 STL  330ms CHANGE FAIL req  89 got   1
TRY             FIREWORK  90 |                 AUTO   1 32768 STL  320ms CHANGE FAIL req  90 got   1
TRY       BLUR_REDUCTION  93 |                 AUTO   1 32768 STL  300ms CHANGE FAIL req  93 got   1
TRY                 AUTO   1 |                 AUTO   1 32768 STL  340ms OK




ubtest.bas seems to work as expected and seems to correctly identify button presses like up, down, left, and right.

Tried creating badpixel.bin and then taking a RAW file - says it worked fine, but on first test, the RAW was right except that it was like it had a purple filter on.  Deleted everything off the card, copied back over the CHDK folder and DISKBOOT.BIN from the -full.zip, again tried making badpixel.bin and then taking a RAW - still purple.  I'd attach a RAW to this post, but it'd be way too big, so I saved it as a .jpg and it still looks the same and I've attached that to this post.  Not sure just what is up there, but at least it's better than random green and blue lines like I got off the last camera I worked with :P  Guessing the color matrix will need a tweak.

I know remote (like Ricoh CA-1) support is still being messed with quite a bit, but I figured I'd test it anyways.  It made the screen flicker off on half down and again on full press.  I checked and it didn't seem to have taken any pictures.  I think this is defauly Canon behavior - I think it is trying to go in to camera link mode when it gets a charge.

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A800 Porting Thread
« Reply #75 on: 08 / February / 2012, 21:58:37 »

Tried creating badpixel.bin and then taking a RAW file - says it worked fine, but on first test, the RAW was right except that it was like it had a purple filter on.  Deleted everything off the card, copied back over the CHDK folder and DISKBOOT.BIN from the -full.zip, again tried making badpixel.bin and then taking a RAW - still purple.  I'd attach a RAW to this post, but it'd be way too big, so I saved it as a .jpg and it still looks the same and I've attached that to this post.  Not sure just what is up there, but at least it's better than random green and blue lines like I got off the last camera I worked with :P  Guessing the color matrix will need a tweak.


This could be if the 'cam_CFAPattern' value is wrong in platform_camera.h (this defines what layout the sensor uses). Currently it is set to RGGB (0x02010100), try GBRG (0x01000201).

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: Re: A800 Porting Thread
« Reply #76 on: 08 / February / 2012, 22:19:01 »
I know remote (like Ricoh CA-1) support is still being messed with quite a bit, but I figured I'd test it anyways.  It made the screen flicker off on half down and again on full press.  I checked and it didn't seem to have taken any pictures.  I think this is defauly Canon behavior - I think it is trying to go in to camera link mode when it gets a charge.
Did you actually go to the Remote menu and enable remote operation and select the CA-1 as your remote device?  If not then the behaviour you are seeing is quite normal - its  trying to go into camera link mode.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A800 Porting Thread
« Reply #77 on: 08 / February / 2012, 22:47:29 »
Did you actually go to the Remote menu and enable remote operation and select the CA-1 as your remote device?  If not then the behaviour you are seeing is quite normal - its  trying to go into camera link mode.

That's what I get for not reading up on that :P  Once I went in to the Misc settings and turned it to CA-1 and Normal it worked just fine :)  Focus on half press, take picture on full press, as expected :)


*

Offline reyalp

  • ******
  • 14082
Re: A800 Porting Thread
« Reply #78 on: 11 / February / 2012, 16:43:48 »

The llibtst.lua test seems to run just fine, but setmode.lua errors and gives this in the log file:

a800 100c CHDK 1.1.0-1650 Feb  8 2012 15:13:17 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  300ms OK
TRY                    P   2 |                 AUTO   1 32768 STL  370ms CHANGE FAIL req   2 got   1
This shouldn't be failing. Was the camera in playback or record mode when you started ?
(edit: it should automatically switch to record if play is detected, but this might narrow down the problem)
Also, it probably won't work if the camera was connected to the USB cable.
Quote
ubtest.bas seems to work as expected and seems to correctly identify button presses like up, down, left, and right.
ubtest takes several pictures with Tv, Sv and ND override. If you can verify that the exposures are different, that confirms that these overrides are working from script.

The log in CHDK/LOGS/LOG_0001.TXT will give the settings and exposure number.

edit:
Problem with setmode is probably the same one that affected sx230, as discussed here http://chdk.setepontos.com/index.php?topic=6397.msg81373#msg81373
If this is the case, the latest setmode.lua from svn should not fail.
« Last Edit: 12 / February / 2012, 20:54:41 by reyalp »
Don't forget what the H stands for.

Re: A800 Porting Thread
« Reply #79 on: 11 / March / 2012, 12:30:13 »
The forums seem to have eaten my last post  ???  In fact, I seem to be unable to use the full 'reply' or full 'modify' screens - when I hit 'post' or 'save' they time out on me so instead I have to use Quick Reply and Modify message.  I hope this is just a temporary issue, but it is preventing me from attaching my full .zip file to this post.

I just grabbed the latest and greatest CHDK-shell (3.43) and trunk (1724), compiled the a800 100c which is there in the trunk as a beta release, and tested out the setmode.lua script.  Well, the good news is that my camera still boots and seems to function as well as it did before.  The bad news is that setmode.lua errors out.  More specifically, I start the script in picture taking mode, it starts spitting out text in the lower left of my camera's screen, and then the screen turns off and as best as I can tell the camera turns off.  Here is what is in setmode.log:

Code: [Select]
a800 100c CHDK 1.1.0-1724 Mar 11 2012 12:11:46 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  250ms OK
TRY                    P   2 |                 AUTO   1 32768 STL  250ms CHANGE FAIL req   2 got   1
TRY            VIDEO_STD   9 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req   9 got   1
TRY        SCN_KIDS_PETS  33 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  33 got   1
TRY         SCN_PORTRAIT  41 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  41 got   1
TRY           SCN_SUNSET  55 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  55 got   1
TRY     SCN_LONG_SHUTTER  60 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  60 got   1
TRY         SCN_LOWLIGHT  64 |                 AUTO   1 32768 STL  270ms CHANGE FAIL req  64 got   1
TRY  SCN_FACE_SELF_TIMER  78 |                 AUTO   1 32768 STL  250ms CHANGE FAIL req  78 got   1
TRY          SUPER_VIVID  83 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  83 got   1
TRY        POSTER_EFFECT  84 |                 AUTO   1 32768 STL  280ms CHANGE FAIL req  84 got   1
TRY                BEACH  87 |                 AUTO   1 32768 STL  250ms CHANGE FAIL req  87 got   1
TRY              FOLIAGE  88 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  88 got   1
TRY                 SNOW  89 |                 AUTO   1 32768 STL  270ms CHANGE FAIL req  89 got   1
TRY             FIREWORK  90 |                 AUTO   1 32768 STL  270ms CHANGE FAIL req  90 got   1
TRY       BLUR_REDUCTION  93 |                 AUTO   1 32768 STL  260ms CHANGE FAIL req  93 got   1
TRY                 AUTO   1 |                 AUTO   1 32768 STL  270ms OK


Any ideas?
« Last Edit: 11 / March / 2012, 12:35:09 by Qanthelas »

 

Related Topics