the sx20 porting thread

SkyWalker9

Markisha
Please help. I'm a total noob with this! I have installed this beta on my 102b sx20. Is there a way to save raw? If there is a way if someone could please give me a step by step it would be much apreciated!
Thank you!

Recommend downloading the latest User Guide from the CHDK usuage webpage. You can find the info for RAW on pages 16-18 of the 'New User Guide April2009'. Here is the shortcut to the guide (PDF):

http://images1.wikia.nocookie.net/__cb20100314070239/chdk/images/3/33/CHDK_UserGuide_April_2009_A4.pdf

After that, you'll want to process the RAW files so then you'll want to checkout http://chdk.wikia.com/wiki/FAQ#Q._I.27ve_shot_some_RAW_pictures._How_do_I_process_them.3F

AK49BWL

First off, THANK YOU for the beta port to 1.02B!! Been waiting for this one a while now 😀

Anyone figure out the video quality buffer overload issue? Shooting in 720p on a 4GB Class 4 SDHC card, I found out that as long as the quality override is kept below 55, the camera does okay (though unless the setting is below 50 sometimes the camera randomly over-buffers and stops the video), and down to about 40-45 the video quality isn't too bad. Is there just too much info (high quality HD video) trying to be passed to the memory card at one time that causes the buffer to overload because the card isn't fast enough to keep up, or is it something else related to CHDK?

Something I have noticed and REALLY like is the smaller file size (meaning more recording time!!) of the so-called lower quality settings... Something I've also gotten very used to on my CHDK'd SD770.

Again, to all the developers, THANK YOU!

m3hwjw

Hi,

Thanks to everyone who is working on this port!

I installed the chdk on a 2 gb card to auto boot and it runs on my camera.

A few issues to report (sorry if known)

1) the chdk menu doesn't clear when I am done selecting options and want to take a picture. I have a work around: press the camera button to go into playback mode and then again to go to record mode.

2) the raw files (.crw) dont seem to be recognized by png4ps-2 or any other raw processor I've tried (ufraw and picasa)

3) When I try to set the dng setting on the raw parameters menu I get an error:
Cannot load CHDK/badpixel.bin
Please run
CHDK/SCRIPTS/TEST/badpixel.lua

Bad pixel removal is the previous option above DNG format. When I go into miscellaneous stuff -> file browser and navigate to badpixel.lua and press the set button the miscellaneous menu redisplays. Is pressing the set button the right way run a .lua when navigated to it in the file browser?

Sorry if known, if these don't happen for other testers, is there something I can try?

I see there is a video for setting up a larger memory card with a dual partitions for auto booting chdk. Are there written instructions anywhere? I saw someone e-mailed something about this to a poster here, was that written instructions? Can you post the instructions in this thread? I have a slow dialup connection and video's don't work well. If not, can somenone give me a brief overview and maybe I can figuire out the rest myself.

Can I ask a question because I'm too lazy to rtfm...

Should the iso override let my camera use higher iso in auto iso mode? Without chdk, the camera will only go to higher iso (above 400) if I use manual iso settings. I'd like to use the auto iso and have it automatically select higher iso's.

Thanks,

acid2000

Read the manual and previous forum posts. All your questions will be answered.

wcem

Follow up to my previous post regarding SX20IS Firmware 1.02b with CHDK.

Motion detection works most of the time. I think it is the display update issues that give the apperance of it not working all of the time since sometimes all I have on the display is a live shot through the lens, no grid, no cells, no CHDK features, but it still captures images when movement is detected.

My bird shots didn't work out as I had hoped. It was too windy, but I got 400+ shots of the feeder swinging in the wind. There were a few shots of birds landing when it was calm, but nothing spectacular. The storms that moved through last night produced flashes hidden by clouds, got a few "bright" shots of the gray cloud base, but nothing worth keeping.

Ultra Intervalometer (multiple versions) locks the camera up and causes a reboot. http://chdk.wikia.com/wiki/UBASIC/Scripts:_Ultra_Intervalometer. It did not matter what mode the dial was set to.

YASS - V2 also locks the camera up and causes a reboot. https://chdk.setepontos.com/d/4920. Same thing with the dial, various settings did not make a difference in its performance.

I'm hopeful that I will be able to do more testing this weekend and work around some of the scripting issues. My basic skills are lacking since I haven't touched basic since my Apple IIe days.

meckymesser69

Hi,

