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

A800 Porting Thread

  • 277 Replies
  • 83281 Views
Re: A800 Porting Thread
« Reply #100 on: 17 / March / 2012, 08:46:10 »
Advertisements
Using waterwingz's second build, upped 'mode change delay, ms' to 500, it seemed to go through a bunch of modes on the screen and it gave this in the logs:
Code: [Select]
a800 100c CHDK 1.0.0 Mar 11 2012 15:07:27 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  280ms OK
TRY                    P   2 |                    P   2 32772 STL  400ms OK
TRY            VIDEO_STD   9 |            VIDEO_STD   9  2618 VID  510ms OK
TRY        SCN_KIDS_PETS  33 |        SCN_KIDS_PETS  33 16402 STL  590ms OK
TRY         SCN_PORTRAIT  41 |         SCN_PORTRAIT  41 16399 STL  280ms OK
TRY           SCN_SUNSET  55 |           SCN_SUNSET  55 16404 STL  220ms OK
TRY     SCN_LONG_SHUTTER  60 |     SCN_LONG_SHUTTER  60 16390 STL  240ms OK
TRY         SCN_LOWLIGHT  64 |         SCN_LOWLIGHT  64 16417 STL  220ms OK
TRY  SCN_FACE_SELF_TIMER  78 |  SCN_FACE_SELF_TIMER  78 16936 STL  230ms OK
TRY          SUPER_VIVID  83 |          SUPER_VIVID  83 16934 STL  270ms OK
TRY        POSTER_EFFECT  84 |        POSTER_EFFECT  84 16935 STL  220ms OK
TRY                BEACH  87 |                BEACH  87 16407 STL  230ms OK
TRY              FOLIAGE  88 |              FOLIAGE  88 16405 STL  240ms OK
TRY                 SNOW  89 |                 SNOW  89 16406 STL  250ms OK
TRY             FIREWORK  90 |             FIREWORK  90 16408 STL  450ms OK
TRY       BLUR_REDUCTION  93 |       BLUR_REDUCTION  93 16435 STL  240ms OK
TRY                 AUTO   1 |                 AUTO   1 32768 STL  250ms OK

Re: A800 Porting Thread
« Reply #101 on: 17 / March / 2012, 09:03:23 »
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.


I just remembered this post so I went and tweaked platform_camera.h as suggested and built it.  RAW pictures are still purple.

