supplierdeeply

A800 Porting Thread

  • 277 Replies
  • 30236 Views
Re: A800 Porting Thread
« Reply #30 on: 23 / January / 2012, 01:21:36 »
Advertisements
Glad to see that this is coming along so nicely :) Keep going mlands, you're on a roll! :D  If you have a new version ready, post it and I'd be happy to test it on my camera.  If you could enable scripts, that would make testing much easier, too :)

Re: A800 Porting Thread
« Reply #31 on: 23 / January / 2012, 10:20:38 »
I am posting source and a compiled version with all options. I test some features according the manual: the zebra I couldn't  see anything althoug I have tried some parameters. The histogram displayed but always black and white. Script was running a default script version . Sometimes I think the <ALT> was kept (in "background") in the screen under the histogram when I've changed to normal operation. Maybe I get lost when testing.

Re: A800 Porting Thread
« Reply #32 on: 24 / January / 2012, 17:23:03 »
I have detected a problem in the last compilation in capt_seq.c on expdrv_task that extends the opening time of the shutter. I will recheck it and try to solve the problem.

Re: A800 Porting Thread
« Reply #33 on: 25 / January / 2012, 00:38:40 »
  I have commented one routine call in expdrv task and the problem appeared when I was revising and included the routine and didn't  test it. At that time I was testing the menus And I thought I had got lost.
   I checked the code and I see no problems (I compared the dump generated do disassembled code). The problem appears when I call apex2us (the patched version). I can see it on the dump generated, but I can't find the src.I image it is on a lib. So if someone could check if there is something I missed, that would be fine. I tested with 3 trunk versions(1487, 1593 and 1610) it behaves the same. The symptom is like the camera being permanently configured to a overexposure (about 2seconds I would say)

As Qanthelas is testing, I am posting a version where I use the firmware apex2us and tests may go on.


*

Offline philmoz

  • *****
  • 2936
    • Photos
Re: A800 Porting Thread
« Reply #34 on: 25 / January / 2012, 02:56:28 »
  I have commented one routine call in expdrv task and the problem appeared when I was revising and included the routine and didn't  test it. At that time I was testing the menus And I thought I had got lost.
   I checked the code and I see no problems (I compared the dump generated do disassembled code). The problem appears when I call apex2us (the patched version). I can see it on the dump generated, but I can't find the src.I image it is on a lib. So if someone could check if there is something I missed, that would be fine. I tested with 3 trunk versions(1487, 1593 and 1610) it behaves the same. The symptom is like the camera being permanently configured to a overexposure (about 2seconds I would say)

As Qanthelas is testing, I am posting a version where I use the firmware apex2us and tests may go on.


In your platform_camera.h you have CAM_PROPSET = 3.
This is probably wrong given the release date of the camera, it's most likely going to be 4.
The result is the camera is looking at the wrong property values for things like the Tv and Av values - this is likely messing up your overrides.

You can turn on the PROPS display in the debug menu and the verify that the displayed values look reasonable for each of the values in propset4.h.

Hopefully you won't have to add a new propset5.h files to the system.

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)

Re: A800 Porting Thread
« Reply #35 on: 25 / January / 2012, 16:01:23 »
Ok.
  I checked some properties (zoom_position, flash_ready,shooting) they were like propset4.h. I have changed and made some tests and it seems ok.Thanks, Phil.
  I am posting sources and a trunk1610 compiled version.
PS: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 #36 on: 30 / January / 2012, 16:07:55 »
Hi,

Recenty bought a800, it has 100b firmware.
I'm new to chdk stuff, but have programming experience.

So I have a question:
- Is it possible to upgrade firmware to 100c and help with development?
- Or should I port 100c code to 100b?



*

Offline reyalp

  • ******
  • 10069
Re: A800 Porting Thread
« Reply #37 on: 30 / January / 2012, 17:22:30 »
- Is it possible to upgrade firmware to 100c
Not unless Canon issued a firmware update, which is extremely rate.
Quote
- Or should I port 100c code to 100b?
It's possible that the 100c version will work unchanged on 100b. If not, then a new port is needed, and if you are a programmer, it's not terribly hard to do. See http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version
Don't forget what the H stands for.


Re: A800 Porting Thread
« Reply #38 on: 30 / January / 2012, 19:02:56 »
Recenty bought a800, it has 100b firmware.
If nothing else, it would be good to have a firmware dump for that version.  That would also tell us whether the 1.00c code would likely run on the 1.00b.
http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper

Re: A800 Porting Thread
« Reply #39 on: 31 / January / 2012, 14:30:39 »

 

Related Topics