how did you start the motion detection? If I choose any script (.bas) I ALWAYS get the text on the console-output:
**** Started ****
This is a default script.
Scripts run when shutter
is pressed in ALT mode.
Press shutter to exit.
*****

It looks like, i cannot choose a scipt. This is my first use of CHDK, it could be possible, that I make a mistake. Can anybody help me? I read the FAQ about scripts and I think I choose it in the right way...

with ALT+Func.Set I get the screen "Load script ..." and i choose one with "Funk.Set". After it I leave the menu with the menu key (the menu is almost visible) and I press the shutter... then the message (*** default script) will be scrolled in the console output.

The other functions like super fine, RAW in DNG Format is great and the results are brilliant! Thanks for the port!

If anyoune has a hint for me, it would be great.

Meckymesser

Canon - SX20 IS - 1.02B CHDK

whim

@meckymesser69

try selecting your script from PLAY mode CHDK menu, then switch to REC mode:
when in REC mode the selected script is already running, so it can't be changed.

HTH,

wim

savalangh

Hi
Has anyone ever used edge overlay on SX20-IS (1.02b)( last release)
I can't use it, or its not possible on current release?

SkyWalker9

SX 20 IS firmware 1.02b

Until Acid2000 (and others) have time to work on the refresh issues, I decided to create a document to help me test items on the menus (it was getting too confusing with all of the overlaps). I photographed and cropped all of the menu options and started adding comments. Although I've only begun testing in earnest, I decided to upload a copy of the document in case it might help others in their testing as well. Here is a link to the PDF on Rapidshare:

http://rapidshare.com/files/382895024/CHDK_Menu_Photos.pdf

requin

I installed the chdk successfully on a 4gb sdhc. I had to make a smaller partition to load the chdk in and a larger partition for pictures. The smaller has fat16 and larger fat 32. Just one fat 32 partition didnt seem to work.

Now I have the issue of the menu being glued tight. I can't get it off from the screen. It does go inactive when i press the alt button, so that i cannot browse the menu no longer(as if the menu were turned off) but the menu screen just don't go away. When I press ALT and func again, the menu become active again. But never does it go away.

lienso

