EDIT: Danke CHDKLover, this 100a version of CHDK is now in the German trunk - Changeset 697 Trac notes here. (I'm a somebody now, I'm thanked on a changeset note
) 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!
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
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
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
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.
