the sx20 porting thread

acid2000

No, and I was already thinking that this might be the problem, and now you kind of confirmed it. I was hoping to be able to take a shortcut for this beta build, so I did not went through every line of firmware code. I was hoping to only need to do that once the few bugs in the beta of 1.02b have been ironed out. What I did was to search for all memory addresses and update them according to the new firmware. I guess this is just not enough and it really is a pain as I am no ASM hacker. By the way, thanks for the usefull debugging tips from both of you neszt and acid2000. But as things now stand I might wait so that I only have to do it once, if at all. Since I do not have a experience with ASM code, I get kind of discouraged by the fact that I have to update thousands of lines of instructions. I truely respect all the work you two have done for the community, now even better.

You probably don't have to change every line but all the subs and the magic numbers will need to be checked. I opened the code in one window and IDA in the other and compared each line side by side. Takes about an hour of concentration (more in the real world)

Basically whenever you see assembler in the CHDK source tree this will need to be checked for each new version.

Don't get too disheartened if you don't known ARM ASM. Most of the real work is just a intelligent comparison between two values. Don't forget to turn IDA ASM macros off. Also if your unsure regarding what's on screen compare the 102b code to the 102b dump. I've gone over it a few times and it should be all correct.

SkyWalker9

zeno
I suggest you download my ACID program...

Its been a long time since I had to check the firmware on a Canon SX20IS. I've used another of your Java apps for script debugging and was impressed. Some how I missed this one - its another winner!

Now I can just have someone send me one of their photos and I can tell them their version - Fantastic! It was sometimes "challenging" to try and explain the "ver.req" process to some of my non-tecky friends/relatives. Many Thanks!

chewielogan

I have a 1.02D camera. Is there anything I can do to help in terms of testing? I have no programming experience whatsoever.

-chewie

anton1962

Thanks a lot zeno.
I used your ACID program to determine my fw - it was actually 1.02b - and I have to admit that CHDK mods really rock!!!

Got one question though: why does my camera shut down after a couple of seconds when recording hd video in "Quality" (99) setting? Is this propably due to my card being slow? "Standard setting seems to work fine.

Thanks again!

cacharrin

chewielogan
I have a 1.02D camera. Is there anything I can do to help in terms of testing? I have no programming experience whatsoever.

-chewie

Me too, I can help testing 😀

JMD

Does anyone else here use CHDKShell? I downloaded the latest version and put it in a new directory (I do have older versions of the trunk and chdkshell in other directories). Anyway, it does not show the SX20 on the list of supported cameras!!! I checked the trunk (913) and there is an SX20 directory. But the camera still does not show up on the main menu. Does anyone have a clue as to why that is?

Thanks

neszt

JMD
Does anyone else here use CHDKShell? I downloaded the latest version and put it in a new directory (I do have older versions of the trunk and chdkshell in other directories). Anyway, it does not show the SX20 on the list of supported cameras!!! I checked the trunk (913) and there is an SX20 directory. But the camera still does not show up on the main menu. Does anyone have a clue as to why that is?

Thanks

Check the Makefile.

JMD

Thanks. There were references to the SX20 in the makefile, but they had been commented out for some reason.

ultimA

acid2000
...

Well, thanks for the encouragement. I will give it a shot, but before I start let me know the status of the bugs that NeoMod reported on th SX20 wiki page. From all of those, I am only concerned over three. I know it is really selfish from me, but I'd like to have those fixed.
- RAW shooting not working "at all". (For me this is the most important, mostly the reason why I want to have CHDK)
- Manual loading. This is a serious usability bug if someone wants to switch between CHDK and the factory firmware often. The blinker software can be loaded from the menu manually, so it should definitely be possible to implement it on this camera for CHDK too.
- The menu disappearance bug. Although the report says it can be brought back with the wheel, I imagine it can get really frustrating.