In the past few days I undertook a search for possible RefreshPhysicalScreen and enabled_refresh_physical_screen candidates in 1.02b. Looking at the SX1 and SX10 code, it is plausible that the structure did not change, and the offset in it should be 34h. Other possible option is 30h, as in ixus870, but this is less likely. The disassembly of SX20 dump gives the following hits (first number - RefreshPhysicalScreen address, second - enabled_refresh_physical_screen address:

0xff8a8ecc 0x4190+0x34
0xff925bd8 0x66d4+0x34
0xff95ba24 0x6fc8+0x34
0xff97dfd8 0x7dfc+0x34
0xff9898dc 0x8020+0x34 good chance
0xff99d9e0 0x85b4+0x34 good chance
0xff9b8f54 0x8a70+0x34 good chance
0xff9b9210 0x8a70+0x34
0xff9ca9ac 0x8dcc+0x34 good chance
0xff9ee000 0x9784+0x34 tested: no effect on screen

I have tested the last one so far. The behavoir is no different from 0xffa0491c in the original acid2000's code - meaning that neither is correct, I guess. Will be digging more in the same direction, probably just trying each address one-by-one.

Anyone with insite what the structure may contain, apart of enabled_refresh_physical_screen, could you advise?

Also, do we know for sure if SX1 and SX10 menu "behaves"? Would be a waste to do all this disassmbly for nothing. So far, the custom vid_bimap_refresh is only used in G11, ixus100, ixus870, ixus980, s1, s10, sx110is, and now sx20. All other cameras use simple call to RefreshPhysicalScreen, with no enabled_refresh_physical_screen setting.

Appreciate any info on this.

acid2000

Great to see I'm not alone in poring through the disassembly!

My thoughts are as follows:

There are a couple of interesting functions that get called in a lot of dialogues and alike, i've called these:

NHSTUB(UnlockAndRefresh,        0xFFA0498C)
NHSTUB(LockAndRefresh,		0xFFA048E😎

These functions wrap ScreenLock and ScreenUnlock which I think actually does the job of refreshing specific parts of the screen. My guess is like other cameras we need to set a pointer before calling these functions to actually get it to wipe the entire screen, these says exactly where to perform the wipe.

My gut feeling says that the SX20 is a bit more like the G11, I'm still really interested to know if people using the 100f are having these issues because if they are not it makes no sense! I've never found a decent 100f firmware dump that doesn't make IDA cry so I tend not to use any 100f stubs.

I think the best move is to find out exactly what happens when the main or function menu is drawn because on my test builds the screen is completely erased. Don't quite know where they are yet through.

I think the vid_bitmap_refresh() might end up looking a bit like this

void vid_bitmap_refresh()
{
	extern int enabled_refresh_physical_screen; // screen lock counter
	extern void _LockAndRefresh();
	extern void _UnlockAndRefresh();


	_LockAndRefresh();
	enabled_refresh_physical_screen = 1;
	_UnlockAndRefresh();
}

acid2000

@lienso, I've been going through some of the values you mentioned, no success yet put here are the ones i've tried:

DEF(enabled_refresh_physical_screen, 0x4190 + 0x2😎	// no obvious effect
DEF(enabled_refresh_physical_screen, 0x66d4 + 0x2😎	// no obvious effect
DEF(enabled_refresh_physical_screen, 0x6fc8 + 0x2😎	// no obvious effect
DEF(enabled_refresh_physical_screen, 0x7dfc + 0x2😎	// no obvious effect
DEF(enabled_refresh_physical_screen, 0x8020 + 0x2😎	// no obvious effect
DEF(enabled_refresh_physical_screen, 0x85b4 + 0x2😎 // no obvious effect
DEF(enabled_refresh_physical_screen, 0x8a70 + 0x2😎 // no obvious effect
DEF(enabled_refresh_physical_screen, 0x8dcc + 0x2😎 // no obvious effect

savalangh

Hi
Has anyone ever used edge overlay on SX20-IS (1.02b)( last release)
I can't use it, or its not possible on current release?

lienso

@Acid2000, I have disassembled the SX1 and SX10 dumps. It seems the signature for RefreshPhysicalScreen is determined. Have not decided what to make of it. It seems to me some code is called no matter what in the structure. ???

; SX1 200H "official" RefreshPhysicalScreen (build 885)
0xff9fa6a8L: e92d4010 stmdb sp!,{r4,lr}
0xff9fa6acL: eb0000cb bl #0x1ea9e0
0xff9fa6b0L: e3100001 tst r0,#1
0xff9fa6b4L: 18bd8010 ldmneia sp!,{r4,pc}
0xff9fa6b8L: e59f414c ldr r4,#0x1ea80c ; = #0xcabc
0xff9fa6bcL: e5940034 ldr r0,[r4,#0x34]
0xff9fa6c0L: e2800001 add r0,r0,#1 ; note add here
0xff9fa6c4L: e5840034 str r0,[r4,#0x34]
0xff9fa6c8L: e5940030 ldr r0,[r4,#0x30]
0xff9fa6ccL: e3500000 cmp r0,#0
0xff9fa6d0L: 1a000005 bne #0x1ea6ec
0xff9fa6d4L: e28f1f4d add r1,pc,#0x134
0xff9fa6d8L: e3a00060 mov r0,#0x60
0xff9fa6dcL: ebfa01e5 bl #0x6ae78
0xff9fa6e0L: e3a00001 mov r0,#1
0xff9fa6e4L: e5840030 str r0,[r4,#0x30]
0xff9fa6e8L: ebfff09c bl #0x1e6960
0xff9fa6ecL: e5940018 ldr r0,[r4,#0x18]
0xff9fa6f0L: ebf8b4e4 bl #0x17a88
0xff9fa6f4L: e3a00000 mov r0,#0
0xff9fa6f8L: e8bd8010 ldmia sp!,{r4,pc}

; Another possibility for SX1 RefreshPhysicalScreen
0xff9fa6fcL: e92d407f stmdb sp!,{r0-r6,lr}
0xff9fa700L: eb0000b6 bl #0x1ea9e0
0xff9fa704L: e3100001 tst r0,#1
0xff9fa708L: 1a000009 bne #0x1ea734
0xff9fa70cL: e59f40f8 ldr r4,#0x1ea80c ; = #0xcabc
0xff9fa710L: e3a05000 mov r5,#0
0xff9fa714L: e5940034 ldr r0,[r4,#0x34]
0xff9fa718L: e2400001 sub r0,r0,#1 ; note sub here
0xff9fa71cL: e3500000 cmp r0,#0
0xff9fa720L: e5840034 str r0,[r4,#0x34]
0xff9fa724L: 0a000003 beq #0x1ea738
0xff9fa728L: b5845034 strlt r5,[r4,#0x34]
0xff9fa72cL: e5940018 ldr r0,[r4,#0x18]
0xff9fa730L: ebf8b4d4 bl #0x17a88
0xff9fa734L: e8bd807f ldmia sp!,{r0-r6,pc}

; SX10 102B RefreshPhysicalScreen
0xff9df0e0L: e92d407f stmdb sp!,{r0-r6,lr}
0xff9df0e4L: eb0000a8 bl #0x1cf38c
0xff9df0e8L: e3100001 tst r0,#1
0xff9df0ecL: 1a000009 bne #0x1cf118
0xff9df0f0L: e59f4160 ldr r4,#0x1cf258 ; = #0xbe84
0xff9df0f4L: e3a05000 mov r5,#0
0xff9df0f8L: e5940034 ldr r0,[r4,#0x34]
0xff9df0fcL: e2400001 sub r0,r0,#1 ; note sub here
0xff9df100L: e3500000 cmp r0,#0
0xff9df104L: e5840034 str r0,[r4,#0x34]
0xff9df108L: 0a000003 beq #0x1cf11c
0xff9df10cL: b5845034 strlt r5,[r4,#0x34]
0xff9df110L: e5940018 ldr r0,[r4,#0x18]
0xff9df114L: ebf92233 bl #0x179e8
0xff9df118L: e8bd807f ldmia sp!,{r0-r6,pc}

lienso

And, o-ops SX20 102b dump has nothing that look like the above signature. Will try G11 now.

kellyrx8

ah man i wish more people had the 1.02c like I do. I have been using chdk on my a6xx powershot for ages and LOVED it.

Just go this new sx20 IS and have been itching for a chdk release...If I can help in anyway with a 1.02c firmware please let me know!

ajax355

Wanted to say a quick thanks to all who are working on this port. I had been using CHDK on my older camera before someone stole it; can't wait to have it again on this new sx20. Quick question if anyone has time for it (my old camera only had an LCD screen)

Using CHDK is it possible to shoot photos through my viewfinder and then have them pop up for review on the lcd? The delay to see my shots is so annoying I just turned it off.

Thanks again! Looking forward to a 1.02c beta release.

lienso

@acid2000
I downloadad G11 100l dump and disassembled some. The result:

0xffa112c4L:  e92d4010  stmdb    sp!,{r4,lr} ; ScreenLock
0xffa112c8L:  eb0000b9  bl       #0x2015b4 ; unconditional call
0xffa112ccL:  e3100001  tst      r0,#1
0xffa112d0L:  18bd8010  ldmneia  sp!,{r4,pc}
0xffa112d4L:  eb0000a7  bl       #0x201578  ; conditional call
0xffa112d8L:  e59f0038  ldr      r0,#0x201318 ; = #0x98b4
0xffa112dcL:  e590000c  ldr      r0,[r0,#0xc]
0xffa112e0L:  ebf89ed4  bl       #0x28e38 ; another call
0xffa112e4L:  e3a00000  mov      r0,#0 ; return code - zero
0xffa112e8L:  e8bd8010  ldmia    sp!,{r4,pc}

0xffa112ecL:  e92d4010  stmdb    sp!,{r4,lr} ;ScreenUnlock
0xffa112f0L:  eb0000af  bl       #0x2015b4 ; unconditional call, same place
0xffa112f4L:  e3100001  tst      r0,#1
0xffa112f8L:  18bd8010  ldmneia  sp!,{r4,pc}
0xffa112fcL:  eb00008e  bl       #0x20153c  ; conditional call, different place
0xffa11300L:  e59f0010  ldr      r0,#0x201318 ; = #0x98b4
0xffa11304L:  e590000c  ldr      r0,[r0,#0xc] ; return code - content 0x98b4+0xc
0xffa11308L:  e8bd4010  ldmia    sp!,{r4,lr}

Now, enabled_refresh_physical_screen points to 0x9840, comment: "//G11 at FFA0ECB8". FFA0ECB8 points to completely irrelevant code. Should it be 0x98b4+0xc? I am truly confused now. ???

ERR99

The comment points to the correction function for the 1.00j firmware , maybe i dont updated all comments in the 1.00l port source code files (its a stupid job... 😉 )

« Previous Page Next Page »