CHDK Forum
CHDK Development => General Discussion and Assistance => DryOS Development => Topic started by: diablo on 21 / November / 2008, 02:01:31
-
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
-
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
-
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
-
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
-
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 (http://chdk.wikia.com/wiki/PropertyCase)
-
Thanks Realp. I will enable propertyIDs in debugger and see if I could find the cause of the problem and resolve it.
-
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
-
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
-
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
-
remember to upload the sources providing a diff file, will make integration into svn much easier :)
-
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.
-
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.
-
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!
-
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 (http://chdk.wikia.com/wiki/FAQ)) 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
-
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 (http://chdk.wikia.com/wiki/FAQ)
-
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.
-
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 (http://chdk.wikia.com/wiki/FAQ)
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! :D
-
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! :D
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?
-
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
-
Another newbie, just want to say that I'll love to see CHDK ported to the A1000IS. Keep up the great work!
-
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.
I was looking for a link to a firmware update, of course.
I am used to the EOS range. Canon has issued several updates for those.
I guess they have to pay more attention to "serious" photographers.
-
I was looking for a link to a firmware update, of course
This wiki page has a link to Canon update site: FAQ - CHDK Wiki (http://chdk.wikia.com/wiki/FAQ#Q._How_can_I_update_the_original_Canon_firmware.3F)
As you will notice, the last official Canon update for P&S dates back to 2006 ...
What i was trying to say, i guess, is that (IMHO, of course) you're better off
concentrating on getting your firmware version ported; even if this is a lot
of work, it will still be a faster way to upgrade your cam than waiting for
Canon ...
Besides, it is unlikely (judging from ported cams) that that differences between
the (currently 2) reported A1000 firmwares actually qualify as 'upgrades',
more likely they are small differences to account for the use of different
sources of custom chips in the cam (according to comments i read from
devs)
hth,
wim
PS you prob already found your cam's wiki page, but if not A1000IS - CHDK Wiki (http://chdk.wikia.com/wiki/A1000IS)
-
Hey michaelkenward, sorry to hear about your different camera firmware. :(
I'm just posting back my results with the current build.
I got the battery meter, the optical temperature sensor, and the clock working on the camera's GUI, which are from CHDK. Everything else seems to be from the same as the default on the camera. I'm not sure I did anything wrong, or if its supposed to be that way - it's my first time using CHDK.
To load the firmware onto the camera, I followed the FAQ (http://chdk.wikia.com/wiki/FAQ#Q._How_do_I_get_CHDK_onto_my_camera.27s_SD_memory_card.3F) on how to format the SD card using CardTricks (http://chdk.setepontos.com/index.php/topic,964.0.html). Then I made the SD card bootable, and copied the most recent DISKBOOT.BIN that Diablo posted here. I locked the SD card, put it in the camera, and turned it on. CHDK seemed to be loading, and then the regular camera GUI appeared, with some extra info on the background (the temperature sensor, battery meter, clock time, and an orange horizontal bar on the bottom left corner that didn't seem to do anything).
When I put the card back in the computer, I noticed a folder called CHDK was created, with empty subdirectories. I went to the CHDK download page (http://mighty-hoernsche.de/) and downloaded the COMPLETE zip files (which include the CHDK folder) for a couple of different cameras (A1000.b wasn't listed). I compared the CHDK folders from the different downloads and they were the same, so I figured that the CHDK folder would be the same for every camera (correct me if I'm wrong) and copied that folder which I just downloaded to my SD card.
I put the card (with the complete CHDK folder now) back in the camera and turned it on. The GUI was still the same.
I understand that this camera port is still at a very early phase in development, but I just wanted to give a report of what I did, and what I got. If I'm going about it the wrong way, point me to some more links or downloads so that I can read up a bit more. :)
If there's anything else I can do to help, let me know... I'm gonna start working crazy hours up until christmas (10 to 17 hour days), but when I have some free time, I'll be glad to help. :)
Once again, thanks a lot for the time and effort to get this camera port to work. I really love this little camera, and CHDK would make it godly.
-
Hi,
Posting the latest status here. Also attaching latest binary.
* 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 seem to open with picassa.
Progress: Partially done
* hijack movie-task.
Progress: testing
* Include multipartition/boot from SDHC support.
Progress: not done.
* BASIC scripting.
Progress: done
* Lua scripting.
Progress: not done
* Overrides.
o AV
o TV
o ISO
o Subject Distance
o Bracketing in cont' mode
Progress: done
* Image enhancement.
o Bad Pixel removal
o custom curves
Progress: testing
Apart from above update, since I am a newbie to use CHDK, I have some basic questions. Senior folks, please help out.
1. RAW support:
I found that there is some differnce between number of bits per pixel to be stored for RAW file. I faced exact situation posted in ixus90/sd790 IS porting (http://chdk.setepontos.com/index.php/topic,2187.msg20752.html#msg20752). So I decided to reduce the Rawbuf size to be copied. I calculated manually the size and used it in hook_raw_size.
Now the RAW files are smaller(~12M) size. The dng4ps2 recognizes the files(earlier it wasn't recognizing). I converted them to get RAW with exif data on it. Finally I tried to open them in almost all RAW processing s/w listed in CHDK FAQ page. But all of them showed a color jig-jag image. Picassa was able to display the image for 1 sec and turns to color jig-jag after one sec.
Then I tried to calculated color matrix by taking snap of color pallete found in a different thread. Still no success. Any help in this regard is appreaciated.
2. Hijack keyboard:
I have no idea what is to be done here. What is expected in this item. Does people use USB attached switch for taking snapshots? I hope I cannot get one of these at my place, unless I make it my self.
3. custom curves:
What are they? Any help or pointer to this is appreaciated.
michaelkenward,
Sorry to hear that you have 1.00a version. Since I have ported 1.00b, I can start porting 1.00a as well. I will let you know once I start it. As I don't have 1.00a camera, I will be working blind and you have to test and give feedback on the changes.
tyrantt23,
As you can see the status above, lot of things are working now. You need to press ALT key(print key) then DISP to get CHDK menu. Read more in CHDK usage page on basic keys and shortcuts for using CHDK.
-Diablo
-
Just wanna give another short "bug"-report: I'm also new to CHDK but tried to get some scripts working, one was a intervall-script which worked fine. I've copied the A720 CHDK directory onto my SD card. Is there any difference between the CHDK directories or are they all the same?
The RAW files couldn't be recognized with ufraw (I'm using linux) but the A1000 showed them correctly. Maybe the new version Diablo posted works better.
The only things that bugs me is that parts of the OSD are remaining on the screen. Btw, I'm using a PAL A1000IS with german OSD, maybe the translation bugs the OSD. And when I press the PLAY button and the shutter is closed it seems the A1000 is shutting down, maybe that's not a bug but a feature of CHDK... ;)
But overall I'm really glad that CHDK is ported to such a nice camera! Keep up the great work, Diablo!!
-
Checked the new version and the new (and smaller) CRW files couldn't be read by either Picasa 3.0 (under Debian) nor ufraw.
-
Did you converted the files using dng4ps2? I was able to open then in picasa 3.
-
Diablo, thank you for the tip. I will read up a bit more on the usage of CHDK, I didn't know I had to push buttons to get the CHDK menus. I'll try out the new update and post back with the results. I'm excited to see that the development is going forward real quickly. :)
And when I press the PLAY button and the shutter is closed it seems the A1000 is shutting down, maybe that's not a bug but a feature of CHDK... ;)
Probably a feature. I had my camera set to work like that on the original Canon firmware by changing a setting in the options with the name "Lens Retract" to 0 seconds I believe. That tells the camera to wait X seconds before retracting the lenses after you push play to look at the pictures. You might be able to find a similar option on CHDK.
I've copied the A720 CHDK directory onto my SD card. Is there any difference between the CHDK directories or are they all the same?
I did the same thing. I checked the size of the directories for different cameras and they were the same, but I'm not sure that the content is exactly the same. My guess is that yes, CHDK and its directories are the same for every camera, only DISKBOOT.BIN (the actual porting of the camera) is different. But... I may be wrong, like I said before, I'm a complete newbie. :)
Keep up the great work, Diablo!!
Quote for truth. Keep it up Diablo. :D
-
Checked the new version and the new (and smaller) CRW files couldn't be read by either Picasa 3.0 (under Debian) nor ufraw.
Like Diablo said, you need to download DNG4PowerShot2 (http://dng4ps2.chat.ru/index_en.html). Here is the link to the CHDK FAQ - I've Shot Some RAW Pictures. How Do I Process Them? (http://chdk.wikia.com/wiki/FAQ#Q._I.27ve_shot_some_RAW_pictures._How_do_I_process_them.3F)
From what I've read, the CRW raw files produced by the PowerShot cameras, are different than the other camera formats. They also don't produce any EXIF information. So, The DNG4PowerShot solves those two problems - it converts the CRW files to Adobe's DNG, and it copies the EXIF information from the corresponding JPEG picture to the new DNG file.
UPDATE: I've just downloaded dng4ps2, and when I select the path to the Raw files, it doesn't list anything on my SD card. I then went to their website to read up a bit about it, and noticed that the A1000 is not listed as one of their supported cameras. How were you able to convert the pictures Diablo? Any pointers or links would be appreciated. In the meantime, I'll read up a bit more and post back here with results.
-
I edited A720 camera profile and used it for A1000IS. You just need to rename the camera(setting->camera options->cameraname, shortname) and change resolution(to 3648x2736 in both sensor size and jpeg size). With this I could get them displayed in dng4ps2 but after covert the images displayed were incorrect.
The images opened properly in picassa3 properly and in 1-2 sec the display changes to jig-jag color.
I am right now in the process of doing color profile calculation. I will let you know once I get good results. It is good if you also can do this simultaneously so that we can get a good color profile. You can read the following thread on how to do it. New project: camera color profile calculation (http://chdk.setepontos.com/index.php/topic,390.0.html)
-
I edited A720 camera profile and used it for A1000IS. You just need to rename the camera(setting->camera options->cameraname, shortname) and change resolution(to 3648x2736 in both sensor size and jpeg size). With this I could get them displayed in dng4ps2 but after covert the images displayed were incorrect.
The images opened properly in picassa3 properly and in 1-2 sec the display changes to jig-jag color.
I am right now in the process of doing color profile calculation. I will let you know once I get good results. It is good if you also can do this simultaneously so that we can get a good color profile. You can read the following thread on how to do it. New project: camera color profile calculation (http://chdk.setepontos.com/index.php/topic,390.0.html)
Just for clarification to other people... the (setting->camera options->cameraname, shortname) is to be done in dng4ps2, not on the camera or CHDK.
Moving on...
aha, that did the trick so that the files are showing on dng4ps2, thank you Diablo. I'll check how the files behave on other RAW Editing Software and post back.
Now, I noticed that on the A720 profile, the sensor size has a bigger resolution than on the JPG file. Should it be this way for the A1000 also, or are both resolutions the same for this camera model?
As far as the color profile calculation, I've already taken the pictures and sent both the RAW and JPG to the developer of dng4ps2, since I couldn't get the files to show on the browser. In about 24 hours I'll be posting the results that I got for the color matrix on the forums.
I have to go to sleep now... just went out for my birthday celebration and drank quite a few beers here in Brazil... and I have to go to work in about 4 hours. I'm always surprised at how coherent I seem to be when writing on the internet, no matter how drunk I am. Please tell me if I'm just fooling myself.
/rant
Moving on... thanks for the help Diablo.
I'll give an update of my RAW situation asap. :)
~ Ralph
UPDATE: I'm having the same problem as you Diablo, I try to open it with a few programs and the picture/thumbnails show up correctly for about 2-3 seconds, then a jigsaw/noise image appears.
Picasa and RAW Photo Desk
- Jigsaw appears
SILKYPIX
- Nothing appears
Photoshop CS3
- Says that it can't complete the request (open the document) because it is not the right type of document
Raw Therapee
- Shows jigsaw thumbnails
tomorrow I'll post the color profile calculation on the right thread. For now, I'm going to bed.
Once again (and I don't mean to sound redundant), thank you for your help Diablo.
-
Just for clarification to other people... the (setting->camera options->cameraname, shortname) is to be done in dng4ps2, not on the camera or CHDK.
Moving on...
aha, that did the trick so that the files are showing on dng4ps2, thank you Diablo. I'll check how the files behave on other RAW Editing Software and post back.
Now, I noticed that on the A720 profile, the sensor size has a bigger resolution than on the JPG file. Should it be this way for the A1000 also, or are both resolutions the same for this camera model?
Sensor size is (almost ?) always larger than jpeg size. Not only is the actual data area a bit larger, there are black border pixels as well. You may be able to figure out the correct dimensions from the hook_raw_size() value, assuming that has been correctly determined.
You should not expect any third party programs to understand the .crw files from a new CHDK port. They aren't canon format CRWs, they are just a dump of the sensor.
-
Just gave a try to run multipurpose motion detection from here UBASIC/Scripts: Multipurpose Motion Detection - CHDK Wiki (http://chdk.wikia.com/wiki/UBASIC/Scripts:_Multipurpose_Motion_Detection). Amazing to see it worked.
tyrantt23, Any updates on color profile calculation?
Folks, apart from RAW support, please tell me if you face any bugs.
Moderators, When and how should I make this into auto build?
-Diablo
-
well, if all tests go well, you are to provide a patch/diff directly from svn. we then comitt this diff to the svn -> autobuild.
-
Hi Diablo,
congratulations to your success!
I followed this thread for a very special purpose. I do hobby aerial photography from a model airplane and I am currently looking for a new compact digital camera. The A1000 IS looked nice to me, except that it had no manual modes, especially shutter priority, which is very much needed. The other very useful feature would be an interval continuous shooting mode, say to shoot a picture every 1 sec with exposure metering every time. Could such a thing be programmed with the CHDK support?
The most important feature for me however would be to be able to set shutter priority with a certain shutter time and ideally also to set focus to infinity. Is this a feasible feature now?
Many thanks for your answer!
Norbert
-
There's still the "bug" of the menus staying onscreen when leaving. Is this a build-in bug by CHDK? Till now, I really like to see the progress you've made, Diablo! Keep it up!
-
I have been watching this post for the same reason as EyP3, (post #34)- RC aerial photography. I am currently using an A570is with CHDK with great results.The A1000is would be an improvement in megapixels, which does increase printing options, and is lighter by 25 grams. As Norbert said in his post, shutter priority is critical to getting sharp photos from a moving camera that is attached to an RC airplane.
I would also like to say thanks to Diablo for his hard work in the development of CHDK for
the A1000is camera. This could be my next camera.
Jim
-
Diablo, I had taken the picture in JPEG and RAW, but since I couldn't get the RAW to open, I didn't know what my next step should be for the profile calculation. Also, I followed the directions stated on the color profile calculation thread
(http://chdk.setepontos.com/index.php/topic,390.0.html) but since the camera doesn't show at exact what optical zoom it's at, I took the picture at what I "thought" was mid-zoom. I hope this doesn't skew the results.
Here, I uploaded both the JPEG and the RAW to this link:
http://www.zshare.net/download/524077889f256482/ (http://www.zshare.net/download/524077889f256482/) let me know if there's anything else I can do to help.
As far as bugs, the other day my camera froze while I was meddling with the CHDK menus. The LCD screen locked and the lenses were sticking out. I wasn't able to turn the camera off, so I had to take the batteries out. When I turned the camera back on, the lenses retracted and everything went back to normal. I tried to replicate the freeze later, but couldn't get it to do that.
The only other thing I have to say is also about the menus not refreshing. I have to push the shutter button halfway for the camera to focus and refresh the screen. Is there some code available to force CHDK to refresh the screen each time you push the "Func. Set" button while navigating the CHDK menu? Everything else seems to be working really well. I'll run some more tests tomorrow with forced aperture, iso, and exposure settings. Great work on the port Diablo. :)
Propfly and EyP3, you can already set the focus to infinity with the default camera firmware, as well as setting the shutter time from 1 to 15 seconds. What you can't do is directly set the aperture, shutter speed or a combination of the two in manual mode. Here's a very useful link that reviews the Canon A1000 IS (http://www.photographyblog.com/reviews_canon_powershot_a1000_is.php). It's from that review that I decided to buy the A1000 instead of the A590.
-
I also cant open the RAW. It's corrupted...
-
tyrantt23,
thanks for the link, for me it was also that review that had me made considering the A1000 :-).
I downloaded the user manual, but I could not find where I would set the focus to infinity (except setting landscape mode). On page 88 it says one can set the shutter speed to make the image darker or brighter. That would be not very useful. I need shutter priority to adjust aperture / ISO accordingly to my chosen shutter time, say 1/1000 sec. As I don't have the camera, I cannot check this. Any help?
Thanks
Norbert
-
...I downloaded the user manual (http://gdlp01.c-wss.com/gds/0300001222/PSA1000IS_CUG_EN_02.pdf), but I could not find where I would set the focus to infinity (except setting landscape mode)...
--> page 65 ! (Button "LEFT", not available in Auto-mode)
-
@EyP3
Not sure if i understand your Q , but AFAIK all Canon P&S can be set to infinity by choosing Landscape ('mountain' symbol)
in the Canon mini menu popping up if you press <Left> (AKA the same place you select macro)
See page 65 of your manual
wim
edit: $#@! too slow again
-
Thanks, got it.
That leaves the questions for the shutter priority mode and continuous shooting with defined interval?
Thanks for any help!
Norbert
-
Hi,
Just want to give a quick update to 1.00a firmware users. I found that a lot of code is same between 1.00a and 1.00b. I might take a while to check everything is same between the two. But I would request 1.00a users to try the binary attached with this message. From what I found, there was a small change in canon_data_src address. So for now I have changed only that and built it. Please spend a couple of minutes in installing this binary and test whether camera boots up or not.
To install->
1. Use card tricks and make your card bootable
2. Copy DISKBOOT.BIN from this msg.
3. Lock the SD card.
4. Start camera.
5. Check the page for how to use: CHDK firmware usage - CHDK Wiki (http://chdk.wikia.com/wiki/CHDK_firmware_usage)
Let me know your observations.
Norbert,
You can have shutter priority mode with CHDK. Also scripts can be written to do continuous shooting with defined interval. Refer to CHDK FAQ and CHDK usage in CHDK - CHDK Wiki (http://chdk.wikia.com/wiki/CHDK) to know how to do it with CHDK. You might want to start right away with the latest binary posted earlier.
-
Diablo,
many thanks for your answer and especially also many thanks for your hard work!
I would start right away to test your port, if I already had the camera :-). However, your message is really good news and so I think next thing for me is to buy the cam. I will have a look at the CHDK faq and as soon as I got the cam, you can count on me as a new tester!
Many thanks!
Norbert
-
As promised, I played around with override shutter speed, ISO, and aperture.
They all seemed to work as they're supposed to. I didn't go as far as opening the pictures on the computer and comparing them at 100% zoom, but from the light exposure difference on the pictures, those features seem to be working and I didn't find any bugs on the quick run down that I did on them.
The same goes for Bracketing in Continuous Mode.
Minor Bugs:
Zebra Mode - When zebra mode is activated, the shutter speed and aperture value that usually show up on the bottom-left side screen (when the shutter button is pressed halfway), only stay on the screen for a short time. As soon as the zebra mode appears on the screen, the aperture value and shutter speed disappear. This can be fixed by turning the zebra mode off.
Note: It seems that checking the Restore OSD option, inside the Zebra Parameters menu causes the apperture value and shutter speed to stay on screen a tiny bit longer.
Unchecking it, and then selecting [OSD] on the "Draw Over Zebra" option, causes the OSD to show up only for a very short time.
I hope this explanation made some sense.
Menu auto-clearing - When browsing through the HDCK menus and the camera detects a face(s) (When the face detection is turned on by the FACE SELECT button), the menu clears. Pushing the up/down buttons on the camera to further browse the menus make the menu reappear once again.
That's all that I got so far. I'm starting to get very comfortable with CHDK, and I'm starting to really love it. I don't mean to sound redundant, but I just can't express it enough... thank you for your efforts Diablo, it's coming out great! :D
-
You are a genuine hero. I have retrieved the file.
As I have had no chance of playing around I need to work out what to do with it. (Maybe we need a guide to CHDK for people who are not intelligent enough to qualify as dummies.)
-
You are a genuine hero. I have retrieved the file.
As I have had no chance of playing around I need to work out what to do with it. (Maybe we need a guide to CHDK for people who are not intelligent enough to qualify as dummies.)
Hey, I'll try to post a short version of a how-to. It should work, but if it doesn't or if you get stuck in some place, let me know and I'll write it up in more detail. :)
Before proceeding, be sure you have already downloaded the latest version of the CHDK port that Diablo has made that works for your camera firmware.
Also, make sure you make make a copy of all the pictures and files in your SD card to your computer. Part of the process will format the SD card to make it bootable, so you will lose everything in it.
1. Download the latest version of Card Tricks from this link (http://chdk.setepontos.com/index.php/topic,964.msg8213.html#msg8213).
2. Extract the downloaded zip file.
3. Insert the SD card into your computer, or a card reader.
4. Run CardTricks.exe
Warning: This next step will erase everything in your SD Card. Make sure you make copies of any files you want to keep.
5. Click on the "Make Bootable" button, under "CHDK Autorun:"
6. Wait for the card to be formated.
7. Copy the CHDK Port from Diablo, DISKBOOT.BIN, to the root of your newly formatted SD Card.
8. Remove the SD card from the computer.
9. Move the "Lock" switch on the SD card onto the Lock position
10. Insert it in the camera, and then turn the camera on. CHDK should now be loaded.
To access the CHDK Menu, push the <ALT.> Button in the camera (the one with the print symbol), and then push the <DISP.> button.
Hope this helps. :)
-
I think I found another minor bug. I will run some more tests tomorrow.
Focus Bracketing:
Suppose I set the focus bracketing to be 5, with a value 100 for multiple, and suppose that my original focus is 50mm. If I set the bracketing type to [ + ], then the continuous pictures should come out with the following focus values:
50mm
50mm + 5*100 = 550mm
550mm + 5*100 = 1050mm
1050mm + 5*100 = 1550mm
1550mm + 5*100 = 2050mm, and so on.
Instead, only the first focus in the bracket seem to come out. Example:
50mm
50mm + 5*100 = 550mm
50mm + 5*100 = 550mm
50mm + 5*100 = 550mm, and so on.
The same thing seemed to happen for the [+/-] bracketing as well, and didn't seem make a difference which value I picked for the focus bracketing/multiple.
ps. Let me know if you think I'm doing something wrong, or if you're pretty certain those parts of CHDK are bug free. I don't want to be posting false bugs and get in your way. :)
Like I said, I'll run some more tests tomorrow. My camera's battery just ran out and I need to recharge it.
-
Hope this helps. :)
It sure does.
I wish I had seen something that simple before I tried it.
It was the last step that I hadn't found.
and then push the <DISP.> button.
Just played around a bit and see all sorts of delights.
I don't seem to have access to the "back" entry in the "Main Menu". It scrolls down as far as "Miscellaneous stuff" and sticks.
But there doesn't seem to be much need for that, even though there is a "back" bar that I cannot reach.
Looks like the "minor tweaks" to get it to work for the "0a" version did a pretty good job. You could describe it as "Diablobolically" neat.
Thanks to everyone.
-
I don't seem to have access to the "back" entry in the "Main Menu".
that's because there is none... where would you want to go "back" to ?
"back" means "1 level up in the menu" (same as pressing <Display> on most cams)
to leave the main menu, just press <Menu>
more interesting keys ? go here: FAQ - CHDK Wiki (http://chdk.wikia.com/wiki/FAQ#Q._What_are_the_key_settings_and_shortcuts.3F)
HTH,
wim
-
I don't seem to have access to the "back" entry in the "Main Menu".
that's because there is none... where would you want to go "back" to ?
"back" means "1 level up in the menu" (same as pressing <Display> on most cams)
to leave the main menu, just press <Menu>
more interesting keys ? go here: FAQ - CHDK Wiki (http://chdk.wikia.com/wiki/FAQ#Q._What_are_the_key_settings_and_shortcuts.3F)
HTH,
wim
That is why I said "there doesn't seem to be much need for that".
But if you read my message, I said that when I look at that screen for the main menu there is a "back" bar. I just cannot get to it.
Actually, I have just looked again, and what seems to be happening is that the "back" bar appears only after you have left the main menu and turned to it.
In other words, there is no "back" bar when you first reach the main menu. It appears only when you have been on to another menu and come back.
Looks like a screen is not rewriting something or other.
Thanks you for the link to FAQ - CHDK Wiki. I have been there a lot, but it is hard to follow in parts. Probably because it is so big. It didn't, for example, have the "dimwits guide" that tyrantt23 kindly offered.
As you linked to a bookmark within the FAQ, that was also a great help. No need to scroll all over the place for things that I didn't know I was looking for. Thanks.
-
Looks like a screen is not rewriting something or other
Aah...now i get it -- ran into that too in one of the earlier A590 versions ...
it'll go away as the port matures, i suppose.
wim
-
I am aware of the screen not refreshing issue. The function "RefreshPhysicalScreen" is not working at all.
Calling or not calling it has no effect. I compared it with disassembly of A720 and G9. For A1000, the method is slightly different. But I made sure that the caller and callee are matched with other cameras. So for now, refreshing can be done by half pressing shoot button.
michaelkenward,
Good to hear that 1.00a is working without major changes. Can you get scripts from other camera and run those on your camera. Also try shooting CRT screen with different values of shutter speed. You should see scan lines. You might as well post your results in porting status template for completeness.
-
Thee screen thing is no big deal when you realise what is happening. I was just being slow.
Will play around as you suggest when I have time.
I still need to learn a few things to make the tweaks stick.
I should have said that my experience of this stuff makes "newbies" look like PhD candidates.
-
Can you get scripts from other camera and run those on your camera. Also try shooting CRT screen with different values of shutter speed. You should see scan lines.
I will try running scripts from other cameras on Sunday when I have the day off, but for now, I'm working 14 hour days... *yikes*
What do you mean to try and shoot the CRT screen and we should see scan lines? Is there a specific shutter speed where the scan lines should start appearing on the pictures? Given that my... oh... never mind, I just remembered that my laptop's screen isn't LCD. That's why it didn't work when I tried yesterday. d'oh!
Anyway... on with the math. Given that CRTs usually have a 60Hertz refresh rate which is about 0.0166666... seconds per refresh, should I try shooting the pictures at 16/1000 and 17/1000 shutter speeds to see the scan lines, or should I use slower shutter speeds? Since I don't have a CRT monitor available here, I'll try the pictures on the TV screen on Sunday as well.
:)
-
Diablo,
I'm testing the 100a build. Having never used CHDK before (but read enough to dump the first a1000 firmware a couple months ago), there were a few things that seemed weird to me. Is there supposed to be a 'back' option on the main CHDK menu? If not, how do you make the menu disappear?
Bugs that I noticed:
- Live histogram doesn't work
- Enabling the startup sound (in the CHDK menu) makes the camera not boot upon restart. The camera shows the bootup screen for about a half second and then appears to shut down.
I'd be happy to test future versions. I will post more bugs as they are discovered. Great work so far. I'm glad to see that the A1000 has gotten ported this fast. Thanks for working on the 100a version as well as the 100b.
Phyrephox: is there a minimum level of functionality (or maturity) before this can be submitted to SVN? I'm asking purely out of curiosity. How many people have SVN commit access?
Lee
-
Is there supposed to be a 'back' option on the main CHDK menu? If not, how do you make the menu disappear?
This came up a couple of messages above this one. It happens after you have been to another page. If you look at the top of the screen, you will see a stray title for another page.
The "back" option is an artefact. The screen is not refreshing. Diablo already knows about (http://chdk.setepontos.com/index.php?topic=2654.msg25856#msg25856).
Keep up the testing. I agree, nice to have someone do all this work for us users of the "a" version.
-
Hi,
I also have the A 1000 IS now, firmware 100b and had success using Diablo's CHDK 0.7.2!
Again, many thanks to Diablo and all who worked hard on CHDK!
I couldn't do very sophisticated testing, but the things I tried worked well.
I tested especially the shutter priority mode together with a time lapse script, because that's what I need most for RC aerial photography. No problems so far, except I had once to replace the cchdk.cfg file with the backup, the file was corrupted and CHDK wouldn't boot.
I will do more testing as I get more familiar with CHDK.
Diablo, do you see problems with the USB hijacking? I am already thinking about using an USB controller for triggering (gentled) in the future.
Cheers
Norbert
-
Hi,
I've got the A1000IS with Frameware-version 1.00b.
I downloaded the file from diablo and tried to start idt, but it doens't work. I guess I'm doihg something wrong.
As said before, I ran CardTricks to make the SD-Card bootable. After that I've copied the DISKBOOT.BIN made by diablo onto the SD-Card and locked it.
For sure I do something wrong trying to start it.
Do I need to start the camera in Playback-Mode?
Which buttons do I need to push then?
With best regards,
Matze1503
-
Firmware:)
-
@matze1503
yeah, lock card and start up in play mode - if your setup is OK you might see CHDK logo (if already implemented)
pop up for a second, but then you would typically not notice CHDK anymore.
Now press <Alt> (should be the Direct Print button on your cam) -> you will see <Alt> @ bottom center screen.
With <Alt> visible, press "Menu" and the CHDK main menu should appear.
If you can't get to the main menu, you:
- didn't prepare the card properly (unlikely if you used CT :D)
- maybe did not download latest DISKBOOT.BIN ?
More keys ? go here FAQ - CHDK Wiki (http://chdk.wikia.com/wiki/FAQ#Q._What_are_the_key_settings_and_shortcuts.3F)
hope that helps,
wim
PS Note I don't have this cam, so i don't know what is already/is not yet implemented ...
PS2: where's my manners: welcome to the forum, hope you'll have fun !!
-
Matze,
yes, just switch the Camera on, if the write protect mode is on, you should either correctly see the CHDK message or the camera would say 'card is locked', this is when CHDK is not recognized.
Norbert
-
-
@matze
Yes...you are. What you're doing there is creating a udump card, this is only necessary as a first step
before porting the cam ... which diablo is doing/has already done.
what you need to do: card in reader -> start CardTricks & select card.
click 'Format as FAT', and then 'Make Bootable'.
Done, now put DISKBOOT.BIN (from this thread)
on your card, lock it, and put in camera. Start camera.
wim
PS if this does not work, your firmware is probably different than the 8 dec. one ...
to test: - same card as above in cam, but no write protect
- start cam, press and hold 'Func' and press 'display'
- real firmware version is shown as 'GM 1xxx'
-
Thanks for your help so far!
My Firmware is form July the 0th 2008...1.00b
Is there a way to make an update?
Matze
-
Thanks for your help so far!
My Firmware is form July the 0th 2008...1.00b
Is there a way to make an update?
Matze
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
Basically, you don't need an update for that camera. CHDK is far better than any update you'll ever get from Canon. :)
-
whops... double post by accident and don't know how to delete it. :-X
-
My Firmware is form July the 0th 2008...1.00b
Is there a way to make an update?
I didn't know there was anything after 1.00b. I asked the same question about 1.00a. Same answer.
These things don't seem to have the same update regime as Canon's digital SLRs.
-
There's only official Canon updates for older P&S ' s ...
For the newer ones, Canon has come up with a brilliant scheme:
they just release new cams i.o. firmware updates, keeping them pesky hackers so busy
that they don't have time to start messing with their precious DSLR's :haha
wim
-
I couldn't work on the bugs posted for a couple of weeks now. Also I am going for a 10-day vacation. Sorry for being lazy in uploading the diff/patch to make this camera's CHDK available on autobuild. I will be doing it in the new year.
Hope to see more bugs reported when I come back.
It would be great if someone can get the color profiling done for this camera to be used for RAW conversion.
-
Diablo,
have great Christmas holidays!
Many thanks for your work!
Norbert
-
Hope to see more bugs reported when I come back.
Well, to me it looks like I found one.
A 1000 IS, Firmware Rev 100b
Aperture override seems not to work correctly.
My settings:
- 'P' or 'AUTO' mode
- any ISO value, e.g. AUTO ISO
- Disable Overrides 'Off' or 'disable'
- all overrides 'off' (except override ap), custom ISO not enabled
- override aperture set to e.g. '3.17'
- displayed (top left) override aperture: AV: 3.17
- displayed (center bottom) and used aperture: 8
other override values of aperture wouldn't work either
automatic aperture with 'disable overrides' set to 'on' would be 2.77
Could somebody confirm this bug?
Thanks
Norbert
-
I couldn't work on the bugs posted for a couple of weeks now. Also I am going for a 10-day vacation. Sorry for being lazy in uploading the diff/patch to make this camera's CHDK available on autobuild. I will be doing it in the new year.
Hope to see more bugs reported when I come back.
It would be great if someone can get the color profiling done for this camera to be used for RAW conversion.
Don't be silly Diablo, we're already really glad that the CHDK port for this camera is coming a long way. I hope you have fun on your vacation... enjoy it. :xmas
As far as the color profiling, I'm needing some help with what step I need to take next. I've already taken the RAW/Jpeg pictures of the color palette, but I don't know what to do from there.
From what I've read, I need to be able to open the RAW to get the matrix values for the color profile, but from what I understand, RAW can't be opened until the color profile is done. I've tried a pletora of different programs, but nothing works. So its like a "what comes first, the chicken or the egg" type of question.
If some CHDK whizz could point me in the right direction of what I need to do with the RAW/Jpeg of the color palette, I'll gladly take care of it. Thanks. :)
Aperture override seems not to work correctly.
The same happens on my camera. I used your values and the same happened, even when I changed the aperture value.
Note:
I have my CHDK to "Show Real Aperture Value" ("Av" on top right) and it always displays 2.68 no matter which aperture I try to set it to.
So here's the break down of the values that show on the camera with the settings posted by EyP3:
- top left: Aperture chosen on override aperture
- center bottom: always 8
- top right: always 2.68
Can someone else confirm this?
-
- top right: always 2.68
Can someone else confirm this?
Yes, confirmed. Always 2.68
(Btw., if anybody wants to try: the clock display has to be turned off, otherwise the values wouldn't show)
Thanks for checking.
Norbert
-
All Canon cameras without aperture priority mode have no real diaphragm, only ND filter (ND Filter - CHDK Wiki (http://chdk.wikia.com/wiki/ND_Filter)) - why a1000/a2000 should be an exclusion?
If some CHDK whizz could point me in the right direction of what I need to do with the RAW/Jpeg of the color palette, I'll gladly take care of it.
For example, DNG4PS-2 0.2.3 Beta 16 (http://dng4ps2.chat.ru/index_en.html), settings->camera options (add new camera)->calc. color profile. Read all instrunction (http://dng4ps2.chat.ru/index_en.html#color_profile) on web page .
-
All Canon cameras without aperture priority mode have no real diaphragm, only ND filter
Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?
Norbert
-
All Canon cameras without aperture priority mode have no real diaphragm, only ND filter
Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?
The aperture things are disabled then (defines in camera.h), only ND filter related things are enabled (e.g. no Av bracketing menu item, only Tv bracketing, additionally ND filter menu...)
When looking directly into the optics (use a strong light, e.g. a pocket lamp) you should see either the aperture changing or the ND filter swinging in & out.
If there's only a ND filter the Canon OSD has only 2 F-stops, e.g. F/2.8 (ND filter off) and F/8.0 (ND filter active, swung in) - only with the zoom you'll get other F-stops...
-
When looking directly into the optics (use a strong light, e.g. a pocket lamp) you should see either the aperture changing or the ND filter swinging in & out.
Just tried that, it's obviously the ND filter kicking in ... :(
Thanks for the explanation!
Norbert
-
All Canon cameras without aperture priority mode have no real diaphragm, only ND filter
Then the aperture overrides wouldn't make much sense either? Too bad.
How is this handled in CHDK normally with these types of cameras?
This is all correct and fine, but still it doesn't necessarily invalidates the idea of aperture override in such cameras.
As an example, I own an IXUS950 that lacks iris aperture. Still, I'd like to be able to set "shutter priority" for shots of rapid motion. How would I go about it? Setting "ND filter out" override? But that invalidates camera's exposure metering, so I'd have to go completely manual. It'd also invalidate the LCD preview.
My solution is this -- define "shutter_priority" and set it in the menus, and then:
void shooting_expo_param_override(void){
// NOTE: should probably check for tv and ND overrides, flash mode, etc... Or use the brain when shooting!..
extern int shutter_priority;
short av,tv;
if (shutter_priority) {
_GetPropertyCase(PROPCASE_AV, &av, sizeof(av));
if (av>512) { // Ixus950: ND filter is used (max without ND = 480, min with ND = 563)
av = av - 275; // remove the filter (275/96 = 2.86 full stops in Ixus950)
_SetPropertyCase(PROPCASE_AV, &av, sizeof(av));
_GetPropertyCase(PROPCASE_TV, &tv, sizeof(tv));
tv = tv + 275; // compensate exposure
_SetPropertyCase(PROPCASE_TV, &tv, sizeof(tv));
}
}
...
}
-
Thanks for the info.
I'm not sure if I understand this correctly, if I go for a certain shutter speed with tv, wouldn't I want exactly that speed, not a corrected one? Would it help to have the ISO adjusted or is that no more free as a parameter then?
Norbert
-
My remark above concerns something that could have been done, but is not actually realized in the CHDK code. A suggestion only.
-
Thanks, I was aware of that. I was thinking if in such a case the ISO could be adjusted instead of the already chosen Tv value, but maybe thats physically not possible? Thanks for any explanation.
Norbert
-
...I was thinking if in such a case the ISO could be adjusted instead of the already chosen Tv value, but maybe thats physically not possible? Thanks for any explanation.
That's what Canon do in the Sports scene mode - increasing ISO...you can do this also manually with CHDK, but the camera doesn't do it automatically.
Controlling the ND filter is useful e.g. in a script where you also set other values 'manually', whoever's way would be helpful with 'normal' shooting when you just want to select the highest 'Av' and let the camera select the adequate values for ISO, Tv & the flash (=Av priority).
Maybe the Extra Photo Operations: Custom Auto ISO (http://chdk.wikia.com/wiki/CHDK_firmware_usage/AllBest#Extra_Photo_Operations_.3E_Custom_Auto_ISO) feature could be helpful, i haven't used it sof far, i normally set up the lowest possible ISO...
-
Hi, I've a A1000IS 1.00b and I'am trying Diablo's port of CHDK from 2nd DEC.
CHDK works excellent, but I'm not able to process RAW...
Common utilites stops with error, but in IrfanView's RAW plugin I can recognize picture data from another image previously stored on the card... Very strange...
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fsmitka.org%2Fraw.jpg&hash=4e6a464bb7bd3c2edf65cd2af4846ab4)
-
but I'm not able to process RAW...
i think it's not ready yet
Norbert
-
Hi -
Sorry for the newbie question, but is there some sort of beta version of chdk for the A1000IS? I noticed several mentions of uploading the build somewhere, but can't seem to find it.
Thanks to all who are putting in the efforts!
-JWheat
-
Welcome to the forum,
smitka and jwheat!
I noticed several mentions of uploading the build somewhere, but can't seem to find it.
I downloaded mine from here: http://chdk.setepontos.com/index.php/topic,2654.msg25324.html#msg25324 (http://chdk.setepontos.com/index.php/topic,2654.msg25324.html#msg25324)
for rev 1.00b
You have to be logged in to see the download.
Norbert
-
A 1000 IS firmware 100b
Custom ISO values are a factor 1.6 off, e.g.
-> extra photo operations -> disable overrides (off) ->
Override ISO value: 10 (swapped, this is actually the multiplier)
Value factor: 10 (swapped, this is actually the custom ISO value)
should result in ISO = 10 . 10 = 100
but resulting ISO value is 160 (10 . 16)
or
Override ISO value: 2 (swapped, this is actually the multiplier)
Value factor: 100 (swapped, this is actually the custom ISO value)
should result in ISO = 2 . 100 = 200
but resulting ISO value is 320 (2 . 160)
Could anybody confirm? Thanks
Norbert
-
A 1000 IS firmware 100b
I noticed that the cchdk.cfg file can easily get corrupted.
For example, a shutdown of the camera due to low battery voltage seems to corrupt the cchdk.cfg file.
The result is, that the cam will not boot into chdk until cchdk.cfg is deleted or restored from a backup.
Maybe an additional 'file close' / 'file open' at a strategic place in the software could help?
Alternatively, could a backup cchdk.cfg be restored if a failure in cchdk is detected?
Thanks
Norbert
-
I noticed that the cchdk.cfg file can easily get corrupted.
For example, a shutdown of the camera due to low battery voltage seems to corrupt the cchdk.cfg file.
The result is, that the cam will not boot into chdk until cchdk.cfg is deleted or restored from a backup.
This doesn't help, but I'd just like to note that for my vxworks a570is I don't remember corrupting cchdk.cfg even once, and I've crashed and shut down the camera in a multitude of ways, including battery low, battrery removal, ext psu removal and crashes with and without watchdog shutdown. I guess I've never had it crash/shut down while exiting alt (I believe that's when cfg gets written, or was it when exiting menu?).
-
Hi, i'm new to the forums because I just purchased a A1000 IS (firmware 1.00b). Thanks to all the authors for this software.
There are some bugs in the software:
* The interface gets stuck in the screen sometimes (i think Diablo already knows about this). A workaround is to press the shutter softly or call the MENU native screen.
* Overriding the subject distance (SD) is prone to hang the camera. It seems to work until the shutter is pressed softly, when pressed firmly it usually hangs leaving the camera dead (the lense is not retracted). I had to switch on the camera again.
* I've seen similar results using DoF bracketing. The camera hangs when going to take the first shot of a serie (using bracketing +, 10 mm increments).
* Sometimes the camera hangs if you push the on button and then hit the play button to switch to shooting mode. Pressing shutter seems to never hang.
* On last use, the camera didn't restart. I was doing some DoF bracketing and after a hang it didn't comeback. I removed batteries but didn't work. So i have to delete cchdk.cfg and that did the trick. I had enabled the option for conserving overrides and bracketing settings after switch off, so maybe that was the problem. But the thing is that before the hang it was working correctly. I took some pictures to make a DoF bracket but without a tripod the results are poor.
Everything else works well. I didn't test what behaviour the aperture override yelds. Thanks to everyone who made CHDK possible, special thanks to diablo who took the time to port this to our model.
-
Hello! I'm a noob, hehe. Based on Diablo's porting of the A1000 I decided to get that camera yesterday. (It was a very difficult decision, but I wanted something a lot more portable than my old A85. Here's hoping this one lasts as long.)
First off, I was amazed by how far cameras have come in base image quality. But it was lacking some manual features (I figured out, eventually, how to do manual long exposure times without hacking it). I have a 1.00b firmware version which came from Circuit City for $150US, btw.
Putting in CHDK from Diablo was pretty easy. I'll want to get a 2GB card since I'm just wasting space formatting this one down to 2, but that's a general issue.
It didn't take long to figure out what a histogram was for and all sorts of other fancy things. Now that I know what bracketing is, it's pretty amazing. Already did my first HDR test with it (I learned what that was a couple days ago - FDRTools so far is the best free app for it). I attached that image if anyone is curious (and trying to see what they can do within about five hours). Note that the yellow part of the exercise ball was completely overexposed and white on most of the six bracketed images I did. I modified the histogram curve slightly to overemphasize the mids and decrease the lows.
Anyway, about the port: I had one 'major' crash which prevented me from being able to start up. I haven't been able to recreate it, however. I was changing too many options at once, but it was a crash on powerup before the splash text displayed (I turned that off in case something it was displaying was wrong). I see at least one other person has had that issue already.
There's two screen display issues I notice. One is the already mentioned problem with wipes. The other seems to come up after I modify the OSD locations. When I return to the regular camera mode it wants to keep redrawing a big black box onscreen. I power the camera off and on to clear that, which isn't too bad of an issue.
So far I'd recommend a blended RGB histogram, just the battery symbol, and maybe the raw image counter. I also kept the clock and the temperature of the lens, but I dunno if that's terribly important to keep track of. Dunno yet what that strange orange box is at the bottom left. I'll figure out how to turn that off sometime... The default positions aren't very good for the OSD displays, though, as they conflict with the normal OSD and sometimes with each other, but it's not too hard to adjust them. The battery needs moving a few pixels to the left. The histogram should be about midway up and to the right a bit, etc.
It would be nice if this camera's CHDK build would use the SET button to bring up the CHDK and DISP for the script. Having it the way it is now seems to reverse the intention of the camera's normal usage where you press SET to adjust your shot parameters. There's probably an option for that I haven't found yet. On the subject of buttons, Face Detect seems like something you'd rarely want to toggle. It would be wonderful to be able to assign that to something like bracketing on/off (which I notice seems to turn itself off every time I turn the camera off and on - annoying).
Otherwise I learned what zebra mode is. It seems to work great. Overriding the shutter speed works, too. :D
But I will note the option for 'disable overrides' is completely illogical. It should be Enable Overrides and just have an enable/disable toggle. Otherwise you're left wondering if 'on' means they're disabled or if it's really enabled and not overridden. Double negative. That's probably a general CHDK issue.
In general I'm pretty happy with this camera. I'm glad I went with it instead of the A590 I was considering, and it's all because Diablo went and started porting it. Waiting a year to be able to do cool things I was reading about would have been interminable (that seems to be how long it took to port the A590)!
I'm sure as I learn more about it, I'll have more useful things to say, but the build is remarkably stable. Even tried toying with Raw, but I know it doesn't work and I can't find anything that won't choke on it yet. Maybe someday. :)
PS. The best part was comparing what my camera can now do with my friend's XTi. His image quality is a bit nicer and he's got amazing zoom, but these features bridge that gap quite a bit. It actually seems like Canon still artificially limits their DSLRs compared to what the hardware is really capable of. Truly it feels like a pocket DSLR which I'll actually use, while his will sit in the case for a long time. ;)
-
Control of the ND filter state would really help.
I did some RC aerial photography with the A1000IS today and tried to use shutter priority of 1/500 or 1/1000 sec.
Problem is that most of the time the ND filter kicked in, resulting in unnecessarily high ISO values.
Example: Shutter time 1/500 sec, Aperture: 8:0 (i.e. ND filter 'in'), ISO set to 200.
I would much prefer to have the ND filter 'out' in that case and have a lower ISO value instead.
Norbert
* Overriding the subject distance (SD) is prone to hang the camera. It seems to work until the shutter is pressed softly
... confirmed.
-
You can probably do it in a script, something like that:
(i) press "shoot_half", wait for metering to complete (perhaps checking propcase 205/206),
(ii) read AV, TV, SV with get_av96, get_tv96, get_sv96,
(iii) from AV, determine if the ND is used (AV >= 576 for f/# >= 8.0),
(iv) remove the filter with either set_nd_filter, or with set_av96_direct AV-ND where ND=96*3 for ND8, whichever (if any) is supported in your camera,
(v) cnange TV and/or SV by ND and write them back with set_tv96_direct and/or set_sv96 to compensate exposure,
(vi) shoot.
This is just an idea -- I didn't test it, nor am I a script writer!
-
You can probably do it in a script, something like that:
(i) press "shoot_half", wait for metering to complete (perhaps checking propcase 205/206),
(ii) read AV, TV, SV with get_av96, get_tv96, get_sv96,
(iii) from AV, determine if the ND is used (AV >= 576 for f/# >= 8.0),
(iv) remove the filter with either set_nd_filter, or with set_av96_direct AV-ND where ND=96*3 for ND8, whichever (if any) is supported in your camera,
(v) cnange TV and/or SV by ND and write them back with set_tv96_direct and/or set_sv96 to compensate exposure,
(vi) shoot.
This is just an idea -- I didn't test it, nor am I a script writer!
Many thanks, that seems very reasonable.
I tried to implement it, but I can't get more than the most simple scripts running.
I got this working correctly which at least correctly shows if the ND filter is applied:
@title Interval Shooting v0.1
print "Time Lapse Loop"
n=1
sleep 1000
goto "shot"
:shot
press "shoot_half"
sleep 2000
print "av: ", get_av96
print "tv: ", get_tv96
print "sv: ", get_sv96
if get_av96 > 575 then print "ND in" else print "ND out"
print "Shot", n
shoot
n=n+1
print "next"
sleep 2000
goto "shot"
and wanted to have something like this:
@title Interval Shooting - not working
print "Time Lapse Loop"
n=1
ND=96*3
sleep 1000
goto "shot"
:shot
press "shoot_half"
sleep 2000
print "av: ", get_av96
print "tv: ", get_tv96
print "sv: ", get_sv96
if get_av96 > 575 then print "ND in" else print "ND out"
if get_av96 > 575 then set_av96_direct get_av96 - ND
if get_av96 > 575 then set_sv96 get_sv96 - ND
print "Shot", n
shoot
n=n+1
print "next"
sleep 2000
goto "shot"
but I already get a 'parsing' error when I insert the line with the 'rem' statement:
@title Interval Shooting - not working
print "Time Lapse Loop"
n=1
ND=96*3
sleep 1000
goto "shot"
:shot
press "shoot_half"
sleep 2000
print "av: ", get_av96
print "tv: ", get_tv96
print "sv: ", get_sv96
if get_av96 > 575 then print "ND in" else print "ND out"
rem if get_av96 > 575 then set_av96_direct get_av96 - ND
print "Shot", n
shoot
n=n+1
print "next"
sleep 2000
goto "shot"
And I get strange parsing errors, e.g. with assignments like
av=get_av96
print "av: ", av
I don't understand this. Could it be the line formatting of the editor?
Is there already a list with the implemented commands for the A1000IS?
Norbert
-
The following simple script that removes ND and compensates exposure by adjusting TV works fine here.
@title Simple "TV/AV priority" test
press "shoot_half"
rem wait for ready-to-shoot
do
get_prop 206 p
until p=1
rem get_tv96 t
get_prop 262 t
rem get_av96 a
get_prop 23 a
rem if no ND, just shoot
if a<512 then goto "fire"
rem remove ND, compensate exposure with TV
rem set_av96_direct a-275
set_prop 23 a-275
rem set_tv96_direct t+275
set_prop 262 t+275
:fire
shoot
end
Should work in your case, unless get_prop/set_prop are not implemented, which would mean ubasic as such were not implemented properly. (I don't know if it is, as I don't use current sources in my home builds.) Note that the script uses "classic" syntax. Recent (and not so recent) additions have relaxed it quite a bit but, as usual, it is not documented anywhere, so go figure. The same goes for whether or not a function is implemented for a particular camera -- you really have to examine the sources. Also, nowadays ubasic is regarded as stone age around here, they use lua for scripting.
-
Many thanks!
Seems to work fine, but I couldn't do much testing.
Will continue next year ... 8)
Cheers!
Norbert
-
I just got my A1000 IS for christmas, im loving it,
all my gadgets are "modded" my ipod, my phone, my comp, all of them, so i figured
Why not my cam???
you guys are are amazing, really! wow!
cheers
happy new year
-
Hi guys, as u know the A1000 hasn't got manual controls.......are you goin' to add them with you CHDK?
That would be great! :)
-
Hi,
you already can have shutter priority, custom ISO, ubasic scripting and a lot more. Please check the previous messages to get an idea what's already implemented by Diablo.
Norbert
-
Hi folks, I stumbled across this a few days ago and have stumbled through the CHDK installation. Many thanks to the many who have worked this out.
Not all of it works straighforwardly, however. For example, the 12/8 DISKBOOT.BIN (most recent I think) doesn't work in my camera (camera won't turn on; firmware 1.00b), but the 12/2 version does work. I'm also having trouble with the raw files. I see that some work was ongoing for this in December, but don't see that anything has occurred since. I can't find any program that will open the files (although some see the files, I've tried Lightbox, ufraw, Picasa3, PS Elements 6, Raw Therapee, XnView, Fast Stone viewer, dcrawui), and the dng4ps2 program doesn't load the files either. I'm not a coder, but is there something I can do to check this out or help the process along?
again, thanks for all the work so far!
-
Hey everyone! Another newbie here, bought my first digital camera yesterday. An A1000 IS, of course :) I installed CHDK right away. I have FW version 1.00b.
I noticed the same thing Mattock did - the 12/08 build wouldn't boot up my camera, 12/08 works fine. I guess we should make an FW dump and compare it to the one Diablo worked with, to see if it's just some glitch or Canon changed the firmware recently.
Mattock, I'm having the same problem with dng4ps2: it wouldn't list the files, and i can't set up the color profile. I'm guessing the version we see now (beta 19) is different from the one Diablo used (beta 16) and isn't working so well. Could someone post the beta 16 version for us? pretty please? :)
I don't think any other program is supposed to read the .CRW file generated by CHDK - this isn't an actual CRW file, as CRW files have defined headers and data structures, this file doesn't. From what I could figure out, it's just a heap of sensor data, 10 bits per pixel, w/o Bayer interpolation. I haven't played around with RAW readers, but if none of them can be persuaded to read this kind of file, I could maybe work out a conversion algorithm in Free Pascal, to convert these files to 16-bit RAW that can be read with Photoshop or other imaging software capable of reading RAW. That is, if I can figure out this Bayer interpolation thingy. I know very little about digital imaging.
Anyway, many thanks to all the people who are developing CHDK, and especially to Diablo, our own community hero :) I just hope you'll be back soon...
-
Hey, to answer tybofborg and mattock's question, the 12/08 version that Diablo made is for the 1.00a firmware. Stick to the 12/02 version if you have 1.00b firmware. :)
As far as dng4ps2 working with these raw files, I remember having a similar problem where it wouldn't detect any files. I also remember making a new camera profile, but the files it created still weren't readable by any programs that can read raw. I don't think raw is fully implemented yet.
And you're right tybofborg, the CRW from CHDK is just a dump from the image sensor.
As far as the development goes, I'm not sure. Diablo hasn't posted here in a while. I hope everything is well with him. :-[
-
Thanks, tyrantt23, I missed that bit about the 1.00a firmware for the 12/8 download.
And tybofborg, I found a link to the dng4ps2 beta 16 here:
http://code.google.com/p/dng4ps2/downloads/detail?name=dng4ps2-0.2.3-beta16.exe&can=2&q= (http://code.google.com/p/dng4ps2/downloads/detail?name=dng4ps2-0.2.3-beta16.exe&can=2&q=) (from a google search on the file name)
While Diablo may have gotten some results with it, I can't get this version to recognize the raw files, same as the current versions.
-
Very little experience w/cameras and it's been 20 years since I coded anything
Loaded the 12/2 binary. Took some time to get "BOOTDISK" text into the SD mbr - hadn't seen that one before and was confused when setting "bootable" in the format apps and partitioners didn't work.
CHDK works more or less (an hour of so of fiddling), except:
1) The two partition scheme outlined in the "Bootable SD" page here doesn't seem to work as advertised. The A1000 just uses the small first partition instead of loading from that and then using the large second partition for storage. Does anybody know what logic is supposed to cause the camera to open the 2nd partition? What the process is? W/out knowing anything about the process, it's hard to figure if something I'm doing causes the problem. The card is a 4GB card. The partitioner I used refused to format anything less than 16 MB w/FAT16; the size of the first (small) partition size is about 24MB. I tried using FAT12, but I think I hadn't got the mbr right at that time. I might try that again, see it shrinking the partition to 2 or 3 MB helps. If not I'll just use FAT16 w/one big partition; just figured I'd see what happens in case I went to bigger cards.
2) Getting out of the ALT mode doesn't seem real consistent. Sometimes the DISP does it, sometime the MENU does it, sometimes ALT does it, sometime SHOOT does it (though last try at that started the stub script). Maybe I just haven't figured it out yet, but I did think the FAQ said that ALT was the way out of that mode.
3) CHDK doesnt want to clear the screen b4 a rewrite - or maybe that's the Canon software?. Others have noted this. It confuses the menus a bit and makes using the OCD editor something of a guessing game.
#1 is the
Anybody know if Diablo uploaded source code? It looks like he may have gotten diverted into other paths for now - maybe burned out a little by that fantastic sprint he put on last year. <g>
Cheers, Rufus
-
I am aware of the screen not refreshing issue. The function "RefreshPhysicalScreen" is not working at all.
Calling or not calling it has no effect. I compared it with disassembly of A720 and G9. For A1000, the method is slightly different. But I made sure that the caller and callee are matched with other cameras. So for now, refreshing can be done by half pressing shoot button.
Don't know if you are still working on this, but I encountered a similar thing on the SD990. It appears to me that there are a pair of functions, one of which looks a lot like what we call "RefreshPhysicalScreen" on other cameras. You have to call both for the update to happen. They are probably intended to wrap the screen access (you can see from the callers they are called in pairs), but just calling them in vid_bitmap_refresh is semi-functional.
On the SD990, these functions refer to strings "ScreenLock" and "ScreenUnlock". ScreenUnlock is what I initially took to be RefreshPhysicalScreen. On SD1100 and a720, the corresponding functions refer to
"Window:EffectiveLockPhysicalScreen"
"Window:IneffectiveLockPhysicalScreen"
with the second being identified as RefreshPhysicalScreen.
Note that RefreshPhysicalScreen is called with an argument (1) but on these cameras, it doesn't actually use it.
-
Just got the A1000 IS, and I'd be pretty thrilled if I could get CHDK working on it. I downloaded Diablo's firmware and followed the instructions in the FAQ for putting it on the card, but as far as I can tell, there's no noticeable difference in the interface when I turn the camera on.
There are two things I'm suspicious of that may or may not be relevant (I don't really know what I'm doing here). The first thing is when I check the firmware version after touching a "ver.req" file, all I get is "Firmware Ver. 1.0.0.0" and not the detailed information the A1000IS wiki page says I should get. So not knowing whether I have version 'a' or 'b', I tried both firmware versions, both with the card locked and unlocked. No dice.
Another thing I'm suspicious of is when I went to make the partition on my SD card bootable with "cfdisk /dev/sdc", I got the error "FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder". So I used fdisk instead, which didn't seem to have any problem.
-
Another thing I'm suspicious of is when I went to make the partition on my SD card bootable with "cfdisk /dev/sdc", I got the error "FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder". So I used fdisk instead, which didn't seem to have any problem.
'bootable' in the context of CHDK is not the same as for PC OS's: you need to write a special bootflag in the cards'
sector 0. Read about it here: http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
to summarise: you need to write 'BOOTDISK' to sector 0 @ offset 0x40
HTH,
wim
-
So definitely one of my problems was I was using FAT32 (I have an 8gb SD card). I created a small FAT16 partition as instructed in the FAQ, and touching a ver.req file on that allowed me to get the exact same firmware version information as is showed on the A1000IS wiki page.
Then I made the small FAT16 partition bootable the propper way, but I still couldn't get CHDK to boot. The camera always said "card locked" and "card full", which I assume is a good indication that CHDK did not boot. I tried recreating the partition table a couple times, and I also tried formatting the small partition on the camera (because I read somewhere that sometimes this needs to be done), but when the camera formats the card it wipes out my partition table and replaces it with one big FAT32 partition. Grrr :-P.
-
@quuxman
when formatting a partition in camera, be sure to set "Low Level format" off
wim
-
whim: I tried with low level formatting on and off. Either way it wiped out the whole partition table.
Apparently other people in this thread have gotten Diablo's firmware working on the A1000IS. Could any of you be so kind as to relate exactly what you did to get it to work? I'd greatly appreciate it :).
-
> make bootable
The partition editors (any of them) won't insert the necessary text in the MBR which CHDK looks for. You need to manually enter the text "BOOTDISK"
-
Continued... Sorry I hit enter too quick. <g>
Follow the instructions in whims link
http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
and note that if one of the easy scripts of programs on the above link don't work for you, you need to use a hexeditor to go into the MBR to insert the text "BOOTDISK" at the correct offset. This can be a pain, depending on what tools you have and are used to using, but there's nothing complicated about the concept - CHDK must find that text at that location. What tools you have depends on your operating system and some hex editors are more hinderance than help; fortunately there are quite few out there to choose from so you can find one that works for you.
The 2 partition scheme for CHDK doesn't work reliably (as of Feb 2009, the last I checked). Get a card working w/one FAT16 partition (4GB) first to make sure you've got the basics nailed. Then try a small FAT12 or FAT16 (remember to insert the "BOOTDISK" text CHDK wants) partition w/a 2nd FAT32. What I experienced was that CHDK boots the small partition and ignores the larger one. Perhaps the code has advanced recently, but another problem is that diablo's bin file is based on the CHDK code from Dec/08 and that won't change until another decent assembler programmer steps up and continues this project.
Diablo has made his source available for now at
https://www.yousendit.com/download/UmNKOGNXcWZQb0t4dnc9PQ (https://www.yousendit.com/download/UmNKOGNXcWZQb0t4dnc9PQ)
"This just includes modified files. You need to checkout and replace files. I know some files might have updated version in the tree. It might not be a good idea to replace those. So Let me know if you want exact diff."
Perhaps if the root code for the 2nd partition has been stabilized it might be possible to create an updated bin file for the A1000 from diablos code w/out detail programming; but that hasn't been done yet.
Rufus
-
rlaggren: thanks for the reply. I'm pretty sure I've been writing "BOOTDISK" in the appropriate place. I'm using the command from the wiki:
echo -n BOOTDISK | dd bs=1 count=8 seek=64 of=/dev/sdc1
And I've verified with a hex editor that it's showing up in the partition at the right offset.
I should have thought of making a single smaller FAT16 partition. I tried that now, but it's still not working.
-
quuxman, were you able to get your firmware revision?
Depending on 'a' or 'b' you have to use a different chdk binary, otherwise chdk would not boot.
Did you try cardtricks.exe to prepare your card? It is available from here: http://chdk.wikia.com/wiki/Cardtricks (http://chdk.wikia.com/wiki/Cardtricks)
Don't give up, just come back and ask.
Norbert
-
Saw the CHDK on hackaday.com a couple weeks back.
So when i picked up a new camera today i thought. i should grab a cannon powershot and see if i can get this CHDK to work. Not knowing the complexity of how CHDK works i grabbed the nicer a1000is power shot. firmware 1.00B ;)
So yes im a noob to this. I have the memory card formatted using cardtricks. i grabbed the DISKBOOT.bin file from a previous post. what else do i need? What should the memory card layout look like?
I'm thinking CHDK has more code then just the bin file right? i guess i could pull another cameras code down and see what i should have.
Diablos link to the source files is down so i can get that stuff. I will keep reading through everything. But if anyone has any more info that would be great. :) Thanks.
edit: i guess after i registerd, the first post has some files too :) i only saw the bin file my first time through after i registerd. That needs to like show you there is a file but cant download until you register or something? Anyways ill post back if everything is good.
-
Profit,
all you need to download is cardtricks.exe and the CHDK binary.
When you prepare your memory card using cardtricks, you should have a CHDK directory on your memory card with 9 subfolders (books, curves, data, fonts, grids, lang, logs, scripts and symbols), you don't have to create these folders manually.
Store the correct diskboot.bin, which you can download here after registering, into the root directory of your card and your'e done.
Set the write protect on your memory card to 'on', put it into the camera and switch on. If all works well you should see the CHDK logo after switching on the camera. Otherwise you get the card locked message.
You need diablo's sources only if you want to continue the porting. Would be great of course if somebody could do this.
Norbert
-
I see Diablo's fileshare post has expired. Is there another location for the latest A1000is CHDK file to try?
Thanks
-
I see Diablo's fileshare post has expired. Is there another location for the latest A1000is CHDK file to try?
Thanks
Sure, here ya go:
http://rapidshare.com/files/219956040/DISKBOOT.BIN (http://rapidshare.com/files/219956040/DISKBOOT.BIN)
-
freyyr890,
you should mention for which firmware revision this binary is built.
The binaries can also be downloaded from Diablo's posts in this forum, they are still available.
Norbert
-
All, does anyone know whether diabolo's sources are still available anywhere? I am interested to have a look...
TIA, Erwin
-
All, does anyone know whether diabolo's sources are still available anywhere? I am interested to have a look...
TIA, Erwin
Same here. Interested in taking a glance and playing around with the code. Might get the inspiration to give an update to the code someday, but first I'd need the source code.
Thanks everyone. :)
-
I got the file from:
http://rapidshare.com/files/219956040/DISKBOOT.BIN (http://rapidshare.com/files/219956040/DISKBOOT.BIN)
It's been working fairly well for me although I have not worked with it a whole lot. I tried scripting a variety of zoom levels and my camera shuts down immediately after the line "set_zoom 0". I can se tthe zoom to any level and shoot but when I tell the camera to set_zoom zero it does but regardless of the next line of code, shuts down.
If anyone has ideas on this I'd appreciate it.
THanks
-
Profit,
all you need to download is cardtricks.exe and the CHDK binary.
When you prepare your memory card using cardtricks, you should have a CHDK directory on your memory card with 9 subfolders (books, curves, data, fonts, grids, lang, logs, scripts and symbols), you don't have to create these folders manually.
Store the correct diskboot.bin, which you can download here after registering, into the root directory of your card and your'e done.
Set the write protect on your memory card to 'on', put it into the camera and switch on. If all works well you should see the CHDK logo after switching on the camera. Otherwise you get the card locked message.
You need diablo's sources only if you want to continue the porting. Would be great of course if somebody could do this.
Norbert
Thanks, I kind of figured that out after reading some more. Maybe that should be added to the CHDK for dummies. Better yet, what you need if the easy to use "card tricks" does not have a link to the in development code for your camera. :)
If i had free time to learn the compiling and reverse engineering for this camera i would probably help out. Hopefully someone will continue the work on this camera. :)
-
Hi,
Its quite long time I even logged in to the forum. I received a message from Norbert(EyP3) that some folks want to continue/complete the porting of A1000IS. I am very happy about this. To tell you why I couldn't complete the porting was I already spent some good amount of time to make the porting to current state and these days I am hardly getting free time.
Attaching the source(changed/added files) with this. Eager to see someone to fix the bugs and support other feature.
-Diablo
PS: Almost forgot to add this. If you need any quick help in working with sources, please send personal message to me as this will send me an alert to my mail-id.
-
Many thanks for posting, Diablo!
Well, at least some have expressed their interest in the source code, but it sure would be great if some/someone could continue!
Norbert
-
Can someone please upload an PS.FI2 file? (i prefer the manual loading method)
-
I have not seen or needed this file for the A100IS. What is it used for?
-
diskboot.bin is used to load CHDK automatically.
PS.FI2 is used to load CHDK manually.
-
Ah, ok. That sounds practical too, but I don't think it has been made for
this project. Maybe someone else knows more about it or can build the file?
-
...try ewavr's fi2encdec.zip (http://chdk.setepontos.com/index.php/topic,2995.msg28164.html#msg28164)...
-
How may I help this along? I have access to an A1000, a 1 GB SD card, a copy of Eclipse and Visual Studio, and a desire to use more features...
-
How may I help this along? I have access to an A1000, a 1 GB SD card, a copy of Eclipse and Visual Studio, and a desire to use more features...
http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
-
How may I help this along? I have access to an A1000, a 1 GB SD card, a copy of Eclipse and Visual Studio, and a desire to use more features...
you can use diskboot.bin to create ps.fi2 with the method which fe50 linked to.
-
I spend some time playing around with the OSD parameters on the A1000, and happened acress the answer to Caly's question:
Dunno yet what that strange orange box is at the bottom left. I'll figure out how to turn that off sometime...
The orange bar on bottom of screen indicates the remaining space on the sd card. To turn it off select 'Show Space Bar' in 'Filespace' in 'OSD parameters' in 'Main Menu', and set to 'Don't'.
Enjoy!
-
Compiling Diablos code from source.
Here is what I have tried:
* install compiler as described in: http://chdk.wikia.com/wiki/Compiling_CHDK_under_Linux, (http://chdk.wikia.com/wiki/Compiling_CHDK_under_Linux,) using the gcc 4.3.1-binutils 2.18 environment kit
* install svn: 'apt-get install subversion'
* download and uncompress Diablos source code. Diablo provided only the files he modified - thus his sources are incomplete and need to be restored (completed)
* use 'svn status -u' to find which revision Diablos files are
* run 'svn co https://tools.assembla.com/svn/chdk/trunk (https://tools.assembla.com/svn/chdk/trunk) chdk --revision 552' to get an unmodified version of the same revision. This created a directory called chdk in the current directory, and placed the files and sub directories in it.
* copy all of the files contained in the zip file into the same directories, thus applying Diablos edits
* one of the makefiles is messed up, and will corrupt the stubs_entry.S file. To fix this I ran: 'svn revert platform/makefile_sub.inc' in the chdk diretory.
* to see only warnings and errors when compiling, I edited makefile.inc, uncomment 'SILENT=SILENT', this edit restored the files default.
* run 'make fir'. After a number of status messages and a few compiler warnings I got: '**** Firmware creation completed successfully'
However, my camera will not recognize the resulting DISKBOOT.BIN, and displays 'Card locked!'. I tested the SD card by placing a copy of the DISKBOOT.BIN on it that Diablo posted earlier in the treat, and it booted fine. Thus I believe the card is good and formatted correctly.
I would like to ask: Has anyone compiled Diablos code from source sucessfully?
-
Is the diskboot you are making encoded with dancingbits ?
-
Hi All,
Let me first thank Diablo for his great work!
Mapless, I followed your steps and tried to update Diablo's tree to the latest revision under svn, hoping that this can help but without luck!
I'm reporting the problem I faced, it would be great if someone could help!
resolved conflicts in:
'platform/makefile_sub.inc'.
'include/camera.h'.
'core/main.c
but I think in camera.h parameters for A1000 (that I took from Diablo's work) are few or incorrect. Could you help me to update/complete? where they come from?
When compiling there are unresolved adresses:
TurnOffBackLight
DoAFLock
UnlockAF
Any suggestion?
Bye
-
Hi All,
Let me first thank Diablo for his great work!
Mapless, I followed your steps and tried to update Diablo's tree to the latest revision under svn, hoping that this can help but without luck!
I'm reporting the problem I faced, it would be great if someone could help!
resolved conflicts in:
'platform/makefile_sub.inc'.
'include/camera.h'.
'core/main.c
but I think in camera.h parameters for A1000 (that I took from Diablo's work) are few or incorrect. Could you help me to update/complete? where they come from?
When compiling there are unresolved adresses:
TurnOffBackLight
DoAFLock
UnlockAF
Any suggestion?
These were probably added since he did the original port. You need to find them in your dump, which you can do by looking at other ports where they are found, and finding the similar code in yours. Or if you just want it to compile, you can just point them at a RET (BX LR) instruction using stubs_entry_2.S
-
reyalp, thank you for pointing out dancingbits. I had compleatly overlooked that.
Revision 552 did not run dancingbits as part of the make. Running dancingbits manually changes the behavior of the camera. Now it will not boot at all. I assume this means it is recognizing the DISKBOOT.BIN, loading it and crashing...
esom:
I tried your approach (thanks for the ideea):
I ran 'svn update' and resolved the conflicts. Then I added 'NEED_ENCODED_DISKBOOT=very_yes' to 'platform/a1000/sub/100b/makefile.inc'.
To avoid function calls to unresolved addresses I edited 'platform/generic/wrappers.c', commenting out the four function calls to unresolved adresses. This turned the edited functions into do nothing functions.
The result is the same. The camera will not boot at all.
-
Revision 552 did not run dancingbits as part of the make. Running dancingbits manually changes the behavior of the camera. Now it will not boot at all. I assume this means it is recognizing the DISKBOOT.BIN, loading it and crashing...
That sounds about right.
Crashing could be a result of incorrectly configured GCC or binutils, although AFAIK the instructions you followed should be OK.
You could also try turning on an LED at various points to see where it is crashing.
-
I inserted code to blink the led's in loader/main.c following the istructions in http://chdk.wikia.com/wiki/Adding_support_of_a_new_camera#A_trick_for_keeping_track. (http://chdk.wikia.com/wiki/Adding_support_of_a_new_camera#A_trick_for_keeping_track.)
It worked! Thank you, Reyalp for the suggestion. Now I can try to track down where my camera crashes...
It turns out most of the LEDs have the same addresses as in the a720. I copied the list of adresses onto http://chdk.wikia.com/wiki/A1000IS (http://chdk.wikia.com/wiki/A1000IS).
-
Hi,
Now I can use CHDK on my A1000Is.
I want to use this camera for aerial photo with RC plane.
But I can't change self timer it only shots max 10 pic.
How do I change it to shots until full SD card ????
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimage.ohozaa.com%2Fi8%2Fvs2st.jpg&hash=ed5d51c01f5be6b32d1e355e360bb923) (http://image.ohozaa.com/show.php?id=0d40d7bb001b5e11485983c89f1c174a)
Please give me more advice .
Thank you
jannoon028
-
anything I can do to help out? I just got a 100a and would love to start hackin'.
-
I would like to ask: Has anyone compiled Diablos code from source sucessfully?
I have compiled it but the camera does not boot.
-
Hi,
I'm going to be trying to port the A2000IS, and I was thinking that this might be a good starting point. so, first , thanks to Diablo for posting your source.
I have a couple questions for the community
- Is the A1000 probably a good starting point, rather than the A720?
- when does a camera get added to trunk? I notice that diablo's a1000 isn't in trunk. Is that because it has not yet reached some standard of doneness? People obviously want to collaborate on this project, but it's difficult to do that if the code is not in source control.
Thanks!
-
Hi,
I'm going to be trying to port the A2000IS, and I was thinking that this might be a good starting point. so, first , thanks to Diablo for posting your source.
I have a couple questions for the community
- Is the A1000 probably a good starting point, rather than the A720?
- when does a camera get added to trunk? I notice that diablo's a1000 isn't in trunk. Is that because it has not yet reached some standard of doneness? People obviously want to collaborate on this project, but it's difficult to do that if the code is not in source control.
Thanks!
Rather than repeating, I'll just link my post in http://chdk.setepontos.com/index.php/topic,3977.0.html (http://chdk.setepontos.com/index.php/topic,3977.0.html)
I would not suggest the A1000 as a reference, because it was unfinished, the code is against an old version of the trunk, and it was done by someone who was fairly new to the CHDK codebase.
Also, you might want to get in touch with the OP of that thread I linked, since he was also going to work on the A2000
As to why A1000 isn't in the trunk yet... partly because it was never finished, and partly because diablo took a long time to post his source, and partly laziness... I will probably check in the platform code so it will be easier for someone to continue work on it.
Ports generally get added to the trunk when they are pretty much complete, although I am in favor of adding work-in-progress as it makes it easier for people to collaborate.
-
Thanks Diablo & others for the effort you put in this project. I am able to get almost all the settings done like ap, iso, shutter speed, etc. Need a couple of clarifications though
1. RAW image saving option is seen, enabled & seen in display. Where can we see the saved raw image? or is it not being saved? any spl process for that?
2. Optical zoom in video mode is not working. pls guide if i need to do smthin.
TIA
-
Hi all, I just got a A1000IS and loaded the beta release of CHDK. Everything seems to be starting up fine, I can run test scripts but I can not get the remote shutter to work. I got the USB cable wired correctly, I have the script (from the WIKI) running and when I close the switch (connect the 5V wire), the camera responds by going to playback mode and no picture is taken. As soon as I disconnect the wire it goes back to normal.
I might be missing something obvious, please help, previous posts indicate the remote shutter is working.
Thanks!
-
Diablo has uploaded all his files to this address :
https://www.yousendit.com/download/YkxKTXRRMm03bUJFQlE9PQ (https://www.yousendit.com/download/YkxKTXRRMm03bUJFQlE9PQ)
I can confirm that the code compiles and after manually encoding it the camera will boot.
It will be online for only about five more days so the relevant files (together with adding 'need_encode = yes' to makefile.inc) need adding to trunk.
David
-
Any sol for viewing/ Editing Raw files? AFAIK, i tried many raw file viewer/ converters but not able to preview let alone edit the images. Also, optival zoom in video mode is not working. Diablo/ GURUs, pls help. Otherwise, no serious prob so far. happy with features i got through CHDK. Feels like getting a high end camera for a very low price. :)
TIA
-
Any sol for viewing/ Editing Raw files?
Have a look to the CHDK wikia: Software - RAW Conversion (http://chdk.wikia.com/wiki/Software#RAW_Conversion); at least the latest DCRaw should be able to read/convert your RAW images...
-
Any sol for viewing/ Editing Raw files?
Have a look to the CHDK wikia: Software - RAW Conversion (http://chdk.wikia.com/wiki/Software#RAW_Conversion); at least the latest DCRaw should be able to read/convert your RAW images...
Downloaded DCRAR.exe, but when trying to run, only Command window opens & nothing after that. Do i have to run it thru commands? & if yes, what are the commands? I am not much in to DOS :(
Thanks for your suggestion.
-
Yes, DCRaw is a command-line app.
You'll get a list of all parameters with dcraw (without any parameters), you should run it manually from a cmd prompt:
Raw photo decoder "dcraw" v8.95
by Dave Coffin, dcoffin a cybercom o net
Usage: c:/windows/dcraw.exe [OPTION]... [FILE]...
-v Print verbose messages
-c Write image data to standard output
-e Extract embedded thumbnail image
-i Identify files without decoding them
-i -v Identify files and show metadata
-z Change file dates to camera timestamp
-w Use camera white balance, if possible
-a Average the whole image for white balance
-A <x y w h> Average a grey box for white balance
-r <r g b g> Set custom white balance
+M/-M Use/don't use an embedded color matrix
-C <r b> Correct chromatic aberration
-P <file> Fix the dead pixels listed in this file
-K <file> Subtract dark frame (16-bit raw PGM)
-k <num> Set the darkness level
-S <num> Set the saturation level
-n <num> Set threshold for wavelet denoising
-H [0-9] Highlight mode (0=clip, 1=unclip, 2=blend, 3+=rebuild)
-t [0-7] Flip image (0=none, 3=180, 5=90CCW, 6=90CW)
-o [0-5] Output colorspace (raw,sRGB,Adobe,Wide,ProPhoto,XYZ)
-d Document mode (no color, no interpolation)
-D Document mode without scaling (totally raw)
-j Don't stretch or rotate raw pixels
-W Don't automatically brighten the image
-b <num> Adjust brightness (default = 1.0)
-g <p ts> Set custom gamma curve (default = 2.222 4.5)
-q [0-3] Set the interpolation quality
-h Half-size color image (twice as fast as "-q 0")
-f Interpolate RGGB as four colors
-m <num> Apply a 3x3 median filter to R-G and B-G
-s [0..N-1] Select one raw image or "all" from each file
-6 Write 16-bit instead of 8-bit
-4 Linear 16-bit, same as "-6 -W -g 1 1"
-T Write TIFF instead of PPM
There are also graphical user interfaces for DCRaw out there, google for "DCRAW GUI"...
You can also put the dcraw.exe in the folder with your image & drag/move the image file with the mouse to the dcraw.exe - it takes some seconds, then you'll get a .ppm file which can be opened in most apps...
-
hello, i just found out about CHDK. Sorry, I must've been living in a cave, lolx.
Wow, nice hack :) really great! Managed to get it to boot :)
Was playing with dcrawms.exe but apparently it also can't recognize the .crw file taken from my A1000 ("cannot decode file")
Pse share suggest story if anyone succeeds.
Thanks!
For info:
Tested dcraw, works on IXUS750 raw file, able to convert to tiff .. etc.
-
Sorry for the repeat, anybody had any luck executing a script to operate the shutter remotely? I am getting the camera to respond after I connect the 5V wire in the USB cable, but the script does not take a picture (I used the script recommended in the wiki and I start it successfully).
Thanks!
-
There are also graphical user interfaces for DCRaw out there, google for "DCRAW GUI"...
You can also put the dcraw.exe in the folder with your image & drag/move the image file with the mouse to the dcraw.exe - it takes some seconds, then you'll get a .ppm file which can be opened in most apps...
Thanks for ur valuable suggestion. Also found out nice gui interface(dcrawGUI-0.04). it loads files & has nice interface for switches. Shows images as processed but can't find the output. Any idea where it stores the output as it's not shown in the inteface. Tried searching using windows search in C drive but no luck. or i have to define the output manually? However drag n drop method didn't work for me. :(
-
@donutlover & nawalsingal
The A1000 RAW feature is broken.
So - until this issue will be fixed, the RAW files of this A1000 CHDK beta port are not usable. :(
-
> anybody had any luck executing a script to operate the shutter remotely?
teras,
afaik the USB support was not finished in Diablos code.
I would also be glad to be able to use the remote shutter.
Norbert
-
I would also be glad to be able to use the remote shutter.
While you are waiting, try this version :-
http://www.zshare.net/download/6464259208e07daa/ (http://www.zshare.net/download/6464259208e07daa/)
Rename to DISKBOOT.BIN and replace existing file on your bootable card.
You do not need a script, just press the button.
A quick on/off for focus and press and release to shoot.
Or, a longer press and release when screen blanks.
Does it work ?
(the person I did this for is waiting to buy a Ricoh switch).
David
-
While you are waiting, try this version :-
http://www.zshare.net/download/6464259208e07daa/ (http://www.zshare.net/download/6464259208e07daa/)
Rename to DISKBOOT.BIN and replace existing file on your bootable card.
Great!
Thanks!
I can boot from it. What else can I do with SDM?
You do not need a script, just press the button.
A quick on/off for focus and press and release to shoot.
Or, a longer press and release when screen blanks.
Like this? http://stereo.jpn.org/eng/sdm/ca1.htm (http://stereo.jpn.org/eng/sdm/ca1.htm)
I would like to be able to use the Gentled Switch http://www.gentles.ltd.uk/gentled/options.htm#CHDK (http://www.gentles.ltd.uk/gentled/options.htm#CHDK)
Will that work?
RAW is the same format as discussed above?
Cheers
Norbert
-
. What else can I do with SDM?
A lot ... but first tell me if the remote USB switch works.
If you want the photo to be taken as soon as you press the switch (rather than on release), in menu Bracketing/Overrides set focus-mode to Manual.
'FAST' should be displayed at the top of the screen.
I would like to be able to use the Gentled Switch http://www.gentles.ltd.uk/gentled/options.htm#CHDK (http://www.gentles.ltd.uk/gentled/options.htm#CHDK)
Will that work?
Certainly will.
Which one do you have ?
I am familiar with the gentLES products.
Just set FAST mode.
RAW is the same format as discussed above?
Yes.
From the SDM website download Common_files.zip.
At the very least, copy script time_lapse.bas to your Scripts folder.
Read the two pages on the website about the use and testing of that script.
David
-
A lot ... but first tell me if the remote USB switch works.
Sorry, don't have any so far.
If you want the photo to be taken as soon as you press the switch (rather than on release), in menu Bracketing/Overrides set focus-mode to Manual.
'FAST' should be displayed at the top of the screen.
No, just says 'Single shot mode' on top of the screen.
At the very least, copy script time_lapse.bas to your Scripts folder.
Read the two pages on the website about the use and testing of that script.
Did so, script runs but eventually hangs.
Which one do you have ?
None so far, was thinking about this one http://www.gentles.ltd.uk/gentled/gentled-ricoh3.jpg (http://www.gentles.ltd.uk/gentled/gentled-ricoh3.jpg)
Norbert
-
Sorry, don't have any so far.
Test by connecting camera to computer with the USB lead, that will provide a 5V signal.
No, just says 'Single shot mode' on top of the screen.
I think you mean DIRECT.
There is text for two focus modes.
I should have said focus mode that comes after 'focus step size'
Did so, script runs but eventually hangs.
Before running script, directly press shutter button.
'Synch' should no longer be displayed.
Then run the script.
Time for bed ........
David
-
Test by connecting camera to computer with the USB lead, that will provide a 5V signal.
ok, will try that
I should have said focus mode that comes after 'focus step size'
ok, 'fast' appears
Before running script, directly press shutter button.
'Synch' should no longer be displayed.
Then run the script.
still hangs when I change from dark to bright scene or vice versa during script
Time for bed ........
same :-)
Norbert
-
Test by connecting camera to computer with the USB lead, that will provide a 5V signal.
When I connect and disconnect USB a shot is triggered with disconnect, when flash is switched on the flash is triggered with both connect and disconnect.
Norbert
-
the flash is triggered with both connect and disconnect.
That is the preflash (for white balance) and main flash.
When you say that time-lapse script does not work, can you describe in more detail ?
That would be very unusual, the code is common to all models of camera.
David
-
still hangs when I change from dark to bright scene or vice versa during script
Script starts ok, I see the countdown to the next shot, and so on, shoots several pics, then pan the cam to another scene and the cam hangs (dark display, no reaction until switch on/off).
Norbert
-
Does the script end after the three shots ?
If so, what happens if you do not pan the camera and start the script again ?
David
-
I can check in the evening.
N.
-
The camera hangs after the third picture. The effect with the panning may have been coincidence.
Norbert
-
At the start of the sequence it focuses and tries to lock focus.
'AFL' (autofocus locked) should be displayed top-left, is it ?
At the end of the sequence it unlocks focus and 'AFL' should no longer be displayed.
Did it unlock focus ?
David
-
At the start of the sequence it focuses and tries to lock focus.
'AFL' (autofocus locked) should be displayed top-left, is it ?
yes.
At the end of the sequence it unlocks focus and 'AFL' should no longer be displayed.
Did it unlock focus ?
no.
Norbert
-
Did it unlock focus ?
no.
It is possible that the function address in the CHDK port is incorrect.
I will see if I can check it.
David
-
Great! Thanks!
Ahm, would it be very difficult to include the USB functionality in the CHDK? I mean, I figure you already did it for the SDM?
That would be really nice.
Cheers,
Norbert
-
Even though it says 'AFL' the focus is not actually locked because on the A1000 CHDK port the DoAFLock() and UnlockAF() functions do not do anything.
Not sure why it hangs though, I will do some tests with another SDM user.
The code for CHDK and SDM is quite different, are you saying that the USB remote switch does not work with CHDK (by plugging USB cable into computer) ?
-
Even though it says 'AFL' the focus is not actually locked because on the A1000 CHDK port the DoAFLock() and UnlockAF() functions do not do anything.
Not sure why it hangs though, I will do some tests with another SDM user.
ok.
The code for CHDK and SDM is quite different
ok, thought this would be maybe the same function.
, are you saying that the USB remote switch does not work with CHDK (by plugging USB cable into computer) ?
That seems to work too, surprisingly.
I was referring to Diablos implementation list:
* hijack Keyboard handler (this includes USB-support)
Progress: not done
thanks again.
Norbert
-
I use a 40D for most of my general photography and all of my astrophotography, a replacement for my trusty Wasia hack modded Rebel which I gave to my sister in law; a G2 with a Gentled for time lapse; a Bell&Howell BH40 1.3MP camera from the digital dark ages for playing with IR and an RCA Small Wonder HD camcorder is being pressed into service for kite aerial video. Now I'm thinking a small Canon P&S w/CHDK would also be great for KAP and time lapse. I can pick up an A1000IS for about $125 but porting CHDK is beyond my abilities. It looks like some progress is being made, but I'm afraid I really couldn't bring anything to the party as far as helping out with getting a final version up and running. It's hard to find the older models for which CHDK is already ported....but I may have found a solution. The lab where I work uses an A590IS (I haven't checked the firmware version yet). I'm gonna offer to buy a shiny new A1000IS for the lab in exchange for the A590IS. I've been lurking the forums (fora?) a long time and following the Wiki and before that the Yahoo Canon hack group, but all this talk of dumping source code, compiling and all that type of stuff was making my head hurt, I know when I'm outa my league. No real point to this post, the fire sprinkler system at work went ape$hit all over my equipment today, it was a rough and costly afternoon and I'm finally getting to relax with an adult beverage.
-
howdy,
so this thread seems to have gone fallow since that last dramatic post.
i just got the a1000is as a gift and then discovered this canon hackability thing and i'm really excited. anyone have any updates or any ETAs on when the project might be finished?
thanks!
-
dang... so... ummm.... abandoned?
darn it. not that i would have done a lot with it but it would have been cool to play around with the hack.
jin
-
Well, most of the features work, just not RAW format or USB.
You will find the info for downloading the software in this thread.
Cheers,
Norbert
-
sweet.
i already got it downloaded. i'm waiting on a ship of some rechargeable batteries but i'll be trying it out soon - hopefully this weekend.
but has all development stopped? cuz i can do without USB but RAW would be nice.
jin
p.s. Oh! and what firmware should i be using? the b version listed on the wiki page? thanks.
Well, most of the features work, just not RAW format or USB.
You will find the info for downloading the software in this thread.
Cheers,
Norbert
-
You can check the firmware of your cam with this method:
http://chdk.wikia.com/wiki/FAQ (http://chdk.wikia.com/wiki/FAQ) 'Q. How can I get the original firmware version number of my camera?'
Most probably it will be rev. B
You will need to download 'diskboot.bin' from this thread, be sure to be logged in.
Cheers,
Norbert
-
thanks norbert.
i have a 1.00b and CHDK is running beautifully.
noticing some funky things - like aperture priority seems stuck at f8 but when i'm on shutter priority, the aperture drifts freely to 2.7 or 5.6 etc..... o read the posts about the ND filter limiting aperture choice but then it's a mystery to me that the aperture is being shown to have as wide a variety as is being reported on my after shot info.
oh and i haven't tried scripts yet. any info about that? do they work? in particular, the intervalometer and motion detection scripts (yes, i want to shoot lightning dammit! : ) ) are of interest to me. if no info available, no prob. will just try it!
thanks much for help and keeping this thread from just going totally dark!
jin
-
That's great!
I have found no reliable way to switch to 2.7 aperture. It seems that the camera decides on itself, depending on the incoming light from the lens. You can check this when approaching a bright light with the cam, at a certain point the ND filter will kick in. The variation on the aperture value depends on the zoom level. More zoom means less light and the aperture values get corrected for that. Just calculated data. Nothing more. The basic scripts work nicely, e.g. intervalometer is fine. Motion detection I did not try. Please tell us if it worked.
Norbert
-
I would expect that the a1000 does not actually have an adjustable iris. In general, if canon does not include an Av mode, then the camera does not have one. The aperture is only determined by the zoom (and the ND filter applies a fake modifier to that in the exif info)
-
That's correct, the A1000 has no adjustable iris, only the ND filter. It's still annoying that the ND filter cannot be switched off on purpose. At least I found no reliable way to do it.
Norbert
-
aha! so the varying aperture values are only estimated values based on lens focal length!
doh... that was vexing the f out of me today... wanted to open wide to try to get some nice shallow focus shots (though the small image sensor conspires against it) but there was just no way to DETERMINE the aperture. it just did what it wanted.
can get pretty good bokeh if i switched to macro though... but the subject couldn't be too far away then....
thanks and will let you know if the motion detector script works.
jin
-
Has anyone successfully gotten SDHC to work with this version? I've correctly partitioned my 8GB SD card (FAT16/FAT32), but I receive the 'card locked' message.
-
in the card tricks interface where you make the card bootable, i think it says that mem cards larger than 4 gb can't be made bootable.
i'm using an 8gb card myself but i put CHDK on the 32mb (right, MB) disk that came with the camera to play around with.
having used it a bit, i don't think it's something you're really gonna want autoloaded anyway. there's no raw and the fact that there is no aperture control kinda limits what you can do with it... i guess the zebra stripes and histograph is kinda cool but again, the lack of control makes it less than useful.
my plan is to make CHDK manually bootable from the 8gb.
jin
-
sonofa...
so has anyone been able to make an fi2 file properly using http://chdk.setepontos.com/index.php/topic,2995.0.html (http://chdk.setepontos.com/index.php/topic,2995.0.html) ?
i've identified the a100is' PID as being 318E from the wiki entry http://chdk.wikia.com/wiki/A1000IS (http://chdk.wikia.com/wiki/A1000IS) but no amount of futzing with the my.map or pack.bat results in a file that will properly load manually.
some folks earlier in this thread pointed peeps to the fi2 encoder... has ANYONE got this to work for the a1000is?
thanks.
jin
-
jinchoung,
I've also been able to use a 32MB SD card with the DISKBOOT.BIN file found earlier in this thread. Just no luck trying to boot off a 8GB card with a FAT 32MB partition.
I came to the same idea of booting manually. Unfortunately, I was never able to create a fi2 file that worked.
My final attempt was setting up the CHDKShell environment and downloading source (found in this thread). After adding some missing parts (like NEED_ENCODED_DISKBOOT=1), I was able to build diskboot.bin. However, this build fails during the boot process. I created a few debug points (flashing the led) and their appears to be an issue in the assembly code. My guess is the problem is with 'sub_FFC194A0_my' in /platform/a1000/sub/100b/boot.c since 'sub_FFC604A4_my' is never reached.
My results are nearly identical to a previous poster. I don't have the expertise to get any further.
-
I created a patch to the latest build of CHDK (836). Hopefully someone with more knowledge than I can use it to more quickly get a build into the trunk.
Using the attached files (don't forget to also grab PRIMARY.BIN), one should be able to patch 836 and build A1000IS firmware. However, as I mentioned in an earlier post, the firmware fails during the boot process.
I'd love to see this merged into the trunk, so that A1000IS development can move forward and not continue to fall behind.
-
actually is the a1000is even in the tracker? i think we're still stuck in beta and not incorporated into the build system yet....
as for implementing new patches into the incomplete a1000is version... i'm not sure if that's doable. i don't think there's anyone here who is actively developing for the a1000is version right now.
alas, i don't have any coding/building/compiling expertise so i'm no help.
but i'll stand beside you and whistle and twiddle my thumbs.... : )
jin
-
Does anyone have a bin file for the july 08 firmware of the a1000? I can't get the posted version to work and I think its because I have the july 08 firmware even though it is version 1.00b. I have used chdk on many other cameras and would really like to get this one working for aerial photography. Thanks a ton in advance.
-
Hi,
the 1.00a version and the 1.00b versions were posted in this forum. Do you believe you have a different firmware than these? How did you check?
Norbert
-
Hi,
the 1.00a version and the 1.00b versions were posted in this forum. Do you believe you have a different firmware than these? How did you check?
Norbert
Thanks for pointing out that 1.00a was also posted, I must have downloaded that one by mistake. I made sure to download the one for 1.00b and now it works. Seems like you have to press disp instead of menu like normal but it'll def work for what I need.
Thanks
-
If anyone wants to try a pre-release version of SDM 1.82 for the A1000, you can get it here :-
http://www.zshare.net/download/69799780047c3dac/ (http://www.zshare.net/download/69799780047c3dac/)
-
I, seems, found, where it is necessary to correct the code for good RAW a1000is.
In code http://chdk.setepontos.com/index.php/topic,2654.120.html (http://chdk.setepontos.com/index.php/topic,2654.120.html) in module a1000_chdk/include/camera.h
#elif defined (CAMERA_a1000)
#define CAM_PROPSET 2
#define CAM_DRYOS 1
//not it is correct
// #define CAM_RAW_ROWPIX 3648 // for new 8 MP
// #define CAM_RAW_ROWS 2756 // for new 8 MP
//it is correct
#define CAM_RAW_ROWPIX 3736 // for new 10 MP!
#define CAM_RAW_ROWS 2772 // for new 10 MP!
#define CAM_JPEG_WIDTH 3648
#define CAM_JPEG_HEIGHT 2736
#define CAM_EV_IN_VIDEO 1
#define CAM_CAN_MUTE_MICROPHONE 1
No calibration with use DNG4PS-2 will not help until it is corrected description CAM_RAW_ROWPIX and CAM_RAW_ROWS.
The Big request to that beside who there is working code. Peretransliruyte with change
or put src working code.
CHDK http://chdk.setepontos.com/index.php/topic,2654.120.html (http://chdk.setepontos.com/index.php/topic,2654.120.html) (http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=3398 (http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=3398))
it is translated, but is not loaded(boot).
-
Hello everybody!My first post here.Dont wanna bother you,yust to ask-is this(last post) prefinal version,or this things have to be solved and corected???
I am the owner of the A1000IS.Is it possible,anytime in the future,that a1000is gonna have his own fully workable Chdk with raw and all that goodies like all other cameras or this is impossible at the end :(?
Cheers :D great work guys and God bless ya all!!!
-
Hello everybody!
I do not think that this last change.
I began to compare RAW, received at the beginning initially work Diablo
http://chdk.setepontos.com/index.php/topic,2654.0.html (http://chdk.setepontos.com/index.php/topic,2654.0.html) (http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=2506 (http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=2506))
or http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=2520]http://chdk.setepontos.com/index.php/topic,2654.15.html([url]http://chdk.setepontos.com/index.php?action=dlattach;topic=2654.0;attach=2520 (http://chdk.setepontos.com/index.php/topic,2654.15.html([url)[/url]) and has seen that he works through once:
1 raw was bad,2 raw - good, 3 raw - bad, 4 raw - good, 5 raw - bad e.t.c therefore that in these 2-h events of importance variables
#define CAM_RAW_ROWPIX 3720 // for 12 MP camera (SX110 IS)
#define CAM_RAW_ROWS 2772 // for 12 MP camera (SX110 IS)
there were take from camera Canon Powershot SX110 IS (12 MP)
Raw, received from http://chdk.setepontos.com/index.php/topic,2654.105.html (http://chdk.setepontos.com/index.php/topic,2654.105.html) (http://rapidshare.com/files/219956040/DISKBOOT.BIN (http://rapidshare.com/files/219956040/DISKBOOT.BIN)) does not work quite since no such cameras with variable
#define CAM_RAW_ROWPIX 3648 // for 8 MP(? camera)
#define CAM_RAW_ROWS 2756 // for 8 MP(? camera)
I offer importances variables, taken from cameras G7 or Canon PowerShot A640
#define CAM_RAW_ROWPIX 3736 // for new 10 MP!(G7 or Canon PowerShot A640 or A1000 IS)
#define CAM_RAW_ROWS 2772 // for new 10 MP! G7 or Canon PowerShot A640 or A1000 IS)
-
Hi
I have A1000IS, version 100b. I tried to use the DISKBOOT and CHDK uploaded by Diablo so many times but failed to upgrade my firmware. I never had that option upgrade firmware. I read FAQs. Double checked my firmware. Downloaded all the Diskboot and CHDK from this forum and tried to use them but I am unable to load the CHDK. Can you guys help me in this. Really want to use CHDK. Thanks in advance.
-
I see Diablo's fileshare post has expired. Is there another location for the latest A1000is CHDK file to try?
Thanks
Sure, here ya go:
http://rapidshare.com/files/219956040/DISKBOOT.BIN (http://rapidshare.com/files/219956040/DISKBOOT.BIN)
Any chance of another location or sending by email? to get a 250kB file off Rapidshare is impossible if you're not a member - I don't want to spend 7$ just for 250kB...
-
Can you guys help me in this.
You could try the version here http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
Download url=http://stereo.jpn.org/eng/sdm/file/common_files.zip]Common_files.zip[/url] as well.
David
-
Hello Everybody-have a question!
Since i downloaded this version(from last post) ive been able to do:
Bracket Override
Zebras
Live Histograms etc.There is no Raw,motion detection etc right?
When i start my camera,i get screen with some googles on it :) not the standard Chdk logo.
When i turn teh camera ON i have some blue horisontal "taskbar" in upper screen.Asking this to see if this is normal?
This is ok for now right?
I have A1000IS GM1.00B firmware version...
Cheers :D
-
When i turn teh camera ON i have some blue horisontal "taskbar" in upper screen.Asking this to see if this is normal?
Yes, that tells which shooting mode you are in, the zoom setting and the synchronisation delay for flash with two cameras.
In menu Stereo, you can choose the Compact header or turn it off.
In the Advanced menu\OSD Parameters, you can set zoom display to real focal-length, 35mm-equivalent focal-length, field-of-view in degrees or zoom-step number.
If 'zoom font size' is non-zero, you can also have a separate display of zoom value in very big letters .. you choose the size.
Use the layout editor to move the displays anywhere on the screen.
David
-
Thanks David!
I`ve got it all :D
Now i understand all stuff.Expecting some RAW support soon from all you clever guys? :)
I cant wait it! 8)
Edit/Modify:
Dont want to owerpost-i have to add question,do i need separate script in corelation with my chdk version for motion detection???
-
I see Diablo's fileshare post has expired. Is there another location for the latest A1000is CHDK file to try?
Sure, here ya go:http://rapidshare.com/files/219956040/DISKBOOT.BIN (http://rapidshare.com/files/219956040/DISKBOOT.BIN)
Any chance of another location or sending by email? to get a 250kB file off Rapidshare is impossible if you're not a member - I don't want to spend 7$ just for 250kB...
The link is still available, but RS limits the download slots for free users...a mirror is here: drop.io link (http://drop.io/hidden/h4fdx2ampugcsj/asset/ZGlza2Jvb3QtYmlu).
-
Testing latest version for a week,all day long :D
Noticed some bugs/errors so i want to share them with some more expirienced users(read genius).
So
Aperture override works just fine.
override shuter also works.problem is override focus.When i set it to ON and try to focus camera shuts down imediatly.
Also,after some time going through chdk menu,camera shuts down by itself(but green led is still working and camera is in freeze mode,only black screen).
Histogram works very fine in all setups,zebra also.
Another problem i noticed is,that after some time my OSD settings going reset,and except histogram,i have noting left on the screen from chdk.He is still there but zoom,battery,focus,and clock info functions that i set in menu,simply dissapear.
These are some problems i have during these days,so,because this is testing mode,i give you my experience for now!
Generaly,i am fascinated with this chdk and everything this marbelous guys achieved!Great work indeed!
Good bles ya all!
-
do i need separate script in corelation with my chdk version for motion detection???
Yes, in Common_files.zip in the Scripts folder there should be MDFB-080914.bas.
If it is the correct version it will say at the top of the file "rem Modified to support 'show sample points' option and turn-off synch mode (SDM 1.82 and later)"
David
-
Testing latest version for a week,all day long :D
Noticed some bugs/errors so i want to share them
Just to be clear, are you testing CHDK or SDM version ?
David
-
SDM sorry for missunderstanding..Talking about Sdm... ;)
-
problem is override focus.When i set it to ON and try to focus camera shuts down imediatly.
I will look at it.
I would think the CHDK version does the same.
Probably an incorrect address for the focus function.
zoom,battery,focus,and clock info functions that i set in menu,simply dissapear.
With SDM in ALT mode, a brief press of the FuncSet button turns the screen information on/off.
Is that what you are doing ?
David
-
Chdk also make same mistakes that i mentioned.Focus override error etc(all mentioned in earlier posts)>
David,yeah,my mistake FuncSet in Alt mode=Additional data On/Off
Sorry.I am newbie but understanding cameras and photography,so i decided to contribue in testing of a1000is chdk versions,so everything i notice i will post here if you guys dont mind. :)
-
Do not apologise for anything, we need people to test builds and report 'problems'.
I will look at the focus problem as soon as I can and report back.
Remember, the CHDK A1000 port was never finished so there may be other bugs.
David
-
Ok David 8)
Is there any possability to expect fully workable CHDK for this cam model in the future,like for non DryOs cams?
???
Edit:when i set shutter override to values over 1/10000(aprox) when i focus,info on OSD reporting just 1/1600 and after that,no matter what more value i set,it says only 1/1600.When i go below 1/10000 than it seems ok.
Is that Canon software up limit in play mode(review info with details after taking a shot) :blink:
-
Is there any possability to expect fully workable CHDK for this cam model in the future,like for non DryOs cams?
I do not know, someone would have to do it, I certainly do not have time.
no matter what more value i set,it says only 1/1600.
That is normal behaviour, the Canon firmware does not know the shutter-speed has been overriden.
The uBasic set_focus (or set_focus_to) command uses the same Canon firmware function as the focus-override option.
So, it will probably crash the camera.
After moving the lens, the focus-override function checks the focus distance using the same Canon function as the uBasic 'get_focus' command.
Let us test if that function causes the problem, run this script :-
@title Get focus
sleep_for_seconds 2
get_focus a
line_1 "#Focus ", a
sleep_for_seconds 5
end
Does it crash the camera ?
-
Hi
I'm new on this forum.
I have A1000IS fw1.0b.
I'm really trilled with abilities of CHDK and I would like to see it fully functional on my camera.
I believe there are a lot of people that would like it too, because I see there is a lot hits on this A1000 forum. Even much more than on some functional cameras.
Only people probably don't want to register so they don't post.
If you want CHDK to work on your camera please show some interest here and maybe we can get some developer to make it.
Because that's what we are missing, a developer.
I tried last Diablo's version.
Basically it works, with some bugs.
Main ones I noticed are that OSD menus stay on screen after exiting it, and this Focus thing.
When I get time I'll do some more detailed testing and I'll post results.
That's all I can do because I have no idea about programing.
I'm glad to see something is happening these last few days.
Hope we'll have fully functional CHDK and SDM for A1000 one day
Thank you all putting your effort in it.
@Microfunguy
I'd love to try this your script but have no idea what to do with it?
-
I edited A720 camera profile and used it for A1000IS. You just need to rename the camera(setting->camera options->cameraname, shortname) and change resolution(to 3648x2736 in both sensor size and jpeg size). With this I could get them displayed in dng4ps2 but after covert the images displayed were incorrect.
I followed this instructions and I do get picture with irfan view after converting RAW. It looks exactly the same as jpg but its bigger
-
Hope we'll have fully functional CHDK and SDM for A1000 one day
Apart from the focus-override, everything works with SDM as far as I know.
I'd love to try this your script but have no idea what to do with it?
Copy-and-paste the above script and save as a simple text named, for example, test.bas.
In ALT mode, load the script and press the shutter button to run it.
Does the camera crash or is a distance value displayed for a few seconds ?
If you are using CHDK, use this script version :
@title Get focus
sleep 2000
get_focus a
print "Focus ", a
sleep 5000
end
-
OK!
I started the script
it said:
*** STARTED ***
FOCUS 502
*** FINISHED ***
I hope this will help.
edit: it's different number each time I start the script
-
Thanks.
At least we know get_focus works OK.
Try something like :-
@title Set focus
sleep 2000
set_focus 1000
sleep 2000
get_focus a
print "Focus ", a
sleep 5000
end
That will probably crash the camera, if previous reports are correct.
-
it didn't crash the camera.
only difference is with one in the lower left corner says Get focus and with the other Set focus.
and two more important Bugs:
CHDK menus stay displayed even when you get out of them. they disappear only when I half press shutter.
Memory card space is always seen as 0M from CHDK
-
it didn't crash the camera.
So did the camera focus and was the reported distance about 1000 ?
and two more important Bugs:
CHDK menus stay displayed even when you get out of them. they disappear only when I half press shutter.
Memory card space is always seen as 0M from CHDK
Unfortunately, I do not have time to work on CHDK as well as SDM so I do not know what the problem is.
-
I don't know if it focus. the green square didn't show if you think that.
set focus reports about 4000 and something.
get focus reports 400, 500 and something and 4000 and something.
-
!!! So I call this way developers that are willing, and have time, to help us make fully functional version of CHDK for A1000IS, please !!!
Anybody else that would like to have CHDK on your A1000 please join me in this appeal. Maybe somebody will have mercy if he/she see there's a lot of us.
Or we can collect something to reward him/her?
and Microfunguy, thank you. every step is a big step if we are staying in place otherwise.
-
First of all,hello Kulen.
Second,relaaaaaaaxxxxxx :D
We are all trying to develop and help developers,so no need to rush.First of all,developers have so little time to spend on every camera.And there is a billion of Cannons to develop!
Then,we are all spectating and analyzing our results with using Chdk and posting them here,so developers can do something about that.There is no need to push guys,they are doing their best,considering their freetime.They have their own lives,beside jobs etc.
So post here everything you notice about chdk,and support these guys by giving them testing info,so they could develop faster!
Thanks for your contribution :D
Cheers 8)
-
OK!
Sorry if you misunderstood me.
I'm not pushing anybody. I'm just thrilled something is happening, because there was almost no posts on this forum for a few months. So as I see it nobody shows any interest for CHDK on A1000. and why should anybody spend any precious time on it?
So I just wanted to point out that there are people that want to see CHDK on A1000, and they should show interest.
an I'm very tankful for every moment anybody spends on making it possible.
And about reward I mentioned - I just wanted to pass experience from some other forum, for mobile devices, where we were in similar situation. no developers and a lot of interest. so we all donated 5-10 Euros to buy 2 devices for 2 developers. and they did great job after that.
I also know that on some forums people collect bounties, a sum of money that is then given (or split if more than one) to a man that does the job.
I'm good for any solution if there's interest from enough people and at least one developer.
If suggesting something like that here is against Forum rules, Moderators please edit this post or warn me to edit it myself.
Thank you
-
Even though I do not have time (and money cannot buy additional time), why not make a list of the CHDK problems still to be fixed ?
-
I plan to test all functions and report back. but I need some time to do that.
In the meantime I tried this scipts with SDM (version that was first posted here)
I first tried focus override function and camera crashed as soon as I pressed shutter.
then I started first script (get focus)
It first reported
-1
finished
And a few other times there were some other numbers. like 4000 and something.
Set focus returns always the same:
1010
finshed
actually not exactly the same but number is always around 1000, and it didn't crash camera
strange thing is that after starting get focus script for the first time, I set override focus again and took a few photos without camera crashed.
After starting set focus it cashes no matter what I do.
Perhaps I did something wrong that time but if I didn't maybe it means something to you.
SDM has same problem as CHDK with menus staying on screen even after exiting them.
Thank you
-
Ok,now i have a problem.Yesterday i loose all my cdhk files from computer.Somebody erased them and i formated my memory card.Can someone please upload the latest chdk version here?
-
I just downloaded the one from this post
http://chdk.setepontos.com/index.php/topic,2654.msg31940.html#msg31940 (http://chdk.setepontos.com/index.php/topic,2654.msg31940.html#msg31940)
because I want to start from fresh, and test what's working and what's not.
I believe it's the last one?
-
Ok,i am traveling these days so i wonder,is it safe to carry with me A1000Is with SDM(latest version) and 4Gb memory SD card.Is this safe and reliable for standard capturing?Recomendations?Is it ok with 4Gb card???Thanks :)
-
I have been going through menus and tested things. There are a lot of things so it goes slow. for now I tested some.
I'll update this post as I test something else.
+ marks working stuff but I'm not much of a photographer so I don't know if I tested well.
I noticed that in compare to user guide this CHDK doesn't have all the same functions in menu (like flash in extra photo operation)
EXTRA PHOTO OPERATIONS
-disable overrides *
include auto ISO *
-override shutter speed +
value factor +
shutter speed enum typ +
-override aperture +
-override subj. dist. val. +
value factor +
-override ISO value +
value factor +
-bracketing in continuous mode +
TV bracketing value +
AV bracketing value +
subj.dist.bracketing value +
value factor +
ISO bracketing value +
value factor +
Bracketing type +
clear bracket values on start +
ad raw suffix *
-custom auto ISO *
-enable fast EV switch +
step size +
* not sure how to test
VIDEO PARAMETERS
-video mode + **
-video bitrate +
-video quality + *****
-clear videoparams on start +
-fast video control *
-video quality control *
-enable optical zoom -
-mute during zooming - ***
-show remaining videotime -
-refreshrate ****
* don't know how to test
** I guess, changed it with lover two settings
*** optical zoom doesn't work so I guess this also
**** since show remaining videotime doesn't work this doesn't work automaticaly
***** camera switched itself off during one test of this.
RAW PARAMETERS
-save RAW +
-dark frame substraction *
-only first raw in series + **
-raw file in dir with jpeg ***
-raw file prefix +
-raw file extension +
-raw sub tract prefix *
-raw sub tract extension *
-subtract input dark value *
-subtract output dark value *
-raw develop *
-bad pixel removal *
* don't know how to test
** it works but photo numbering seems to be wrong
*** no aditional directories created? not sure how this should work.
OSD PARAMETERS
not tested
VISUAL SETTINGS
not tested
HISTOGRAM PARAMETERS
not tested
ZEBRA PARAMETERS
not tested
SCRIPTING PARAMETERS
not tested
CUSTOM CURVES
not tested
REMOTE PARAMETERS
-Enable remote - +
+on switch press screen goes black and if hold longer it switches to play mode. on switch release it goes back to camera mode.
other in this menu not tested.
FYI in SDM remote works.
MISCELLANEOUS STUFF
not tested
BUGS:
-menu stay on screen after exiting
-Memory card space allways 0M
-
Hello everybody!. To whom needs the assembly CHDK for a1000 is with normal processing RAW, leave;quit;get out; on your email.
Can send and sourcre code Shdk_a1000is_1000b_090(svc_633). RAW is processed XnView, Ufraw, Zoner Photo Studio 12. Also works the convertor RAW in DNG in camera. The Assembly on sourcre code for Diablo, thank you him for work!)
-
... a1000 is with normal processing RAW, leave;quit;get out; on your email.
Can send and sourcre code Shdk_a1000is_1000b_090(svc_633). ....
Hi All.
I correctly understand -
You compiled and got really working DISKBOOT.BIN with a file RAW(CRW) ?
You send her on me mail ? If s?, send it, and source. I will test badpixel.
This DISKBOOT.BIN, interests for all.
Better, You can attach this .BIN here or place it to any hosting?
Source Shdk_a1000is_1000b_090(svc_633) - It is a that last version what present from diablo ?
Changes only in include/camera.h CAM_RAW_ROWPIX / CAM_JPEG_WIDTH ?
( http://chdk.setepontos.com/index.php/topic,2654.msg33964.html#msg33964 (http://chdk.setepontos.com/index.php/topic,2654.msg33964.html#msg33964) )
I get this wersion, but I don't compiled - not found file descript function sig_ref_dryos_1000.txt, for example.
SVC/TRUNK, not found version for a1000.
If it the last working with all changes, possibly temporally to place source code to any place?
p.s. to All: We will continue work for CHDK A1000 ?
bolalex I speak Russian .... chy sho ... :)
-
? ??? ????????????? ?? ?????????? CHDK. ?? Diablo ????????, ?????? ??? ??????????? ??? ?????????. ?? ?????? ?????, ?? ?????? ? ??????????? ???-?? MP ?? ??????? a1000 is.
?????? ???? ?????????? ?????????? ?????? ???(??????? 12 MP), ??? ? ? a2000 ??? SX 110.
????????? ? ???? 0.90(0633) ?????? CHDK ? ??????? ?? Diablo(?? ??????? ? 0.72(552), ?? ??? ???
???????? ?????????????? ????????? ? CRW ?? DNG ? badpixel. RAW ? ???????? ???. ???? ???????? ???? EMAIL, ?? ????? ???(?????? ? ????????????~ 2 ??). ? ???, ???? DISKBOOT.BIN ??? ????? CHDK ?? ????????.
????.
-
In russian does not leave. If from Russia write on forum http://chdk.setepontos.com/index.php?action=pm;sa=send;f=inbox;pmsg=5340;quote;u=11721 (http://chdk.setepontos.com/index.php?action=pm;sa=send;f=inbox;pmsg=5340;quote;u=11721)
-
Hi All. New for a1000is
http://chdk.clan.su/_fr/3/a1000is-100b-82.zip (http://chdk.clan.su/_fr/3/a1000is-100b-82.zip)
http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip (http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip)
-
Thank very much you for this.
did you make it?
But could you provide some more information? Are any bugs solved here? or is it just new version but everything works the same?
-
Thank you Bolalex! Just loaded your new build, works okay with firmware 1.00b. It seems to be a newer CHDK version, there are little icons for menu items, and a few new options (like manual flash power setting). The initial testing shows that the same things are working/not working as in Diablo's build, except for RAW output, which now seems to work perfectly (only tried it in XnView though). Thanks for fixing it! Now I can play around with 12-bit precision :)
-
Hi everyone. This not my assembly. This continuation of the work commenced Diablo. I have corrected RAW. All rest from new assembly. RAW was got 12 bit like as camera a2000.
-
are you planning to continue working on this?
do you need some kind of support? for testing and so
-
First of all,thanks for everything you guys!You are great!
Second,i tested latest version ,and noticed some bugs:
:When costumising osd aperance,camera crash!
When selecting additional data on display-crash
Changing menu fonts-crash...
Is Raw in 10 or 12bit dept now???
Cheers
-
12 bit
-
Thx bolalex...
Also,my Raw images are now in greater than max resolution from jpgs,not 3648 * 2736!
they are in 3684 * 2760 px.
I processed some of them and they are really great!Diference is there!
-
I processed some of them and they are really great!Diference is there!
That is good news.
Can you upload the original raw and jpg somewhere so that we can see how great the difference is ?
-
I have some exam tomorrow,so after that i wil upload some of my raw comparsions!Cheers people! :D
-
I have some exam tomorrow,so after that i wil upload some of my raw comparsions!
Good luck with your exams :)
-
Hello!
I'm new in this forum. The reason is that I bought a A1000IS in order to be able to get better possibilities for microscope and hdr photos than with my A530. CHDK is working well on the A530, but the LCD screen is very small and rather weak. So I took a special offer to get the A1000IS.
For me who comes to this forum it's not just easy to find out the latest information available. So I ask you to help me.
First I would like you to tell me where I get the latest diskboot.bin for my camera. Presently I have one installed on it, but overriding shutter speed isn't possible. As it is told to function, it seems that I have an older version.
I think I don't need help installing the software, since I already have some experience with my A530.
But please tell me where I can download the latest CHDK version. The a1000is-100b-82.zip offered by Bolalex in his reply #239 contains so many files that I'm confused a bit.
Thank you for your help. If I can help you by reporting my experience, I will do that.
Greetings
Gernot
-
Gernot,
go back a few posts and look for the two links by bobalex.
Version 0.9 should be the latest, the file is still there, I just checked it.
Norbert
-
-
That's great.
One problem I found is that the ND filter keeps kicking in, more or less at random. Not so much at HI-ISO setting, though.
Greetings
Norbert
-
Sweet, now I can try the RAW images and see how they come out. Thanks bolalex for the continued support.
-
Any luck getting a motion detection script to work with this? There is lightning today. Would be great to get some shots if possible. i tried one but the camera would close and power off each time it tried to take a shot.
-
Meanwhile I got CHDK running on my A1000IS, and I'm happy that everything (including scripts) is running excellently. :)
What does it mean everything is running excellently?
Some time ago I sarted testing what works and what doesn't, but there was too many things that don't work (especially when I got to OSD parameters) so I just stopped testing.
Is there some new fully functional version?
Thank you!
-
Hello, Kulen!
I was absent for some days and read that you were surprised that I reported that everything worked.
I extracted the version of the a1000is-100b-82.zip offered by Bolalex in his reply #239.
Maybe you tested other things than I need. But I can report that settings (like histogram and zebra mode) and scripts which I used on my A530 are working. So I'm fully satisfied. :)
Gernot
-
Hello everybody! I do next version
http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip (http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip)
-
Bolalex
You are doing a great job moving things ahead on this project. I loaded your latest version and see that the menu behavior is much cleaner and the remaining RAW indicator now works. I did notice that the zebra function seems to be acting differently. If I point it directly at a light I see a zebra indication outlining the over exposure image but its offset to the right about 3/4 inch.
-
Hi there,
Thanks bolalex!
I experienced the same problem as h. Zebra and edge were working fine with the previous version, now it seems that the "resolution" of the zebra layer is different (wrong) from the real one.
Another annoying problem is the menu refresh... Does someone know the solution?
Could you post the diff of the latest code versus the main svn version?
-
Hello everybody! Thanks all I change zebra function
http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip (http://chdk.clan.su/_fr/3/a1000-100b-0.9..zip)
-
Hi bolalex,
Fantastic, I'm going to try it...
Thanks again,
Cheers
:( Unfortunately it seems to not work. Zebra and Edge are not working my side.
Could be possible to post the code modification you did? we could help, someway...
-
Hi All. Reload please
http://chdk.clan.su/_fr/3/a1000-100b-099.zip (http://chdk.clan.su/_fr/3/a1000-100b-099.zip)
I change agane code for zebra function
-
Hi,
Zebra is working now, great!
Quick test up to now is ok
Is it possible to commit the source changes in the main tree?
-
Hi All,
did you try test script? I experienced some camera crashes :-(
-
-
I see that menu still stays on screen after exiting from it.
-
Hello everybody,
have raw to DNG question.What is the bad side of converting the Chdk Raw into DNG files?When i open Dng in Photoshop,it says that it has only 8bit depth.What is wrong?
Cheers :)
-
I just got the A1000is thinking that I might like to try the experimental versions mentioned here.
I was able to get the latest Bolalex version ( thank you, Bolalex) to run an intervalometer script.
I did need to create a bootable SD card in cardtricks, as I did not find a firmware option in the A1000is.
I may have crashed it a couple of times, and I'll try to remember how I did it for future reference.
I also was unable to exit the CHDK menu, it would seem that exiting ALT mode and pressing the shutter removes it.
The "loading script from file" menu does not have a "back" function - the "disp." button seems to bring you back to the main menu -pushing "disp" again seems to close the CHDK menu, but it seems like the camera might not know to "unwrite" the screen, so it just stays under the histogram(I think that's what it is)
-
Error 404: File Not Found
Page (or file) you requested has been moved or deleted
-
I have been sifting through this page for highlights and I've been on IRC and people like reyalP have been quite helpful. I just got 2 used A1000 IS cameras, one has 100a firmware and one has 100b firmware. I installed the SDM for the A1000 (they only have a 100b version) and it works fine on the 100b camera but won't load on the 100a camera. (Download for SDM here (http://stereo.jpn.org/eng/sdm/download.htm)) Since apparently you cannot just update the 100a firmware to 100b firmware (which still blows my mind but anyways) I am now on a quest for a working SDM for 100a. I would also like to see fully functioning 100a and 100b CHDK versions. Here are some main posts for those not wanting to sift through all this:
diablo's source files: http://chdk.setepontos.com/index.php?topic=2654.msg33964#msg33964 (http://chdk.setepontos.com/index.php?topic=2654.msg33964#msg33964)
kulen's test results for the latest diablo build (if I understand things correctly): http://chdk.setepontos.com/index.php?topic=2654.msg46615#msg46615 (http://chdk.setepontos.com/index.php?topic=2654.msg46615#msg46615)
the latest version in this thread, posted by bolalex: http://chdk.setepontos.com/index.php?topic=2654.msg50133#msg50133 (http://chdk.setepontos.com/index.php?topic=2654.msg50133#msg50133)
The original 100a version: http://chdk.setepontos.com/index.php?topic=2654.msg25703#msg25703 (http://chdk.setepontos.com/index.php?topic=2654.msg25703#msg25703)
Some other links of note
A Google translation of the German thread for the A1000IS (which includes a new 1.1.0 version for the 100b): http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fforum.chdk-treff.de%2Fviewtopic.php%3Ff%3D12%26t%3D2171 (http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fforum.chdk-treff.de%2Fviewtopic.php%3Ff%3D12%26t%3D2171)
The CHDK-DE download page which has a .zip file for "a1000-100b-1.1.0-full_ALPHA_rev_690" http://forum.chdk-treff.de/download.php (http://forum.chdk-treff.de/download.php) (under "PowerShot A Serie")
The CHDK (English) wiki page for the A1000IS which includes a 'firmware dump' for 100a and 100b: http://chdk.wikia.com/wiki/A1000IS#Firmware_info (http://chdk.wikia.com/wiki/A1000IS#Firmware_info)
__________________________________
If your A1000 has the 100b firmware (you can check using "ACID (http://www.zenoshrdlu.com/acid/acid.html)") then I would suggest using the German 1.1.0 alpha version or the SDM version. If your A1000 has the 100a firmware, then you and I are in the same boat and I am hopeful that someone will help us :)
I'll update this post if I found out more.
EDIT
It looks like the two 'newest' versions of the A1000 1.00b CHDK are not in English - one is German and one is Russian. The Russian version was posted here (the 0.99 version) and the German version is the one at the German download link. For me, the 0.99 Russian version loads fine on my camera but the German 1.1.0 version will not load (my camera won't turn on with it in.) I have PMed CHDKLover, the German person behind the 1.1.0 version (and its addition to the German svn.) I am hoping he can sort things out. I am also really hoping he speaks English :)
For what it's worth, here are links to the Russian and German forum threads for A1000IS porting (run through Google Translator)
German: http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fforum.chdk-treff.de%2Fviewtopic.php%3Ff%3D12%26t%3D2171 (http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fforum.chdk-treff.de%2Fviewtopic.php%3Ff%3D12%26t%3D2171)
Russian: http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=ru&tl=en&u=http%3A%2F%2Fchdk.clan.su%2Fforum%2F22-388-1 (http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=ru&tl=en&u=http%3A%2F%2Fchdk.clan.su%2Fforum%2F22-388-1)
-
If your A1000 has the 100a firmware, then you and I are in the same boat and I am hopeful that someone will help us :)
If nobody else gets to it first, I'll do a 1.00a CHDK verision for you from the 1.00b. Won't be right away, I'm kind of tied up for the next three or four weeks but there is hope.
The big questions is, how good is the 1.00b version? My most recent conversions between different firmware versions on the same camera have ranged from easy (S95) to hard (IXUS980_SD980) to downright nasty (A495). If there is a CHDK port for the 1.00b that is clean and runs well then it will only take me a few hours to do the conversion and that could be squeezed in over the next couple of weeks. If the 1.00b is wobbly then it will take longer to find the time.
-
If nobody else gets to it first, I'll do a 1.00a CHDK verision for you from the 1.00b. Won't be right away, I'm kind of tied up for the next three or four weeks but there is hope.
Hey waterwingz! reyalP on IRC thought you might be the person to talk to about getting a 100a version so I'm glad you saw my post :D
The big questions is, how good is the 1.00b version?
I have been using the SDM but I will try to get the German 1.1.0 100b version up and running (on my 100b camera, just to clarify, I have one of each) and I'll test it out and edit this post with the results. From what I've read, it seems like the 100b version works except perhaps the remote and the motion detection scripts. Stay tuned :)
UPDATE
Well, the German autobuild version does not work - my camera will not turn on. The .bin file form the German forums shows "Card locked!" when I turn the camera on (and then the camera turns on normally, not in CHDK.) I tried out some of reyalp's and waterwingz's potential fixes (on IRC) but no luck yet. I'm currently hoping that CHDKLover can help us out (since he is the one who made the German 1.1.0 version.)
-
Please forgive the multiple posts but I'm trying to keep things (at least sort of) orderly. I have been e-mailing Microfunguy (the man behind the SDM fork of CHDK) and he helped me debug the German autobuild source. Since his SDM build was similar to the German autobuild, he tweaked his stubs files to work with the German autobuild. I have loaded up this version on my camera and it works with the huge caveat that the menu isn't right (the text is stretched and not centered properly and some of it seems to be off screen) so I would not recommend actually using this build as is, but it at least gives source for a working version of the code that's in the German autobuilder. I'm hopeful that waterwingz and reyalp will be able to use this to make a working version of 100b CHDK with the menus looking like they are supposed to and from there a 100a version :) Since he also made a .bin file for me to test, I have attached that to this post, too.
Note that I did get Microfunguy's permission to post this here - he said that is what it was for :)
EDIT: To help clarify what I mean by "text is stretched and not centered properly..." here are some pictures :)
http://imgur.com/a/MBjyy (http://imgur.com/a/MBjyy) (this is a gallery with a few pictures - there seems to be a two attachments per post limit on the forums so it'd be a bit tedious to post them all here.)
-
With some coaching from reyalp I was able to get CHDK-Shell up and running and I tweaked the German svn platform_camera.h and now the display seems to work properly :) As far as I can tell, there was a bunch of extra code in there about adjusting the display that was not necessary (and presumably copy/pasted from some other camera.)
I have done a bit of testing and things like Zebra, Histogram, and Edge seem to work as does the Misc OSD stuff and the depth of field OSD aid. When I tried to use the Raw Parameters -> Create badpixel.bin menu option, it doesn't seem to quite work - it takes one picture but then just sits there. (My understanding is that it should take two pictures and then do some thinking and make that badpixel.bin file.) Also, when I set OSD parameters ->Show Temperature? to Battery my camera turned off and when I'd turn it back on it'd turn right back off. I finally had to turn it on and quickly hit the play mode button so I could then go in to the menu and turn that back off. Apparently this camera either doesn't have the battery temperature sensor or it is not properly mapped in the stubs files.
Anyways, here is the source and the full .zip (with CHDK folder and .bin for your camera) for my modified version :)
-
CHDKLover has made some edits and posted them to the German trunk (as svn 695.) I built this version and it will take RAW pictures as .CRW but it would not build badpixel.bin to take DNG photos. I talked with reyalp on IRC and he pointed me towards the platform_camera.h file and these two lines:
#define CAM_RAW_ROWPIX 3736 // for new 10 MP http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273 (http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273)
#define CAM_RAW_ROWS 2772 // for new 10 MP
From one of the .CRW files I took with the camera (opened in UFRaw as an addon for GIMP) I found that the size was wrong. I changed those two lines to this:
#define CAM_RAW_ROWPIX 3684 // for new 10 MP http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273 (http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273)
#define CAM_RAW_ROWS 2760 // for new 10 MP
I saved and rebuilt and now badpixel.bin can be created successfully :) (Through the Raw options -> Create badpixel.bin menu options on the camera in record mode.) When I set to record DNG, take some pictures, and try to open them in UFRaw or IrFanView, they look kinda like the fuzzy lines on a TV when it has bad reception and mostly in two colors (like green and purple.) I've attached a screenshot of one of my .DNG files in UFRaw to this post so you can see what I mean. I have also attached the full .zip file (with everything you'd unzip on to your camera, but note that when I unzipped this onto my camera I deleted the German language file so that it would automatically load in to English. If English is your language of choice I suggest you do the same.)
EDIT: I forgot to mention, I also changed the #define CAM_COLORMATRIX1 part of platform_camera.h by copy/pasting over that part of the sx110's platform_camera.h (to see if the different color matrix would fix the DNG files, but it didn't.) So note that the color matrix that was being used and the sx100's color matrix both don't seem to fix the issue.
________________
UPDATE: The plot thickens...When I have taken a .DNG picture on my camera and then go to Main Menu -> Raw parameters ->RAW develop -> (go through the folders to find a .DNG, press Right, go back up to it, press left, select "DNG -> CHDW RAW") it makes a .CRW file and I can open that .CRW file in UFRaw in GIMP. Thus somewhere inside my .DNG file (which is not displaying correctly at all in UFRaw) is my actual picture. Note that reyalp thinks that this is perhaps not actually using RAW develop (but rather just using RAW develop to get to the file browser) but in any case, it seems to show that it is not a matter of my .DNG files not capturing the image, it is something else (perhaps bad metadata?)
-
CHDKLover has made some edits and posted them to the German trunk (as svn 695.) I built this version and it will take RAW pictures as .CRW but it would not build badpixel.bin to take DNG photos. I talked with reyalp on IRC and he pointed me towards the platform_camera.h file and these two lines:
#define CAM_RAW_ROWPIX 3736 // for new 10 MP http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273 (http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273)
#define CAM_RAW_ROWS 2772 // for new 10 MP
From one of the .CRW files I took with the camera (opened in UFRaw as an addon for GIMP) I found that the size was wrong. I changed those two lines to this:
#define CAM_RAW_ROWPIX 3684 // for new 10 MP http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273 (http://chdk.setepontos.com/index.php/topic,2654.msg46273.html#msg46273)
#define CAM_RAW_ROWS 2760 // for new 10 MP
I saved and rebuilt and now badpixel.bin can be created successfully :) (Through the Raw options -> Create badpixel.bin menu options on the camera in record mode.) When I set to record DNG, take some pictures, and try to open them in UFRaw or IrFanView, they look kinda like the fuzzy lines on a TV when it has bad reception and mostly in two colors (like green and purple.) I've attached a screenshot of one of my .DNG files in UFRaw to this post so you can see what I mean. I have also attached the full .zip file (with everything you'd unzip on to your camera, but note that when I unzipped this onto my camera I deleted the German language file so that it would automatically load in to English. If English is your language of choice I suggest you do the same.)
EDIT: I forgot to mention, I also changed the #define CAM_COLORMATRIX1 part of platform_camera.h by copy/pasting over that part of the sx110's platform_camera.h (to see if the different color matrix would fix the DNG files, but it didn't.) So note that the color matrix that was being used and the sx100's color matrix both don't seem to fix the issue.
Your CAM_RAW_ROWPIX & CAM_RAW_ROWS still look wrong.
The raw image buffer size is 0xEC04F0 on this camera = 15467760 bytes or 10311840 pixels.
3684 x 2760 = 10167840 pixels.
The original values 3736 x 2772 = 10356192 pixels which also doesn't match the buffer size.
I'd suggest the RAW image size is the same as the A2000 - 3720 x 2772 = 10311840 pixels.
Try CAM_RAW_ROWPIX 3720
and CAM_RAW_ROWS 2772
Phil.
-
Your CAM_RAW_ROWPIX & CAM_RAW_ROWS still look wrong.
The raw image buffer size is 0xEC04F0 on this camera = 15467760 bytes or 10311840 pixels.
3684 x 2760 = 10167840 pixels.
The original values 3736 x 2772 = 10356192 pixels which also doesn't match the buffer size.
I'd suggest the RAW image size is the same as the A2000 - 3720 x 2772 = 10311840 pixels.
Try CAM_RAW_ROWPIX 3720
and CAM_RAW_ROWS 2772
Phil.
I hereby award you one free internet! :D I followed your suggestion and now the CAM_RAW lines in platform_camera.h look like this:
#define CAM_RAW_ROWPIX 3720 // tweaked at philmoz's suggestion to match the A2000 http://chdk.setepontos.com/index.php?topic=2654.msg69715#msg69715 (http://chdk.setepontos.com/index.php?topic=2654.msg69715#msg69715)
#define CAM_RAW_ROWS 2772 // tweaked at philmoz's suggestion to match the A2000
I saved the changes, built this in CHDK-Shell, loaded it on my camera, created a badpixel.bin, took two DNG photos, and they open up in UFRaw (in GIMP) and look like what I took a picture of! Yay! I think the color matrix might still need tweaking, but it at least seems to successfully take CRW and DNG RAW pictures now!
EDIT: I reverted the color matrix section of the platform_camera.h file to what it was (in the German trunk695 and trunk694) to try and avoid some confusion. I built it, put it on my camera, made a badpixel.bin, took a DNG picture, put the card in my computer, opened up that DNG in UFRaw, and it indeed looks like what I took a picture of, so it seems to be OK.
I have attached my Source folder (which is basically the German trunk695 with some tweaks to platform_camera.h) and the full .zip with everything you'd want to put on your camera to run this (and remember, if you want it to just be in English, delete the German file from the LANG folder.)
-
(Mods, if there are no double posting rules on this forum, please forgive me! Rest assured that my intentions are good :D )
I just downloaded waterwingz's CHDK-PT (http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera) tool to see if I could get it to make an a1000 100a version off of the source code I just posted for a 100b version (which is the modified German trunk695.) I am not able to get this to work :(
First off, I used the Dumper Canon Basic Script (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper) to get the PRIMARY.BIN files for both the 100a and 100b (since I have one of each.) I am confused to find that they are both 4096 KB and they both show a date modified of 12/31/1999 11:00 PM. When I start running them through CHDK-PT and comparing the output, I can't find much at all that is different. About the only noticeable difference I've encountered so far is in the address.txt file for the each version.
100a:
line 78 " LDR R0, =0xFFEEAFD0 \n"
100b:
line 77 " LDR R0, =0xFFEEAE90 \n"
When I try to run Convert -> Address List nothing seems to happen - it thinks for a little bit and shows "analyzing... 0 lines" then finishes and there is nothing in the text box area and when I hit Save it just saves a blank file. I don't know what this means.
On a random sidenote, perhaps info from these address.txt files could help fix video recording in CHDK? So far as I know, none of the video recording features of CHDK are available for the a1000 so far (in this most recent build or any other build for that matter.) Maybe the info here could help with that, I'm not sure.
Anyways, here are links to both PRIMARY.BIN files (renamed so you can tell them apart :P) - Note that I would have just attached these to this post but they are too big =/
http://www.mediafire.com/?5sxdemtamb682 (http://www.mediafire.com/?5sxdemtamb682)
-
(Mods, if there are no double posting rules on this forum, please forgive me! Rest assured that my intentions are good :D )
I just downloaded waterwingz's CHDK-PT (http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera) tool to see if I could get it to make an a1000 100a version off of the source code I just posted for a 100b version (which is the modified German trunk695.) I am not able to get this to work :(
First off, I used the Dumper Canon Basic Script (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper) to get the PRIMARY.BIN files for both the 100a and 100b (since I have one of each.) I am confused to find that they are both 4096 KB and they both show a date modified of 12/31/1999 11:00 PM. When I start running them through CHDK-PT and comparing the output, I can't find much at all that is different. About the only noticeable difference I've encountered so far is in the address.txt file for the each version.
100a:
line 78 " LDR R0, =0xFFEEAFD0 \n"
100b:
line 77 " LDR R0, =0xFFEEAE90 \n"
When I try to run Convert -> Address List nothing seems to happen - it thinks for a little bit and shows "analyzing... 0 lines" then finishes and there is nothing in the text box area and when I hit Save it just saves a blank file. I don't know what this means.
On a random sidenote, perhaps info from these address.txt files could help fix video recording in CHDK? So far as I know, none of the video recording features of CHDK are available for the a1000 so far (in this most recent build or any other build for that matter.) Maybe the info here could help with that, I'm not sure.
Anyways, here are links to both PRIMARY.BIN files (renamed so you can tell them apart :P) - Note that I would have just attached these to this post but they are too big =/
http://www.mediafire.com/?5sxdemtamb682 (http://www.mediafire.com/?5sxdemtamb682)
The dumper script doesn't set the date correctly on the PRIMARY.BIN file which is why they are both the same date, they should both be the same size.
I use my new address finder (http://chdk.setepontos.com/index.php?topic=6560.0 (http://chdk.setepontos.com/index.php?topic=6560.0)) on both versions and the only differences I can see are for levent_table and FlashParamsTable. The changes only seem to be in the data segment so probably just translated text corrections.
The changes values for stubs_min.S for 1.00a are:
levent_table = 0xffeab5b8
FlashParamsTable = 0xffeca0bc
To use CHDK-PT you need to supply it with the addresses and lengths of the functions you want to port in the original version and then it tries to extract the equivalent stuff from the new version. Since the code segment seems to be the same in these two versions you probably don't need this.
Phil.
-
The dumper script doesn't set the date correctly on the PRIMARY.BIN file which is why they are both the same date, they should both be the same size.
I use my new address finder (http://chdk.setepontos.com/index.php?topic=6560.0 (http://chdk.setepontos.com/index.php?topic=6560.0)) on both versions and the only differences I can see are for levent_table and FlashParamsTable. The changes only seem to be in the data segment so probably just translated text corrections.
The changes values for stubs_min.S for 1.00a are:
levent_table = 0xffeab5b8
FlashParamsTable = 0xffeca0bc
To use CHDK-PT you need to supply it with the addresses and lengths of the functions you want to port in the original version and then it tries to extract the equivalent stuff from the new version. Since the code segment seems to be the same in these two versions you probably don't need this.
Phil.
Thanks, that is reassuring :) I changed my 100a subs folder's stubs_min.S file to use the values you gave for levent_table and FlashParamsTable. I am still getting the same error I was getting when I try to compile it in CHDK-Shell. Here is that error:
========== C:\CHDK\DE\TRUNK\TRUNK695\BIN\LOGS\ERR-A1000-100A.TXT ==========
Time to generate stubs 7.25 seconds
../platform/a1000/libplatform.a(wrappers.o): In function `remount_filesystem':
wrappers.c:(.text+0x120): undefined reference to `_Unmount_FileSystem'
wrappers.c:(.text+0x124): undefined reference to `_Mount_FileSystem'
../platform/a1000/libplatform.a(wrappers.o): In function `rewinddir':
wrappers.c:(.text+0x46c): undefined reference to `_rewinddir'
collect2: ld returned 1 exit status
C:\CHDK\gcc451\bin\gmake.exe[1]: *** [main.elf] Error 1
gmake: *** [all-recursive] Error 1
Just to make sure I didn't break something, I compiled the 100b version again and it seemed to compile just fine. I have attached the full log for my attempt to compile 100a to this post in case it might have some useful info. For comparison, I also attached the log from my successful 100b attempt.
-
In 100b stubs_entry_2.s,
NSTUB(Unmount_FileSystem, 0xFFC00940)
NSTUB(Mount_FileSystem, 0xFFC00940)
NHSTUB(UnsetZoomForMovie, 0xFFC00940)
NSTUB(rewinddir, 0xFFC00940)
is obviously incorrect and NSTUB should be NHSTUB.
I can only assume CHDK does not use those functions.
You need to set to a NULLSUB address.
-
FFC00940 is a nullsub addres ;)
-
FFC00940 is a nullsub addres ;)
Fair enough, but in the CHDK source that I used there was no mention of that ... unusually.
-
In 100b stubs_entry_2.s,
NSTUB(Unmount_FileSystem, 0xFFC00940)
NSTUB(Mount_FileSystem, 0xFFC00940)
NHSTUB(UnsetZoomForMovie, 0xFFC00940)
NSTUB(rewinddir, 0xFFC00940)
is obviously incorrect and NSTUB should be NHSTUB.
I can only assume CHDK does not use those functions.
You need to set to a NULLSUB address.
Ah thanks, I see what is going on now. I added in the items you mentioned to the 100a stubs_entry_2.S (and changed them to NHSTUB instead of NSTUB), tried to compile, and got this error:
========== C:\CHDK\DE\TRUNK\TRUNK695\BIN\LOGS\ERR-A1000-100A.TXT ==========
Time to generate stubs 7.21 seconds
../platform/a1000/sub/100a/libplatformsub.a(stubs_entry_2.o): In function `_qsort':
(.text+0xb0): undefined reference to `NULL_STUB'
collect2: ld returned 1 exit status
C:\CHDK\gcc451\bin\gmake.exe[1]: *** [main.elf] Error 1
gmake: *** [all-recursive] Error 1
The line in stubs_entry_2.S for qsort is basically the same for both the 100a and the 100b.
For the 100a:
NHSTUB(qsort, 0xffe2bbec)
For the 100b:
NHSTUB(qsort, 0xffe2bbec) //SDM
I don't see anything related to qsort and NULL_STUB - only the three items I just added (Unmount_FileSystem, Mount_FileSystem, and rewinddir) are NULL_STUB in stubs_entry_2.S for the 100a. I gotta get going now but I'll poke at this later. If any of you have an idea on what the problem might be please post :)
EDIT: I saw reyalp's post about FFC00940 being a null address so I changed "NULL_STUB" for "FFC00940" in my 100a stubs_entry_2.S file and now I get this error:
========== C:\CHDK\DE\TRUNK\TRUNK695\BIN\LOGS\ERR-A1000-100A.TXT ==========
Time to generate stubs 7.21 seconds
../platform/a1000/sub/100a/libplatformsub.a(stubs_entry_2.o): In function `_qsort':
(.text+0xb0): undefined reference to `FFC00940'
collect2: ld returned 1 exit status
C:\CHDK\gcc451\bin\gmake.exe[1]: *** [main.elf] Error 1
gmake: *** [all-recursive] Error 1
This leads me to think that it's one of the 3 NHSTUB entries that I just added for the 100a that is causing this to error out (even though it talks about '_qsort', presumably one of these 3 is called by qsort.) In the past (on other small programming-ish tweaking projects) I've missed some little thing when copy/pasting (like a tab or a space) and that breaks the world. I'm gonna fiddle with things a bit and see if perhaps the values are right I just copy/pasted them wrong.
ANOTHER EDIT: To see if I could isolate if it's just 1 of the 3 new lines I added that is breaking, I changed NHSTUB(rewinddir, FFC00940) to NHSTUB(rewinddir, NULL_STUB) and then I get this error on compiling:
========== C:\CHDK\DE\TRUNK\TRUNK695\BIN\LOGS\ERR-A1000-100A.TXT ==========
Time to generate stubs 7.21 seconds
../platform/a1000/sub/100a/libplatformsub.a(stubs_entry_2.o): In function `_qsort':
(.text+0xb0): undefined reference to `FFC00940'
../platform/a1000/sub/100a/libplatformsub.a(stubs_entry_2.o): In function `_qsort':
(.text+0xc4): undefined reference to `NULL_STUB'
collect2: ld returned 1 exit status
C:\CHDK\gcc451\bin\gmake.exe[1]: *** [main.elf] Error 1
gmake: *** [all-recursive] Error 1
So nuts, looks like either way it doesn't know what this null stub thing is :P
EDIT ONCE MORE, WITH FEELING: Derp! I just realized that I forgot the "0x" at the begging of "FFC00940" and also that the 100b version of stubs_entry_2.S that I was looking at had this line near the top "#define NULL_STUB 0xFFC00940". After adding that define line to my 100a file and changing the 3 references to NULL_STUB, it compiled!
-
I feel like I've edited that last post enough. Now I am at a loss for what to do next. I finally got the 100a CHDK version to compile so I loaded it up on a card, stuck it in my 100a camera, and it won't turn on. Just out of curiosity, I then put it in my 100b camera and it does turn on. (I took a picture and ran it through ACID.jar just to be sure that was indeed my 100b camera and indeed it is.) So apparently I've missed something important, but I don't know what. I'm attaching my whole a1000 folder to this post in a .zip - if you have any ideas, let me know :) I've also attached the full compiled '100a' (which is apparently really a 100b) version .zip folder to this, too, just as a 'for what it is worth'. (Note, I had the PRIMARY.BIN file for the 100a in the sub/100a folder but I took it out before I zipped this since the file would be to big to post on the forums otherwise. On a sidenote, am I not supposed to have that PRIMARY.BIN file in there? It looks like the trunk sub/100b folder just has an empty file called PRIMARY.BIN at 0KB.)
-
I feel like I've edited that last post enough. Now I am at a loss for what to do next. I finally got the 100a CHDK version to compile so I loaded it up on a card, stuck it in my 100a camera, and it won't turn on. Just out of curiosity, I then put it in my 100b camera and it does turn on.
It looks like just using the tasks .C files from the 100b for the 100a is not going to work. Your earlier comment about :
100a:
line 78 " LDR R0, =0xFFEEAFD0 \n"
100b:
line 77 " LDR R0, =0xFFEEAE90 \n"
should have been a clue. The files really need to be translated - CHDK-PT can help with that but it still a couple of hours work for someone who knows what they are doing.
On a sidenote, am I not supposed to have that PRIMARY.BIN file in there? It looks like the trunk sub/100b folder just has an empty file called PRIMARY.BIN at 0KB.)
This is normal - the 0KB version of the file prevents the signature finder from running each time a compile is done. The output of that step - the stubs_entry.S file should never change for a given primary.bin file and doing this results in a considerable time savings when building the entire trunk of all cameras. It also cuts the size of the source download as the 4M & 8M promary.bin files are not distributed.
-
It looks like just using the tasks .C files from the 100b for the 100a is not going to work. ... The files really need to be translated - CHDK-PT can help with that but it still a couple of hours work for someone who knows what they are doing.
Well nuts, figures it couldn't be quite as easy as I might have hoped ;) I really am not sure what all is different between the two firmware versions so I think I'm just out of my league with this whole conversion thing.
This is normal - the 0KB version of the file prevents the signature finder from running each time a compile is done. The output of that step - the stubs_entry.S file should never change for a given primary.bin file and doing this results in a considerable time savings when building the entire trunk of all cameras. It also cuts the size of the source download as the 4M & 8M promary.bin files are not distributed.
Ah OK, that makes sense and it's good to know. It also explains why compiling my '100a version' (which is apparently really a 100b version) took longer than I thought it normally did to complete.
-
I feel like I've edited that last post enough. Now I am at a loss for what to do next.
@Qanthelas : here are two things you can try.
100a:
line 78 " LDR R0, =0xFFEEAFD0 \n"
100b:
line 77 " LDR R0, =0xFFEEAE90 \n"
These specify different start addresses for the data space. It possible the 1.00b boot.c code will be alright for the 1.00a if you simply change the value on line 33 from 0xFFEEAE90 to 0xFFEEAFD0.
I went through the rest of the boot.c file and flagged anything that was different than what's in the 1.00a primary.bin file (other than the CHDK required mods). File attached - there were 10 things different between the 1.00b and 1.00a - marked //** different than 1.00b in the attached file.
See if that will compile and run ?
-
EDIT: Danke CHDKLover, this 100a version of CHDK is now in the German trunk - Changeset 697 Trac notes here (http://tools.assembla.com/chdkde/changeset/697). (I'm a somebody now, I'm thanked on a changeset note :D ;)) On an amusing sidenote, since my timezone is several hours behind Germany, when I just went and built the 100a version with CHDK-Shell from the new German trunk (697) it gave me a bunch of errors in errors.txt about "[some file] has modification time in the future (1309911526 > 1309902833)". We are traveling through time! :P Still, the 100a version compiles and I just tested it out in my camera and it seems to work :)
...
These specify different start addresses for the data space. It possible the 1.00b boot.c code will be alright for the 1.00a if you simply change the value on line 33 from 0xFFEEAE90 to 0xFFEEAFD0.
I went through the rest of the boot.c file and flagged anything that was different than what's in the 1.00a primary.bin file (other than the CHDK required mods). File attached - there were 10 things different between the 1.00b and 1.00a - marked //** different than 1.00b in the attached file.
See if that will compile and run ?
It works!!! Waterwingz, I hereby award you one free internet! I copied and replaced over the boot.c file in my sub/100a directory with the one you linked to your post, compiled it in CHDK-Shell, loaded the resulting files on to my SD card, plugged it in to my 100a, and for the first time ever the 100a turned on! (Just out of curiosity, I then tried it on my 100b and it did not turn on.)
I did a little testing and it looks like things like Histogram and Zebra work (although I was getting a bit of lag on the screen or sometimes part of the screen would still show the orange lines of something like Edge even after I released the trigged but then once I did it again the orange lines would be repainted for the right spot. On a related note, the menu text for both this 100a version and my 100b version will sometimes 'stick' so you have to toggle out of "ALT", hit the menu button, then hit the menu button again - basically make the camera 'redraw' the screen.) I also tested out RAW and it seemed to work but I'm guessing the color matrix will need to be fixed (and, for that matter, probably needs some tweaking on the 100b.) I honestly don't know that much about all that so I'll leave that to someone else :P Anyways, I was able to create badpixel.bin, turn on DNG recording, and take a couple DNG pictures and then when I put the SD card back in my computer I was able to open those DNG files with UFRaw and they did indeed look like what I took a picture of. I also tested a .jpg with ACID.jar to make sure this was indeed my 100a camera and indeed it was :D
On a sidenote, I noticed that CHDK-DE has a new release out (696) and it looks like it includes the tweaks to the a1000 100b platform_camera.h file (to fix the RAW width and height.) I'm going to see if I can make a 696 version of 100a (currently I have a 696 version) and I'll edit this post with what I find out.
EDIT: Well I'll be...it works! In the CHDK/DE/trunk696/platform/a1000/sub folder I copied 100b and renamed the copy 100a. I then copied and replaced over the following files from my newly working trunk695's 100a folder:
stubs_entry.S
stubs_auto.S
boot.c (Note that this is the one from waterwingz's post)
stubs_entry_2.S
stubs_min.S
capt_seq.c
lib.c
PRIMARY.BIN
Note, I don't think all of these would have been actually required but I just went and copied over anything with a "Date modified" from the last few days (which is while I've been working on the 100a port.) I also had to copy Makefile from CHDK/DE/trunk/trunk695 and paste it to /trunk696 (in order to get CHDK-Shell to notice that I had a 100a sub folder in there.) I then fired up CHDK-Shell and compiled it. As with the 695 version, when it finishes the "100 A" area by the checkbox by A1000 goes yellow (instead of green) and an error pops up that reads:
========== C:\CHDK\DE\TRUNK\TRUNK696\BIN\LOGS\ERR-A1000-100A.TXT ==========
Time to generate stubs 7.21 seconds
Not sure why this is, but it does compile the .zip files and they seem to work :) I loaded up my SD card with the contents of a1000-100a-1.1.0-r696-full.zip (then deleted the CHDK/LANG/german.lng file so that it'd be in English), put it in my 100a camera, and it started up :) I tested Histogram and Zebra and they seemed to work fine. I then created badpixel.bin (through the Raw options menu), turned on DNG recording, and took a couple DNG pictures. I then put my SD card back in my computer and those DNG files open in UFRaw and do indeed look like what I took a picture of. I also ran one of the .jpg files through ACID.jar to make sure that was my 100a camera and indeed it was :)
So, now we seem to have a fairly functional 100b and 100a build for the a1000IS :D This is the point that I was trying to get to (well, and then an SDM build for the 100a) so as far as I'm concerned this is a good release, but I am willing to help people test and whatnot to fix a few little remaining issues (for example, I think the OSD counters for pictures remaining and whatnot are not accurate - the numbers never seem to decrease.)
I have attached my CHDK-DE trunk696 a1000 folder (in a .zip and without PRIMARY.BIN) to this post and I've also attached the compiled a1000-100a-1.1.0-r696-full.zip.
-
I realized after I had put the two .zip files in my last post that you also need a modified Makefile (for the trunk696 folder) in order to get CHDK-Shell to recognize the 100a stuff. I've attached my modified Makefile to this post. (Note that makefile.inc should probably also be tweaked, but I didn't find any mention of the a1000 in the CHDK-DE 695 makefile.inc - perhaps this is why I get an 'error log' that isn't really an error log when I compile the 100a?)
Out of curiousity, how hard is it to go from the German trunk to the English trunk? I would kinda like to see the a1000 become part of the English trunk (with both the 100a and 100b sub folders.) I'm guessing this would require tweaking a few files (like kbd.c, which was recently cleaned up in the German version by the way.) If someone could get around to that I'd appreciate it :)
Also, I want to thank some people for their help :) Thanks to CHDKLover for watching this forum thread and updating the German trunk with the changes. Thanks to reyalp for being a huge help on IRC. Thanks to waterwingz for making some tweaks and coming up with ideas here on the forums and on IRC. Thanks to philmoz for some key info to get this up and working. Thanks to Microfunguy for help getting the German autobuild alpha version of the 100b to actually boot up on my camera (and, hopefully, some help in getting a 100a SDM version! :D) I don't think they are around much to read this any more, but I also want to say thanks to diablo for starting this project and bolalex and the rest of the Russia team who worked on this for patching some things. I am not sure who all helped CHDKLover with the German version, but thanks to all of them, too!
I also want to say thanks to anybody reading this and everyone who has posted over these last 20 pages - it has taken a while (mainly due to some long gaps in development) but I think we have a working version of CHDK for the A1000IS - both 100a and 100b! Now with luck we can get some more bug squashing and feature implementing so this can finally be a 'full' release and not just a 'beta' release :D
-
Out of curiousity, how hard is it to go from the German trunk to the English trunk? I would kinda like to see the a1000 become part of the English trunk (with bothTthe 100a and 100b sub folders.) I'm guessing this would require tweaking a few files (like kbd.c, which was recently cleaned up in the German version by the way.) If someone could get around to that I'd appreciate it :)
Takes a few tweaks. Also your source zip files is missing the loader files for the A1000.
-
Takes a few tweaks. Also your source zip files is missing the loader files for the A1000.
I made this using the German trunk and it already contains the loader/a1000 folder. (The one a few posts up is from the platform folder, by the way.) I have attached it as a .zip to this post just in case, but yeah, this is all part of the German trunk now :D
-
Over 175 e-mails and 45 tests later, Microfunguy and I finally seem to have figured out why SDM for 100a was crashing on turning the camera back on after taking a DNG. Apparently it has to do with SDM trying to open a file that the camera itself hasn't closed all the way or something like that. In any case, I have attached a working 100a SDM to this post.
-
Taking a DNG, was a red herring.
Any menu change that caused a CFG file to be created caused a crash on rebooting if the default script file could not be found on the previous boot.
That resulted in the current script name in the CFG file being set to "" (null).
Maybe that speeded-up the boot sequence loading such that a file handle used by the Canon firmware had not been closed but was inadvertantly being allocated to the cfg or other file.
This is with SDM, I don't know if CHDK boot has the same problem, it is a timing issue.
For SDM, philmoz's boot fix simply and easily cures the problem.
In the case of CHDK, if necessary, you add the following to platform_camera.h :-
#define CAM_STARTUP_CRASH_FILE_OPEN_FIX 1
Maybe this also applies to the A3000.
For 100a and 100b, the firmware addresses for 'Open' and 'open' are correct.
David
-
Hello,
sorry for a dumb question. I have an A1000 camera with 1.00b firmware. I tried loading the r695 version of CHDK, I formatted the SD card and extracted the archive onto it, turn camera on in the playback mode but the Firm Update menu option is missing. I then tried loading other versions of the firmware, went through all menus but the option is not there. Thanks for your help.
-
I tried loading the r695 version of CHDK, I formatted the SD card and extracted the archive onto it, turn camera on in the playback mode but the Firm Update menu option is missing.
The "Firm. Update" menu item is only visible when there's a file "PS.FI2" stored in the card's root folder.
If the CHDK download you want to test doesn't include this ps.fi2 file (e.g. diskboot.bin only),
you can start CHDK with a CHDK-bootable, locked SD card
--> http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
I suggest to load the latest CHDKDE complete package
(rev. 745, from here: http://forum.chdk-treff.de/download.php - select the "Komplett" option).
Expand all files to your card's root folder, start in playback mode...
To change the CHDK language from german to english, just delete the file \CHDK\LANG\german.lng on your SD card.
Note: using a Mac, read http://chdk.wikia.com/wiki/FAQ/Mac (http://chdk.wikia.com/wiki/FAQ/Mac) and especially http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F (http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F)