A1000IS porting...

  • 297 Replies
  • 64717 Views
  • Publish
    A1000IS porting...
    « on: 21 / November / 2008, 02:01:31 »
    Advertisements
    Hi,

           I am a newbie here. I started porting CHDK for A1000IS, firmware ver. 100b. I am done 30-40% with porting. I copied the tasks template from other porting efforts. I will upload the code and update the task template in my next mail. Just to hint you where I am, getting led-blinker, GUI, dumping RAW images, live histogram.

    Tasks:

        * Get the cam started.
              o start cam under chdk-control without any extensions
              o create led-blinker-test-task
          Progress: not done
        * GUI output.
              o General output
              o Histogramm
              o Zebra mode
          Progress: not done
        * hijack Keyboard handler (this includes USB-support)
          Progress: not done
        * hijack shoot-task.
              o control darkframe subtraction.
              o implement raw-save:
          Progress: not done
        * hijack movie-task.
          Progress: not done
        * Include multipartition/boot from SDHC support.
          Progress: not done
        * BASIC scripting.
          Progress: not done
        * Lua scripting.
          Progress: not done
        * Overrides.
              o AV
              o TV
              o ISO
              o Subject Distance
              o Bracketing in cont' mode
          Progress: not done
        * Image enhancement.
              o Bad Pixel removal
              o custom curves
          Progress: not done

    - Diablo
    « Last Edit: 21 / November / 2008, 02:29:42 by diablo »

  • Publish
    Re: A1000IS porting...
    « Reply #1 on: 22 / November / 2008, 00:42:50 »
    Hi,

    Here is the update along with a1000 specific changes attached with this. Lot of below tasks need to be tested to know whether they are working or they need more work.

        * Get the cam started.
              o start cam under chdk-control without any extensions
              o create led-blinker-test-task
          Progress: done
        * GUI output.
              o General output
              o Histogramm
              o Zebra mode
          Progress: done
        * hijack Keyboard handler (this includes USB-support)
          Progress: not done
        * hijack shoot-task.
              o control darkframe subtraction.
              o implement raw-save: Raw files saved. Tried to use them but all tools I tried returned format error.
          Progress: not done
        * hijack movie-task.
          Progress: not done
        * Include multipartition/boot from SDHC support.
          Progress: not done
        * BASIC scripting.
          Progress: not done
        * Lua scripting.
          Progress: not done
        * Overrides.
              o AV
              o TV
              o ISO
              o Subject Distance
              o Bracketing in cont' mode
          Progress: not done
        * Image enhancement.
              o Bad Pixel removal
              o custom curves
          Progress: not done

    - Diablo

  • Publish
    Re: A1000IS porting...
    « Reply #2 on: 22 / November / 2008, 01:18:52 »
    Hi,

    I am uploading compiled final binary. Please test it and post your comments.
    Use cardtricks to make your SD card bootable, copy the attached file to the card and lock the card.
    Note that it will work only on firmware version 1.00b.

    -Diablo

  • Publish
    Re: A1000IS porting...
    « Reply #3 on: 24 / November / 2008, 01:47:53 »
    Hi Guys,

    I hit one more blocker. This one, I may need help from some experienced ones.

    At present, the scripts that test zoom are working fine. But scripts that override iso, exposure, shutterspeed are not at all able to change any values.

    The function "SetPropertyCase" which is used for overriding any property is causing some problem. From script I could call set (tv96,av96,iso) and a subsequent get (tv96,av96,iso) to verify whether set is working fine or not. I am not able to change any of these with set and get displays the same value all the time.

    I verified with A720 and G9 cameras and found the mapping of SetPropertyCase and GetPropertyCase are correct. I then started suspecting the property IDs. Where can I find the property IDs? I saw that all(most) digic3 cameras use propert2.h. Can I be sure that property IDs are same in A1000IS? Does somebody faced similar problem with setting and getting properties?

    -Diablo


    *

    Offline reyalp

    • ******
    • 9874
  • Publish
    Re: A1000IS porting...
    « Reply #4 on: 24 / November / 2008, 02:02:29 »
    There are two currently known propcase sets. Common values can be found in propset1.h and propset2.h

    It is possible that canon has come up with yet another one for the A1000.

    If you have the property case browser (in the debug menu) working, you can use that to display various propcase values. Pick a known propcase from one of the sets, and watch it to see if it has the expected values when you change settings on the camera.

    edit:
    see also PropertyCase - CHDK Wiki
    « Last Edit: 24 / November / 2008, 02:07:05 by reyalp »
    Don't forget what the H stands for.

  • Publish
    Re: A1000IS porting...
    « Reply #5 on: 24 / November / 2008, 02:23:35 »
    Thanks Realp. I will enable propertyIDs in debugger and see if I could find the cause of the problem and resolve it.

  • Publish
    Re: A1000IS porting...
    « Reply #6 on: 25 / November / 2008, 04:07:19 »
    Hi,

    I couldn't spend much time on this. But I tried to debug set and get of PROPCASE_TV. This camera doesn't have manual control to change shutter speed. I could get this property that matches with the shutterspeedtable but I couldn't set it. Can it happen that it is readonly? What can we do if something is readonly?

    -Diablo

    *

    Offline whim

    • ******
    • 2013
    • A495/590/620/630 ixus70/115/220/230/300/870 S95
  • Publish
    Re: A1000IS porting...
    « Reply #7 on: 25 / November / 2008, 04:54:37 »
    Could it be that the cam just overwrites the values you set ?
    I would imagine that the cam keeps updating the memory location
    until the exposure is locked.
    Just my 2 c

    wim


  • Publish
    Re: A1000IS porting...
    « Reply #8 on: 25 / November / 2008, 16:09:42 »
    Hi,

    Thanks for your help whim. I found root cause of this problem. The function mode_get() was never returning MODE_PLAY. Now I can override the aperture,exposure and ISO values. Bracketing is working. I will upload sources and binary soon.

    -Diablo

    *

    Offline PhyrePhoX

    • *****
    • 2253
    • make RAW not WAR
      • PhyreWorX
  • Publish
    Re: A1000IS porting...
    « Reply #9 on: 25 / November / 2008, 16:12:48 »
    remember to upload the sources providing a diff file, will make integration into svn much easier :)

     

    Related Topics