the sx20 porting thread

anonfelon

Hey ! Somebody please build a stable version for us 1.00f users.. please..

Thanks in advance

zippovka

anonfelon
Hey ! Somebody please build a stable version for us 1.00f users.. please..
Thanks in advance

http://chdk.neszt.hu/bin/

jan

zippovka

anonfelon
Hey ! Somebody please build a stable version for us 1.00f users.. please..
Thanks in advance

http://chdk.neszt.hu/bin/

Actually, this version is missing some RAM optimizations and at least for me, it is not very stable. Sometimes it crashes on startup and I have to disable CHDK because it won't turn on otherwise or the camera freezes when using it. Maybe this is related to missing RAM. I hope that someone out there can update the 1.00f port.

ultimA

jan
...

I spent 5 minutes creating an updated 100f build. I basically just pulled the sources from neszt's git and mixed in his sub/100f folder with the latest revision of chdk. This might not have all the fixes/functionality from the other firmware versions, but since the RAM-optimizations live in the non-firmware specific part of the code, this *should* give you all the fixes for the memory problems. I hope you'll be free from most of the crashes now (unless there are bugs in the 100f port itself).

Get it here: http://drop.io/hidden/jlqkjtgpqd29rhy/asset/c3gyMC0xMDBmLTAtOS05LTk1NC1mdWxsLXppcA%253D%253D

Someone with a 100f should finish up this port. There shouldn't be too many things left to do, if at all. I did need to add "NSTUB(Restart, 0xff83a540)" to stubs_entry_2.S to make it compile with the latest CHDK. The address is not verified or tested, but if you ask me it is probably the same as in the other versions, so I just assumed it is. Anyone who picks up this port should verify it.

@jan, anonfelon: For the sake of all 100f users, please leave feedback on this forum and tell us what exactly does/doesn't work.

jan

I tried the new build, and at first it crashed on startup, then I deleted the CHDK folder and the camera starts up fine now. I already deleted the folder some time ago, but that didn't have any effect then. Hopefully it does work now.

After a short time of testing I noticed one problem with the new build. When zebra or edge detection are enabled, the Canon OSD does only get updated when releasing the shutter. The CHDK OSD and both zebra and edge detection work fine.

edit: Actually the problems with the Canon OSD do appear as well after entering and exiting alt mode. The Canon OSD is updated as usual after switching to play mode and back.

cacharrin

There's a little bug with the OSD (I'm using latest 1.02d)

If I turn the LCD in this position:

The CHDK menu is not correctly showed... it appears X-Inverted

There's a way to correct this?

Thank you for your effort guys!!!

fe50

cacharrin
The CHDK menu is not correctly showed... it appears X-Inverted
There's a way to correct this?

You can disable Canon's "Reverse Disp" setting, see also here: https://chdk.setepontos.com/d/3564/13

cacharrin

ok, Thanks 😀

AK49BWL

Okay, I must say I'm a very satisfied user of CHDK on my SX20 102b since the middle of May (still using the May 16th build lol, should probably update this thing already)... But I have a question. I tend to use video mode almost more than taking pictures, and was just wondering if it would be possible to enable the full zoom speed mode in video, either by script or by modifying the CHDK build somehow... And I'm not worried about the noise from the zoom. I would assume it's similar to how zoom-in-video was enabled for my SD770, but I really have no clue. I tire of waiting for the lens to just get out there when I want it to, haha. So, is this possible, or am I pretty much out of luck?

mmrto

Hello,

first of all, thank you for porting chdk for SX20 with firmware 1.02D. I was able to run it in a 8GB flash card with a boot partition.

I noticed that the raw files was not saved in the correct folder when "save raw file in dir with Jpeg" was marked. My raw files always appeared at the 100CANON folder. This cause the camera to not show any of the pictures taken. When switching on the camera again in preview mode, the "no image" appeared.

So I believe that the camera didn't like that 100CANON folder. My sx20 store the pictures in a monthly changed folder inside DCIM. Something like "100___10" for a picture taken in October. If I put the raw files inside these folders, the pictures can be previewed in camera's display. So I concluded that the raw folder was messing up the camera firmware behavior.

I recompiled chdk, modifying the raw.c source file, in order to include the month number in the dir name where the raw files are stored. Now my chdk correctly save the raw in the same folder of the jpeg. But the "save raw file in dir with Jpeg" have no more effect because I don't check that flag in my code.

I have done this in order to check if the raws are visible by usb. But, unfortunately, this is not happening. I tried several combinations of raw prefixes and extensions, following the hints posted in this forum, but the raws are still hidden, no matter if they are DNG or not.

