A1000IS porting...

bolalex

Hi All. Reload please
http://chdk.clan.su/_fr/3/a1000-100b-099.zip
I change agane code for zebra function

esom

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?

esom

Hi All,
did you try test script? I experienced some camera crashes 🙁

kulen

I see that menu still stays on screen after exiting from it.

bekisha

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 😀

PovertyLabs

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)

kenxho

Error 404: File Not Found
Page (or file) you requested has been moved or deleted

Qanthelas

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) 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: https://chdk.setepontos.com/d/2654/126

kulen's test results for the latest diablo build (if I understand things correctly): https://chdk.setepontos.com/d/2654/235

the latest version in this thread, posted by bolalex: https://chdk.setepontos.com/d/2654/264

The original 100a version: https://chdk.setepontos.com/d/2654/44

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

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 (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

__________________________________

If your A1000 has the 100b firmware (you can check using "ACID") 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

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

waterwingz

Qanthelas
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.

Qanthelas

waterwingz
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 😁

waterwingz
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.)

Qanthelas

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 (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.)

From Microfunguy Source CHDK_A1000_100b.zip

29.75KB

From Microfunguy A1000_100b_3.zip

216.44KB

Qanthelas

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 😀

German-autobuild-and-Microfunguy-tweaked-by-Qanthelas-SOURCE-a1000-100b-Modified-platform_camera.zip

38KB

a1000-100b-1.1.0-r694-full-German-autobuild-Microfunguy-edits-tweaked-by-Qanthelas.zip

392.38KB

Qanthelas

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 https://chdk.setepontos.com/d/2654/200
#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 https://chdk.setepontos.com/d/2654/200
#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?)

CAM_RAW_ROW-tweaks-a1000-100b-1.1.0-r695-full.zip

392.19KB

philmoz

Qanthelas
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 https://chdk.setepontos.com/d/2654/200
#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 https://chdk.setepontos.com/d/2654/200
#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.

Qanthelas

philmoz
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! 😁 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 https://chdk.setepontos.com/d/2654/278
#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.)

SOURCE-German-trunk695-tweaked-CAM_RAW_ROW-a1000.zip

38.3KB

Tweaked-CAM_RAW_ROW-a1000-100b-1.1.0-r695-full.zip

392.42KB

Qanthelas

(Mods, if there are no double posting rules on this forum, please forgive me! Rest assured that my intentions are good 😁 )

I just downloaded waterwingz's CHDK-PT 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 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 😛) - Note that I would have just attached these to this post but they are too big =/

http://www.mediafire.com/?5sxdemtamb682

philmoz

Qanthelas
(Mods, if there are no double posting rules on this forum, please forgive me! Rest assured that my intentions are good 😁 )

I just downloaded waterwingz's CHDK-PT 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 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 😛) - Note that I would have just attached these to this post but they are too big =/

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 (https://chdk.setepontos.com/d/6560) 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.

Qanthelas

philmoz
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 (https://chdk.setepontos.com/d/6560) 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.

log-a1000-100a.txt

5.63KB

log-a1000-100b.txt

6.52KB

Microfunguy

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.

reyalp

FFC00940 is a nullsub addres 😉

« Previous Page Next Page »