Also, I see that at some points you have added your own ASM lines. How should I deal with those? Just port them over, or leave them out because they are probably not compatible with another version? And a last question, is there a way to export C-style ASM from IDA easily? Or do I have to edit each line manually (adding all those "",\n 's)?

Thank you for your help.

reyalp

ultimA
- The menu disappearance bug. Although the report says it can be brought back with the wheel, I imagine it can get really frustrating.

The CHDK menu disappearing when the canon OSD updates is normal.

Also, I see that at some points you have added your own ASM lines. How should I deal with those?

Ideally, you understand what they are for and either copy or correct them as needed. If you are unsure, you ask about specific instances.

Just port them over, or leave them out because they are probably not compatible with another version?

Generally speaking the differences between firmwares are ROM addresses, and possibly variable addresses.

And a last question, is there a way to export C-style ASM from IDA easily? Or do I have to edit each line manually (adding all those "",\n 's)?

Thank you for your help.

look at asmify.sh in the tools directory.

You might also want to have a look at http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version
There's a description of how to correct the ASM if the differences between the firmwares aren't too large.

acid2000

RAW shooting not working "at all". (For me this is the most important, mostly the reason why I want to have CHDK)

Works for me and has done for ages

Manual loading. This is a serious usability bug if someone wants to switch between CHDK and the factory firmware often. The blinker software can be loaded from the menu manually, so it should definitely be possible to implement it on this camera for CHDK too.

I think this has to be fixed upstream. You can always use the write protect slot.

The menu disappearance bug. Although the report says it can be brought back with the wheel, I imagine it can get really frustrating.

This is the same on all CHDK variants, its unlikely it will get fixed but isn't really a problem.

acid2000

Double post error

neszt

For those (beta testers) with SX20 firmware version 1.00F. Please report bugs against the lastest beta version (here: http://chdk.wikia.com/wiki/SX20), let me see, if there need to fix.

Reyalp, fe50! Can you add the 1.00f version to the trunk, if the testers reports that 1.00f has the same functionality as 1.02b?

http://chdk.neszt.hu/git/

afrikaa

Hi, I wanted to know if someone is working on firmware 1.02C

ultimA

Hi,

I have began work on 1.02d (this time checking the ASM code thouroughly) and have almost finished boot.c , except I have following questions:
- Subroutine calls to occurences of j_nullsub_xxx are commented out. This is no wonder, since they all seem to be empty infinite loops. But what are they doing there in the dissassembly? Same for nullsubs. If they are really there in the factory firmware, how could they have worked? Or are they not infinite loops?
- In task_Startup_my() a call to sub_FF83A708 is commented out. It has the comment "start diskboot.bin". Why is it deactivated?
- sub_FF86E724_my(): //"LDRB LR, [R4,#0x1FF]\n" // a2k uncomment ?
- sub_FF86E724_my(): // "LDRB R12, [R4,#0x1FE]\n" + 2 lines ?

Thx.

reyalp

ultimA
I have began work on 1.02d (this time checking the ASM code thouroughly) and have almost finished boot.c , except I have following questions:
- Subroutine calls to occurences of j_nullsub_xxx are commented out. This is no wonder, since they all seem to be empty infinite loops.

No they aren't. They are calls to functions that consist entirely of a RET instruction. This is presumably something that is a real function under some other canon build (development or other models). If you comment them out, it saves a tiny bit of RAM, and causes no harm.

- In task_Startup_my() a call to sub_FF83A708 is commented out. It has the comment "start diskboot.bin". Why is it deactivated?

This the code that starts diskboot. If you don't comment it out you get a boot loop, since CHDK will get there and re-load itself.

Don't know about the others.

ultimA

I am happy to announce that I have a port of 1.02D (beta). The games are deactivated. It seems to work fine, but I have only done very few tests (playback, image, movie, zebra, DNG, badpixel.lua work fine), so please test. Based on acid2000's 1.02b and trunk 913.

Link to download.

I will wait for feedback and then later prepare the sourcecode for the trunk.

(update 09/aug/2010: link updated to newest build)

acid2000

I am happy to announce that I have a port of 1.02D (beta). The games are deactivated. It seems to work fine, but I have only done very few tests (playback, image, movie, zebra, DNG, badpixel.lua work fine), so please test. Based on acid2000's 1.02b and trunk 913.

Great news! Well done I'm sure lots of people will be very pleased

Lghost

Hi, I've been following progress on the 1.02D build for a while and registered today to see if I can help out ( I've got a 1.02D sx20 bought here in France about a month ago ..and have IDA ..but don't really know how to use IDA much as yet ) ..anyway ..enormous thanks to all involved 😀) Been waiting for raw on this camera ( I like canons vari screen models immensely ..but their jpeg compression and their handling of chromatic aberrations in camera don't live up to the cameras potential ) ..I have an S2Is which now belongs to my son which is a great camera thanks to CHDK and all of you who have worked on it 😀 ..again thanks ..

feedback for ultimA ..first note ( I only loaded your beta about 10 minutes ago and have not had time to test it ..but ) ..I first thought it hadn't worked and that maybe I had a variant on the 1.02D firmware ..

Previous experience with CHDK ..the S2Is boots straight in from a card flashes the CHDK logo and the camera "chimes" and the lens powers out and the display comes on as usual and then one navigates to alt menu options etc ..

your beta boots from the card ..the CHDK logo flashes .."the camera "chimes" ..but the screen then says "no image" ( this message stays on screen ) and the lens does not power out ..then if one touches the shutter trigger button ( just a half press like one would to pre-focus ) it all lights up ..the lens powers out and all is as normal ..I say this just in case anyone else tries your beta and thinks their camera is "borked" ..it isn't 😀 ..very nice beta ( and if I can help in any way other than testing I'm more than willing but you'll have to walk me through using IDA ) ..

now off to load the ultimA's beta onto a bigger card and see what awaits ..😀

Btw ..we are scheduled some thunderstorms here in the next few days ( Brittany ) .so if motion capture for lightning etc is in ? I'll maybe be able to test it ..

if needed ( and if ultimA wishes ) I can put the beta onto rapidshare or one of my own web spaces .. if anyone has problems with media fire ..

Ps ..agree about the games ( never did use them ..actually never did use zebra either ) i suspect most folks are more concerned with raw and convert to dng in camera than anything else ..

did I say thanks ? to all , ultimA , acid2000 ,..everyone 😀

f_m_b

I have prepared a fix for bug "option @shutter half-press [seconds] or [don't] does not work in zebra-mode. Always shows full clock."

The svn-patch-file (based on rev. 914) is attached.
Also for testing a bin file based on rev. 914.

Can anyone test it?
And if ok check in svn?

I don't have commit-rights. 😉

Bye Frank

« Previous Page Next Page »