What can I do to make the raw files available by usb?

If you have any clue, please share with me.

Best regards and sorry any English mistakes.

Miguel

lemonhawk

I have version 1.00f and when I make the bad pixel file it indicates 16403 bad pixels. When I look at the .DNG file that gets made its horrible compared to the .jpg. Any hints on how to make a badpixel file is useful? it does make some complaint when storing the file something about the OS ...

cyberd

Just passing by to thank all developers for the great job done with the Sx 20's CHDK!

Cheers guys!

ultimA

lemonhawk
I have version 1.00f and when I make the bad pixel file it indicates 16403 bad pixels. When I look at the .DNG file that gets made its horrible compared to the .jpg. Any hints on how to make a badpixel file is useful? it does make some complaint when storing the file something about the OS ...

16403 sounds many, but in reality it is somewhat average. So you don't have to worry about it. The fact that the DNG looks bad probably has some other reason. Without further information, it is hard to say. What software are you using to look at the DNG? Maybe, can you post a 100% crop of both the JPG and DNG?

RogueRanger

I've noticed that I can't get a faster shutter than the built-in 1/3200sec. When I set a faster shutter override value, I get 1/3200 in the actual shot - I tried with different aperture values, same result. I saw that this was a bug in the sx10, and it was fixed. The fix was added to the autobuild (which I'm using), as you can read here:
https://chdk.setepontos.com/d/4392

However, it seems like with the sx20 the fix doesn't work. Anyone else have this problem?

fe50

Hello & welcome, RogueRanger !

RogueRanger
I've noticed that I can't get a faster shutter than the built-in 1/3200sec. When I set a faster shutter override value, I get 1/3200 in the actual shot - I tried with different aperture values, same result. I saw that this was a bug in the sx10, and it was fixed. The fix was added to the autobuild (which I'm using), as you can read here:
https://chdk.setepontos.com/d/4392

Pls. try again in P or M mode: set the CHDK override (you should see Tv😖xx on the screen), then shoot directly into a strong light bulb; change the Tv override & take another shot...you should see a difference in the histogram / image brightness.

Note - the Canon OSD doesn't show the correct values when CHDK overrides are active...

RogueRanger

Thanks a lot for your reply. You were right, the override does work - for some reason when I tried it the first time (in M mode) I didn't see a difference.
I wonder what the actual fastest shutter is? there's no information at the moment for the SX20 or the SX10 (I assume it's similar for both models).

cacharrin

Hi everyone,

I have problems trying to run a script... in my older A430 camera i used some scripts like Yet Another Intervalometer, ultra intervalometer and MD scripts... i tried this scripts with my new SX20 IS, but almost all scripts has problems... some of them block input to camera, and i need to delete the last script executed to allow CHDK to run again... with others, i select them and apparently they dont get loaded because i dont see the script name neither the parameters configuration...

Can somebody help me?

I have this scripts saved in "H:\CHDK\Scripts\OtherSubfolder"... H is my card reader drive letter...
Do i need to save the scripts directly in "CHDK\Scripts" Folder?

Im searching primary for a intervalometer script...

Which script do you use for this purpose?

thanks a lot 😀

reyalp

cacharrin
I have this scripts saved in "H:\CHDK\Scripts\OtherSubfolder"... H is my card reader drive letter...
Do i need to save the scripts directly in "CHDK\Scripts" Folder?

CHDK doesn't require that you put scripts in a particular folder, but dryos cameras appear to have some (not clearly defined) path restrictions. Try putting it in CHDK\SCRIPTS, or CHDK\<some other short name>

I suggest always use directory names <= 8 characters, and using only uppercase letters.

cacharrin

Ok, thanks, i will try it 😀

jvdvegt

I've installed CHDK on my SX20 1.02d camera. Thanks for all the hard work!
I had some issues activating the DMG format using two partitions my SD card, as it wasn't until page 62 that I read only diskboot.bin had to be on the first partition. As a result, I didn't see any scripts, so I could not create badpixels.bin
I tried the tools to use on a PC mentioned in this thread (http://chdk.wikia.com/wiki/Badpixel_removal ), but my CGW file format wasn't recognized. I merged the source of both tools mentioned and added these specs:

[tt] case (4080*3048*12)/8: rowpix=4080; rows=3048; bits=12; black_level<<=2; threshold<<=2; break; // another 12 MP with 12 bit RAW[/tt]

This resulted in a badpixels.bin file I could use to enable DMG files. But now that I've got the scripts working, I suppose badpixels.lua generates a better file.

« Previous Page Next Page »