G11 porting - page 27 - DryOS Development - CHDK Forum supplierdeeply

G11 porting

  • 530 Replies
  • 233213 Views
*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #260 on: 14 / January / 2010, 15:07:43 »
Advertisements

Re: G11 porting
« Reply #261 on: 14 / January / 2010, 15:56:10 »

*

Offline reyalp

  • ******
  • 14082
Re: G11 porting
« Reply #262 on: 15 / January / 2010, 03:58:32 »
Then you have another option in the debug menu, which calls the FW function "GetLogToFile",
and this will do the job and creates a file in the root of your SD-Card with the assert/exception information of the last crash.
You can also do this with the eventproc interface and a lua script, no patch needed. You probably need to call "System.Create" or "SystemEventInit" first.

I was going to merge the GetLogToFile patch, but I couldn't get it to work under vxworks, so I couldn't test it.

You can also read the log directly from ROM, seems to always be at FFFFE000 on the cameras that I've looked at. Some decoding would be required.
Don't forget what the H stands for.

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #263 on: 17 / January / 2010, 02:56:01 »


*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #264 on: 17 / January / 2010, 02:58:41 »
You can also do this with the eventproc interface and a lua script, no patch needed. You probably need to call "System.Create" or "SystemEventInit" first.

Cool. I think it would be very helpfull (for bugreports and also in generell for development), if its possible to get the ErrorLog via a script on every dryos camera without need of patching CHDK.

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #265 on: 17 / January / 2010, 03:12:04 »
The port is almost finished, but during my test i found three things that are not working as expected:

1) If CHDK is used to put in the ND-Filter, the ND-Filter snaps in (good), but after 2-3 Seconds the camera throws an assert.
    If i put in the ND-Filter via the original canon menu, and then via CHDK no assert happens, maybe they have now a check in the
    code to verify (hw via. sw) state of the ND-Filter. So i currently disabled the HAS_NDFILTER option in camera.h for my port.

2) The lua testscript almost works, but there is one FAIL entry left. The "Remove" command is not able to remove the "A/MDTST0" directory. Removing files in the directory is working fine.

3) The Zebramode looks strange. With the standard zebra-osd-code, i got the screen half filled with strange pixel fragments. So i add the g11 to the define checks in gui_osd.c (#if defined (CAMERA_sx200is) || defined (CAMERA_g11)). So the sx200is code is used know, because of the same framebuffer & resolution layout. This looks a lot better, but not perfect. The zebra drawing does not match the overexposed areas, it is allways drawn under it.  :blink:

Re: G11 porting
« Reply #266 on: 17 / January / 2010, 06:21:58 »
Can you post an image showing a simple shape, such as a lightshade or overexposed computer monitor ?


Re: G11 porting
« Reply #267 on: 17 / January / 2010, 07:06:51 »
The position in the buffer of a pixel at x,y is  :-

sy=y*screen_buffer_width;
s=sy+x*2;

because every x pixel is drawn twice (or four times for multichannel).

If the zebra is drawn too low but correctly positioned horizontally, the value for screen_buffer width must be too big.


*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #268 on: 17 / January / 2010, 07:19:13 »
Okay, here is one example picture, the zebra drawing is to low and also streched.
Horizontally positioning looks ok, i think.

Currently, i use this size:
long vid_get_bitmap_buffer_width() { return 960; }

As may you can see, also a green distortion line on the top of the display often occurs with activated zebra drawing.
« Last Edit: 17 / January / 2010, 07:20:47 by ERR99 »

Re: G11 porting
« Reply #269 on: 17 / January / 2010, 07:26:56 »
viewport_width = vid_get_viewport_width();

What width are you using for the live viewport ?

It is normally 360 but maybe it is 480 with the G11 ?

(I cannot remember if you have tested other features that require a correct value for viewport width, such as edge outline and motion detection).
« Last Edit: 17 / January / 2010, 07:42:37 by Microfunguy »

 

Related Topics