CHDK Forum
Using CHDK => CHDK Releases => Topic started by: RaduP on 07 / October / 2009, 19:54:10
-
Almost everything works now, please download the attachment from this post then see: http://chdk.setepontos.com/index.php/topic,4335.msg42314.html#msg42314 (http://chdk.setepontos.com/index.php/topic,4335.msg42314.html#msg42314)
-
Update
Please download it again, I replaced the attachment with the new version.
Here are the changes:
1. No more crashes when switching to video mode, or from playback to record modes.
2. Now you can set the ND filter override.
3. Focus distance override also works.
4. Histogram in playmode too.
-
Update
Please download the file again.
Changes:
You can now zoom in movies. However, the other movie parameters do not work.
Fixed some script bugs, such as the scripting console not working.
Now you can execute the badpixel script. You must move it from the lua directory to the script directory though, for now you can't enter subdirectories.
Usb remote works now, as tested with the remote script.
-
Thanks very much! Starting to look better and better. Appreciate all the effort. I think the SD980 has lots of potential to be unlocked.
-
Hi, I tried this on my camera I've got few days ago. When I start the Firmware Update it says: " Update firmware version? 1.0.1.0 -> 1.0.0.0". After starting the update with "Ok" the screen stays black for ever and nothing happens. Only removing the battery helps.
So I guess I have a firmware version not compatible with this CHDK release? Or could this be another problem too?
-
Use vers.req to find out what firmware version your camera has. See http://chdk.wikia.com/wiki/FAQ#Q._How_can_I_get_the_original_firmware_version_number_of_my_camera.3F (http://chdk.wikia.com/wiki/FAQ#Q._How_can_I_get_the_original_firmware_version_number_of_my_camera.3F)
edit:
Radups version is made for 1.00C
edit x2:
You can probably also get the firmware version number (but not letter AFAIK) from the exif of an image taken with the camera.
-
You can probably also get the firmware version number (but not letter AFAIK) from the exif of an image taken with the camera.
>exiftool IMG_NNNN.jpg -MakerNotes:FirmwareRevision
Firmware Revision : 1.01 rev 2.00
this means 1.01B (second number is 1.00=A, 2.00=B, 3.00=C etc.).
-
The ver.req method seems not to work with the SD980 (actually I have a IXUS 200 IS but it's the same). I also tried vers.req and different combinations of buttons, but no result.
Anyway, exiftool says "1.01 rev 3.00" so I have 1.01 C which is different to 1.00 C.
How can I help to get it running on my firmware version too? First step would be to dump my version I guess. Are there any chances to get a dump without blinking?
-
Yes, you can probably make a modified udumper based on the 100C dump.
-
If you have programming skills and some very little electronics skills, you should be able to get the firmware. Let me know and I will give you the instructions.
-
I have a new, beta version available. Now everything should work fine, except:
Flash override doesn't work.
The feature where you can make a card bootable, and swap partitions does not work though.
The file time of the raw/dng files will sometimes be wrong.
All those things are relatively minor and should not be a big deal.
Now the bootdisk method is supported as well, so I am attaching a bootdisk too.
Due to the filesize limits of the attachments on the forum, you will have to download the file in the first post, then download the ps.fi2 and diskboot.bin from this post, and overwrite the old ones.
-
Here is the ps.fi2
-
Good work.
...updated the wikia news.
-
I'm a newbie - just purchased the sd980 to try some aerial photography (so I want to use the usb remote trigger). Tried ver.req and couldn't get the firmware info so I then used card tricks to download RaduP's latest. Slid the lock on the SD card, put it into the camera, and....nothing. Thoughts?
The ver.req method seems not to work with the SD980 (actually I have a IXUS 200 IS but it's the same). I also tried vers.req and different combinations of buttons, but no result.
Anyway, exiftool says "1.01 rev 3.00" so I have 1.01 C which is different to 1.00 C.
How can I help to get it running on my firmware version too? First step would be to dump my version I guess. Are there any chances to get a dump without blinking?
-
Hello & welcome, Dabossajk !
Slid the lock on the SD card, put it into the camera, and....nothing.
To use the autoboot loading method, the SD card must be CHDK-bootable & the diskboot.bin file must be placed on the card's root.
To load CHDK manually, just copy the PS.Fi2 file from radup's post to the card's root, power on the camera in playback mode, enter the Canon menu & select "Firmware Update..."
Note: the "Firmware Update" menu item is not visible in record mode or with the lens expanded.
Read more here: http://chdk.wikia.com/wiki/FAQ (http://chdk.wikia.com/wiki/FAQ)
IF you're using a Mac, read also the Mac FAQ: http://chdk.wikia.com/wiki/FAQ/Mac (http://chdk.wikia.com/wiki/FAQ/Mac)
-
Folks,
I'm up and running with the CHDK on the SD980 thanks to fe50 and RaduP - and now I'm working on getting the USB remote trigger to work. RaduP have you (or has anyone else) tried that on the 980? I enabled remote triggering and then selected the simple remote script. Hooked up 3 AAAs in series to pins 1 & 4 of the mini usb, switched the pack on....and (drumroll) the camera focused but didn't fire.
Thanks!
-
Hooked up 3 AAAs in series to pins 1 & 4 of the mini usb
Strictly, it is pins 1 and 5.
Anyway, it is the outside pins.
It is possible that you have them connected the wrong way around.
the camera focused but didn't fire.
Use a USB cable plugged into your PC as the source for +5V.
That will show if your switch is faulty.
David
-
I tried it with the simple basic script, remote or something like that, and it worked. Can you try it too?
-
How can I help to make chdk compatible to my canon with firmware 1.01C?
-
Well, one thing you could do, if you have some electronic skills, is to try to get the firmware out of the camera..
-
This could be too difficult for me.
Is there no way to get the firmware from Canon or elsewhere?
What about a downgrade?
-
This could be too difficult for me.
Is there no way to get the firmware from Canon or elsewhere?
What about a downgrade?
No, there's no fw update from Canon for the SD980; downgrading is not possible.
The udumper could be modified for the SD980 to dump the fw out of your camera...
-
I doubt it would be easy to modify the udumper, because the SDwrite function doesn't seem to work like before, even when used after CHDK has started. I guess someone more experienced than me must take a look at it.
-
Any news on CHDK for SD980IS? I get the black screen which requires the battery be removed. I am trying to learn, if there is something I can do to help please let me know.
-
Hi
What firmware version do you have?
-
Hi.
Just tested the CHDK on my brand new Ixus200IS. Scripting works perfectly, thanks for that. But how can I disable raw image writing? I don't wont them(because non of the mentioned tools in FAQs can read them). There is no other menu except Script menu available. Is that right or is my 'back' menu item not working?
greets from Austria.
-
On most cameras, the func/set button takes you directly to the script menu (and back doesn't work if you get to it that way). The menu button should take you to the full CHDK menu.
-
No other menu except for the script menu? How do you get to the main menu?
-
Hi, first of all thanks for making this posible on SD980.
Does this phone support automatic booting from SD cards bigger than 4GB? :xmas
-
Hi
What firmware version do you have?
I tried to look at the data in adobe bridge but it did not state a version. However I believe when I went to firmware it stated 1.0.1.0 to 1.0.0.0
I will confirm that tonight.
-
Hi, first of all thanks for making this posible on SD980.
Does this phone support automatic booting from SD cards bigger than 4GB? :xmas
I guess you mean camera, not phone :)
Anyway, it does, but it is more tricky: http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
-
I have tried using the various cardtricks udumpers to no avail. perhaps someone can point me in the right direction or has found a way to dump the new firmware!
When I use the files provided or any of the cardtricks udumpers the camera simply wont start up, it goes to a black screen. I take that back.. Using DryOS it does start up, and I weight a minute or two and then remove the card. the empty.dum file is not changed from the one which was placed on the card by cardtricks.
I would really like to get this going, I am a bit limited on knowledge when it comes to hacking my camera. I wish I was more help.
Hopefully I am not missing the obvious... I unpacked your 980.zip file and updated the files with the bootdisk.bin and the new fl2 file. I have tried manual load and automatic load and both ways gives me a blackscreen.
-
Thanks reyalp.
Now the Cam works the way I need.
PERFECT WORK!
Greets
-
When I use the files provided or any of the cardtricks udumpers the camera simply wont start up, it goes to a black screen. I take that back.. Using DryOS it does start up, and I weight a minute or two and then remove the card. the empty.dum file is not changed from the one which was placed on the card by cardtricks.
I would really like to get this going, I am a bit limited on knowledge when it comes to hacking my camera. I wish I was more help.
Hopefully I am not missing the obvious... I unpacked your 980.zip file and updated the files with the bootdisk.bin and the new fl2 file. I have tried manual load and automatic load and both ways gives me a blackscreen.
Unfortunately, the stock udmper won't work on this camera. The only method that works (for now) is the LED blinking one..
-
Hi, first of all thanks for making this posible on SD980.
Does this phone support automatic booting from SD cards bigger than 4GB? :xmas
I guess you mean camera, not phone :)
Anyway, it does, but it is more tricky: http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
oups, i was looking at a phone on the next windows when I typed this. Sorry, yes - i meant camera :-D
-
Makes me sad that I cant try out all the cool features. Hopefully in the future.
-
Can't seem to find the list of chdk features reported to be working on this camera.
Is intervalometer working? ???
-
Can't seem to find the list of chdk features reported to be working on this camera.
Is intervalometer working? ???
An intervalometer function is possible on all CHDK-driven cameras, e.g. with a little script...
Try Minimalistic_Intervalometer (http://[url=http://chdk.wikia.com/wiki/LUA#Minimalistic_Intervalometer) or yet_another_accurate_intervalometer (http://chdk.wikia.com/wiki/LUA#yet_another_accurate_intervalometer)
(both are Lua scripts, use .lua as filename extension) - or have a look to the uBasic scripts on the wikia: http://chdk.wikia.com/wiki/UBASIC/Scripts (http://chdk.wikia.com/wiki/UBASIC/Scripts)
-
Can't seem to find the list of chdk features reported to be working on this camera.
Is intervalometer working? ???
An intervalometer function is possible on all CHDK-driven cameras, e.g. with a little script...
Try Minimalistic_Intervalometer (http://[url=http://chdk.wikia.com/wiki/LUA#Minimalistic_Intervalometer) or yet_another_accurate_intervalometer (http://chdk.wikia.com/wiki/LUA#yet_another_accurate_intervalometer)
(both are Lua scripts, use .lua as filename extension) - or have a look to the uBasic scripts on the wikia: http://chdk.wikia.com/wiki/UBASIC/Scripts (http://chdk.wikia.com/wiki/UBASIC/Scripts)
Cool, thanks for the detailed tips fe50.
-
So far this looks like the best match if someone is looking for the following features all in one:
- CHDK
- 24mm wide angle
- 720p @30FPS HD video
- pocketable
I wonder why it's not discussed much among the Aerial Photography people...
I'm hopefully gettin one for the holidays.
-
22mm wide angle in RAW.
But yes, most people totally ignore this camera, and I have no idea why. For good light, it is the best compact camera of it's size.
-
22mm wide angle in RAW.
But yes, most people totally ignore this camera, and I have no idea why. For good light, it is the best compact camera of it's size.
is the jpg cropped? i thought the dimentions of the processed image was always identical to RAW source.
-
Yes it cropped for the lens correction, then resized to 12mp.
-
I also own a new Ixus 200IS which is the same as SD980 and my firmware is 1.0.1 C. How can I help to make chdk compatible to this firmware version?
-
The first step is to get the firmware out of the camera. For that you will need some hardware, and you will have to do some soldering. Are you good with that?
-
Mine is still in order stage (processing). Ironically it's one of the rare times, when people wish that the goods they buy would come with an old firmware.
Ironically, i'm getting a Weller WD1000M Soldering station as my other holiday gift (something I wished for, since last holidays) :lol
What else do we need to help the gurus people to get hold of the latest firmware?
-
Two questions for SD980 (Ixus 200IS) owners:
Is there an HD output while recording the video
Is there a timer option for Video mode which allows you to record a frame every 1 or 2 secods?
-
You will need a phototransistor, a 10K ohm resistor, and a COM interface with a COM cable. If you don't have a computer with a COM interface, an USB com dongle will do.
And you can record stills every 2-3 seconds if CHDK runs on it.
-
You will need a phototransistor, a 10K ohm resistor, and a COM interface with a COM cable. If you don't have a computer with a COM interface, an USB com dongle will do.
Ok, i have those things. The use of phototransistor puzzles me. Does the camera dump the firmware via a LED?
And you can record stills every 2-3 seconds if CHDK runs on it.
You mean Videos with 1fps and 0.5fps?
-
Yes, you dump it via a LED (unless if you want to open it and solder stuff on the board).
And no, I mean still photos, not videos. I don't think you can (yet) to change the frame rate like that. Besides, that would only work at night, or else you need the mechanical shutter to 'fire' after each frame.
-
Yes, you dump it via a LED (unless if you want to open it and solder stuff on the board).
Ok, that makes sense. I'll dig more for the phototransistor schematics.
And no, I mean still photos, not videos. I don't think you can (yet) to change the frame rate like that. Besides, that would only work at night, or else you need the mechanical shutter to 'fire' after each frame.
On my Ixus 70, i had this forever. I'm not sure if it's part of the CHDK (i had CHDK on it, since the camera was delivered). In video mode, when you press the Timer/Drive button then there's an option to record a frame every 1 or 2 seconds. You basically leave the camera in video recording mode, and it takes timelapse video (yes video). I'll check tonight, if it's built-in feature or CHDK
-
On my Ixus 70, i had this forever. I'm not sure if it's part of the CHDK (i had CHDK on it, since the camera was delivered). In video mode, when you press the Timer/Drive button then there's an option to record a frame every 1 or 2 seconds. You basically leave the camera in video recording mode, and it takes timelapse video (yes video). I'll check tonight, if it's built-in feature or CHDK
No, it's not a CHDK feature.
It's a feature Canon implemented in some of the Powershot cameras, e.g. also on the SD870; it looks like Canon removed this feature on the newer cameras, maybe 'cause the video format has changed (MJPEG on older cameras, Quicktime on newer ones)...
-
Thanks, my old cam is an SD1000 (Ixus 70) and I really liked this feature. But luckily timelapse videos can still be shot in photo mode in a much higer quality with CHDK.
Still waiting for my SD980 to arrive this week.
Has any one tried the Saleae "Logic" logic analyzer (http://www.saleae.com/home/ (http://www.saleae.com/home/))? I'm thinking about trying it out to see if I can dump the firmware this way. It's not an ideal LA, but for the money it looks a good addition to my tools.
Apparently the software can aquire 1000M samples.
A 1.7MB firmware is around 1.8M Bytes (million bytes), with the led blinker method, it's 8 times of that which just a little over 14M bits.
I was told that for a good timing registration the instrument should preferably be 5x-8x more in its measuring speed, which makes it 70M samples (minimum). Apparently, with a simple level shifter a led output can be attached to the LA and the data can be exported as a binary file or a CSV.
At the moment, i am unsure about a few things:
The LA has a list of fixed frequencies with which the unit (or the software that came included) can aqcuire:24Mhz(i would not rely on this since it depends on PC and other USB deviches on the same channel), 16Mhz, 12Mhz, 8Mhz, 4Mhz, 2Mhz, 1Mhz, 0.5Mhz, 0.25Mhz and 0.2Mhz.
1. What frequency is the blinker working at?
2. Can the "blinker" be tweaked for a higher frequency?
3. I assume that at higher frequencies "blinking" will be affected negatively unless the LED is removed (since it will act like a capacitance and smoothen the signal edges on Raise (and perhaps on Falls), is it so?
-
Just a small update, mine came in a few minutes ago.
The firmware version is 1.01 rev 3.00 (1.01C).
Guess now it's time to try to get the firmware out.
-
1. What frequency is the blinker working at?
2. Can the "blinker" be tweaked for a higher frequency?
3. I assume that at higher frequencies "blinking" will be affected negatively unless the LED is removed (since it will act like a capacitance and smoothen the signal edges on Raise (and perhaps on Falls), is it so?
I've never had to dig into all that blinking stuff, but http://chdk.wikia.com/wiki/Porting_the_CHDK (http://chdk.wikia.com/wiki/Porting_the_CHDK) has a bunch of info about it, including some timing stuff. The blinker code can of course blink much faster (previous blinkers try to match reliable serial port baudrates or audio input bandwidth and also cope with rather slow phototransistor receivers). Eventually you'll run into either maximum I/O speed for the ARM at that time or maximum speed for switching that particular LED circuit.
-
If you want, I can give you my blinker, which should be compatible with your model too, unless if Canon did some major changes.
But you will need to get the ARM toolchain, so that you can compile the code.
-
yes please.
-
Sent
-
Sent
Thanks, got it. Managed to view the txt correctly. Got all the details. Gonna build the cable tomorrow.
My Logic Analyzer has not arrived yet, so ill go with the sound card solution first.
-
Why not go to the COM solution?
-
Why not go to the COM solution?
gotta dig out an old laptop with a RS232
-
Ok, the setup seems to be running. Blinking the first trial now :xmas
-
You can always get an USB to COM adapter, they are like 10 bucks on Amazon.
-
Ok, i will try the COM way. The sound card dump is way too inconsistent. ADC.EXE giving Sync Error!
The AF addresses seems to remain unchanged: C0223030
The addresses I probed are
GREEN color of the LED: C0220130
RED color of the LED:C022034
-
RaduP,
Can you confirm the dump i got from a 1.01 Rev3.0 (1.01C) is the actual firmware?
I tried a few times, these two trials are quite identical but there are still some tiny differences. I don't know how critical these differences are.
http://rapidshare.com/files/319539534/sd980_v1.01C__trial1_.bin.html (http://rapidshare.com/files/319539534/sd980_v1.01C__trial1_.bin.html)
http://rapidshare.com/files/319540087/sd980_v1.01C__trial2_.bin.html (http://rapidshare.com/files/319540087/sd980_v1.01C__trial2_.bin.html)
The Phototransistor used is the Osram SFH300-3/4. Build based on the http://chdk.wikia.com/wiki/File:Serial_Blinker_Receiver.png (http://chdk.wikia.com/wiki/File:Serial_Blinker_Receiver.png)
-
Ok, I only tried the first one, which does indeed seem to be the actual firmware, but there is something slightly wrong with it. I think there are some leftover checksums.
Did you use the exact program I give you to upload in the camera and dump the firmware with? If not, try to use it unmodified.
And what did you use on the PC side to get it?
-
Ok, I only tried the first one, which does indeed seem to be the actual firmware, but there is something slightly wrong with it. I think there are some leftover checksums.
I removed the lines with 1234567890.. (the last one was the linefeed & carriage return). I did not clean the end of the file, since i could not figure out what to remove. Should I upload the raw (unmodified) dump?
Did you use the exact program I give you to upload in the camera and dump the firmware with? If not, try to use it unmodified.
And what did you use on the PC side to get it?
The exact one did not work, since it was for platform id=31E6, but mine is 31E5. So i had to recompile it with 31E5.
In all cases, at the end, at 4 Mbytes, the load.exe timesout and stops, the camera does not turn off, and the AF led stays on forever (no blinking) so turn off the camera by removing the battery. Is it normal?
-
Well, the thing is, the program I made that cleans the dump need those 1234.. lines to be there. Otherwise it gets confused. So please give me the dump with those lines.
And by using the same program i meant the same source code, not the same binary.
Anyway, it is normal for the camera to do hang at the end.
-
Heres my firmware dump from 1.01C (1.01 Rev 3.0) SD980 (Ixus 200 IS)
http://rapidshare.com/files/320665256/sd980_v1.01C.bin (http://rapidshare.com/files/320665256/sd980_v1.01C.bin)
Thanks a lot to RaduP for his guidance!
-
Hi all,
I just bought the ixus 200 IS - SD980 and the firmware is 1.01C ( Rev. 3 ) version
There is hope of operating the CHDK with this firmware?
Thanks
-
Hi all,
I just bought the ixus 200 IS - SD980 and the firmware is 1.01C ( Rev. 3 ) version
There is hope of operating the CHDK with this firmware?
Thanks
there's always a hope..
-
I've just purchased an IXUS 200 IS and found that it (unfortunately) has firmware 1.01 rev3 on it. I've been following the posts in this thread and am really impressed with how much work everyone is putting in to get CHDK working on this camera (especially RaduP and valour - great job!).
I'm really looking forward to you guys creating a version that works with my firmware. If there is anything I can do to help, please let me know. I have enough electronics and programming skills to follow instructions reliably, but have no experience programming for cameras.
Good luck and keep up the good work!
-
Hi K8,
If you have programming skills along with some basic assembly that would help. The 1.01C firmware is dumped and ready for analysis.
Please drop a PM to Radup asking for the files he used for 1.00
-
oh
-
Any updates for the 1.01 firmware? thx
-
Any updates for the 1.01 firmware? thx
unfortunately no progress so far, since we are busy at work :(
-
I've been trying the beta on my ixus 200is but when i startup on the CHDK enabled SD card the camera stays off and I have to remove the battery to reinitialize it. Seems like the port doesn't work on my cam firmware.
Camversion says it's a Powershot (edited) ixus SD980 IS version 101c
I need this port very badly for a pro application, I can support any developper that 'll make it work on my cam.
billvestre {at} me 'dot' com
-
I've been trying the beta on my ixus 200is but when i startup on the CHDK enabled SD card the camera stays off and I have to remove the battery to reinitialize it. Seems like the port doesn't work on my cam firmware.
It does not make sense, are you trying the 980 beta on your 200is?
So far there's no working CHDK for 980IS v101c. The v101c has been dumped, but we need someone to do the actual porting.
-
Well I mixed Up between powershot and ixus, sorry
-
Hi,
I am new to this board, and Canon Powershot Cameras in general.
However, I am looking to get an SD980iS in the next few weeks, and have all the skills
required to help develop the port for a new release.
Based on the previous posts, it is likely I will get firmware version 1.01C - which I expect to be able to help port.
It looks like a great fun project to play with!
Until I do get my camera, and can verify the firmware version, I will just download the Shell and start playing around with IDA, and other things.
(getting an overview of the environment, running up the learning curve, etc.,)
I expect my time to work on the project will increase in the summer and decrease in other times of the year.
I don't want to raise anybody's hopes too high, but I think I can contribute in a significant way, and I am definitely looking forward to playing around with this "toy".
-
Hi Symbol,
Welcome to the project, good timing too :)
I really hope your camera comes with 1.01C too :xmas
-
Thanks for the welcome.
I have received my camera (today) and verified that it has Firmware Version 1.01C (according to EXIFTOOL anyway).
I have looked at IDA (and my mouth watered), but I cannot afford the price tag.
(Well, strictly speaking, I won't even try to convince my wife that we can afford it. :-X )
So, I have looked at other ways to examine the 1.01C code.
I have the 4MB (incomplete) dump - thanks to whoever created it (was it valor?)
I have created a dis-assembly file using the scripts from another developer thread here.
I have found a tool that allows me to "simulate" the execution of the program from the .BIN file - it is Crossware - Community Edition.
I set up a completely different ARM processor - using the AT91SAM9G20 - and I "skip around" instructions that are not well handled because of the different base architecture (PMU vs. MMU, for one).
I have emulated enough of the code to notice that the 4MB dump is not the complete firmware dump.
(for starters, the startup code copies code from ffc0282c through ffc2181b to location 00001900.)
However the dump data ends at ffc0fbff.
This means that there is some code missing in the dump.
Does anybody know yet how to get the remaining dump data?
I noticed a post or two that indicates that the LED dumping hangs at the end of the first 4MB. (which is what this dump essentially is)
I am lazy enough to not particularly wish to try dumping additional memory if someone else is better set up for this than I am.
I was unable to obtain the beta source code for CHDK for the FW1.00 SD980 port.
(Something about a limit on the number of downloads, or some such)
So my efforts to understand the CHDK source code have gone not very far yet.
I have tried a binary compare of the 1.00 dump to the 1.01C dump.
Much is the same, but much is also different
Quick scanning, however, seems to show most changes are simply new memory addresses for routines, etc.
This is all going to take considerable time, but now that I am started, I can keep "chugging away" at it.
Anyway, it is getting late here so I am off to bed.
Good night...
-
Hi, let me post the latest source code from my port, it should help you quite a bit port the new firmware.
-
Thank you RaduP.
I have looked the code over (briefly) - looks *very* useful.
I did notice that a lot of the disassembled startup code is present as straight assembly - with no comments at all.
Is there some reason for the lack of comments (other than: nobody has done it yet)?
If there is no reason not to, I can contribute quite a few comments on the startup code already as I have been concentrating on understanding what is going on, and not just skipping past this code.
I am expecting to use Yagarto tools and Eclipse as my cross development platform.
This could also take a while to set up for CHDK - or not.
I have experience with these tools, and am currently working with the AT91SAM9G20 (which is why I am using it as my base for the investigative emulation of the code)
Thanks again,
Symbol
-
Hi again RaduP. Which svn revision did you start with?
-
I did notice that a lot of the disassembled startup code is present as straight assembly - with no comments at all.
Some other ports are commented (not always correctly ;)). This code is very similar between cameras.
I am expecting to use Yagarto tools and Eclipse as my cross development platform.
CHDK is very picky about toolchain configuration. I would either use one of the pre-built ones or build your own. If you happen to be a GCC/ARM expert and can explain what needs to be changed to make this saner, please do :)
-
Thanks reyalp.
I will look at other comments and compare mine.
I will incorporate them into my version
Also thanks for the tips about the toolchains.
While I probably could figure out how to use another toolchain, I don't really want to spend the time.
I am working out how to use the CHDK-Shell as my tool.
At this point, I have a working directory under Tortoise SVN control - with all the source checked out from assembla, and starting to add new development directories/folders.
The first job to complete is to add in the Source from RaduP (and version 1.00C) and get it building.
Then I want to start building my version 1.01C and get it operational.
-
At this point, I have a working directory under Tortoise SVN control - with all the source checked out from assembla, and starting to add new development directories/folders.
The first job to complete is to add in the Source from RaduP (and version 1.00C) and get it building.
Then I want to start building my version 1.01C and get it operational.
Great. You may find the G11 port a useful reference, since it's another one of the newest dryos verion cameras that has been pretty much fully ported.
-
Hi Symbol,
Thanks for taking the initiative.
The 1.01C dump I made was prepared for a release with some help from RaduP, it should be complete, but if you find out that it lacks some bits, I still have the the IR COM cable, so i can i blink the firmware out again.
-
Thanks for the tip reyalp. I was scanning releases to see which might be most useful.
That is valuable information.
valor - the dump I got (probably yours) is not complete.
It is a full 4Mbyte dump, but as my previous post indicates, the startup code expects something in the ROM (actually, it is probably Flash memory) at least all the way to 0xffc2181b (which would take at least 4.068 <binary> Mbytes of dump to get it complete)
Perhaps if I get a small amount of code working from your dump, I can get a complete dump put onto an SD card from my camera using CHDK (ultra-lite)
-
valor - the dump I got (probably yours) is not complete.
It is a full 4Mbyte dump, but as my previous post indicates, the startup code expects something in the ROM (actually, it is probably Flash memory) at least all the way to 0xffc2181b (which would take at least 4.068 <binary> Mbytes of dump to get it complete)
Perhaps if I get a small amount of code working from your dump, I can get a complete dump put onto an SD card from my camera using CHDK (ultra-lite)
Sure, if you can make an SD which can fetch the dump that would be ideal, otherwise if you hit a deadend with the current dump, just let me know. We can retry with the "blinking".
-
Thanks for the tip reyalp. I was scanning releases to see which might be most useful.
That is valuable information.
Other useful references may be sx10 (fairly recent and fully functional, done by ewvar) and sd990 (I tried to put in lots of comments when I did it)
valor - the dump I got (probably yours) is not complete.
It is a full 4Mbyte dump, but as my previous post indicates, the startup code expects something in the ROM (actually, it is probably Flash memory)
Yes "ROM" is internal flash. The camera stores things like settings and crash logs in "ROM" along with the actual firmware code.
at least all the way to 0xffc2181b (which would take at least 4.068 <binary> Mbytes of dump to get it complete)
Perhaps if I get a small amount of code working from your dump, I can get a complete dump put onto an SD card from my camera using CHDK (ultra-lite)
You should be able to get enough working write a dump with normal IO functions without too much trouble. Generally, the difference between canon versions that breaks CHDK is just address moving. Canon adds some code, and this moves changes the address of any following functions. Any additions to the code will also move values for initialized data in ROM down, which means that if you use the startup code from the old FW (the first loop that copies stuff), it will initialize all the variables with the wrong values. Figuring out how much things moved is pretty straightforward, see http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version (http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version) for some tips.
-
Hi,
I just bought an sd980, also firmware 101.c, wouldn't you know it? ::)
Just checking in to see if there is any progress with this one?
Dan
-
Anybody there? :-[
I don't mean to be a pest, after reading up on the wiki about the steps involved in porting or adding firmware, I realize how much work this takes. I'm just curious on how the 101.c stuff is going?
Cheers,
Dan
-
i extremely want to use chdk. But where i can find chdk for my ixus 200 is firmware? also 1.01 C (by exiftool). i made a big mistake buying ixus 200 is. Image quality is terrible, too much noise and low light performance is very bad, it's the despair of me. so i hope chdk can help me improve that.
-
i made a big mistake buying ixus 200 is. Image quality is terrible, too much noise and low light performance is very bad, it's the despair of me. so i hope chdk can help me improve that.
No, it can't. These are characteristics of the hardware.
-
i made a big mistake buying ixus 200 is. Image quality is terrible, too much noise and low light performance is very bad, it's the despair of me. so i hope chdk can help me improve that.
No, it can't. These are characteristics of the hardware.
it's almost right but i think that manual setting, raw file...can help gain good exporsure, avoid shaking camera by setting at faster shutter speed even improve image stabilization :D i hope that, if not i will sell this [admin: avoid swearing please]
-
I accidentally made a discovery that might be on interest to the developers.
I downloaded the Beta version, put it on a card, and went and shot with an SD980 in a store. CHDK loaded and worked partly. The zoom during video worked,for example, and the camera recorded RAW files, but the files could not be opened with dng2ps (which usually works fine for me with CHDK RAW shot on another Canon.)
This camera, it turns out, was FW ver 1.00C. (not 1.01C)
I just bought an SD980 at Costco, and it's got FW ver 1.01C, which doesn't load at all, and crashes the camera if you try.
SteveM
-
For those checking up on progress...
I am working on a port for 1.01C, but it will take some time.
Don't expect much before at least 3 months from now.
I have other things taking time right now.
Co-incidentally, my real name is Steve M. too (metaphorce), but I would bet the M. is different from yours..
I have made some progress, but am still in "learning-curve" mode.
I have the CHDK Shell compiling the currently supported firmware version of the beta
I have started making source code changes for the 1.01C version.
I think I could have it going much faster if I wanted to skimp on understanding what I was doing, but part of the fun for me is to understand what is going on "under the covers".
So hang in there, be patient.
I am still working on the boot.c source file - for those who know what that means.
Regards,
Symbol
-
Thanks, Symbol,
I have looked at many posts about coding, and can tell I am way out of my league as far as c and asm goes, but will be willing to help with any testing, or however I can help. Enjoy the work, I look forward to a port when it happens.
Dan
-
Thanks symbol, it's a really good sinal. I hope that you will make chdk version for 1.01c asap.
-
Can anyone give me some detail infomation about processing?
-
Hey, any word on other firmware versions or the new ixus 210?
My ixus 200IS is broken, which had FW 1.00C, but i don't know yet what the new one will have ;)
-
@Symbol(Steve)
Hi, I'm just checking in to see how things are going? Are you learning lots about the code? I am really not trying to pressure, just curious on your progress. Anything interesting?
Regards,
Dan
-
I just gotten my new Ixus 200 in, and ofc, Firmware Revision: 1.01 rev 3.00
Waiting patiently now :)
-
Just out of curiousity, does anyone use Virtual Machines? If one person got a nice ubuntu development environment set up then we could all share it, and someone like me (coder without a LOT of free time, but want to help where I can) might be able to make more substantive contributions. I do all my work in VMs.
Just a thought.
-
I also took a shot at starting a port for the v1.01C firmware:
http://chdk.setepontos.com/index.php/topic,5321.msg51577.html#msg51577 (http://chdk.setepontos.com/index.php/topic,5321.msg51577.html#msg51577)
If anyone with more CHDK/ASM experience can help complete it, let me know...
-
My is 1.00d, Who have the CHDK for it?
-
My is 1.00d, Who have the CHDK for it?
From what I can find, work has not even started on this revision. If you have any coding skills, you might want to start with a firmware dump.
-
My is 1.00d, Who have the CHDK for it?
It would be great if you could post the output from the ver.req in this thread if you used that method. How exactly did you get you version info?
-
So among the other things todo I managed to
1) Get the Crosscompiler tool chain working fully from source scratch on my 64Bit Linux. :D
2) run IDA on my temporary WIN partition.
3) I have the 100C source
4) 1.01c Firmware dump
Now onto the next step.... reading more of the Wiki and post
Just FYI: IXUS200 SD980 v1.0.1c porting info will be in:
:o http://chdk.setepontos.com/index.php/topic,5321 (http://chdk.setepontos.com/index.php/topic,5321)
-
OK, a dilemma.
I currently use an IXUS 70 for RC aerial photography, I wrote my own interface for a PIC12F675 to use a RC servo channel to output USB pulses to control the camera via CHDK.
I would like to switch to a camera with a much wider angle, it becomes less critical to point the plane at what you want to take a photo of.
This IXUS200\SD980 camera has the equivalent of a 24mm wide angle in 35mm terms, so it would seem a good choice.
However how can I work out, before purchase, what version of the firmware is in the camera, it would not be worth purchasing without the ability to run CHDK ?
-
srnet, well there are only so much firmware versions.... Indeed it is a gamble which I took to discover my firmware was not yet supported :( So I decided to take development into my own hands and start working on it :haha . Now that the OBC2010 Challenge is past I can devote time to the 1.0.1c firmware again. And if I can make one firmware no doubt I can make it for other firmware versions also. But that is for the future...
The sooner you buy the Device the higher the chance it is an older firmware and more change of getting a patched one soon...
BTW great if you could post a link to your PIC to Ixus 70 hardware project of schematics.
Just FYI: IXUS200 SD980 v1.0.1c porting info will be in:
:o http://chdk.setepontos.com/index.php/topic,5321 (http://chdk.setepontos.com/index.php/topic,5321)
-
-
-
Would there be general interest in seeing the code for a RC to CHDK remote control ? Easy circuit, single 8 pin IC (12f675) written in Mikrobasic which is free to use for the 2K PICs. All you need is a PIC programmer.
Certainly would.
Could you recommend and give links for the software and suitable programmer ?
-
There are plenty of easy to make DIY PIC programmers out there, either connected via the parallel port or serial port. This is an example;
http://www.semis.demon.co.uk/uJDM/uJDMmain.htm (http://www.semis.demon.co.uk/uJDM/uJDMmain.htm)
Run an eBay search on 'PIC programmer' and you will find several from around $15.
Myself I use a PicKit2, fairly cheap and easy to use.
I will go through the code I have to make sure its legible, its written in Mikcrobasic for a 12f675, and failrly easy to amend.
-
I have CHDK running on my IXUS 200, but one thing is puzzles me.
It does not power on\boot when the power button is pressed. The card write protect switch is set and the power button works as normal in non CHDK mode.
It does however start when the playback button is pressed, this starts CHDK and the autorun script runs.
Its not a serious issue since the script waits for a USB pulse and takes a picture at which point it changes from playback mode into record mode.
Should CHDK be starting when the power button is pressed ?
-
It does not power on\boot when the power button is pressed.
...Should CHDK be starting when the power button is pressed ?
The camera always start in playback mode when CHDK is enabled, this is the normal behaviour on cameras without a mechanical switch for playback/record mode selection.
* When powered on in playback mode, just press the shutter button full or halfway once to switch to record mode
* To turn the camera on directly in record mode, try holding the POWER button for ~1 second
You don't need a (autorun) script to start/run CHDK...
-
Just FYI: IXUS200 SD980 v1.0.1c porting info will be in:
:o http://chdk.setepontos.com/index.php/topic,5321 (http://chdk.setepontos.com/index.php/topic,5321)
-
Hello to all,
I've been trying to get chdk work for a many days now, and I would need some help...
First of all, I'm not able to see the firmware version of my Ixus 200 IS, ver.req or vers.req
trick does'nt seem to work on my cam. exiftool says Firmware Revision : 1.01 rev 3.00.
Automatic boot does'nt work eather. But I can run chdk by "firmware update". It ask me if
I want to update from 1.0.1.0 -> 1.0.0.0. After that I see chdk splash screen for a few seconds
and the camera turns off. I have tried few versions of chdk that I found, and one version hangs
the whole camera.
Does someone know what I'm doing wrong? Should these beta versions buut up at all?
-
hello, I would like to download the beta for this camera but all links are broken - is there another linke where one can download the beta?
thanks
Werner
-
@wbloos
Here (http://chdk.bplaced.net/content/download/view.download/8/33.html) you can find the last raduP version. Perhaps helps this link.
msl
-
Just a THANKS for all the determination and creativity that went into this port so far!
I got it working on my 200IS which luckily still has the early firmware.
Obviously I can not use many of the scripts that I have on a S3IS, and it is not clear to me what would be the best way to go with this port in order to do exposure bracketing for HDR processing. The shots will later be stitched as 360 panoramas, so I would like to have the camera do 5-or-so bracketed shots each time it is rotated to position- possibly using USB/wireless for remote/hands off.
Sure would appreciate pointers here since I'm still green at CHDK. Should I go with LUA over BASIC for more speed and functionality?
This is all very inspiring and exciting stuff, really, it just makes me grin :-]
-
Is there a location for SD980 1.01C code? All of the links I can find here seem to be dead ends?
tnx
mgg
-
Is anyone still working on this? There seemed to be sufficient interest and skills..?
Also, as others have noted, the beta links no longer function. Does anyone have the files so that we could repost them?
Alternatively, if someone would send them to me, i'd greatly appreciate it. I also am having trouble finding my fw version, but i've just started, really, altho' i've spent several hours researching CHDK.
I will pledge to match the $15 offered by others in this thread for an official autobuild for the SD980/IXUS200.
i'll just add that the function i'm most interested in right now is the intervalometer, followed closely by usb remote. If anyone has options of alternatives, please let me and others know.
thanks in advance.
-
Is there a location for SD980 1.01C code? All of the links I can find here seem to be dead ends?
Also, as others have noted, the beta links no longer function. Does anyone have the files so that we could repost them?
Here you go - source code : IXUS200 SD980 firmware 1.01c (http://www.box.net/shared/xjb8vd7lrr)
I will pledge to match the $15 offered by others in this thread for an official autobuild for the SD980/IXUS200.
Thanks - but as I have posted elsewhere, at $10/hr the average port is probably worth over $1000. And you won't find many software developers interested in working for $10/hr. But the gesture is appreciated by some of us.
If there is anybody with a 1.01c firmware SD980 willing to test the beta, I will rebuild it against the current source. If it works fabulously, I'll even submit it as a patch file for the autobuild server. But if the beta is bad, I don't have a SD980 and am not really interested in trying to debug another camera remotely. Sorry.
UPDATE : Built it - no idea if it works but here you go CHDK load for IXUS200 SD980 firmware 1.01c (http://www.box.net/shared/9d44o8kg9f) <does not work
-
Thank you so much for that, waterwingz, and i fully understand and appreciate the time:cost factor. In my work i frequently get the client who is surprised at how much it costs for me to do something that they consider simple, tho' they are unable to do it themselves. ::)
Unfortunately, no workie for me- on a mac, i unarchived the new load using stuffit instead of the osx utility, then tried both manual and SDM Installed card-loading methods.
one thing; i did have to add the ps.fi2 file from this German chdk page: http://chdk.bplaced.net/content/download/summary/8/33.html (http://chdk.bplaced.net/content/download/summary/8/33.html) Adding this file enables the (otherwise missing) 'firmware update' menu entry in the camera. Upon choosing the update, i get the black screen requiring the battery removal process.
could the borrowed ps.fi2 file have something to do with it not working? if not, i guess i'll give up.
thanks much again for your efforts, waterwingz! :)
attaching the found build from which i used the .fi2 file:
-
Unfortunately, no workie for me- on a mac, i unarchived the new load using stuffit instead of the osx utility, then tried both manual and SDM Installed card-loading methods.
So many questions here - the file you downloaded might be fine but you did not prepare the card correctly. What size SD card did you use ? Single or dual partition ? Did you set it up as bootable ? Did you move the card lock tab to the locked position ?
could the borrowed ps.fi2 file have something to do with it not working? if not, i guess i'll give up.
A ps.fi2 file is just the bootdisk.bin file encoded differently. So what you downloaded had nothing to do with what I posted and tells us unfortunately nothing.
-
I have 101C afaik, i can check it.
Just need to figure out how to format the sdcard properly.
Edit: used the http://chdk.wikia.com/wiki/CHDK_for_Dummies#I_have_the_camera_already.21 (http://chdk.wikia.com/wiki/CHDK_for_Dummies#I_have_the_camera_already.21) method
no response whatsoever from the camera regarding the FW
-
ha. of course the one detail i thought important, wasn't. i mentioned the .fi2 file because i noticed earlier that without that file, there is no 'firmware update' entry on the camera menu. i was trying various ways with the German version before your help above.
ok- your q's: started with 4GB Sandisk w/ single partition, then tried 2GB Kingston (all FAT16). Formatted in the camera, to start, but also tried using SDM Installer and the two applescripts listed on the mac faq. Locked card after each install attempt, turned camera on with play/review button (but tried regular on/off, too, for kicks). SDM and manual method were single partition; the 2 applescripts used a dual partition. Tried both manual and app/scripted methods of making SD card bootable. osx 10.5.8.
None of the recommended procedures resulted in any response from the camera; not even the 'firmware update' menu entry appearing. Is there any advantage to using a PC for this? (dumb question?) i so want to make this work, dangit
-
ok- your q's: started with 4GB Sandisk w/ single partition, then tried 2GB Kingston (all FAT16). Formatted in the camera, to start, but also tried using SDM Installer and the two applescripts listed on the mac faq. Locked card after each install attempt, turned camera on with play/review button (but tried regular on/off, too, for kicks). SDM and manual method were single partition; the 2 applescripts used a dual partition. Tried both manual and app/scripted methods of making SD card bootable. osx 10.5.8.
None of the recommended procedures resulted in any response from the camera; not even the 'firmware update' menu entry appearing. Is there any advantage to using a PC for this? (dumb question?) i so want to make this work, dangit
The only advantage to using a PC is that I know it works and there are more people here using PC's that might be able to help you.
One other kind of important thing - did you check to make sure your camera actually has firmware ersion 1.01c. Close does not count with firmware versions.
-
got the old PC fired up here; will try again later today. and i double-checked with two tools: fw v. 1.01 rev3.00, which as i understand = 1.01c, correct?
and for titbb, try using cameraversion: http://chdk.wikia.com/wiki/CameraVersion (http://chdk.wikia.com/wiki/CameraVersion) if you're on a PC. i forget what i used on the mac.
waterwingz, what method do you recommend using on the PC? manual or autoboot; card size vs partition, etc. your knowledge is appreciated.
-
waterwingz, what method do you recommend using on the PC? manual or autoboot; card size vs partition, etc.
There is no ps.fi2 file available right now so you can only do autoboot. I'd recommend a 2G or 4G card so that you don't have to play with partitions right away . Cardtricks or sdminste.exe should both work fine for your needs.
-
UPDATE : Built it - no idea if it works but here you go CHDK load for IXUS200 SD980 firmware 1.01c (http://://www.box.net/shared/9d44o8kg9f)
So far 10 people have downloaded this. Two have tried to use the ps.fi2 method to start, only to find that there is no ps.fi2 file available. It would be good to hear for somebody else about whether this loads or not using the "Card Lock" method.
(Note that the link won't work in a quoted text box - go back to the original post if you want to download.)
-
@jamabushi ill try thx
@waterwingz unfortunately the cardboot/ lock method does not work, the update firmware just doesnt become available
-
"no pictures. card locked." each time. no luck using a PC, CardTricks, 2GB then 4GB card, twice each. tried removing the changelog just in case. no go.
I might have been two of those 10; i downloaded on 2 computers.
anyway, ack.
-
@waterwingz unfortunately the cardboot/ lock method does not work, the update firmware just doesnt become available
The update firmware will never be available without a ps.fi2 file - it sounds like you are confusing the two methods ?
-
"no pictures. card locked." each time. no luck using a PC, CardTricks, 2GB then 4GB card, twice each. tried removing the changelog just in case. no go.
Not much I can do if without having the camera at this point. The beta build should have at least loaded based on earlier posts in this forum. One last thing we can try - I'll do a version that turns on the camera LED's at the very start of the boot loader process - which should confirm that the image was placed correctly on the card and the card correctly formatted.
-
@waterwingz unfortunately the cardboot/ lock method does not work, the update firmware just doesnt become available
The update firmware will never be available without a ps.fi2 file - it sounds like you are confusing the two methods ?
I'm sorry, i was a bit short in my reply. The autoboot with locked card had no ' chdk' response.
Just got no pictures notice with Card Locked. CHDK wouldn't show up, not even when i went to normal mode.
-
ixus 200 is / sd980 - version 1.01C
The same at me. Its possible to downgrade the firmware to 1.00. But where can I get it?
With v. 1.01c and DISKBOOT.BIN CHDK dont show anythink. And with PS.FI2 (firm update) the camera dont work.
-
ixus 200 is / sd980 - version 1.01C
The same at me. Its possible to downgrade the firmware to 1.00. But where can I get it?
With v. 1.01c and DISKBOOT.BIN CHDK dont show anythink. And with PS.FI2 (firm update) the camera dont work.
Canon doesnt provide firmware updates afaik, so not possible to downgrade, unless you can dump and write the full FW, which i doubt
-
Did some research here : http://chdk.setepontos.com/index.php?topic=5321.0 (http://chdk.setepontos.com/index.php?topic=5321.0)
It does not look like the 1.01C code that I reposted was ever completed - or that it even booted. Sorry.
I can take a further look but having the source code for the original 1.00c would help. Does anyone have a link for that ?
-
http://chdk.bplaced.net/content/download/viewcategory/8.html (http://chdk.bplaced.net/content/download/viewcategory/8.html)
This might be the thing your looking for, but i cant be sure since my german aint my strongest
-
http://chdk.bplaced.net/content/download/viewcategory/8.html (http://chdk.bplaced.net/content/download/viewcategory/8.html)
This might be the thing your looking for, but i cant be sure since my german aint my strongest
That's not the source code, it's a binary (1.00c) ;)
-
i'm using lunch to look thru this thread again: http://chdk.setepontos.com/index.php?topic=4335.15 (http://chdk.setepontos.com/index.php?topic=4335.15)
it looks like they had a version of CHDK working on 1.00c, but all d'load links are dead. going to try reaching member RaduP; seems he was on top of development at that time
still reading...
-
http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454 (http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454)
looks like they did a dump of the 1.01c fw; of course the rapidshare links are long dead...
-
http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454 (http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454)
looks like they did a dump of the 1.01c fw; of course the rapidshare links are long dead...
Hi Jamabushi,
Sorry that my link went dead.
I've reuploaded the dump at
https://rapidshare.com/files/390363769/sd980_v1.01C.bin
good luck CHDK'ing :)
-
I've reuploaded the dump at
https://rapidshare.com/files/390363769/sd980_v1.01C.bin
Thanks valor. Although I just have to comment that rapidshare is definitely not my favorite file sharing site - its making me wait 5 minutes before it will download your file. No such restrictions at box.net.
-
Yea, but box.net required a login, and uploading to rapidshare was the fastest option.
You are welcome to crate a mirror and upload to the box.net :)
-
http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454 (http://chdk.setepontos.com/index.php?topic=4335.msg44454#msg44454)
looks like they did a dump of the 1.01c fw; of course the rapidshare links are long dead...
Hi Jamabushi,
Sorry that my link went dead.
I've reuploaded the dump at
https://rapidshare.com/files/390363769/sd980_v1.01C.bin (https://rapidshare.com/files/390363769/sd980_v1.01C.bin)
good luck CHDK'ing :)
The firmware dump is too small - it's only 4MB.
Since the load address for this camera is 0xff810000 the firmware dump should be 8MB.
The 1.00c firmware dump that I have from box.net is also too small.
If anyone has the complete firmware dumps I can run the new signature finder I'm working on across them which might help.
Phil.
-
If anyone has the complete firmware dumps I can run the new signature finder I'm working on across them which might help.
@phil : I was going to ask jamabushi to run the Canon BASIC dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper) and see if we can get a better dump. With your new sigfinder and CHDK-PT it should be possible to put together a port fairly quickly.
-
Thanks - thats looking good. I hope you get the right "diskboot.bin" sometime.
-
Haven't followed the CHDK on SD980 for a while, so i don't know if somehting has changed lately, but back then (when I had the camera) I did several dumps all resulting a 4.1MByte file so wonder what went wrong.
-
Valor returns valiantly- thanks! (couldn't resist)
i've PM'd some of the other guys who were at advanced stages; we'll see what we can find. "morale is high", as my old fire chief used to say.
@waterwingz: i'll be able to run that when i get home this evening.
thanks to everyone for their time and effort.
-
Hi all
I can update my old source code, any idea what site to use for quick and painless file uploads?
Nvm, seems that I can still upload here, so there it is.
-
Hi all
I can update my old source code, any idea what site to use for quick and painless file uploads?
Nvm, seems that I can still upload here, so there it is.
With a little tweaking, I got it to build against the current trunk. If philmoz can figure out how to work with the 4G ROM dumps or jamabushi can produce an 8G dump, we may have some progress.
-
Why are you looking for 8mb dumps, when 4mb is what is needed?
-
Why are you looking for 8mb dumps, when 4mb is what is needed?
I have been working on improved methods of finding the functions CHDK needs in the firmware.
There are tables in the data section of the firmware that reference many of these functions - these tables are missing in the 4MB dumps so my signature finder won't work.
Phil.
-
Why are you looking for 8mb dumps, when 4mb is what is needed?
@RaduP : If you still have your camera, any chance you can try for an 8G dump using Canon BASIC dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper) ?
-
I tried to dump the OS with the cardtricks tool, i tried all 3 OS, new dryos, dryon and vxworks. Card locked.
Only the new dryos stayed on the black screen, but doesnt write ANYthing.
So, i cant help much more for the OS dump, since it doesnt seem to work for me :(
-
I tried to dump the OS with the cardtricks tool, i tried all 3 OS, new dryos, dryon and vxworks. Card locked. Only the new dryos stayed on the black screen, but doesnt write ANYthing. So, i cant help much more for the OS dump, since it doesnt seem to work for me
As noted here (http://chdk.setepontos.com/index.php/topic,964.0.html) : "You can not use CardTricks to dump 'newer' DryOS cams". You need to use the Canon BASIC Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
-
Ok, my bad.
Used the proper way mentioned @ http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup (http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup)
I managed to get a 8mb dump of the OS. Ill upload in a bit
http://www.megaupload.com/?d=89QCBPBR (http://www.megaupload.com/?d=89QCBPBR)
-
thanks for that, titbb, work got in my way.
waterwingz, is that the data you're looking for?
i'll probably do a dump 'just because'.
-
waterwingz, is that the data you're looking for?
Looks about right - we will have to see how it runs through philmoz's new sigfinder.
I would also be nice if somebody could dump and post an 8G file for firmware 1.00c.
-
Thanks titbb, added (http://chdk.setepontos.com/index.php?topic=288.msg68440#msg68440) your IXUS200_SD980 1.01C full (8mb) dump to the box.net/chdk (http://www.box.net/chdk) repository.
-
Cool cool, let's hope its of use to @philmoz
-
Cool cool, let's hope its of use to @philmoz
philmoz sent me the signature analysis for that file - working with it now
-
Okay - first try at a new build. Philmoz's new stub addresses and a new boot.c from the 8G dump using more current code stolen from the A495 and S95.
SD980 firmware 1.01c Beta 2 (http://www.box.net/shared/9d44o8kg9f)
Should slam all the LED's fully ON as the very first thing it does once the loader boots CHDK. So if this does not run, do the LED's at least turn on right away ?
(in the unlikely event CHDK boots fully, I turned off all the other tasks for now so other than menus and games, nothing else will work)
-
First off all, i appreciate the effort! Shame i have no programming knowledge whatsoever to help more in htat regard :(
I used cardtricks on a 512mb card, formatted it, made it bootable and used the chdk -> card part, locked it, inserted into camera and pressed play.
Just got a No Image, Card Locked notice, nothing else happens unfortunately.
-
First off all, i appreciate the effort! Shame i have no programming knowledge whatsoever to help more in htat regard :(
I used cardtricks on a 512mb card, formatted it, made it bootable and used the chdk -> card part, locked it, inserted into camera and pressed play.
Just got a No Image, Card Locked notice, nothing else happens unfortunately.
Added LED code to the Loader code (http://chdk.setepontos.com/index.php?topic=5321.msg56794#msg56794) - it doesn't get much more basic than this. Hopefully we can get a couple of people to try it and report results here.
SD980 TEST3 Download File (http://www.box.net/shared/tant55k9x9dc3e0ysbm8)
-
Is this now ready for use with sd980 v. 1.01c ?
I load it (format card - make bootable aso.) but - shitt happens - nothing.
I think the camera only works with ps.fi2 and is not able to start in automodus with diskboot.bin ?!?
-
Is this now ready for use with sd980 v. 1.01c ?
Supposed to be. Just trying to help out here - I don't have the camera so there is only so much I can do.
I load it (format card - make bootable aso.) but - shitt happens - nothing.
Do any of the LED's come on - especially the AF LED on the front of the camera ? Are you starting the camera by pressing the Play button pn the back ? I think I read somewhere that you might need to do that rather than pressing the on/off button on top.
I think the camera only works with ps.fi2 and is not able to start in automodus with diskboot.bin ?!?
Diskboot.bin works for the 1.00c firmware (http://chdk.setepontos.com/index.php?topic=4335.msg42314#msg42314). Seems unlikely it doesn't work for the 1.01c.
-
I pressed the Play button and the power on. It will be the same. Is thomething wrong because the cam has a touch screen?
-
I pressed the Play button and the power on. It will be the same. Is thomething wrong because the cam has a touch screen?
I guess I stuck unless somebody else can get it to boot. The camera should work - there is a working port for firmware 1.00c
-
Well,
since there aren't many leds on the camera it shouldn't be hard to see if it works or not.
i reformatted and made the card bootable, just to be sure, but the only thing i get is just 3 green flashes, but they always come when the play button is pressed at poweroff.
so, im afraid to say it doesn't work also :((
-
so, im afraid to say it doesn't work also :((
As a test, I cut and pasted the code I added to the SD980 loader and boot.c files into the SD940 camera files (I have one of those). The resulting LED pattern is really slow and obvious - you could not possibly miss it if it runs.
The SD980 boot loader code and LED addresses are identical to the SD940 so I tried booting that DISKBOOT.BIN file. Nothing happened - just like everyone here has reported. Strange - I should have at least seen the boot LED pattern.
Time to dig a little deeper I guess.
Update : I took the SD980 boot source code and used it as a the boot source code for the SD940. Works fine for the SD940. Somewhere I have address wrong in the build files I'm thinking.
-
OK, i'm back. haven't had time to do another 8G dump, but looks like it's not necessary?
@waterwingz, just d'loaded the 0.9.9TEST3 version, will load and test now. it looks like i'm looking for led flashes if chdk doesn't run?
-
Progress ! Not being able to boot at all does not make any sense. So with a little digging I noticed an underscore ( _ ) character in front of NEED_ENCODED_DISKBOOT in makefile.inc. That would pretty much explain everything right there. So here's a rebuild - see if this flys now ?
IXUS200-SD980 Test Version 4 (http://www.box.net/shared/0yb21oqkby2hxnclqq6s)
-
Its a [admin: avoid swearing please], 1 little thing wrong and the whole doesn't work!
Progress now though! Blinking leds! Front AND back, when it stops and when pressed function key i get the CHDK logo!
-
Okay - here's the full build with everything turned on. Start testing !
CHDK for the IXUS200-SD980 firmward 1.01c (http://www.box.net/shared/0hpz0ittx1cbriu4nou0)
UPDATE : file updated 2011Jun12 to include philmoz fixes and built against trunk 1204
-
autoboot dont works :(
-
autoboot dont works :(
Strange - did it work with the Test4 version a few posts back ?
Update : I loaded it on my camera (not an SD980) just to see it autoboot, blink the AF led and then crash (as expected - wrong camera). So autoboot does work - you might have missed a step in configuring your SD card ? Did you remember to put the lock switch into the lock position ? What formatting procedure did you follow ?
-
locked switch - ok, formated with card tricks fat16 - ok, decompressed your file with card tricks to 2GB sdcard - ok, maked sdcard bootable - ok. Nothing else to do.
-
locked switch - ok, formated with card tricks fat16 - ok, decompressed your file with card tricks to 2GB sdcard - ok, maked sdcard bootable - ok. Nothing else to do.
I'm going to need a little more information if I'm going to be able to help here. What happens when you press the "Play" button to start (rather than the on/off switch) ? Does the AF led and green LED come on briefly and then the Orange LED ? Or does the display just say "Card Locked" ?
Also, did you try the Test4 version posted earlier ? I have confirmation that autoboot works with that file.
-
I tested both files for 1.01c. WHEN I push the play button the green LED is blinking. The display shows only "no image".
-
progress! cardtricks-->2GB--->locked turning on with play/review button gets the CHDK logo screen! (in orange, my favorite color, too)
autofocus led also blinks rapidly, i am able to read build info on splash screen, it lasts maybe 3 seconds, then shuts down, but does NOT lock up the camera; i can continue to turn on, and it tries to autoboot before shutting down.
what do we do next?
i was starting to think i would just have to sell this and get an SD940, but i REALLY want the 22/24mm wide angle lens on the 980- one of the main reasons for wanting this model.
waterwingz, you rock.
-
autofocus led also blinks rapidly, i am able to read build info on splash screen, it lasts maybe 3 seconds, then shuts down, but does NOT lock up the camera; i can continue to turn on, and it tries to autoboot before shutting down.
What do the last 8 words mean? Sounds like the camera starts up with CHDK running - the logo is supposed to display for about 3 seconds and then clear. Does the camera stay running at that point or shut down (crash). Can you press the Display button, get the <ALT> indicator on the screen and then the CHDK menus when you press Menu ?
It the camera crashes, did it crash the same way when you were running the Test4 version ?
i was starting to think i would just have to sell this and get an SD940, but i REALLY want the 22/24mm wide angle lens on the 980- one of the main reasons for wanting this model.
The SD940 is a really nice camera. 8)
waterwingz, you rock.
Thanks - but there is still a lot of work to do to make this port stable and I only have a little time available. Progress will slow down - I was hoping that once I had it building & booting (a BIG step) somebody with a little software knownledge could take over the debugging. We will see.
-
I tested both files for 1.01c. WHEN I push the play button the green LED is blinking. The display shows only "no image".
As jamabushi reports autoboot working properly, I have to assume something else is wrong. For example, if CHDK does not autoboot and the SD card lock switch is in the lock position, you should get a "Card Locked" error message - not "no image".
-
Thanks - but there is still a lot of work to do to make this port stable and I only have a little time available. Progress will slow down - I was hoping that once I had it building & booting (a BIG step) somebody with a little software knownledge could take over the debugging. We will see.
I have some time to look at the code if you want to send me a copy.
Phil.
-
I have some time to look at the code if you want to send me a copy.
Here you go : SD980 Source for fw 1.01c (http://www.box.net/shared/vd5968jifc3ryp5z893a)
Notes :
1) stubs_entry_2.S is a hybrid from the file you sent me from your new signature finder. Still a few things nullsub'd in there.
2) lib.c and stubs_min.S are just as I found them - probably need to be checked line by line
3) there is no ZSTEP_TABLE_SIZE & nTxtbl[] in core/kbd.c for this camera - something I only noticed because I have had to add it for all the other ports I've worked on
Related note : if we can't get an 8G ROM dump for the 1.00c, I'll use CHDK-PT to convert the stub_entry_2.S from this version. That should cover both firmware versions that people have mentioned.
-
I have some time to look at the code if you want to send me a copy.
Here you go : SD980 Source for fw 1.01c (http://www.box.net/shared/vd5968jifc3ryp5z893a)
Notes :
1) stubs_entry_2.S is a hybrid from the file you sent me from your new signature finder. Still a few things nullsub'd in there.
2) lib.c and stubs_min.S are just as I found them - probably need to be checked line by line
3) there is no ZSTEP_TABLE_SIZE & nTxtbl[] in core/kbd.c for this camera - something I only noticed because I have had to add it for all the other ports I've worked on
Related note : if we can't get an 8G ROM dump for the 1.00c, I'll use CHDK-PT to convert the stub_entry_2.S from this version. That should cover both firmware versions that people have mentioned.
Code looks pretty much ok.
Startup crash could be bad address for RefreshPhysicalScreen (this is one my new finder still has trouble with).
Here's some address updates I've found:
stubs_entry_2.s:
NHSTUB(RefreshPhysicalScreen,0xFF9F8694)
NHSTUB(ScreenLock,0xFF9F98B4)
NHSTUB(ScreenUnlock,0xFF9F98DC)
stubs_min.s:
DEF(FlashParamsTable,0xFFBDAB94)
DEF(levent_table,0xFFB7A2A0)
Phil.
-
What do the last 8 words mean? Sounds like the camera starts up with CHDK running - the logo is supposed to display for about 3 seconds and then clear. Does the camera stay running at that point or shut down (crash). Can you press the Display button, get the <ALT> indicator on the screen and then the CHDK menus when you press Menu ?
It the camera crashes, did it crash the same way when you were running the Test4 version ?
[/quote]
the logo does display for approx 3 sec. then clears with a crash- no response from any buttons unless i try to power on again. this behavior is consistent when using the power button on top as well, not just the play/view button, and the lens does not extend. it does this as long as the card is locked; unlocking returns camera to regular operation.
i think that test4 version didn't run for me, but i've been running around so much today i don't remember for sure. i can reload that version and check, if that will help?
you've definitely made the leap, hopefully we can maintain some momentum and lighten your load, too.
-
led blinks fast green, then orange, then goes back to green
CHDK logo shows up for 3 seconds then the camera shuts down again, seems its crashing on something thats loaded after the CHDK logo shows up
-
Hi all,
great that we have some progress here!
Okay - here's the full build with everything turned on. Start testing !
CHDK for the IXUS200-SD980 firmward 1.01c (http://www.box.net/shared/0hpz0ittx1cbriu4nou0)
I've tested this version. It boots okay as reported earlier. Front&Back LED blinking. CHDK Logo shows up for about 3 seconds and then camera turns off. When PLAY is pressed within the 3 seconds [alt] shows up. But entering CHDK Menu by pressing MENU then fails. Pressing MENU without [alt] enters the normal Menu but after 3 seconds camera turns off too.
I really appreciate your efforts. Looking forward to test new versions.
Simon
-
At first I used a SanDisk EXTREME III. Now , with a extrememory PREMIUM , its the same like simon96.
CHDK screen for 3 sec. and leds (green, orange) are flashing but the cam dont start.
-
Test5 based on the code waterwingz posted with the RefreshPhysicalScreen address fixed.
Phil.
Edit: Added source code .zip file for the Test5 changes to the platform directory.
-
thx philmoz!
ill give it a try
-
hmmm, seems to be working now, no crashes or shutdowns after FW loaded
also getting the CHDK menu now, also in p&s mode, the menu however keeps disappearing at times, when i press up/ down and such it reappears.
-
Super. I have to push the play button, thann the power button, than the play button again and the menu button, than CHDK shows all settings.
Ok, its not 100% yet but you are on the way.
thank you
-
i see a .fi2 is there also, so no need for a bootable card
i tried to use bracketing on the camera, but it doesnt work yet (chdk standard)
gonna try to use a script now
-
seems there is still a bug somewhere,
it keeps mentioning i need to be in REC mode, while im in shoot mode, guess something is set wrong :(
I imagine there will be many bugs to iron out - hopefully since it's running now things will progress.
It's late for me here, off to get some sleep - the code for the changes I made is in the previous post, in case waterwingz has some time to investigate.
Phil.
-
seems there is still a bug somewhere,
it keeps mentioning i need to be in REC mode, while im in shoot mode, guess something is set wrong :(
I imagine there will be many bugs to iron out - hopefully since it's running now things will progress.
It's late for me here, off to get some sleep - the code for the changes I made is in the previous post, in case waterwingz has some time to investigate.
Phil.
Atleast it works! Appreciate your efforts!
Sleep well
-
At first I used a SanDisk EXTREME III. Now , with a extrememory PREMIUM , its the same like simon96.
CHDK screen for 3 sec. and leds (green, orange) are flashing but the cam dont start.
This is the second time in two weeks somebody has had trouble booting with a particular SD card (http://en.wikipedia.org/wiki/Secure_Digital#Speed_Class_Rating). Too soon to say if its related to the speed - fastest cards that I have are Class 4 and your SanDisk is a class 6. Something for us to keep an eye on though.
-
also getting the CHDK menu now, also in p&s mode, the menu however keeps disappearing at times, when i press up/ down and such it reappears.
This is unfortunately seems to be normal in all ports of CHDK when you are in shooting mode. The Canon coded does not really support having foreign tasks writing to the screen - or at least nobody has figured out a good way to do that.
-
Super. I have to push the play button, thann the power button, than the play button again and the menu button, than CHDK shows all settings.
There is code in boot.c - currently commented out - that addresses the handling of the on/off switch. I left it commented out so as not to risk introducing an additional source of errors. Once other things settle we can try enabling it too.
-
Wow, definitely better than Version 4!
No shutting down or crashing whatsoever.
Menu appears in playback and in shoot mode.
Noticed some slight cases of menu disappearance while scrolling but it reappears if one keeps on scrolling.
Managed to show up some debug information in live view, however showing histogram data failed.
Saving RAW data seems to work.
GOOD WORK SO FAR!
So maybe now we should prioritize and work topically. So we can all focus on the same things at the same time.
Once again MANY THANKS FOR YOUR EFFORTS, philmoz and waterwingz!!!
-
Hey ALL.
I just want to say your doing great work!! thanks for picking up this port again.
-
<snip?
Saving RAW data seems to work.
<snip>
So maybe now we should prioritize and work topically. So we can all focus on the same things at the same time.
Looks like philmoz and I are both headed into a busy period for the next couple of weeks. Albeit on opposite sides of the globe.
To make things not come to a complete halt, I have a couple of requests.
1) Tell us what works. Like RAW & DNG. Post a list of things you have tested.
2) Tell us what does not work. Please be specific about the steps you followed and what happened. There is no length limit on what you are allowed to type in this forum.
Oh, and the menus disappearing when the background image changes (i.e. in shooting mode when you move the camera) is normal - there is currently nothing that can be done about that. Just use the up/down key to restore them.
Also, if anybody has a 1.00c camera, or any other firmware version, we need an 8G dump before we can go any farther supporting that. Lots of info on how to do that in this forum thread or over at the wiki. Post here if you need help.
-
I seem to have some problems using the HDR bracketing inside CHDK.
When camera is put on continious, and the EV is set to 2, both +- it keeps making very bright pictures, and doesnt use the -2 0 part.
Can anyone confirm?
-
i tried the latest recompile from waterwingz, works same, no pf2 file though, so autoboot is only option
also, the back option in the menu, when you are located in the scripting parameters doesn't work
i also cant seem to get the +2 0 -2 ev continious bracketing to work in here
-
Hi,
RAW file works fine but I'm unable to open the CRW file. Any suggestions?
Max
-
Hi,
RAW file works fine but I'm unable to open the CRW file. Any suggestions?
Max
Use the searchfunction. It has been mentioned so many times ...
Canon uses a diff kind of normal raw.
-
Hi,
RAW file works fine but I'm unable to open the CRW file. Any suggestions?
Max
Use the searchfunction. It has been mentioned so many times ...
Canon uses a diff kind of normal raw.
http://chdk.wikia.com/wiki/Raw (http://chdk.wikia.com/wiki/Raw)
http://chdk.setepontos.com/index.php?topic=1532.0 (http://chdk.setepontos.com/index.php?topic=1532.0)
-
Hi,
RAW file works fine but I'm unable to open the CRW file. Any suggestions?
Max
Use the searchfunction. It has been mentioned so many times ...
Canon uses a diff kind of normal raw.
http://chdk.wikia.com/wiki/Raw (http://chdk.wikia.com/wiki/Raw)
http://chdk.setepontos.com/index.php?topic=1532.0 (http://chdk.setepontos.com/index.php?topic=1532.0)
Thank for your suggestions :)
...now, I'm having some trouble when shot a photo: info on display shows, for example, 60/2.8 but the camera shutter stays open for much longer time and taken photos are all over exposed.
This issue occours also in fresh installed firmware.
-
Wow, i'm still impressed that finally I at least see the CHDK menu on my 200IS.
I was waiting for sooo long ;-)
Here are my first impressions of version TEST5:
Boots okay in Card Lock Boot Method AND in Firmware Update Method.
Extra Photo Operations: Seems like settings here have no effect whatsoever.
Video Parameters: Did not look into that.
Raw Parameters: Seems okay at first glance
Edge Overlay: Did not look into that.
Histogram Parameters: Live histograms are not working.
Zebra Parameters: If it is supposed to show up in live view (pressing shutter half) then it's not working.
OSD: Mostly working. Layout Editor working. Grid is not showing up. Battery percentage info seems wrong (shows 0).
Visual settings: working
Scripting Parameters: Scripts get loaded and can be started. However camera seems not to shoot (e.g. interval script is starting ok but no shooting at all).
Misc stuff: Did not test remote function.
Also noticed that somehow all pics get overexposed.
Simon
-
Here are my first impressions of version TEST5:
Boots okay in Card Lock Boot Method AND in Firmware Update Method.
Extra Photo Operations: Seems like settings here have no effect whatsoever.
Video Parameters: Did not look into that.
Raw Parameters: Seems okay at first glance
Edge Overlay: Did not look into that.
Histogram Parameters: Live histograms are not working.
Zebra Parameters: If it is supposed to show up in live view (pressing shutter half) then it's not working.
OSD: Mostly working. Layout Editor working. Grid is not showing up. Battery percentage info seems wrong (shows 0).
Visual settings: working
Scripting Parameters: Scripts get loaded and can be started. However camera seems not to shoot (e.g. interval script is starting ok but no shooting at all).
Misc stuff: Did not test remote function.
Also noticed that somehow all pics get overexposed.
Great start to a testing list Simon. As stated earlier, not much time to work on this right now. I suspect it needs a couple of hours looking at the values in stubs_min.S and lib.c - not sure these were well tested during the original port.
It would be interesting to know if movie recording still works ? Can you change the video quality if so ? (note : fast SD card required at top quality setting or recording will stop after a few seconds). Can you zoom the lens manually during video recording ?
I will give you one "free fix". The default range for the battery icon in the OSD is most likely set too high. You can change this in the OSD setup parameters - try setting the min to 0 and the max to 5V and see if you get a reading somewhere between that. With most cameras, you need to test a fully charged battery and then with a battery that has just reached the point of shutting down the camera to determine the correct range. Post the results here and I will change the defaults.
-
Here are my first impressions of version TEST5:
Boots okay in Card Lock Boot Method AND in Firmware Update Method.
Extra Photo Operations: Seems like settings here have no effect whatsoever.
Video Parameters: Did not look into that.
Raw Parameters: Seems okay at first glance
Edge Overlay: Did not look into that.
Histogram Parameters: Live histograms are not working.
Zebra Parameters: If it is supposed to show up in live view (pressing shutter half) then it's not working.
OSD: Mostly working. Layout Editor working. Grid is not showing up. Battery percentage info seems wrong (shows 0).
Visual settings: working
Scripting Parameters: Scripts get loaded and can be started. However camera seems not to shoot (e.g. interval script is starting ok but no shooting at all).
Misc stuff: Did not test remote function.
Also noticed that somehow all pics get overexposed.
Great start to a testing list Simon. As stated earlier, not much time to work on this right now. I suspect it needs a couple of hours looking at the values in stubs_min.S and lib.c - not sure these were well tested during the original port.
It would be interesting to know if movie recording still works ? Can you change the video quality if so ? (note : fast SD card required at top quality setting or recording will stop after a few seconds). Can you zoom the lens manually during video recording ?
I will give you one "free fix". The default range for the battery icon in the OSD is most likely set too high. You can change this in the OSD setup parameters - try setting the min to 0 and the max to 5V and see if you get a reading somewhere between that. With most cameras, you need to test a fully charged battery and then with a battery that has just reached the point of shutting down the camera to determine the correct range. Post the results here and I will change the defaults.
I made some tests in video mode and it seems works fine. Increasing "Video quality" I noticed also bitrates value is bigger but my sd is not very fast and the video was not really smooth.
Zoom works too but until you are inside the optical range, if enter in digital zoom you can't come back to optical.
I hope you help.
P.S. please please please take a look to raw issue :)
-
Zoom works too but until you are inside the optical range, if enter in digital zoom you can't come back to optical.
Got the same complaint on the A495 port. My SD940 does this as well so it seems to be a generic CHDK problem rather than port specific.
P.S. please please please take a look to raw issue :)
What raw issue ? Your earlier post only says "Raw Parameters: Seems okay at first glance"
-
Zoom works too but until you are inside the optical range, if enter in digital zoom you can't come back to optical.
Got the same complaint on the A495 port. My SD940 does this as well so it seems to be a generic CHDK problem rather than port specific.
P.S. please please please take a look to raw issue :)
What raw issue ? Your earlier post only says "Raw Parameters: Seems okay at first glance"
Here it is:
...now, I'm having some trouble when shot a photo: info on display shows, for example, 60/2.8 but the camera shutter stays open for much longer time and taken photos are all over exposed.
This issue occours also in fresh installed firmware.
-
Here it is:
...now, I'm having some trouble when shot a photo: info on display shows, for example, 60/2.8 but the camera shutter stays open for much longer time and taken photos are all over exposed.
This issue occours also in fresh installed firmware.
So is that only happening with RAW enabled ? Do you have the problem with normal JPG shooting when CHDK is loaded ?
-
Here it is:
...now, I'm having some trouble when shot a photo: info on display shows, for example, 60/2.8 but the camera shutter stays open for much longer time and taken photos are all over exposed.
This issue occours also in fresh installed firmware.
So is that only happening with RAW enabled ? Do you have the problem with normal JPG shooting when CHDK is loaded ?
I just made a new test with raw disabled and the same problem happens.
-
Got the same complaint on the A495 port. My SD940 does this as well so it seems to be a generic CHDK problem rather than port specific.
I found a way around this for the G12 and SX30 - see the special case code for these cameras in lens_set_zoom_point (platform/generic/wrappers.c).
You'll need to find the equivalent property values and function address for PT_MoveDigitalZoomToWide.
Phil.
-
Thanks waterwingz, changing min./max. value has indeed some effect on battery status information.
I can confirm that video recording works well. (Although I've not tested each and every quality level due to my poor sd card.)
Also same issues here with zoom in/zoom out behavior. Switching back to optical zoom failed.
As stated in my last post, images are constantly overexposed (regardless of the activation of raw capturing).
I think this could be related to the ineffective settings in Extra Photo Operations. Maybe somehow settings are predetermined or fixed in the first place. This could lead to a constant overexposure or wrong measures which then lead to overexposure.
I tried to took at stubs_min.S and lib.c but to be honest it's all greek to me ;-)
So i think it's up to you to push things forward here ;-)
Simon
-
As stated in my last post, images are constantly overexposed (regardless of the activation of raw capturing).
I think this could be related to the ineffective settings in Extra Photo Operations. Maybe somehow settings are predetermined or fixed in the first place. This could lead to a constant overexposure or wrong measures which then lead to overexposure.
@simon96 : Great feedback. You are probably correct about the exposure problem being related to the Extra Photo Operations. Is all likelyhood, something in stub_min.S is pointed at the wrong place. I'll wade through that but it won't be for a couple of days.
-
I'll wade through that but it won't be for a couple of days.
Hey there's no hurry. We're not in a rush. Take your time.
Waited for so long now, that "days" make no difference.
It won't raise boredom here. ;-)
It's great that you wanna stick to it, anyway.
Simon
-
-
Spent a happy couple of hours fixing up stubs_min.S and lib.c for firmware 1.01c.
Time for a little more testing please : IXUS200_SD980 firmware 101c Beta5 (http://www.box.net/shared/1bg4kidmsmr7ub3xn4g8)
Card lock boot method only as usual.
Let me know what you find - even if its just "boots" or "everything works". Frustrating not being able to test this myself to make sure it still at least boots.
-
Ciao !
Still some problems with the exposure.
When i set the iso to 80, the image is reasonable decent, but looking @ EXIF the exposure time is way too high.
When CHDK is loaded, exposure is going 1/15 or 1/20, and when i take a picture without CHDK it lowers to 0.5/0.6.
Setting disable overrides in the extra photo menu doesnt help, also making pictures with EV +/ 2 in continiousmode, crashes the camera at the 2nd picture taken continiously.
Will post more when i find it. Thx again for the new beta
Edit1: shows battery time at 0%, and raw are also over exposed.
Edit2: seems the problem is more related to the ISO values always going to 800 when they are set to auto that cause the exposure time to be raised., when manually setting ISO to 80 it lowers the exposure time and pictures are decent enough.
-
Still some problems with the exposure.
Always a good idea to delete the CCHDK.CFG file when before loading a new version. Delete it from your card and see if that helps ?
Edit1: shows battery time at 0%, and raw are also over exposed.
from one of my previous posts here :
I will give you one "free fix". The default range for the battery icon in the OSD is most likely set too high. You can change this in the OSD setup parameters - try setting the min to 0 and the max to 5V and see if you get a reading somewhere between that. With most cameras, you need to test a fully charged battery and then with a battery that has just reached the point of shutting down the camera to determine the correct range. Post the results here and I will change the defaults.
-
Always a good idea to delete the CCHDK.CFG file when before loading a new version. Delete it from your card and see if that helps ?
I always reformat the card before im trying a new test version, everything is fresh.
from one of my previous posts here :
I will give you one "free fix". The default range for the battery icon in the OSD is most likely set too high. You can change this in the OSD setup parameters - try setting the min to 0 and the max to 5V and see if you get a reading somewhere between that. With most cameras, you need to test a fully charged battery and then with a battery that has just reached the point of shutting down the camera to determine the correct range. Post the results here and I will change the defaults.
Ill check that out, thx!
-
@titbb
... shows battery time at 0% ...
You might want to try MAX = 4100, MIN = 3000 mV as a first approximation.
That works for my S95 (which uses the same battery: NB-6L)
wim
-
@titbb
... shows battery time at 0% ...
You might want to try MAX = 4100, MIN = 3000 mV as a first approximation.
That works for my S95 (which uses the same battery: NB-6L)
wim
I'll update the defaults with that - my SD940 is close to that too.
-
I found a way around this for the G12 and SX30 - see the special case code for these cameras in lens_set_zoom_point (platform/generic/wrappers.c).
@philmoz : Put the changes into a test build for my camera but before building it I did some more testing. In video mode, if the camera goes from mechanical to digital zoom, then when later you zoom back out it stops when it hits the wide limit for digital zoom.
But, at this point if I release the zoom lever and then re-engage, it will continue to zoom out mechanically.
Not sure I really need to go ahead with your patch then - is this not how the G12 works ?
-
I found a way around this for the G12 and SX30 - see the special case code for these cameras in lens_set_zoom_point (platform/generic/wrappers.c).
@philmoz : Put the changes into a test build for my camera but before building it I did some more testing. In video mode, if the camera goes from mechanical to digital zoom, then when later you zoom back out it stops when it hits the wide limit for digital zoom.
But, at this point if I release the zoom lever and then re-engage, it will continue to zoom out mechanically.
Not sure I really need to go ahead with your patch then - is this not how the G12 works ?
No, on the G12 once you zoom into the digital range in video mode you're stuck there (without the patch I added).
With the patch I get the same behaviour as you do - zooming out of digital stops at the wide end of the digital range; but releasing and re-pressing the zoom lever will continue on.
Phil.
-
Fixed the battery defaults :
IXUS200-SD980 firmware 1.01c BETA 6 (http://www.box.net/shared/1bg4kidmsmr7ub3xn4g8)
-
Great progress!
On the quick:
Histogram seems to work now.
Edge overlay seems to work now too.
Grid works too, but grid is not centered on display (rather left-aligned).
Battery status ok (BETA6).
Not looked into video zoom issues.
Still issues with shoot from scripts. Maybe we can agree on some test procedures to sort this out.
Still issues with over exposure. Same as with scipts: Maybe we all could agree on the same test routines. This should simplify solving the problem.
Simon
-
Edge overlay seems to work now too.
Grid works too, but grid is not centered on display (rather left-aligned).
Can you tell if edge overlay has a centering problem too. Typically edge overlay, zebra and grid will display incorrectly if the camera pixel size of the display or the "ASPECT" scaling parameters are wrong. Can you or somebody else confirm the X & Y resolution of the display - the quick look I took via the reviews in the wiki only gives a useless total pixel count.
Not looked into video zoom issues.
I didn't attempt to fix anything there although I did look at philmoz's patch for the G12.
Still issues with shoot from scripts. Maybe we can agree on some test procedures to sort this out.
Still issues with over exposure. Same as with scipts: Maybe we all could agree on the same test routines. This should simplify solving the problem.
I believe several things have changed with scripts over the years and I suspect some older script tried to shoot in different ways. Try this lua script ( call the file multishoot.lua ) :
--[[
@title LUA Test 1
--]]
repeat
press("shoot_full")
release("shoot_full")
sleep(5000)
until false
or this (call it multishoot.bas) :
rem Test Shooting
@title Shoot Test
:nextshot
press "shoot_half"
sleep 5000
press "shoot_full"
sleep 500
release "shoot_full"
release "shoot_half"
sleep 2000
goto "nextshot"
-
I confirm the issues with over exposure :(
-
Waterwingz you are right, zebra & edge suffer from the same de-centering.
Your example script did not shoot once started, although it behaved like it should, like
"wait, half press shutter (red front light on), [full press shutter], start again".
It does everything except full press shutter.
Simon
-
Waterwingz you are right, zebra & edge suffer from the same de-centering.
So now I need somebody to confirm the size of the LCD display in pixels (x & y - not total count).
Your example script did not shoot once started, although it behaved like it should, like
"wait, half press shutter (red front light on), [full press shutter], start again".
It does everything except full press shutter.
Did you try both scripts ?
-
Can not find any info about real xy resolution. 320x240 like other 3" canon lcd's?
SORRY: Re-tried both scripts multishoot.bas WORKED!
Simon
-
Can not find any info about real xy resolution. 320x240 like other 3" canon lcd's?
Not sure - marketing literature suggests its a bigger display.
SORRY: Re-tried both scripts multishoot.bas WORKED!
CAM_PROPSET is set to 2 - other cameras from that time period use 3. I guess I need to check everything done in the original 1.00c port.
-
Wait, multishoot.lua also seems to work now that i've tried a third time.
Don't know exactly what i missed the first time. Sorry. So please dont bother with scripting.
So how can we pinpoint the correct measures of the display? Some kind of test background image?
-
Can not find any info about real xy resolution. 320x240 like other 3" canon lcd's?
Not sure - marketing literature suggests its a bigger display.
SORRY: Re-tried both scripts multishoot.bas WORKED!
CAM_PROPSET is set to 2 - other cameras from that time period use 3. I guess I need to check everything done in the original 1.00c port.
It's a dryos R39 cam, so my bet would be 3
-
It's a dryos R39 cam, so my bet would be 3
I'll rebuild with 3. How did you now its an R39 ?
-
@waterwingz
How did you now its an R39
It's in the dump strings, search for "DRYOS version" ... for example, from strings.txt for 101c:
00000032EAC4 00000032EAC4 0 DRYOS version 2.3, release #0039
hth,
wim
-
It's in the dump strings, search for "DRYOS version" ...
<snip>
hth,
Yup - that helps a lot. I've been ignoring that file - the one that gets packaged with all the firmware dumps. I guess I assumed it was a hang-over from the days before people who have access it IDA finished all the macros used in CHDK dissassembly.
-
It's a dryos R39 cam, so my bet would be 3
I'll rebuild with 3. How did you now its an R39 ?
vim PRIMARY.BIN
/#00
;)
-
the one that gets packaged with all the firmware dumps.
Those strings files are generated with McAfee's (free) BinText utility
* http://www.mcafee.com/de/downloads/free-tools/bintext.aspx (http://www.mcafee.com/de/downloads/free-tools/bintext.aspx)
-
Beta 7 for 1.01c firmware - changed PROPSET from 2 to 3. This should fix a few things.
IXUS200-SD980 firmware 1.01C Beta 7 (http://www.box.net/shared/blj2yvkun36ykobonsc9)
Still need more info on LCD XY resolution.
-
Still need more info on LCD XY resolution.
The LCD resolution doesn't matter; but the aspect ratio does.
It looks like it has a 16:9 LCD display - take a look at what Brend R did with the Ixus 1000 (I think).
I added some additional functions in lib.c for handling multiple image aspect ratios (see G12). There are defaults for these that you will probably need to override.
Also the viewport display width and buffer width may be different (again this can be handled in the new functions in lib.c).
It would help to see a photo of what the zebra/edge overlay actually looks like on the LCD.
Phil.
-
Phil, I attach two images of what the grid overlay looks like (on BETA6).
Hope this will help. If you really need a picture of the edge overlay please let me know.
Simon
-
Phil, I attach two images of what the grid overlay looks like (on BETA6).
Hope this will help. If you really need a picture of the edge overlay please let me know.
Simon
Thanks for that, yes a photo of the edge/zebra would help.
Grids are a different problem - they were designed for 4:3 LCD displays and the grid code isn't really set up to handle a 16:9 display. I think there were some work arounds done for the Ixus 1000; but there are fundamental problems that need to be solved. For example the 3:2 grid on a 4:3 display shows two lines, one near the top and one near the bottom - what should this grid look like on a 16:9 LCD? I think it should be two vertical lines; but there is no easy way to transform the grid file to do this in the code.
Phil.
-
Beta 7 for 1.01c firmware - changed PROPSET from 2 to 3. This should fix a few things.
IXUS200-SD980 firmware 1.01C Beta 7 (http://www.box.net/shared/blj2yvkun36ykobonsc9)
Yeah! Looks like over exposure issue is gone! This really rocks!
Thank you very much!
Simon
-
Beta 7 for 1.01c firmware - changed PROPSET from 2 to 3. This should fix a few things.
IXUS200-SD980 firmware 1.01C Beta 7 (http://www.box.net/shared/blj2yvkun36ykobonsc9)
Yeah! Looks like over exposure issue is gone! This really rocks!
Thank you very much!
Simon
Yes, I confirm that shoot works fine, also in dng format.
Just one strange thing: when I try to turn on the camera in record mode, after the cdhk logo, it power off automatically while switching from play mode it works like a charm.
Max
-
Thanks for that, yes a photo of the edge/zebra would help.
Okay here are two pics of edge overlay.
-
... and here are two pics of zebra which is actually not working correctly.
This is what happens when I half press shutter.
-
Thanks for that, yes a photo of the edge/zebra would help.
Okay here are two pics of edge overlay.
Well the zebra looks really weird but at least the edge overlay is recognizable so lets start there.
What does the edge overlay look like if the camera image size is set to 16:9 (again a photo would help)?
Phil.
-
I own this camera, and I basically need CHDK for this camera to be worth anything to me.
So, I figured I'd finally try to assist after lurking this thread for so long.
The LCD display is said to be "230,000" pixels on various sites. It is 16:9.
Using this handy chart on wikipedia: http://en.wikipedia.org/wiki/List_of_common_resolutions (http://en.wikipedia.org/wiki/List_of_common_resolutions)
You can see that 230,000 pixels must be 640x360. Although in that chart the closest thing is 230,400 pixels. So maybe it's a few horizontal lines short of that.
If you need high resolution images of the camera doing anything in CHDK I'll try to get that for you.
-
Well the zebra looks really weird but at least the edge overlay is recognizable so lets start there.
What does the edge overlay look like if the camera image size is set to 16:9 (again a photo would help)?
Phil.
I'm not sure that one can actually change the size of the live view image. Think it is fixed at 4:3.
-
Well the zebra looks really weird but at least the edge overlay is recognizable so lets start there.
What does the edge overlay look like if the camera image size is set to 16:9 (again a photo would help)?
Phil.
I'm not sure that one can actually change the size of the live view image. Think it is fixed at 4:3.
The sensor is 4:3; but according to the manual (pg. 73) you can change the image size to 'W' (widescreen) which should be a 16:9 image (4000 x 2248 pixels). This will capture a cropped portion of the sensor.
If it works like the Ixus 1000 then the image should fill the live view area.
Phil.
-
Ah okay, I understand. Will have a look at it when i'm back home. Simon
-
Okay, here are edge overlay test photos i've taken with wide screen live view size.
Hope they help as motives and quality are kind of [admin: avoid swearing please]. So if you need something specific, please let me know.
-
With lots of help from philmoz, here's a new Beta version that we hope will address some of the problems with zebra & edge overlay.
IXUS200-SD980 firmware 1.01C Beta 8 (http://www.box.net/shared/x6sd7lv5im7b94mhuvhm)
Also, can anybody confirm they have RAW and DNG working ?
Edit : now at Beta 9 or higher
-
I enabled RAW and DNG. It's not saving RAW files now. Earlier betas were savings RAWs. It is saving DNG files however. They also seem to be properly formed. I opened one up in photoshop.
I created a badpixel.bin using the camera. It seems to have actually saved the two shots it takes to do that. I don't remember that being the case on my a480.
-
This release has working bracketing for me. That's a huge one for me. Thanks for getting this so far.
I've just barely tested this beta, but so far it's looking really good.
Thanks again to everyone involved with this.
-
If I turn off DNG saving I do get RAW files. Maybe this is how it is supposed to work?
-
Upon playing around with bracketing some more, I've found that Tv bracketing doesn't work with the custom timer set to multiple shots. It only works with regular continuous mode with the shutter button held down.
I suppose I can get by with a script to do steady brackets.
-
Here are two sets of images. One is a DNG and the corresponding JPG file. The second is a RAW and the JPG.
https://sites.google.com/site/tylervagle/files/IMG_0002.JPG
https://sites.google.com/site/tylervagle/files/CRW_0002.DNG
https://sites.google.com/site/tylervagle/files/IMG_0010.JPG
https://sites.google.com/site/tylervagle/files/CRW_0010.CR2
Both sets are of the same scene with the same lighting and exposure.
It is kind of impressive how much post processing the camera is doing to the RAW. the DNG is a nice middle ground. I shot these at maximum zoom out. ISO 80. You can probably see all that in the exif.
-
If I turn off DNG saving I do get RAW files. Maybe this is how it is supposed to work?
Yes.
-
Upon playing around with bracketing some more, I've found that Tv bracketing doesn't work with the custom timer set to multiple shots. It only works with regular continuous mode with the shutter button held down.
I have not played with bracketing much so I'm not sure how its supposed to work, but this does not sound like something related to the 1.01C port - more a CHDK general thing.
-
Upon playing around with bracketing some more, I've found that Tv bracketing doesn't work with the custom timer set to multiple shots. It only works with regular continuous mode with the shutter button held down.
I have not played with bracketing much so I'm not sure how its supposed to work, but this does not sound like something related to the 1.01C port - more a CHDK general thing.
I have done a lot of bracketing on an a480 with CHDK. I can use the custom timer, and it is consider the "right" way to do HDR stacks these days. The custom timer replaced many scripts.
-
Some of you might find this interesting.
Here is an HDR made with jpgs.
https://sites.google.com/site/tylervagle/files/HDR-Jpg-based.jpg
Here is the same basic scene with the same hdr processing settings but done with dngs.
https://sites.google.com/site/tylervagle/files/HDR-Dng-based.jpg
The jpegs look better. The fish eye effect of the actual lens with no correction is pretty interesting though
with the DNGs.
Compared to the DNGs my a480 spits out, the ones from the sd980 seem to have more dynamic range available in them, and less noise.
The colors are magically awful in the straight RAWs. Everything is sort of puke green.
-
I have done a lot of bracketing on an a480 with CHDK. I can use the custom timer, and it is consider the "right" way to do HDR stacks these days. The custom timer replaced many scripts.
Thanks - learned something new tonight. I didn't even know my camera (SD940) had a "custom timer". It was kind of hard to find but knowing it was somewhere, I got it. Now to play HDR stack.
-
Some of you might find this interesting.
Here is an HDR made with jpgs.
These are even more striking when compared to the jpgs you posted earlier in this forum.
-
There is a little bit of blurring in the HDRs because my hand is shaking while I hold down the shutter button.
-
Here is an HDR made with jpgs.
https://sites.google.com/site/tylervagle/files/HDR-Jpg-based.jpg
Here is the same basic scene with the same hdr processing settings but done with dngs.
https://sites.google.com/site/tylervagle/files/HDR-Dng-based.jpg
The jpegs look better. The fish eye effect of the actual lens with no correction is pretty interesting though with the DNGs.
The DNGs appear quite blurred compared to the jpeg. There is obvious camera movement between the shots, but in the jpegs they appear quite distinct. Canon jpegs generally have sharpening to counteract the mud from their noise reduction, but seems like something else might be going on.
The DNG is a bit warmer, but it's pretty close for a first cut color calibration.
The colors are magically awful in the straight RAWs. Everything is sort of puke green.
That's down to whatever software you are using to display/manipulate the CHDK raw. The image data is identical to what is used in DNG (except for badpixel removal) CHDK raw doesn't have *any* metadata, so without additional information, programs that load it have to take a wild guess at the colors.
-
I can't seem to get any of the old bracketing scripts to work.
-
More HDR Experiments
https://sites.google.com/site/tylervagle/files/photoshop-hdr-jpegs.jpg
https://sites.google.com/site/tylervagle/files/photoshop-hdr-DNGs-lens-corrected.jpg
These are done in photoshop and are much more natural than my previous HDRs. I did a custom lens correction on the dngs. I think it looks better than what the camera does internally on the jpegs.
The dng based one looks more like reality to me.
-
Upon playing around with bracketing some more, I've found that Tv bracketing doesn't work with the custom timer set to multiple shots. It only works with regular continuous mode with the shutter button held down.
@reyalp : should the IXUS200 be added to the list of cameras in shooting_get_drive_mode() (in platform\generic\shooting.c) that use
_GetPropertyCase(PROPCASE_TIMER_MODE, &n, sizeof(n));
rather than
_GetPropertyCase(PROPCASE_DRIVE_MODE, &m, sizeof(m));
-
@reyalp : should the IXUS200 be added to the list of cameras in shooting_get_drive_mode() ( in shooting.c) that use
_GetPropertyCase(PROPCASE_TIMER_MODE, &n, sizeof(n));
rather than
_GetPropertyCase(PROPCASE_DRIVE_MODE, &m, sizeof(m));
Sound likely.
-
Latest test build : IXUS200_SD980 firmware 1.01C Beta 9 (http://www.box.net/shared/83zabfkxn7chld333o60)
@trif : Please test to see of Tv bracketing now works with the custom timer ?
-
Again, really good work!
Tv bracketing works fine now with custom timer.
Edge overlay looks good now in 4:3 but it is out of alignment in 16:9 wide mode.
Quite contrary to zebra which is working ok now in 16:9 but is out of alignment in 4:3.
Thanks everyone!
Simon
-
Again, really good work!
Tv bracketing works fine now with custom timer.
Edge overlay looks good now in 4:3 but it is out of alignment in 16:9 wide mode.
Quite contrary to zebra which is working ok now in 16:9 but is out of alignment in 4:3.
Thanks everyone!
Simon
Good news!
Can you post some more sample images so I can try and work out the edge / zebra problems.
Phil.
-
Good news!
Can you post some more sample images so I can try and work out the edge / zebra problems.
Phil.
Sure. Here are the edge pics.
-
... and here are the zebra pics.
-
Latest test build : IXUS200_SD980 firmware 1.01C Beta 10 (http://www.box.net/shared/83zabfkxn7chld333o60)
@simon96 : per a philmoz request, I reverted the routine *vid_get_viewport_fb() to an earlier version. Please test zebra and edge overlay again and post new pictures ?
-
woot woot!
grabbing beta 10 now to test, thx!
-
@waterwingz:
Now both (zebra&edge) are correct in 16:9 but both out of alignment in 4:3.
Trying to make a few pics. Think the incorrect 4:3 will be sufficient?!?
Simon
-
Now both (zebra&edge) are correct in 16:9 but both out of alignment in 4:3.
Trying to make a few pics. Think the incorrect 4:3 will be sufficient?!?
Thanks - that tells us something. I suspect philmoz is asleep and I know that I'm online on my lunch hour. We'll take a look later - we are very close here and once this is done I'm going to tie a bow on it and submit to the autobuild server. Great team work on this one !
-
HDR bracketing seems to work nice and pretty fast too even!
MD script seems to also work perfectly fast!
Histogram also works on my card.
Raw also works quite well atm
ND filter also seems to work.
-
Please somebody tell me how to activate extra photo operation (on, off or disable?)... autobracketing seems not to works for me. I flagged "include auto iso and bracketing", in "bracketing in continuous mode" i set 2 ev in "tv bracketing value", and +/- in "bracketing type". Once i set the custom timer i shot 3 pics with no differences (but overexposed). Any tip? I have the beta 10.
All the pics i shot are totally overexposed...
-
@Dummi
Make sure you're really using BETA10 first.
On a FRESH install go to Extra Photo Operations/Bracketing in Continuous Mode/ and set TV Bracketing Mode to 2/3 Ev.
Then activate custom time and set it to 3 pics. Press the shutter. It should then take three pictures.
One should be ok, one over- and one underexposed. It works!
-
Does anyone can help me to make necessary postprocessing steps with photoshop to make the raw image quality like the jpeg?
thank you in advance
Max
-
Does anyone can help me to make necessary postprocessing steps with photoshop to make the raw image quality like the jpeg?
@maxbaron : If you read through all the debate about RAW vs JPEG on this forum, you might come to understand why I find your post is amusing. In any case, here's some things to look at.
CHDK Wiki RAW/DNG Page (http://chdk.wikia.com/wiki/Raw)
CHDK Forum on RAW Thread (http://chdk.setepontos.com/index.php?topic=1532.0)
CHDK Forum on Raw Processing Thread (http://chdk.setepontos.com/index.php?topic=6328.0)
Also, you might get more responses by making any further posts in the last thread above rather than in a SD980 specific thread.
-
Hello, this might be a stupid question, but I don't know how to take pictures with CHDK (Ixus200)?
I have CHDK on a 1GB card, and it boots up just fine, but it boots up into a play mode, how can
I change mode so that it will open objective and to be ready to shoot? If I press on/off key, it will
just shutdown...
-
Hello, this might be a stupid question, but I don't know how to take pictures with CHDK (Ixus200)?
I have CHDK on a 1GB card, and it boots up just fine, but it boots up into a play mode, how can
I change mode so that it will open objective and to be ready to shoot? If I press on/off key, it will
just shutdown...
Two choices :
1) When the camera is off, start the camera with the Play mode key. Then press the shutter (shoot) button briefly to change into shooting mode.
2) When the camera is off, hold the On/Off key for 2 seconds. (That might or might not not work - I think I need to enable that code for that yet - sorry.)
-
Ok, Thanks, I need to test those!
-
@waterwingz:
Now both (zebra&edge) are correct in 16:9 but both out of alignment in 4:3.
Trying to make a few pics. Think the incorrect 4:3 will be sufficient?!?
Simon
Thanks Simon, I think we're getting close.
Can you do the following for me please.
- Go into the CHDK > Miscellaneous stuff > Debug parameters menu
- Set Debug data display to Props
- Set the PropCase/ParamsData page to 29
- Exit CHDK Alt mode
- Set the Image Size to 4:3 and note the value set for property 294 on the CHDK OSD
- Change the Image Size to 16:9 and again record the property 294 value.
- Change the PropCase/ParamsData page to 4
- Record the value for property 49 in both 4:3 and 16:9 modes.
- Post the property values.
Phil.
-
@phil
value for property 294 stays 0 on both 4:3 and 16:9
value for property 49 is 32772 on both 4:3 and 16:9
-
@phil
value for property 294 stays 0 on both 4:3 and 16:9
value for property 49 is 32772 on both 4:3 and 16:9
Odd; but that would explain why it doesn't work.
A couple more things to check.
- Record the value of property 220 (page 22) for each of the image sizes (L, M1, M2, M3, S & W).
- Check if any other property on page 29 or 30 changes to 1 when you select the 'W' image size (16:9); but is 0 for all other image sizes.
Phil.
-
value for property 220
L=0
M1=1
M2=2
M3=3
S=4
W=8
All properties on page 29 & 30 stay 0 when changing to any image size.
-
value for property 220
L=0 M1=1 M2=2 M3=3 S=4 W=8
All properties on page 29 & 30 stay 0 when changing to any image size.
Got the same thing testing the SD940. Philmoz sent me code changes based on this - cross your fingers and take a look. How do edge overlay and zebra look now ?
IXUS200-SD980 Firmware 1.01c Beta 11 (http://www.box.net/shared/6q86hbeccua1u0sypgq0)
-
Well, mission accomplished! ;-)
Edge/zebra looking perfect now in 4:3 AND 16:9.
Thank you very much! You did a wonderful job!
Think we're ready to merge to upstream code.
KEWL!!!!!
Simon
-
Well, mission accomplished! ;-)
Merged into the main trunk code today. Should be available via the autobuild server within the next 24 hours.
That was fun !
-
THX all :)
-
Wow! :o
my internet connection's been down for a while now ( a big deal out here in the boonies), and i'm amazed by the progress i missed.
I want to thank everyone for all their hard work. This has brought this neat little p&s into a whole other league, thanks to you guys.
the last version i was able to get was beta 5, so i'm chomping at the bit for the autobuild, especially since i have to drive into town for a connection... ahhh, country livin'.
you guys rock.
-
got it.
stoked.
thanks.
-
In this final release the bracketing don't works anymore
-
in beta 11 the bracketing works just fine
-
In this final release the bracketing don't works anymore
in beta 11 the bracketing works just fine
I know what the problem is - I'll post an update in the next 12 hours. Sorry about that.
Likely relates to this : http://chdk.setepontos.com/index.php?topic=4335.msg69137#msg69137 (http://chdk.setepontos.com/index.php?topic=4335.msg69137#msg69137) I missed this in the patch file for the official release.
-
i grabbed the autobuild from the CHDK server, and bracketing still works nicely, didnt test on custom timer yet
-
tibb it's just with the custom timer that don't works
-
In this final release the bracketing don't works anymore
in beta 11 the bracketing works just fine
I know what the problem is - I'll post an update in the next 12 hours. Sorry about that.
Likely relates to this : http://chdk.setepontos.com/index.php?topic=4335.msg69137#msg69137 (http://chdk.setepontos.com/index.php?topic=4335.msg69137#msg69137) I missed this in the patch file for the official release.
don't worry waterwings... i am very grateful to you!!
-
don't worry waterwings... i am very grateful to you!!
Thanks !
I submitted a patch file to fix this. If it gets in tonight, there should be a working version in the autobuild server tomorrow.
-
don't worry waterwings... i am very grateful to you!!
We all are ;)
-
I found 2 bugs in the last release of the great waterwings.
When in video mode and set the following values: quality - 99, the recording stops at 1 second.
Furthermore, in the recording, you can zoom in but you can't zoom out.
A question: how to delete the limit of 1 gb in video records?
-
When in video mode and set the following values: quality - 99, the recording stops at 1 second.
This usually a problem related to the speed of your SD card. At maximum quality, the camera generates data faster than it can be written to the SD card so it just stops recording. There is nothing CHDK can do to fix that. Either record at lower "quality" or buy a really fast SD card.
Furthermore, in the recording, you can zoom in but you can't zoom out.
You can zoom in & out as long as you don't transition from mechanical to software zoom. This is a know bug in CHDK that affects several camera models. There is a "fix" from philmoz for a couple of cameras but it has not been implemented on the SD980.
A question: how to delete the limit of 1 gb in video records?
Unknown.
-
Can someone please repost some of the earlier beta builds? Whatever is currently on autobuild does not work for my sd980. My firmware is unknown as SET + display w/ ver.req or vers.req does not work. What does happen is a solid orange light immediately after confirming ok to the firmware update.
-
Found this in my box.net deleted file. Sometimes you just get lucky.
ixus200_sd980-101c-0.9.9-r1206-Beta10.zip (http://www.box.net/shared/0pdnbrz1cure1egkduxt)
Let us know if it works - seems strange that the autobuild version did not run for you.
-
@gbit - what does ACID say about your firmware version. It's usually very reliable. See http://www.zenoshrdlu.com/acid/acid.html (http://www.zenoshrdlu.com/acid/acid.html)
-
Well I appreciate the help but it appears like I am on firmware 1.0.1d :(.
Can I dump this firmware for yall? If so, how difficult/long may it take to bring CHDK over? Normally I would not ask such a question as I understand that no one pays yall for doing this great work, but I purchased this camera thinking it would have 1.0.1c on it and for a business project that has an approaching deadline. If I can't make use of this camera I will have to purchase a different camera.
-
As soon as I get to work I will follow this guide http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup (http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup) as someone here earlier in the thread did this to get the full dump on 1.0.1c. Whether I keep this camera or not at least we will have the firmware for 1.0.1d.
-
Here is a firmware dump of 1.0.1d! I hope porting it over to this firmware is a relatively easy exercise since the work has already been accomplished on 1.0.1c. The firmware dump is 8,124kb in size and the cbdumper.log file says
Started
FF810000 dry
done
http://www.multiupload.com/R5K4T19WXA (http://www.multiupload.com/R5K4T19WXA)
-
Can I dump this firmware for yall? If so, how difficult/long may it take to bring CHDK over? Normally I would not ask such a question as I understand that no one pays yall for doing this great work, but I purchased this camera thinking it would have 1.0.1c on it and for a business project that has an approaching deadline. If I can't make use of this camera I will have to purchase a different camera.
I'm backlogged for at least the next two months with stuff I've already committed to doing so I can't help you here. Standard CHDK disclaimer available here : CHDK porting status (http://chdk.wikia.com/wiki/FAQ#Q._My_camera_isn.27t_ported_yet._Is_a_port_planned.C2.A0.3F_When_will_it_be_ready.C2.A0.3F_How_can_I_help.C2.A0.3F)
-
Thanks for letting me know waterwingz. I will get started on it this weekend then. (If anyone is also interested and has more experience then please let me know.) I will be posting my progess as I go along if I have issues and can't find the documentation to help me get through it. There is so much documentation though I feel like that is likely not going to be much of an issue :).
Also in your opinion if I follow the documentation in these forums and use your CHDK-PT program, do think this is something that I can do in a weekend? I've done some basic programming in C++, Java, and mostly PHP.
-
Thanks for letting me know waterwingz. I will get started on it this weekend then. (If anyone is also interested and has more experience then please let me know.) I will be posting my progess as I go along if I have issues and can't find the documentation to help me get through it. There is so much documentation though I feel like that is likely not going to be much of an issue :).
Also in your opinion if I follow the documentation in these forums and use your CHDK-PT program, do think this is something that I can do in a weekend? I've done some basic programming in C++, Java, and mostly PHP.
A port between firmware versions if you really know what you are doing takes 4 to 8 hours. I would expect it will take you longer but two 10 hour days might do it. Just a guess.
I'll keep an eye on the #chdk IRC channel - faster help that the forum.
UPDATE : I attached a file that should help you with the CHDK=PT conversion
-
CHDK for firmware 1.0.1d (BETA 2)
I completed this just before midnight and so far it appears to work just fine on my camera. Although when I am in the CHDK menu while in the P Mode it appears like the menu sometimes disappears randomly. The menu works much better while in playback mode from my experience. Not sure if this is an issue with 1.0.1c beta as well or just my port to 1.0.1d.
Also the estimation on how long this would take was pretty close, I'd say it took me about 8 hours and even 10 if you include the time I wasted on figuring out ps.fi2.. and then the issues I had with using a SDHC card to boot the dang thing.. I have a lot of 2gb SD cards as well though for testing & older cameras. Although that addresses file provided by waterwingz did save me some time as well.
Thanks to waterwingz for the awesome work and assistance, as well as relayp over in IRC.
Here is the file, and like usual I take no responsibility for the damage or it may or may not cause. :)
-
Wow - congratulations. I think you are actually the first "newbie" to complete a port from one firmware version to another of the same camera using CHDK-PT !
Although when I am in the CHDK menu while in the P Mode it appears like the menu sometimes disappears randomly. The menu works much better while in playback mode from my experience. Not sure if this is an issue with 1.0.1c beta as well or just my port to 1.0.1d.
This tends to be a issue for all versions of CHDK on all (recent) cameras. A limitation of CHDK's ability to work with the Canon firmware to share the screen.
Also the estimation on how long this would take was pretty close, I'd say it took me about 8 hours and even 10 if you include the time I wasted on figuring out ps.fi2.. and then the issues I had with using a SDHC card to boot the dang thing.. I have a lot of 2gb SD cards as well though for testing & older cameras. Although that addresses file provided by waterwingz did save me some time as well.
Did you also use philmoz's new sigfinder ? There were a bunch of things that it found in the 1.01C code that really should be checked.
-
Wow - congratulations. I think you are actually the first "newbie" to complete a port from one firmware version to another of the same camera using CHDK-PT !
Thanks, I was pretty motivated to get this ported. I have a timelapse scene I need to do for a video project which will be shown on the largest HD screen in the world (Dallas Cowboy Stadium). I also did not want to have to return this camera. It has an awesome 24mm wide lens and the alternative was the S3 IS with 28mm, but at twice the cost and no discernable advantage for my particular setup I wanted to make this camera work.
Did you also use philmoz's new sigfinder ? There were a bunch of things that it found in the 1.01C code that really should be checked.
Actually I did not get to installing the new sigfinder. I may do so during the week though, particularly if I find that I am unable to run scripts on it 24/7 for the next few days.
I am a bit surprised that there is not even more activity on getting all of these canon cameras and their fw revisions CHDK'd. The tools and the documentation are surprisingly good and mature. I know I had moments of frustration, but it could have been a lot worse. I really appreciate all the help and the tools to make it happen.
-
Actually I did not get to installing the new sigfinder. I may do so during the week though, particularly if I find that I am unable to run scripts on it 24/7 for the next few days.
I am a bit surprised that there is not even more activity on getting all of these canon cameras and their fw revisions CHDK'd.
So what are you going to do next with your source ? If you want to zip the sub directory and send it to me, I can convert quickly to a patch file for the trunk. Or you can read up on Tortoise.svn tools and do it yourself.
Prior to doing that though, I'd run the new sigfinder and look at what the revised stubs_entry.S tells you. A little clean-up is probably warranted if you just accepted what came in with the 1.00c port.
-
Well for now here is the source, I have not ran the sigfinder against it, but when I compare the stubs_entry.S file to that of your 101c they are an exact match other than the differing address offsets. I am going to go outside and get some sunshine in the nice 105 degree weather I am having. :o
http://www.multiupload.com/WBMRYH3X8J (http://www.multiupload.com/WBMRYH3X8J)
-
Well for now here is the source, I have not ran the sigfinder against it, but when I compare the stubs_entry.S file to that of your 101c they are an exact match other than the differing address offsets.
I downloaded and built it just fine. The new sigfinder only found three things of possible concern :
//DEF(task_InitFileModules ,0xff894550) //107 **** stubs_entry_2.S: 0xff89447c
//DEF(levent_table ,0xffb7a458) // Found @0xffb7a458, ** != ** stubs_min = 0xffb7a464 (0xFFB7A464)
//DEF(movie_status ,0x000067e0) // Found @0xff94addc, ** != ** stubs_min = 0x00005430 (0x53F8+0x38)
The InitFileModules warning probably means that your version of CHDK will not support FAT32 - that's the reason for hooking that task in the first place as far as I know (I've been wrong before). It also means that there should be several seconds delay after the camera starts before the logo appears. Does that seem right ?
-
Well there is about 5 seconds before it loads the logo.. and maybe this explains why the logo is not showing completely on my 32gb card but it did on my 2gb :|. So are you saying I got an address wring with the InitFileModules? I would like to get FAT32 working, had not realized that it was not.
-
Well there is about 5 seconds before it loads the logo.. and maybe this explains why the logo is not showing completely on my 32gb card but it did on my 2gb :|. So are you saying I got an address wring with the InitFileModules? I would like to get FAT32 working, had not realized that it was not.
The five second delay indicates that the InitFileModules task is not running ( it sets a flag to tell the spy_task it can run - otherwise the spy_task sits in a loop and waits for several seconds before it proceeds and shows the logo - amongst other things. )
What does the logo not working completely mean ? You get the text box but not the round dial picture ? That can happen if the logo image file is not stored on the larger partition if you are using dual partitions. Or are you using a ps.fi2 file to firmware update boot ?
As you did the rest of the port pretty much on "blind faith", it seems that changing the three values posted makes some sense. You should see an immediate change in the time it takes the logo to display if the new sigfinder is right about the task address. And the levent_table value almost always seems to change between firmware versions. I have no idea what the movie_status will do to you if its wrong.
-
I've replaced the diskboot.bin on the other page with the newly compiled file based on what your sigfinder found. It is booting up quicker and fat32 compatibility has been restored. Thanks! Fortunately no one had downloaded it just yet.
Also I never got ps.fi2 working and since I got the autoboot going on my sdhc I don't really care about it to be honest.
-
Posted your source to the trunk with the three fixes noted above after testing to be sure it builds.
Also added the CAM_DETECT_SCREEN_ERASE fix so the "disappearing menus" in shooting mode should be fixed for both the 1.01C & 1.01D when the patch gets into the nightly build.
-
Hello,
I'm a newbie with a IXUS200 IS - I couldn't get the display firmware to work using the readme instructions so I used the exiftool to display the Firmware Revision which is 1.00 rev 3.00
Can I assume I cannot load CHDK. The posts were some time ago so just checking if this is now possible ?
Thanks in advance
Greg
-
The links to the Bin file at the start of this thread is no longer available ?
-
@waterwingz:
Thanks for the update ;-)
@Greg:
If you could provide a firmware dump of version 1.00, i'm sure someone could port chdk easily now that we have a working port for 1.01.
-
@Greg:
If you could provide a firmware dump of version 1.00, i'm sure someone could port chdk easily now that we have a working port for 1.01.
He has 1.00C judging by his post - the same version Radup was working on at the start of this thread.
UPDATE : if I can get a valid ROM dump, I'll do the port at some point (unless someone else is happy to do it first) but I'm on vacation for the next couple of weeks and away from my PC
-
Thanks for your responses..
I'm happy to follow instructions !! but need some hand holding I'm afraid.
I'm struggling to understand the relationship between the dump of my firmware and the "port" - presumably this is because the CHDK software for this camera is in Beta ?
I have no idea how to do a dump of the firmware...
I also confused about the relationship of the ""step one" of viewing the firmware version on the camera which implies that the "vers file" is written to during this step... which I assume is a pre-requisite for the bin bootfile file to work ....as it reads the ver file??
In which case.. wouldn't this need to be created in a different way because the type of camera (with its touch screen and all) that doesn't seem to accept the key press roll the finger thing as suggested in earlier posts.
Like I said - happy to follow instructions - and appreciate the expertise on the forum - fingers crossed I'll get this working :)
Greg
-
Thanks for your responses..
I'm happy to follow instructions !! but need some hand holding I'm afraid.
I'm currently travelling on vacation so can't manage a long explanation from my mobile device. There is probably a valid firmware dump for your camera already but I can't check that easily while on the road. If there is, then about the only thing you can do is wait for someone to convert the current port to work with your firmware version.
-
@Greg:
CHDK software needs some porting (or adjusting if you will) for every camera AND every firmware version due to some small differences in each firmware. So in order to get CHDK running on your camera/firmware setup you first of all need to determine your firmware version. Look in the WIKI for further information on that topic if you are interested e.g. in vers.req.
But you already know your firmware version and have noticed that there currently is no v1.00c adjusted port of CHDK software.
So in order to build it one would need a firmware dump of the v1.00c firmware. If you want to provide one have a look at the wiki "How to dump firmware" to get an brief overview on how you could achieve this. I think you want to use Cardtricks. Also look have a look through this thread. Someone lately dumped an other version. So maybe there you get more input on how he did it.
Firmware dump results in a ~8mb file. Upload it here.
-
Many Thanks All..
Found the correct CHDK Software on the German site mentioned through the thread
http://chdk.bplaced.net/content/download/viewcategory/8.html (http://chdk.bplaced.net/content/download/viewcategory/8.html)
I should be OK now
Thanks again
Greg
-
Many Thanks All..
Found the correct CHDK Software on the German site mentioned through the thread
http://chdk.bplaced.net/content/download/viewcategory/8.html (http://chdk.bplaced.net/content/download/viewcategory/8.html)
I should be OK now
Thanks again
Greg
@Greg : as we worked on the later firmware versions of the SD980, it was not clear how well the 1.00C version in the CHDK-DE server actually worked. Please report back here with what you find. When I get a moment to create a version for the CHDK sever, your feedback and help testing will be essential
-
Thanks waterwingz. :D... I was already wondering why the build was not in the Autobuild server releases. So much effort was given for the 100C version, would be a waste not to have it in Autobuild. I had to dig it up from here http://chdk.bplaced.net/content/download/summary/8/33.html (http://chdk.bplaced.net/content/download/summary/8/33.html)
As I do have two IXUS 200/S980 - one 100C and one 101C model. I thus can perform a functionality comparison test easily. Also have Gentled USB cable and model 2 for functions-test over RC pulses in.
So, I'll await the 100C on autobuild then will do comparison tests.
-
Did a remote shutter test. It worked for IXUS200 and not for the IXUS100. Did the test on IXUS 100 with SDM and the shutter worked, that maybe a good hint to fix it ? Will retest with some other settings on the IXUS 100. Will do more tests if there is an autobuild version for the IXUS 100 v100c but will not polute this thread with that info then.
OK, now I'm on to more IXUS00/SD980 tests, and hope to speed-up the time between pictures by tweaking some values.
-
Did a remote shutter test. It worked for IXUS200 and not for the IXUS100. Did the test on IXUS 100 with SDM and the shutter worked, that maybe a good hint to fix it ? Will retest with some other settings on the IXUS 100. Will do more tests if there is an autobuild version for the IXUS 100 v100c but will not polute this thread with that info then.
OK, now I'm on to more IXUS00/SD980 tests, and hope to speed-up the time between pictures by tweaking some values.
Posted in the wrong forum for the IXUS100 comments ? Regardless, you might want to look at doing the port to 1.00C yourself ? With the new sig finder and CHDK-PT its a much easier !
-
Have a working CHDK firmware for IXUS 200 v100c, whomever created that, I neet to look it up. Highly likely I also still have the source since I started porting to IXUS200 v1.01c. which was as you know now already done, not by me ;)
Thanks for the CHDK-PT, will look into it. Very nice to have more options there. Since like to build firmware from scratch with the Linaro toolchain on Linux. This make it easier for me to modify source and improve without waiting for someone to do it. In the past painstakingly disassembled using IRDA.
And, yes I was also busy with my other cam the IXUS 100 version 100c will report back in that thread.
-
Thanks for the menu erase fix waterwingz. I have noticed an odd issue with the playback option, when there are several hundred (maybe thousands of pictures) stored on my 32gb (dual partition) SD card it appears to be busy infinitely which prevents the viewing of other pictures. I will do some more testing and post back. So far everything else seems to work very well.
I also just received a refurb of this camera with 1.01d on it as well, will be doing further testing with it.
-
Reading back through these posts, I can't tell if anyone actually wants a 1.00c version available in the autobuild server. If there is a need, and you are willing to test a port (i.e. go through multiple iterations while we get it working) then send me a PM with a real email address as contact info. Otherwise I will consider this closed and not make plans to work on it.
-
Yes please, and it is good for me to have some practice for future CHDK work. I'm willing to test. Have also Gentled USB2 cables and some remote cables so can do some remote shutter and zoom tests also. Will send email. TIA
-
Hello all, I'm a newbie here, testing 101c on my IXUS200 (SD980). Suggest me, how and where to report bugs? I found an important one, and some minor too.
------------------------------------------------------------------------------
An important issue for me is: shooting process doesn't work properly within the script, when AEL (AE-lock) is on. If using the 'shoot' command, it stops at the second shot (just a bit after). When using 'click "shoot_full"', it stops just after a last shoot in the sequence. (Any delays before, between and after doesn't mean. Cycle or linear sequence, doesn't mean. Script works fine when AEL is off, and when AFL is on or off. Shooting manually works fine). The camera operation is not hanged when this stopping occurs, it seems that script (or interpreter?) is waiting for some reaction. The screen is cleared from any CHDK messages/output/menus/remarks. If I switch off CHDK blindfold (by pressing "play" button), then switch off AEL, then switch on CHDK again, script continues and works fine till the end. Sometimes CHDK functioning seems someway corrupted, because "play" button leads to the play mode, not to CHDK mode (don't catched when, exactly).
I found it on the 1344 build, and it still the same on the more fresh 1385 (dated 23th october 2011). However my test script stopped more early on 1344 then on 1385 (giving just 1-2 shots), so there are some progress ;)
The minor issue is the strange behavior of the ND-filter override. The Tv override works stably, and ND- seems to work too: setting "ND Filter In" gives more dark pictures, and vice versa. However a) this is not reflected on the screen, (the value at the bottom is always 2.8 or what was selected by camera automatically). b) This is not written to EXIF, so it cannot be checked by no means.
This ND-filter is a riddle for me, because on my IXUS200 it have at least three gradations (at the minimal zoom) - 2.8, 3.2 and 4.0. So what exactly happens when setting ND-filter just "In" or "Out" , I can only guess :(
(I'm trying to establish an automated shooting process for panoramas, so identical Av and Tv values, like in the Manual mode, required). Sorry for my humble English and if I should do more, I can ;) [study and report problems more thoroughly, for example].
-
Canon IXUS 200 (SD980)
Firmware version 1.01c
Using CHDK from the autobuild server revision 1390 (and 1391)
CHDK loads fine into normal mode, but I have been unable to get into alternative <alt> mode.
The usual method seems to be using the DISP button (as this camera doesn't have the direct print button), I have tried various durations of pushing this button - all it does is just change the brightness of the display. I that I have also tried every combination of buttons/switch on the camera including FUNC.SET + DISP.
The only CHDK function I have been able to access is the live histogram by holding the self timer button whilst half pressing the shutter.
Can anyone give me any pointers as to how to get into alternative <alt> mode?
or might it be a problem with the camera and the current (2011/11/02) builds?
(I have have plenty of prior experience of using CHDK with A570, A590, IXUS 860 (SD870))
-
I have just solved my own problem, a short press of the play button, switches the camera between Normal and Alternative<alt> mode.
How I didn't find that earlier, I don't know..
-
hamfent, hello. Do you know something about IXUS200 aperture? It seems to be a real diaphragm, with at least four values: 2.8; 3.2; 3.5; 4.0. Strangely, but anything about it anywhere (in the camera's manual, DPreview and so on).
-
@lalex
I assumed the SD980 (200Is) only used a ND filter, but I now realise this is not the case.
Looking at test shots, and reading the EXIF data, it seems obvious that the depth of field is increased as the f-stop increases. On my IXUS the crispness of focus seems to be at its best around f5.6.
With its 24mm equivalent wide angle offering this little gem of a camera really rocks :)
-
hamfent...Do you know something about IXUS200 aperture? It seems to be a real diaphragm,...
Using a torch light (and maybe a magnifying lens) you'll see the real mechanic structure ;)
-
"you'll see the real mechanic structure"
Yeah, saw it! Thanks. But the diagnosis means that the "ND-filter" item in the "Extra photo operations" menu is an atavism and will not work correctly. As I described above, it works only in non-script mode, and the result is not reflected in EXIF. So it gives the doubtful result. Setting ND-filter IN/OUT gives maybe 1 step, maybe more. Now I have a courage to try "set_av", at least.
The next issue is a set of props, I found here the most fresh "New Digic IV (http://chdk.wikia.com/wiki/PropertyCase#New_Digic_IV_.28propset3.29)". Doubtful that it's fully convenient to our camera (as well as all previous sets). Now I'm trying to set/determine the shooting process, and any of props 200 - 210 don't return anything except zeros. The #208 seems to give a 1 after a shot is made, but it's marked as "Flash Ready status" in the previous "Digic III & Digic IV" propset.
Seems that branch is abandoned by developers, so we have to maintain it ;) Our beta seems to be far from end :(
-
Seems that branch is abandoned by developers, so we have to maintain it ;) Our beta seems to be far from end :(
CHDK is an all volunteer affair - there are no "developers" who maintain things. Code for a camera is either maintained by someone who owns the camera or it becomes abandoned. From that point of view - you are now a "developer". Welcome onboard !
-
"you are now a "developer""
I had to guess it before :( So now I must tesst not only 10 props, but all of them.
NB: prop 208 becomes 1 when half_shoot is pressd, prop 210 - only when flash is activated. What to do with this knowledege?
-
As far as I can tell - as indicated by the IXUS 200/SD980 the diaphragm has ten steps giving the following apertures:
f 2.8, 3.2, 3.5, 4.0, 4.5, 5.0, 5.6, 6.3, 7.1, 8.0
-
Yeah, great!
But this doesn't help to manipulate it from the CHDK menu or script. Any attempts seems to be inefficient. I tried all: set_av, set_av_96 etc, as well as props from Digic III and IV and of course, "ND-filter" from "Extended photo operations" :(
I didn't test totally my A530 (because it has Manual mode)? but remember that its ND-filter was also similarly stubborn. I may be wrong, but this aperture/NDfilter issue may be just declared, but not resolved in CHDK. To test some other cameras can be useful to understand.
-
@lalex
I've enabled the iris (CAM_HAS_IRIS_DIAPHRAGM) in this build:
CHDK-ixus200_sd980-101c-1.0.0.zip - 0.20MB (http://www.zshare.net/download/99392277b4264006/)
Let us know whether it works.
-
@srsa_4c
I have tested the iris with the given build, all the values in CHDK work upto 8.56, and every chdk value that works gives a different aperture/iris size.
Tested in fairly dark conditions with a 4second exposure, ISO 80, lens fully zoomed out.
chdk values = camera/exif values
2.87 = 2.8
3.01 = 3.2
3.18 = 3.2
3.38 = 3.5
3.64 = 3.5
3.98 = 4.0
4.44 = 4.5
4.80 = 5.0
5.05 = 5.0
5.49 = 5.6
5.37 = 5.6 (in wrong position should be between 5.05/5.49)
6.05 = 6.3
6.80 = 7.1
7.63 = 8.0
8.56 = 8.0
9.61, 10.79, 12.11 all give the same iris size as 8.56
thanks
hth
-
2srsa_4c: "@lalex: I've enabled the iris (CAM_HAS_IRIS_DIAPHRAGM) in this build: CHDK-ixus200_sd980-101c-1.0.0.zip (http://www.zshare.net/download/99392277b4264006/) - 0.20MB Let us know whether it works."
Thanx you very much. Sorry, but I missed the gift: уour link doesn't work anymore (((
-
Thanx you very much. Sorry, but I I missed the beginning of distribution: уour link doesn't work anymore (((
Don't worry about that. The change got into the official CHDK, just download a current autobuild version.
-
Downloaded 1791b, it works, GREAT! I can now make auto-panoramas!!!
Repeated the test of Hamfent in the low daylight (in the room), with 1/60 shutter speed. The same results with non-significant difference:
chdk values - camera - exif values
2.87 - 2.8 - 2.8
3.01 - 3.2 - 3.19
3.18 - 3.2 - 3.19
3.38 - 3.5 - 3.51
3.64 - 3.5 - 3.51
3.98 - 4.0 - 4.00
4.44 - 4.5 - 4.51
4.80 - 5.0 - 5.02
5.05 - 5.0 - 5.02
5.49 - 5.6 - 5.60
5.37 - 5.6 - 5.60 (still in wrong position)
6.05 - 6.3 - 6.30
6.80 - 7.1 - 7.10
7.63 - 8.0 - 8.00
8.56 - 8.0 - 8.00
9.61, 10.79, 12.11 all give the same as 8.56. Zoom, ISO and shutter speed doesn't change this in any way.
-
Thanks a lot to the developers. Did not yet succeed in installing but still working.
Tomas
-
Reading back through these posts, I can't tell if anyone actually wants a 1.00c version available in the autobuild server. If there is a need, and you are willing to test a port (i.e. go through multiple iterations while we get it working) then send me a PM with a real email address as contact info. Otherwise I will consider this closed and not make plans to work on it.
Yes please. I just bought an Ixus200 this week with 100c firmware. I am trying to install CHDK but obviously could find the correct version. I would happily do the testing or send a PM - only I don't know what PM is :-) Anyway my email address is [email protected]
Thanks for any help/advice
-
I would happily do the testing or send a PM - only I don't know what PM is :-)
PM = personal message. I suppose it might also stand for private message. In any case, its lets you send a message to a registered forum user without everyone else needing to see it. In this case, it would have kept your email address private and less exposed to spammers.
Get there via the little text comment icon under people's nicknames on the left hand side of every forum posting.
I'm away from my development computer for the next couple of days and its been a while since I looked at the state of the SD980. I should be able to take a look next week though.
UPDATE : the PRIMARY.BIN file for IXUX200_SD980 f/w 1.00c (https://www.box.com/chdk/4/55272271/536022011/1#/s/tscho3m30j/4/55272271/536059291/1) is truncated. Looking back in the forum, it appears to have actually been "blinked out" with an LED. To proceed, I really need a full 8M dump using the Canon BASIC dumper : http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
-
Downloaded 1791b, it works, GREAT! I can now make auto-panoramas!!!
Repeated the test of Hamfent in the low daylight (in the room), with 1/60 shutter speed. The same results with non-significant difference:
chdk values - camera - exif values
2.87 - 2.8 - 2.8
3.01 - 3.2 - 3.19
3.18 - 3.2 - 3.19
3.38 - 3.5 - 3.51
3.64 - 3.5 - 3.51
3.98 - 4.0 - 4.00
4.44 - 4.5 - 4.51
4.80 - 5.0 - 5.02
5.05 - 5.0 - 5.02
5.49 - 5.6 - 5.60
5.37 - 5.6 - 5.60 (still in wrong position)
6.05 - 6.3 - 6.30
6.80 - 7.1 - 7.10
7.63 - 8.0 - 8.00
8.56 - 8.0 - 8.00
9.61, 10.79, 12.11 all give the same as 8.56. Zoom, ISO and shutter speed doesn't change this in any way.
In case somebody with the camera reads this: aperture_sizes_table[] in platform/ixus200_sd980/shooting.c probably needs to be fixed, the above test shows many duplicate values in that table. Not a big problem, just a cosmetic change.
-
The autobuild has now been updated to include support for firmware version 1.00c.
This port is still a beta - the modemap and other tables do not look like they have been configured correctly for this camera (something I can't fix without access to the camera or a SD980 owner willing to help out.)
I did make a few corrections in addresses for the other two firmware versions - that may fix some strange behavior for some people.
-
I just picked up an SD980 FW 1,01c...
Let me know if there is anything I can do to contribute.
-
The camera is now supported in the autobuild: http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/)