I tried attaching a full .zip file of my tweaked 1748 build and a reduced sized .jpg conversion of my purple RAW picture but my browser still times out when trying to use the full post interface here on the forums :(
« Last Edit: 17 / March / 2012, 09:08:36 by Qanthelas »

Re: A800 Porting Thread
« Reply #102 on: 17 / March / 2012, 09:30:58 »
Can you post the settings you have used in platform_camera.h for the raw image ?
« Last Edit: 17 / March / 2012, 09:32:43 by Microfunguy »

Re: A800 Porting Thread
« Reply #103 on: 17 / March / 2012, 10:02:21 »
Can you post the settings you have used in platform_camera.h for the raw image ?

I'm away from my main computer now so I can't but all I did was copy the latest trunk folder (1748), renamed the trunk folder, and edited the spot philmoz had suggested - so I changed the line about 'cam_CFAPattern' to 0x01000201 instead of 0x02010100.

I must admit that I am surprised that the RAW picture was still purple - I expected it to change, maybe not to what it should be but at least to something different.


Re: A800 Porting Thread
« Reply #104 on: 17 / March / 2012, 10:38:59 »
I just wanted to check that cropping started on an even-numbered row, which it does.

Guess you could use DNG4PS2.

Re: A800 Porting Thread
« Reply #105 on: 17 / March / 2012, 12:02:02 »
I must admit that I am surprised that the RAW picture was still purple - I expected it to change, maybe not to what it should be but at least to something different.
Did you try changing something else so that you can be sure you build what you edited ?  Tweaking a menu title is an easy one.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A800 Porting Thread
« Reply #106 on: 17 / March / 2012, 12:25:25 »
Once I get back to my main computer I'll try to tweak something else to make sure it's building with my tweaks in place.  For now, I have my camera and I just ran a bunch of tests (because I'm bored.)

These are using the latest autobuild from http://mighty-hoernsche.de/ which is a800-100c-1.0.0-1747-full_ALPHA.zip

Under Misc. -> 'Show Memory Info' it shows:
Free Memory: 374984 bytes
CHDK size: 273216 bytes
loaded at: 0x1F5FFE0

When I try setmode.lua (with no modifcations to the script settings) it seems to work just fine - it cycles through a bunch of different icons in the upper right and shows this in the setmode.log file:
Code: [Select]
a800 100c CHDK 1.0.0-1747 Mar 17 2012 06:46:51 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  270ms OK
TRY                    P   2 |                    P   2 32772 STL  240ms OK
TRY            VIDEO_STD   9 |            VIDEO_STD   9  2618 VID  500ms OK
TRY        SCN_KIDS_PETS  33 |        SCN_KIDS_PETS  33 16402 STL  620ms OK
TRY         SCN_PORTRAIT  41 |         SCN_PORTRAIT  41 16399 STL  300ms OK
TRY           SCN_SUNSET  55 |           SCN_SUNSET  55 16404 STL  260ms OK
TRY     SCN_LONG_SHUTTER  60 |     SCN_LONG_SHUTTER  60 16390 STL  290ms OK
TRY         SCN_LOWLIGHT  64 |         SCN_LOWLIGHT  64 16417 STL  270ms OK
TRY  SCN_FACE_SELF_TIMER  78 |  SCN_FACE_SELF_TIMER  78 16936 STL  240ms OK
TRY          SUPER_VIVID  83 |          SUPER_VIVID  83 16934 STL  250ms OK
TRY        POSTER_EFFECT  84 |        POSTER_EFFECT  84 16935 STL  220ms OK
TRY                BEACH  87 |                BEACH  87 16407 STL  230ms OK
TRY              FOLIAGE  88 |              FOLIAGE  88 16405 STL  240ms OK
TRY                 SNOW  89 |                 SNOW  89 16406 STL  270ms OK
TRY             FIREWORK  90 |             FIREWORK  90 16408 STL  560ms OK
TRY       BLUR_REDUCTION  93 |       BLUR_REDUCTION  93 16435 STL  310ms OK
TRY                 AUTO   1 |                 AUTO   1 32768 STL  300ms OK

DRAWTEST.LUA works until it gets to this part (note that it seemed to do the 2000 lines fine, which it hadn't last time I tested)
Code: [Select]
If you press 'menu'
it will try to draw
1000 random lines
not enough memory
PRESS SHUTTER TO CLOSE

LLIBTST.LUA works fine with this in the log:
http://pastebin.com/E6VRY3mN


ROMLOG.LUA shows this on the screen:
Code: [Select]
***STARTED****
:16 ERROR: your CHDK doe
s not support native func
tion calls
PRESS SHUTTER TO CLOSE

SETREC.LUA shows this on the screen:
Code: [Select]
***STARTED****
record: true
set record to: false
record: false
***FINISHED***

TSTCALLF.LUA shows this on the screen:
Code: [Select]
***STARTED****
1 FAILED
***FINISHED***
and this in the log file
Code: [Select]
native call interface not found, aborting!
1 FAILED

UARTRTST.LUA shows this on the screen:
Code: [Select]
***STARTED****
:7 ERROR: requires CHDK
build with native functio
n call support
PRESS SHUTTER TO CLOSE

Re: A800 Porting Thread
« Reply #107 on: 17 / March / 2012, 12:36:02 »
These are using the latest autobuild from http://mighty-hoernsche.de/ which is a800-100c-1.0.0-1747-full_ALPHA.zip
Looking pretty good now.   Most of the "errors" are because the autobuild version does not support native LUA calls.  That was done to protect the naive user from accidentally doing something in a script that might brick his camera.

The other error looks like maybe there is still not enough memory even though the latest version loads in EXMEM.   Have you tried the same test(s) on the dev versions ? It uses loadable modules and takes up less memory room.

http://mighty-hoernsche.de/trunk/

Ported :   A1200    SD940   G10    Powershot N    G16


Re: A800 Porting Thread
« Reply #108 on: 17 / March / 2012, 13:26:53 »
This round of tests using the latest build from http://mighty-hoernsche.de/trunk/ which is a800-100c-1.1.0-1748-full_BETA.zip

'Show Memory Info' gives this:
Free Memory: 425688 bytes
CHDK size: 222544 bytes
loaded at: 0x1F5FFE0

DRAWTEST.LUA works with no errors (even at the 1000 random lines)

FILETEST.LUA does indeed open the file browser (I had forgotten to test this one before)

LLIBTEST.LUA runs with no errors and this in the log file: http://pastebin.com/UQyb6nVB

ROMLOG.LUA gives the same error 16 about not supporting native function calls

SETMODE.LUA runs with no errors and this in the log:
Code: [Select]
a800 100c CHDK 1.1.0-1748 Mar 17 2012 06:33:33 dryos 0x3226
START                        |                 AUTO   1 32768 STL
TRY                 AUTO   1 |                 AUTO   1 32768 STL  250ms OK
TRY                    P   2 |                    P   2 32772 STL  300ms OK
TRY            VIDEO_STD   9 |            VIDEO_STD   9  2618 VID  510ms OK
TRY        SCN_KIDS_PETS  33 |        SCN_KIDS_PETS  33 16402 STL  620ms OK
TRY         SCN_PORTRAIT  41 |         SCN_PORTRAIT  41 16399 STL  300ms OK
TRY           SCN_SUNSET  55 |           SCN_SUNSET  55 16404 STL  260ms OK
TRY     SCN_LONG_SHUTTER  60 |     SCN_LONG_SHUTTER  60 16390 STL  290ms OK
TRY         SCN_LOWLIGHT  64 |         SCN_LOWLIGHT  64 16417 STL  270ms OK
TRY  SCN_FACE_SELF_TIMER  78 |  SCN_FACE_SELF_TIMER  78 16936 STL  240ms OK
TRY          SUPER_VIVID  83 |          SUPER_VIVID  83 16934 STL  260ms OK
TRY        POSTER_EFFECT  84 |        POSTER_EFFECT  84 16935 STL  220ms OK
TRY                BEACH  87 |                BEACH  87 16407 STL  220ms OK
TRY              FOLIAGE  88 |              FOLIAGE  88 16405 STL  240ms OK
TRY                 SNOW  89 |                 SNOW  89 16406 STL  270ms OK
TRY             FIREWORK  90 |             FIREWORK  90 16408 STL  530ms OK
TRY       BLUR_REDUCTION  93 |       BLUR_REDUCTION  93 16435 STL  300ms OK
TRY                 AUTO   1 |                 AUTO   1 32768 STL  240ms OK

SETREC.LUA seems to run with no errors as it did before

TSTCALLF.LUA gives the same '1 Failed' message on screen and the same thing in the log:
Code: [Select]
native call interface not found, aborting!
1 FAILED

UARTRTST.LUA gives the samme error 7 about needing native function call support


As a side note, the battery level monitor seems to freak out a bit - using the same non-rechargable AAs that I've been using all along (so I imagine they are nearly dead by now) and it varies between showing 30% to around 50% and the low battery image flashed in the upper left.  It wouldn't surprise me if the camera did this in the native firmware, too, though - plain AA batteries seem to mess with battery level gaugers as they lose 'juice', I've noticed.

Re: A800 Porting Thread
« Reply #109 on: 17 / March / 2012, 14:07:03 »
Here's the dev version built with Lua native calls enabled.  See what that does ?

http://www.box.com/s/c416c81923a2acd6df61

Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics