the sx10 porting thread

cormac

Just uploaded the updated movie_rec.c to http://drop.io/wltyjxn.

That didn't fix the crash. I suspect I screwed up a jump table somewhere.

cormac

Did a quick code audit and found a couple of wrong addresses.

I've updated the zip to include the movie_rec.c and my fixes at http://drop.io/wltyjxn - look for the one with the date.

Same crash as before however.

I'll look at it tomorrow after some sleep.

gexplorer

Hi there, is there any chance that there will be developed something for the 1.03a? Mine has that FW and I was greatly disapointed for not being able to use CHDK on my SX10...

cormac

gexplorer
Hi there, is there any chance that there will be developed something for the 1.03a? Mine has that FW and I was greatly disapointed for not being able to use CHDK on my SX10...

1.03a is pretty recent, so there is a good chance that it will be done. What is needed currently is a dump of the 1.03 rom. This can be done using cardtricks from http://chdk.wikia.com/wiki/CardTricks

Rumours suggest that 1.03 is pretty close to 1.02, and if it is, then the port will be developed fast.

orozco

I'd be excited to test a 1.00c port. I finally started trying to work on it last week, but I don't think I know what I'm doing enough to finish it (and it looks like cormac's already done much more than me). For reference, this camera was ordered from Newegg around the beginning of March '09.

Thanks for working on it!

nimrod

cormac or anyone else:

If you're going to insert debug code, here's some stuff to know. It took me a bit to realize all the issues with this stuff and ARM assembly. Here's the LED blink function I used:

#define LED_PR 0xC0220060
#define LED_SPIN_DELAY 5000000

int led_blink(int save_R0) {
	int i;
	volatile long *p=(void*)LED_PR;

	p[0] = 0x46;
	for (i=0; i< LED_SPIN_DELAY; i++) // Wait a while
	{
	     asm volatile ( "nop\n" );
	}
	p[0] = 0x44;
	for (i=0; i<LED_SPIN_DELAY; i++) // Wait a while
	{ 
	    asm volatile ( "nop\n" );
	}
	return save_R0;
}

(That was thrown together mostly by copying similar stuff from the wiki and hardware addresses from the sx10 platform code.)

Unlike IA-32 (Intel), the ARM calling convention does not require that any called function preserve all the registers. Functions are allowed to stomp all over r0-r3, and gcc behaves accordingly as does whatever compiler canon uses. So when you see something like:

    MOV     R0, SP
    MOV     R1, #0x74
    BL      sub_FFB003BC
    MOV     R0, #0x53000

Don't put "BL led_blink" right before "BL sub_FFB003BC" and after the arguments are placed in r0-r3. Otherwise led_blink() will conceivably stomp all over r0 and r1 (in the example above) unless it does something special to preserve them. (In the code above, a trick is used to preserve r0 by specifying an argument, the first of which will always be passed via r0, then returning it which will also always be returned via r0.)

It looks like the easiest thing to do is use the r0 preserving trick above, then put the call to led_blink or whatever just after a call to something else. That way we know "BL sub_FFB003BC" has stomped all over r0-r3 and placed it's return value in r0. So we only have to preserve r0 for the code immediately after that to get what it expects. If gcc decides to use r4+ then it knows it has to preserve those and we don't have to worry about it as it should generate the right code.

(I was stumped for a bit as to why something like led blinking code would crash the camera when I was messing with this.)

See http://chdk.wikia.com/wiki/CHDK_Coding_Guidelines

cormac

I was using calls to debug_led, but that seems to break things. I'll try this and see how it goes.

Thanks!

patdop

Hi all,

What's wrong ?
ok so I load it and it works.
but then I try to load a script or change the language and CHDK can't see files.
I do it well (I guess) note pad then save as*.bas but it doesn't work.
have try to benchmark my 32GB SDHC card and what a surprise my class 6 is a fake one. it's only a class 3.
so when I record video in full quality it only rec for a couple of seconds.
I have a question I see somewhere on the site that the native quality of video is 75. so why the default of CHDK is 84 ?
thanks and tell me about script if I'm wrong

fe50

patdop
but then I try to load a script or change the language and CHDK can't see files.

Do you use the "complete" package from the Autobuild Server ?
If you use a partitioned card, the CHDK files must be placed on the 2nd partition; on such cards CHDK starts from the first (small) partition and then swaps to the big one...

I have a question I see somewhere on the site that the native quality of video is 75. so why the default of CHDK is 84 ?

No, the default value for the CHDK video quality normally is 84, this should match the Canon quality setting.

Tyler Durden

Use the first version on the DL page. The second version does not seem to work- the camera hangs and resets itself after a few seconds of trying to start the script.

3rdeye

I am looking to buy this camera. So far all I can find in stores is firmware version 1.00C. All ports are for firmware versions 101A,1.01B, or 1.02B. Were would I find firmware to upgrade to one of these versions? The Canon web site show no firmware updates available.

JB

cormac

GM1.00c Updates:

I've gotten a 1.00c firmware chdk actually booting! It shows the logo!

Downsides... it's crashing when loading a script, and switching into shooting mode 🙁

More debugging is needed, but I'm almost there.

Tyler Durden

As I understand it, most current raw import programs can't handle the CRW files produced by the digic IV processor in the SX10. I have successfully opened and tweaked DNG files with UFraw plugin and gimp. Is there any way to shut off recording of .CRW files and just record .DNG instead? Right now if I want to use the raw feature each picture requires 5 MB for the jpg, 15 for the CRW and another 15 for the DNG. Did I miss something?

Thanks,
TD

gexplorer

cormac

gexplorer
Hi there, is there any chance that there will be developed something for the 1.03a? Mine has that FW and I was greatly disapointed for not being able to use CHDK on my SX10...

1.03a is pretty recent, so there is a good chance that it will be done. What is needed currently is a dump of the 1.03 rom. This can be done using cardtricks from http://chdk.wikia.com/wiki/CardTricks

Rumours suggest that 1.03 is pretty close to 1.02, and if it is, then the port will be developed fast.

Man, I would gladly help, but I don't know what do you mean with needing a dump of the 1.03 rom...

cormac

gexplorer

cormac

gexplorer
Hi there, is there any chance that there will be developed something for the 1.03a? Mine has that FW and I was greatly disapointed for not being able to use CHDK on my SX10...

1.03a is pretty recent, so there is a good chance that it will be done. What is needed currently is a dump of the 1.03 rom. This can be done using cardtricks from http://chdk.wikia.com/wiki/CardTricks

Rumours suggest that 1.03 is pretty close to 1.02, and if it is, then the port will be developed fast.

Man, I would gladly help, but I don't know what do you mean with needing a dump of the 1.03 rom...

You will need a blank SD card (I use a 1 Gb SD card, but anything up to 4Gb should work ok)
Download cardtricks from http://chdk.wikia.com/wiki/CardTricks and run it.
Put your blank SD card into a card reader
Click on the SD card picture and select the drive with the SD card in it.
Click on NewDryOS in the "Create/Inspect Universal Dumper" section.

The card will now be formatted

Eject the card and slide the lock tab so that the card is in the write locked position.
Put the card in your camera and close the door to the SD slot.
Press the picture playback button and wait at least 30 seconds.

Note: You won't see anything on the display and the camera will not do anything during this process

Open the battery compartment, and with the batteries open, remove the SD card from the camera
You can now close the battery compartment

Put the SD card in the reader, and select it with cardtricks.
Click on "Strings" and if the dump worked, you will get a text listing.
Click on "Clean" and save the .BIN file to your hard drive.

This will be the dump of the 1.03 rom that can then be uploaded somewhere (I like drop.io)

Let us know here in this thread where the dump can be downloaded from.

You can then unlock the card and reformat it for normal use.

nimrod

I'm willing to work on 1.03a if we get a reliable dump.

I haven't really done anything on 1.00c since cormac seems to be making progress, and I've been either busy or lazy.

cormac: That's great that it's actually booting now! Did you happen to verify everything in stubs_min.S? That's the one that's a big pain and one of the ones that seems like it might be more likely to cause a crash during operation as opposed to boot.

Also, if you have two things you need to do (like say, check stubs_min.S and stubs_entry_2.S or something) that we can split, let me know if I can do one part while you do another. I just don't want to uselessly duplicate effort..... Just let me know which part to look at.

For debugging you might want to try disabling the OSD, then go into "record" (shooting) mode just to see if it's OSD-related.

(BTW, does CHDK always go into "play" mode when it starts up? I thought I had it booting into "record" mode at one point.)

hoelk

First, thanks for the porting efforts 😀 chdk was the main reason for me for buying another canon compact camera.

I'm using the 1.02b Beta build, and i have one more or less serious problem:

The camera doesn't switch on correctly every time. Sometimes the screen (and the seeker) just stay black.
This can happen, as far as i recall, in all 3 ways to switch it on ("play" button, "on" button, "on" button pressed for a few seconds)

Is this a know issue? any idea what it could be connected to? it really seems to be happening rather randomly.

cormac

nimrod
I'm willing to work on 1.03a if we get a reliable dump.

I haven't really done anything on 1.00c since cormac seems to be making progress, and I've been either busy or lazy.

cormac: That's great that it's actually booting now! Did you happen to verify everything in stubs_min.S? That's the one that's a big pain and one of the ones that seems like it might be more likely to cause a crash during operation as opposed to boot.

Also, if you have two things you need to do (like say, check stubs_min.S and stubs_entry_2.S or something) that we can split, let me know if I can do one part while you do another. I just don't want to uselessly duplicate effort..... Just let me know which part to look at.

For debugging you might want to try disabling the OSD, then go into "record" (shooting) mode just to see if it's OSD-related.

(BTW, does CHDK always go into "play" mode when it starts up? I thought I had it booting into "record" mode at one point.)

The stubs was the core of the problem. I made it rescan (dropping primary.bin into the sub directory) and it fixed most of the problems, after I found two typos in addresses. The main problem I have is that if I go into shooting mode, it blinks the OSD then it immediately powers down, and the same happens if I try go into "Load scripts from file..." from the menu.

I turned off the OSD for everything and I was able to go into shooting mode, start the menu and setup to take a RAW photo in CRW mode.

I'm trying to figure out what call uses scripts and osd in common, then beat on it.

Regarding the play mode, the power button seems to have two modes (at least in my build). A short press on the power button boots into playback mode, a long press on the power button goes into shooting mode.

Edited: I might have turned off that funtion in the code -recompiling...
Edited again: I did have that turned off, switched it back on, and no difference... short press playback, long press shooting.

cormac

I've uploaded the latest 1.00c source at http://drop.io/CHDK_GM100c

Once I've gotten the OSD problem fixed I'll upload a compiled test version for people to beat on.

alberto1x3

I have tried CHDK for 1.01b.

First of all, it works!
I didn't found where the feature "Motion detection" is but i think this is my fault, i didn't read the manual well enough.

Sometimes the ALT menu disappear, if you press "down" or "up" it behaves like it has always been there, just invisible.
i think this is related to face recognition.

After some tests it stopped working, when i choose "update firmware" it just shut down the camera.
I think this is related to some configuration i made... resetting the configuration make it work again.

I didn't try to make the card bootable, it was just a test of this beta version.

Thanks to everyone, nice project! I really like custom grids!

« Previous Page Next Page »