A1000IS porting...

diablo

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

diablo

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

a1000IS_100b_chdk.zip

768.38KB

diablo

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

DISKBOOT.BIN

244.74KB

diablo

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

reyalp

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

diablo

Thanks Realp. I will enable propertyIDs in debugger and see if I could find the cause of the problem and resolve it.

diablo

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

whim

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

diablo

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

PhyrePhoX

remember to upload the sources providing a diff file, will make integration into svn much easier 😀

michaelkenward

Another newbie. This time, though, one sitting here awaiting the output.

Happy to test anything you want checked. Got the camera last week.

Thanks in advance for the effort.

tyrantt23

Sorry for the newbie post, but how do I check to see what's the firmware version on my camera?
New member here. Just wanted to say, thank you so much for your efforts on the development for the Canon A1000IS. I'm looking forward to using it to its full potential. 😀

Once again, thanks.

letsapocalypso

Like michaelkenward and tyrantt23, I'm also a newbie with a new A1000IS...

Diablo - We're all deeply appreciative of your time and hard work towards porting this model, and I'd like to help with the effort in whatever way possible...

I'll be uploading the next binary you post, and trying to find any remaining bugs not listed in the "known issues"...

Thanks again, Diablo!

diablo

Hi,

As you might already know if you read my first post, I am also a newbie. To add more to that, this is my first camera and I never heard of CHDK till one month back.

Refer to FAQ(FAQ - CHDK Wiki) if you have any basic question in installing or using CHDK

Though I already found some issues, I am uploading the latest binary that I have.

Note that, this is supported only for A1000IS, version 100b. Refer FAQ for finding which version you have.

-Diablo

DISKBOOT.BIN

244.76KB

michaelkenward

tyrantt23
Sorry for the newbie post, but how do I check to see what's the firmware version on my camera?

This is question number 3 in the FAQ:

FAQ - CHDK Wiki

michaelkenward

diablo
Hi,

As you might already know if you read my first post, I am also a newbie. To add more to that, this is my first camera and I never heard of CHDK till one month back.

Yes. I did notice, and have great admiration for your willingness to jump in at the deep end!

I would not know where to begin.

tyrantt23

michaelkenward

tyrantt23
Sorry for the newbie post, but how do I check to see what's the firmware version on my camera?

This is question number 3 in the FAQ:

FAQ - CHDK Wiki

Ah, thank you very much. I thought I had already looked on the FAQ, but I guess not. I'll be sure to check it again before asking any trivial questions. 😀

Turns out my camera's firmware version is 1.00b. I'll go ahead and download the latest version and try running it on my camera when I come back from work. Once again, million thanks Diablo.

ps. Looks like Diablo 3 is gonna rock! 😁

michaelkenward

tyrantt23
Turns out my camera's firmware version is 1.00b. I'll go ahead and download the latest version and try running it on my camera when I come back from work. Once again, million thanks Diablo.

ps. Looks like Diablo 3 is gonna rock! 😁

My firmware is, unfortunately, 1.00A.

I have looked everywhere I can think of for an update. US site, European site. Nothing.

None of the pointers from this site get me anywhere.

Anyone got a working link?

whim

Anyone got a working link?

a link to what ? Canon only very rarely issues 'updates', and only they know if cams with
different firmwares are totally identical hardware-wise.
So, each firmware version requires it's own port.
You can dump your firmware, and compare it with the existing dump, though.
If you're very lucky, they are identical enough not to require a separate porting process
(based on previously ported cams, there's only a couple of % chance though)

wim

clemsche

Another newbie, just want to say that I'll love to see CHDK ported to the A1000IS. Keep up the great work!