A800 Porting Thread

Qanthelas

71

Re: A800 Porting Thread

« Reply #110 on: 17 / March / 2012, 15:04:31 »

Advertisements

Quote from: waterwingz 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

Here's the tests with this version.

Draw test, File test, Lua Lib test, Rom Log, Set rec/play, Textbox test (which I hadn't seen before), and the UAR redirect test all seem to work just fine.

Setmode gives the 15 failed check log error

Test native func interface still gives the '1 FAILED' message on screen

Log files
llibtst: http://pastebin.com/Zh3tQGA6
ROMLOG: http://pastebin.com/N9b6SaGe
setmode: http://pastebin.com/GcJqMTWS
TSTCALLF: http://pastebin.com/JfQLdzt0
UARTRTST:

Code: [Select]

uartr.lua: start UART redirection
Sat Mar 17 14:01:55 2012 UART redirect Test (uartrtst.lua) OK
uartr.lua: stop UART redirection

I'm a bit suspicious since the autobuild setmode.lua works and the builds I've gotten from you, waterwingz, error out in the same way - did something get tweaked on your trunk?

Logged

waterwingz

12138

Re: A800 Porting Thread

« Reply #111 on: 17 / March / 2012, 15:21:46 »

Quote from: Qanthelas on 17 / March / 2012, 15:04:31

I'm a bit suspicious since the autobuild setmode.lua works and the builds I've gotten from you, waterwingz, error out in the same way - did something get tweaked on your trunk?

Could be. I've been building those on my Linux box using the most current svn source - I'm 100% sure that part is correct. However, its possible I have one of the build options different. Its also possible that I'm using a different compiler version than what's the autobuild uses. When I get a minute, I'll reboot into Windows and try a CHDK-Shell build.

Logged

Ported : A1200 SD940 G10 Powershot N G16

reyalp

14037

Re: A800 Porting Thread

« Reply #112 on: 17 / March / 2012, 15:34:16 »

Quote from: Qanthelas on 17 / March / 2012, 13:26:53

ROMLOG.LUA gives the same error 16 about not supporting native function calls
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

There's really no need to report all of these scripts telling you that your build doesn't have native calls.... these scripts don't run if your chdk isn't built with that feature, and except for tstcallf don't really test much of anything. They are useful for testing, but are not tests themselves.

Romlog functionality is now built into CHDK, so there isn't much need for the script.

The number is the line number btw.

Edit:
I do appreciate your effort to test this thoroughly.

« Last Edit: 17 / March / 2012, 15:39:59 by reyalp »

Logged

Don't forget what the H stands for.

Qanthelas

71

Re: A800 Porting Thread

« Reply #113 on: 17 / March / 2012, 15:46:13 »

Quote from: waterwingz on 17 / March / 2012, 15:21:46

Could be. I've been building those on my Linux box using the most current svn source - I'm 100% sure that part is correct. However, its possible I have one of the build options different. Its also possible that I'm using a different compiler version than what's the autobuild uses. When I get a minute, I'll reboot into Windows and try a CHDK-Shell build.

Sounds good, that seems like a likely culprit there.

Quote from: reyalp on 17 / March / 2012, 15:34:16

There's really no need to report all of these scripts telling you that your build doesn't have native calls.... these scripts don't run if your chdk isn't built with that feature, and except for tstcallf don't really test much of anything. They are useful for testing, but are not tests themselves.

Romlog functionality is now built into CHDK, so there isn't much need for the script.

The number is the line number btw.

Edit:
I do appreciate your effort to test this thoroughly.

*shrugs* At least it seems to work now, even Romlog (for all that it matters

) I figured you probably didn't need all those error logs, but I figured the more the merrier when it comes to log files

Logged

Qanthelas

71

Re: A800 Porting Thread

« Reply #114 on: 18 / March / 2012, 11:19:03 »

Quote from: waterwingz on 17 / March / 2012, 12:02:02

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.

OK, I thought I knew how to do this but I've been trying to find the menu titles so I can tweak one and I can't find them and I'm guessing it's because I'm looking in entirely the wrong place

I just tried a fresh build with this as line 58 in platform_camera.h:

Code: [Select]

    #define cam_CFAPattern                  0x01000201 // Green Blue Red Green, at philmoz's suggestion to make RAW photos not look purple

and I enabled EXMEM in the build options but RAW pictures are still purple.

Logged

waterwingz

12138

Re: A800 Porting Thread

« Reply #115 on: 18 / March / 2012, 11:32:25 »

Quote from: Qanthelas on 18 / March / 2012, 11:19:03

OK, I thought I knew how to do this but I've been trying to find the menu titles so I can tweak one and I can't find them and I'm guessing it's because I'm looking in entirely the wrong place

The file you are looking for is trunk/CHDK/LANG/english.lng . Change the 7th line to :

Code: [Select]

  1 "xMain Menu"

Logged

Ported : A1200 SD940 G10 Powershot N G16

Qanthelas

71

Re: A800 Porting Thread

« Reply #116 on: 18 / March / 2012, 11:47:44 »

Quote from: waterwingz on 18 / March / 2012, 11:32:25

The file you are looking for is trunk/CHDK/LANG/english.lng . Change the 7th line to :
Code: [Select]
1 "xMain Menu"

That makes a lot of sense and I was looking in entirely the wrong places

Alright, with it set to 'xMain Menu' and with the platform\a800\platform_camera.h file changed to philmoz's suggested cam_CFAPattern value, I built it with EXMEM and when I put it in my camera, sure enough, the main menu is called "xMain Menu". I set it to enable RAW capture (didn't change anything else, just enabled that option) and my picture is still purple.

For what it's worth, I tried opening the RAW file (a .CR2) in another program and it still has purple in it but it is more like the shadows are purple. Here's a screenshot of what it shows in ufraw and an exported untouched (just exported as .jpg) file from irfan view: http://imgur.com/a/1hHl5 (I think ufraw is doing some automatic correction and that is why it's more like purple shadows than a purple filter.)

« Last Edit: 18 / March / 2012, 12:21:21 by Qanthelas »

Logged

waterwingz

12138

Re: A800 Porting Thread

« Reply #117 on: 18 / March / 2012, 12:03:24 »

Quote from: Qanthelas on 18 / March / 2012, 11:47:44

I set it to enable RAW capture (didn't change anything else, just enabled that option) and my picture is still purple.

Per this post :
http://chdk.setepontos.com/index.php?topic=7674.msg82190#msg82190
it seems that if the CFAPattern is not solving the problem then maybe the address used for the raw buffer is off by a little bit ?

Logged

Ported : A1200 SD940 G10 Powershot N G16

reyalp

14037

Re: A800 Porting Thread

« Reply #118 on: 18 / March / 2012, 14:48:36 »

Quote from: Qanthelas on 18 / March / 2012, 11:47:44

For what it's worth, I tried opening the RAW file (a .CR2) in another program and it still has purple in it but it is more like the shadows are purple.

That really doesn't tell you anything, because it's up to the individual program to interpret the raw. CFA pattern *only* affects DNG. CHDK raw is just a frame buffer dump. The only thing that affects the content of the file is the start address, dimensions and bit depth.

Logged

Don't forget what the H stands for.

reyalp

14037

Re: A800 Porting Thread

« Reply #119 on: 18 / March / 2012, 15:01:47 »

Can you upload a CR2 raw somewhere ?

Logged

Don't forget what the H stands for.