CHDK for S5 Status
Just posting a summary as I saw a few questions about it in other threads.
CHDK uses the "Firmware Update" function of the Digic II based cameras.
This has been ported to the Digic III in the G9.
Canon has removed the "Firmware Update" item from the S5, so there is currently no way to load any external code. Getting a copy of the S5's ROM to work with is needed, but it's unknown if it will be possible at all.
Dissassembling the camera and reading the ROM directly might be possible, if expensive as a camera would need to be sacrificed.
If Canon releases a firmware update for the S5, it can be examined to find out how the new loading code works.
Somone might (but it's very unlikely) stumble across a button combo to load firmware by accident.
If anyone finds out something or knows something, please let us know. The S5 is a great camera, but it's frustrating to have it's expansion ability crippled.
Anyone making any progress on this, or is it looking like it will be impossible until if and when Canon puts out an S5 ROM update that can be poked at?
so Update firmware option was removed?
it may still be possible to run code from .bin file from SD card if you will mark card bootable
CHDK uses 2 different aproaches to load code into camera ( .FIR and .bin files)
did you try to load .FIR file only or you have checked autoloading of diskboot.bin also?
to load .bin files you have to mark your SD card as bootable ( change some bytes in boot sector ) and make it readonly ( Lock switch on SD card)
it is possible that 3 bin files can be loaded such way : diskboot.bin, romwrite.bin, upgrader.bin
here you can find 3 .bin files (they do nothing. you can see sources)
purpose of these .bin files to hang your camera - to show you the code actually have been executed
here you can find 2 sectors from G7 SD card - original one and another marked as bootable
you can make your SD card bootable manualy editing boot sector in hex editor
I have used HDHacker tool to extract from and write back this sector to SD card
Any hex editor can be used to write "BOOTDISK" into this bin file.
offset : 0x40
hope this trick will help you to launch blinker on S5
Aha, this did work. Using diskboot.bin I got the camera to hang. So it is doing something at least.
I compiled the program in this thread http://forums.dpreview.com/forums/read.asp?forum=1010&message=24988142 and ran it, but nothing turned on. The S5 memory locations probably are not quite the same, but I am new to this all and am not sure where to start poking. It's possible the code is not being loaded into the right memory location as well.
Strange how I and some others couldn't get any of this to work before. I am pretty sure I tried the diskboot.bin file before.
I got it to work finally.
The green LED address is 0xC02200E0 so I'll be working on seeing if I can get the firmware out overnight tonight.
I got it to work finally.
The green LED address is 0xC02200E0 so I'll be working on seeing if I
can get the firmware out overnight tonight.
Good luck with that! A lot of folks are definitely looking forward to it.
Canon G7, S5, SD850
I got it to work finally.
Congratulations! I hope you will get the dump.
BTW. Could you add some useful camera-related info into this page: http://chdk.wikia.com/wiki/S5IS . At least P-ID and LED-addresses known. Thanks.
I'm dying to know how this S5 CHDK work progresses!
Even if it should eventually require an S5 to disassemble and use as a guinea pig, it seems like it should not be difficult to get at least 15, 20 people who would be willing to chip in and help buy a camera for the right developer. I would.
I don't own a Digic III cam, but it's great to hear that nevertheless!
Perhaps people with other new Digic III cams (A650, G9, ...) now can hope, too, since it seems that you guys found a way around the changed update procedure.
Good luck to you all!
I don't have a firmware dump yet, but this morning before I went to work I did get all the hardware set up and was able to get a good recording of the green led output into my sound card.
So tonight I'll run the full dump and see what it gives me in the morning.
I don't have a firmware dump yet, but this morning before I went to
work I did get all the hardware set up and was able to get a good
recording of the green led output into my sound card.
So tonight I'll run the full dump and see what it gives me in the
I'm refreshing this page every 5 minutes
can't wait any more
Been a busy few days for me so I have not been able to perform the dump yet.
Trying to find a program to record 10 hours of audio in the right format is a pain as well. Anyone have a freeware program that can record PCM files from the sound card direct to disk?
I'm going to get some parts today to improve the capture quality too I hope.
I have Audacity and use it for various stuff, but it doesn't save RAW files or record direct to disk, so recording 10 hours would be rough.
I'm trying the serial port hack now.. I got it to give me random data.. it's a start.
I have Audacity and use it for various stuff, but it doesn't save RAW
files or record direct to disk, so recording 10 hours would be rough.
Using the soundcard is slow but I got abount 1mb per hour. Using the bootdisk-method mentioned in this thread I made a dump of my A720IS.
Since signal quality was not good enough to recognise eight identical bits in a row, I modified the blinker to use the Manchester-Code. This way signal changes occur more often and are less likely to fail - and if they fail it will be noticed. To read the recording I wrote a (very slow) perl programme.
My Dump is not quite ready, yet. When it is I will post links to my code in the A720IS-Wiki-Article ( http://chdk.wikia.com/wiki/A720IS ) and you may try this one.
I remember using this old program in the past: messer-v0992-setup.zip (originally found at http://www.dago.pmp.com.pl/messer/ , now - http://dtserv3.compsy.uni-jena.de/ws2005/allgpaed_uj/47695491/content.nsf/Pages/678EE2A4C7903A46C12570BB0054CB6F )
No bugs AFAIR, does not use RAM, records until the disk is full, shows signal level etc.
Maybe someday we will get it for the S5. I didnt buy the camera with knowledge of possibly being able to have this (didnt even know stuff like this was done). So if someone finally gets the CHDK for the S5, it'll just be a plus I guess. I would try myself but I think this type of work might be past my skills, Im more of hands on person, bits of code looses me quick.