the sx20 porting thread

DJB1

I'm testing the 1.02B build and the only problem I'm coming across is the .CRW files can't be read by any program I try (Photoshop, Bridge, dng4ps, etc.). I've tried to run the badpixel script so that I can save the files as DNG's but that's not working either. Anything I've missed??

DJB1

viulian
@kaych - I do the conversion in the camera (in RAW menu I choose save as RAW and somewhere in the middle there's save as DNG). I believe that for DNG that you have to create the badpixel.txt file yourself, off camera, as the LUA libs were disabled (in 100f code) because of some incompatibilities ? So the camera can't do the file itself. Then you put it into CHDK/ folder on the card - and that's it.

What did you include in your badpixel.txt file?

acid2000

OK so i've looked at the colours again as last time I didn't remove my CCHDK file! None of the CAM_BITMAP_PALETTE are suitable for the SX20 so i've create my own and given it the number 6. Here it is:

#elif CAM_BITMAP_PALETTE==6 //(sx20)
#define COLOR_TRANSPARENT   0x00
#define COLOR_WHITE         0x01
#define COLOR_RED           0x91
#define COLOR_GREY          0x0F
#define COLOR_GREEN         0xA9
#define COLOR_BLUE_LT       0x2D
#define COLOR_BLUE          0x3B
#define COLOR_YELLOW        0x8B
#define COLOR_BLACK         0xFF
#define COLOR_BG            0xFE
#define COLOR_FG            COLOR_WHITE
#define COLOR_SELECTED_BG   COLOR_RED
#define COLOR_SELECTED_FG   COLOR_WHITE
#define COLOR_ALT_BG        COLOR_BG
#define COLOR_SPLASH_RED    COLOR_RED
#define COLOR_SPLASH_PINK   0xEA
#define COLOR_SPLASH_GREY   0x16
#define COLOR_HISTO_R       COLOR_RED
#define COLOR_HISTO_R_PLAY  COLOR_RED
#define COLOR_HISTO_B       COLOR_BLUE
#define COLOR_HISTO_G       COLOR_GREEN
#define COLOR_HISTO_G_PLAY  COLOR_GREEN
#define COLOR_HISTO_BG      COLOR_BLUE_LT
#define COLOR_HISTO_RG      COLOR_YELLOW
#define COLOR_HISTO_RB      COLOR_RED
#define COLOR_HISTO_RB_PLAY COLOR_HISTO_RB
#define COLOR_HISTO_B_PLAY  COLOR_HISTO_B
#define COLOR_HISTO_BG_PLAY COLOR_BLUE_LT
#define COLOR_HISTO_RG_PLAY COLOR_YELLOW

And away we go from trunk again... I suppose this isn't to bad though.

I should post my code soon just in case anyone else wants to help or try and compile the 100f.

savalangh

Hi friends
I cant see anything in mini-console , just a black box!
I cant make badpixel.bin with the script.

viulian

acid2000
5. rotation data isn't put into the EXIF or is incorrect.

After 3 hours, I found the culprit 😀

in propset2.h, the:

#define PROPCASE_ORIENTATION_SENSOR			219

is incorrect (location 219 always returns 0). Correct value is 221. On my 100f is working now!

savalangh

******** CAPTURING DNG IN CAMERA ***********
ok, just follow these steps,
1- take one raw image with camera and export it to a folder

2- Download show_bad_b.exe from the link and copy it to above folder:
http://chdk.wikia.com/index.php?title=Special:Outbound&f=Badpixel_removal&u=http%3A%2F%2Fewavr.nm.ru%2Fchdk%2Fshow_bad_b.zip

(you can give some information about this in the forum, http://chdk.wikia.com/wiki/Badpixel_removal#Links)

3-in command line type this string, with the name of raw file in step 1:
show_bad_b.exe <CHDK_RAW_FILE_NAME>

4- in same folder after this process you can find the file : badpixel.bin

5- copy it to CHDK folder inside the memory card

6- now you can adjust the DNG format in chdk menu and take DNG photos 😀

acid2000

viulian I think you need to be using propcase 3, in camera.h.

#define CAM_PROPSET 3

I'm starting to think we need a common code repo.

Lectrichead

warfarefx
Trying to test , not sure what I have done wrong as I have followed everything as far installation wise,keep getting a Update file error on the firmware update prompt screen or the CHDK logo on write protect and the camera freezes?? Any ideas on this? CHDK screen shows correctly and shows the correct 102b build, also shows the correct beta build.

I get exactly as you describe on mine also, thought I had done something wrong but I tried it twice.

I really appreciate what everyone is doing.

acid2000

I get exactly as you describe on mine also, thought I had done something wrong but I tried it twice.

I really appreciate what everyone is doing.

Guys i'm not psychic. Things I need to know from people having issues getting it to work.

*Make and model of your SD card.
*Partition format FAT32 / FAT16.
*How you made the card i.e. card tricks.
*Is it bootable, have you been able to confirm it.
*The size of the SD card and how many partitions have been created on it.
*Have you used CHDK before.

acid2000

To anyone who is interested in helping to code for the SX20 I have made my source tree publicly available via http://bitbucket.org/acid2000/chdk_sx20

viulian, you might want to try merging any 100f specific changes you have and building off this tree. It should allow you to get lua support.

is incorrect (location 219 always returns 0). Correct value is 221. On my 100f is working now!

Really, on mine the EXIF is set properly if I take a portrait photo with the hand grip at the top, however if the hand grip is at the bottom then the EXIF data is upside down. Can you reproduce?

stotes57

acid2000, first, I want to thank you for all your work on the 1.02B port. 😁

I have installed it on my camera, but seem to have a few issues. I did previously use CHDK on my A630, so I've got some understanding from the user's point of view, but certainly not from the programmers!

I'm using a SanDisk Ultra 8Gb SDHC 4 card. Partitioned with SDM into a 2 MB FAT 12 primary and the remainder a FAT 32 (i think). CHDK installed using CardTricks. No problem there - CHDK shows 7.6 GB space remaining.

Please let me know if the following are normal with CHDK on this camera.

First, I now have to use the playback/shoot button to turn my camera on - not the on/off button.

Then I get the splash screen: CHDK 0.9.9-885. Build Apr 18 2010 19:01:27 Camera sx20 - 102b.
Not that it's a big deal, but the splash screen doesn't show the CHDK graphic - just the text.

To get to shooting mode, I now have to half-press the shutter.

The shortcut button invokes <ALT> mode fine, with "Default Script" in the bottom left corner of the screen.

Menu button brings up the Main Menu, but the only way I seem to be able to get rid of the main menu is to toggle to playback mode, then back to shooting mode. Then I have to press the shortcut key again to reactivate the OSD. With the 630, another press of the menu key turned off the main menu.

I hve enabled symbols, but they don't show up. Also, when I go to a sub-menu, the previous menu stays on in the background.

I have enabled superfine mode in the CHDK menu, but don't seem to be able to activate it from the Canon Function menu.

In reading the various posts regarding installation, I got the impression that I was to somehow merge the .bin file with the existing build for the SX10. I don't believe that I have accomplished that (and don't really know how I should), but I seem to have most of the features working. However, what I don't have is things like the predefined grids. Is this what I was supposed to get from the SX10 build?

OK - I think I figured that part out. Unzip the SX 10File, then unzip your new .bin file into the same folder, then zip the whole thing again and install. Worked fine, but CHDK wants to look in the larger FAT32 partition for the grid files.

Thanks again for all your hard work.

stotes57

viulian

acid2000
Really, on mine the EXIF is set properly if I take a portrait photo with the hand grip at the top, however if the hand grip is at the bottom then the EXIF data is upside down. Can you reproduce?

Cannot reproduce, now that I changed the value to the 221 .. Both photos taken vertically (portrait), either with the hand grip on top, or hand grip on bottom, they look correct when viewed with IrfanView (<- this is how I check).
For hand grip top - Orientation sensor value is 'left bottom'.
For hand grip down - Orientation sensor value is 'right top'.

With the older value (219), it didn't work properly when the hand grip was down. The photo was vertical (resolution was set correctly), but the orientation flag was not set to 'right top' but to 'left bottom'. I had to rotate the photo with 180 degrees on PC to see it correctly.

PS - thanks for the code!

Later edit: I found that the value is bad because I read somewhere on page 12 that the raw_savefile is called even for normal photos, but just to remove the bad pixels. And since the camera had DNG_SUPPORT enabled, CHDK was actually computing the EXIF values (according to the code) [I was afraid that the camera computed the values and CHDK would mess some stack around, making the camera to compute bad values]. But it turned out that the CHDK computes everything, hence, when checking how, I realised that the only was if the orientation sensor define was not pointing to the right value.

I made the script below:

@title Orientation Find
@param a Index
@default a 0

print "Loading..."

get_prop a v
print "Index: ", a, ":", v
sleep 1000

end

and took it to around 200 and then I started taking photos horizontally and vertically for each value. For value 219, the result read was 0 in both directions. But for 221, the result was either 0 (horizontally), or 90 (vertically, hand grip down).

Lectrichead

acid2000
Guys i'm not psychic. Things I need to know from people having issues getting it to work.

*Make and model of your SD card.
*Partition format FAT32 / FAT16.
*How you made the card i.e. card tricks.
*Is it bootable, have you been able to confirm it.
*The size of the SD card and how many partitions have been created on it.
*Have you used CHDK before.

Sorry.

Card is a SanDisk 4GB SDHC, the only other info I have is the long number on the back. It has only one partition.

I formatted it clean using CardTricks, Fat16; and made it bootable.

I have used CHDK a number of times before on other cameras, successfully so I'm family with the process of installing it.

I downloaded the CHDK for the SX10, and then inserted the .BIN file posted in this thread into the zip (taking out the old one first), and then used CardTrick to send it to the card in the card reader .

As mentioned above the camera sticks on the opening logo screen for CHDK and won't do anything else when the card is write-protected, but shows the correct firmware version. When the card is not write-protected the Firmware Update menu option on the camera shows a 'Firmware Update Error'.

acid2000

When the card is not write-protected the Firmware Update menu option on the camera shows a 'Firmware Update Error'.

I might be being really stupid but i'm sure I don't have that option on my camera. From the menu screen were can the firmware update menu be found?

You 100% sure your not actually running a 100C firmware.

If there is a file on your memory card called \CHDK\CCHDK.cfg then remove it.

Lectrichead

acid2000

When the card is not write-protected the Firmware Update menu option on the camera shows a 'Firmware Update Error'.

I might be being really stupid but i'm sure I don't have that option on my camera. From the menu screen were can the firmware update menu be found?

You 100% sure your not actually running a 100C firmware.

If there is a file on your memory card called \CHDK\CCHDK.cfg then remove it.

You had me doubting myself, but using the SET and DISP. buttons shows the firmware version as GM 1.02B.

The only way I know to get to the Firmware Update option is to make sure the camera is turned off, then press the Playback Button. Now when you press the Menu button there should be an option for Firmware Update as the last option on the first tab.

There doesn't seem to be any file called "CCHDK.cfg" (or "CHDK.cfg") on the card.

acid2000

Lectrichead,

Try deleting all the files on the card apart from DISKBOOT.

If it still doesn't work can you tell me if any folders do actually get created?
Have you tried a different memory card, I have one card that CHDK just doesn't seem to boot of - in any camera.

Fredrock

Any word on when a 102C FW will be worked on?

DJB1

@savalangh...thanks for the badpixel.bin info.

I'm now able to shoot and save in DNG format. The first few images came out a shade of green. However, I imported them into Camera Raw and fixed the white balance and they came out fine. I'll continue to test this out. Thanks for everybody's hard work.

acid2000

First, I now have to use the playback/shoot button to turn my camera on - not the on/off button.

On my camera I can use the on and off button.

To get to shooting mode, I now have to half-press the shutter.

Correct, you should also be able to press the mode change button

The shortcut button invokes <ALT> mode fine, with "Default Script" in the bottom left corner of the screen.

Thats correct

Menu button brings up the Main Menu, but the only way I seem to be able to get rid of the main menu is to toggle to playback mode, then back to shooting mode. Then I have to press the shortcut key again to reactivate the OSD. With the 630, another press of the menu key turned off the main menu.

This I think to do with the refresh bug. I haven't found how to fix this yet, any help is greatly appreciated.

I hve enabled symbols, but they don't show up. Also, when I go to a sub-menu, the previous menu stays on in the background.

This bug I think is the reason why zebra and console output is not displayed correctsm the second point is the refresh bug. These two bugs may be related.

I have enabled superfine mode in the CHDK menu, but don't seem to be able to activate it from the Canon Function menu.

I could be wrong but I don't think it does, just take a picture and look at the file size

Fredrock,

Any word on when a 102C FW will be worked on?

I don't think anyone with 102C has started yet. It isn't too difficult but you do need to be a software developer.

warfarefx

My camera and card are exactly the same as his was and I solved my error problem by removing the batteries (while recharging them) and deleing everything from the card except the DiskBoot.

Its at the point now where I can test with it, already pulled several DNG files off of it to play with and love the battery status! Many thanks guys for the work on this port!

« Previous Page Next Page »