the sx20 porting thread

fe50

@SkyWalker9
What's in the EXIF data of the images ?
Normally the images are always stored in one / the same direction, the rotation info is only written to the EXIF meta data; the camera shows the image based on this data and the setting from the Canon menu.

Most imaging applications does it the same way, they rotate the image based to the EXIF data; e.g. the Canon software (ZoomBrowser) works this way.

Could you compare the EXIF data from two images, with CHDK & Canon-only ?
If you remove the EXIF data, how do the apps show the images ?

ferrari

Please, is somebody working also on CHDK for FW 1.00F? Or is somebody planning? Neszt did something, but it needs some modifications...
Or is there any way to change (upgrade) FW in camera?
Thanks in advance

SkyWalker9

fe50
@SkyWalker9
What's in the EXIF data of the images ?
Normally the images are always stored in one / the same direction, the rotation info is only written to the EXIF meta data; the camera shows the image based on this data and the setting from the Canon menu.

Most imaging applications does it the same way, they rotate the image based to the EXIF data; e.g. the Canon software (ZoomBrowser) works this way.

Could you compare the EXIF data from two images, with CHDK & Canon-only ?
If you remove the EXIF data, how do the apps show the images ?

@fe50
The EXIF Orientation is the trigger for the viewing software being used. IrFanView indicates the EXIF Orientation is Left Bottom or Right Top and ExifPro indicates the EXIF Orientation is 90 degrees CW and 90 degrees CCW respectively on the CHDK photos.

I also checked the photos on the following viewers: Canon on-camera viewer, Picasa v3, ACDSee Pro v3, IrFanView, ExifPro and the Windows Photo Gallery. All but the Windows Photo Gallery displayed the non-CHDK and CHDK SD card photos as mentioned in the previous posting. The Windows Photo Gallery displayed the photos as all horizontal with the 90 degree CCW vertical photo with the top to the right and the 90 degree CW vertical photo with the top to the left.

DandyOne

Yup, the 90 degrees clockwise taken photos are upside down (the EXIF info is wrong). I just realized that I automatically take vertical pictures that way because my previous camera had a flash on its left side.

SkyWalker9

Since many of the FW versions are still being worked, this might be of interest when you start testing the builds. I wrote a script that generates a "snapshot in time" report of the camera settings using the currently available "get" statements in CHDK uBasic - with the exception of "get_platform_id" and "get_tv".

You can find it here: https://chdk.setepontos.com/d/5326

gimzo

Hi
Not trying to be boring or bug anyone, but does anyone know if 1.02D is being worked on ?
Thanks

f_m_b

fe50
When a new camera is ported, the port stays in BETA phase for some time, dependend on the feedback of the users and also on the time the porter/developer invests...
BETA state will be removed after some weeks/months when the common CHDK features are working & the feedback of testers is positive.
The SX20 1.02b has been included into the official CHDK source code tree (the "trunk") some day's ago, only one feedback/user report (reply #666, still open) until now... 😉

Talking about beta...
I'am "fighting" with a lot of crashes with CHDK 0.9.9-885 from 16 Mai 2010.
I think in most cases the crash happens when i use zebra and "half shutter down".

reyalp
I'm not aware of any "crash-dump" capability. The closest I've come is in scripting by using print statements that dump the values just before execution of a particular code statement.
There is https://chdk.setepontos.com/d/2509/71

I tried to use the crash-dump tool, but I start the script and became following answer: "your CHDK does not support native calls"
So i think the "dump"-script doesn't work with this CHDK. 🙁

Any Idea?

reyalp

f_m_b
I tried to use the crash-dump tool, but I start the script and became following answer: "your CHDK does not support native calls"
So i think the "dump"-script doesn't work with this CHDK. 🙁

Any Idea?

You need to build it with OPT_LUA_CALL_NATIVE=1 set in your buildconf.inc

Crashing with zebra could be due to lack of free memory.

afrikaa

I'll do maybe a stupid question, but I wanted to know what is the difference between the various firmvare 100F, 102B, 102C, 102D?
The Canon has corrected the defects?

reyalp

afrikaa
I'll do maybe a stupid question, but I wanted to know what is the difference between the various firmvare 100F, 102B, 102C, 102D?
The Canon has corrected the defects?

Most likely. Other possibilities are hardware changes in production, or adding support for features required for certain markets. They appear to only offer updates to the public if it's a major issue.

The changes between many canon releases are small, sometimes < 100 bytes difference between versions. It shouldn't be too hard to figure out what they did, but no one has bothered that I know of.

f_m_b

@reyalp:
Thanks. 😀

reyalp
You need to build it with OPT_LUA_CALL_NATIVE=1 set in your buildconf.inc

Crashing with zebra could be due to lack of free memory.

OPT_LUA_CALL_NATIVE=1 means, that i have to recompile the chdk?
At the link of acid2000 there are no source-files. Is that correct?
Where can i found it?

🙁
Problems i found:

a)
To find out why most of my dng are corrupt, crashes are not useful. So i avoid the crashes by disabling all chdk functions but raw.

I found out that the problem (about 80% of the dng's are corrupt) comes when i disable "RAW file in dir with JPEG".
If i enable that feature, all dng's are non corrupt and readable.

b)
If the first foto after starting the sx20 is shot with enabled dng, the first dng file has a time/date-stamp from 1.1.2000 00:00. Following dng's are set with correct time/date-stamp.
If the first foto after starting the sx20 is shot with disabled dng (only jpg) all following dng's have the correct time/date-stamp.
jpg Files doesn't have this problem.

c)
With the following settings i became every start of the sx20 a new foldernumber and the filecount begins at IMG_0001.jpg:
"create Folder" = daily or month
"file numbering" = continous

d)
In "play"-mode i can't show all fotos which are on the card. Only the newest fotos are visible.

😀
I found a solution for my problem with the neverending partition-swapping on my 8GB-SD card:
I partitioned the SD-card (and set the bootable flag) with gparted in two 4GB FAT16 partitions.
CHDK is on both of them.
I take fotos on the first partition and without swapping i can read it on the PC (XP).
When the first partion is full i swap to the second partition with "Miscellaneous stuff"->"Swap partitions" in 'ALT'-Mode and can use the next 4GB on the second partition.

fe50

f_m_b
OPT_LUA_CALL_NATIVE=1 means, that i have to recompile the chdk?
At the link of acid2000 there are no source-files. Is that correct?
Where can i found it?

In the official CHDK trunk:

fe50
FYI - the SX20 102B port is in the official CHDK trunk now:
...
To compile a full package (like the packages delivered by the Autobuild Server), simply use the CHDKShell and let the shell download the latest trunk; then edit the makefile - delete the leading # from the lines with "SX20" & save the makefile. Restart the CHDKShell, now the SX20 1.02b will be listed and can be compiled like all the other firmwares...

SkyWalker9

f_m_b
I found a solution for my problem with the neverending partition-swapping on my 8GB-SD card:
I partitioned the SD-card (and set the bootable flag) with gparted in two 4GB FAT16 partitions.
CHDK is on both of them.
I take fotos on the first partition and without swapping i can read it on the PC (XP).
When the first partion is full i swap to the second partition with "Miscellaneous stuff"->"Swap partitions" in 'ALT'-Mode and can use the next 4GB on the second partition.

You mentioned using "gparted" to setup your partitions, but I'm not sure many people would know how to use it. I decided to checkout your "discovery" and modified my previous tutorial to include how to setup an 8G card like you mentioned using the Active@ Partition Manager (free). Here is a link for anyone who is interested in the tutorial: http://rapidshare.com/files/400436852/Installing_CHDK_on_SD_Cards__Windows_OS_.pdf

I have tested your "discovery" and really like what I see so far. The numbering sequences of the photos are correct after swapping and you can use the USB to PC transfers from either partition (JPGs and movies - still not DNGs, etc.) To make sure the photos and movies get placed on the swapped partition, you must power the camera off/on for the camera to recoginize the partition after swapping. This appears to be a handy "discovery" especially if you want to keep events or other things on separate partitions.

This becomes even more important when you consider that if you currently remove the SD card to unload the larger partition of the SD card (DNGs, etc.), you usually are required to do two partition swaps using SDM Installer. With this new setup, you simply remove your SD card, unload then put the SD card back in the camera and you are ready to start again. You don't use the SDM Installer during this process therefore you can unload on a computer without the SDM Installer installed.

Appreciate you sharing this "discovery"!

Update: CHDK estimates show each partition can have approx 1205 JPGs (fine mode) or 180 DNGs (with accompanying JPGs - fine mode) - plenty of room on each partition.

DandyOne

I guess this trick can't be used for 16GB cards? It's limited to 2 partitions?

SkyWalker9

DandyOne
I guess this trick can't be used for 16GB cards? It's limited to 2 partitions?

Interesting question. Using the Active@ Partition Manager you could easily set up four 4G (approx) partitions and possibly format each bootable, FAT16 with the SDM Installer - I haven't tried more than two partitions using the SDM Installer to see if it can handle more than just two.

If you could setup the partitions, then it would be interesting to see what would happen when you used CHDK Misc > Swap. Would it just continue to swap (cycle) through all four partitions and then re-start with the first one again? Would it just swap between the first two partitions ? Lots of questions, but no answers. I'd love to try this just to see what happens but I don't use 16G SD cards.

Update: I tested the SDM Installer using three partitions and it wasn't able to handle more than two partitions, so the SD card would have to be setup using another app.

reyalp

My guess is it would just swap the first two. Supporting more shouldn't be too hard.

bdasmith

Also very much looking forward to the 1.02d firmware port....I am excited to try this out...Love this camera, and RAW support would make me love it even more 😀

Thanks to all who are working so hard on all this. Any way to contribute funds for peoples time or anything?

f_m_b

Hello fe50

I checked out the trunk-version at your link with tortoise and build it with the following comand line:

gmake PLATFORM=sx20 PLATFORMSUB=102b fir

fe50
In the official CHDK trunk

I became errors in gui.c while using "draw_set_environment" (gcc 3.4.6).
I wonder about that because the #include "gui_draw.h" is set and other commands like draw_init() are working fine. The syntax of draw_set_environment(NULL, NULL, SCREENX, SCREENY); seems to be ok.
I have commented out all draw_set_environment-commands and the build generate me a new DISKBOOT.BIN file. 😁
The commented lines brings me a very small CHDK screen on the camera. 🙁

Then i tried the VERY COMFORTABLE 😁 way with CHDK-Shell-v271.exe
with the same compileroptions?, same sources, same gcc 3.4.6:
build needs a lot more time (full compile-flag is not set in Shell)...
... and brings following errors without building the new DISKBOOT.bin file:

*** Warning: File `../platform/sx20/libplatform.a' has modification time in the future (1277143414 > 1277050339)
*** Warning: Clock skew detected. Your build may be incomplete.
... and many more of that warnings ...
gmake: *** Warning: Clock skew detected. Your build may be incomplete.

a build with version 342 ended with the same errors.

Do you have any idea what is my fault or what happens? 😀

Bye the way what are the version-numbers in CHDK-Shell-v271.exe
Yesterday i had version number 341 and today 342, but svn-update on my source folder says, there is no code changed?

Bye Frank

fe50

Hi Frank,

i guess you mixed up some things...

f_m_b
*** Warning: File `../platform/sx20/libplatform.a' has modification time in the future (1277143414 > 1277050339)
*** Warning: Clock skew detected. Your build may be incomplete.

The .a files are locally compiled binaries, not source code files from the SVN; there's either something wrong with your system (check your time/clock settings), or you didn't run a "make clean" after your first test & before compiling again.

I suggest to
- install a new CHDKShell into a new folder
- let the CHDKShell load the gcc env (you can also copy the \gcc and \gcc4 folders from your existing installation)
- select the SVN source (button "Set SVN site..."): CHDK for the official trunk (CHDKDE is the german version, with some modifications and additions)
- let the CHDKShell download the latest trunk (changeset #905 atm)
- adjust the "Compile options...": select the gcc 4.4, some of the newer ports may not compile with the old gcc 4.3 version

Now select any of the cameras, e.g. one of the SX10 firmwares; compile this to make sure the dev env works flawless.

Now you can edit the main makefile & remove the leading # from the SX120 lines as described above...

Bye the way what are the version-numbers in CHDK-Shell-v271.exe
Yesterday i had version number 341 and today 342, but svn-update on my source folder says, there is no code changed?

These are CHDKDE version numbers, latest CHDK trunk is #905.
The changeset number increments on changes in all branches of the SVN tree, also on commits in personal branches; #342 was a commit from yesterday in the CHDKDE trunk...

Some basics for using the CHDKShell & the different SVN sites & branches:
- select the SVN site (CHDK for the official site, CHDKDE for the german one)
- select "trunk" (above the "Change" button) to use the trunk of the site you've selected; this is the source used by the autobuild servers
- if you want to use one of the branches, make your choice with the "Branches" button

Note: the personal branches are personal test builds, nothing official, there may be errors, bugs or critical features which could harm your camera !
Also often the personal branches are incomplete or need special local settings to compile (e.g. my fe50 or fe50t branches - don't use them).

In the german CHDKDE, the SX20 is already enabled in the main makefile, the german autobuild server delivers ready-to-use packages... http://www.wirklemms.de/chdk/forum/autobuild.php

Microfunguy

f_m_b brings following errors without building the new DISKBOOT.bin file:

*** Warning: File `../platform/sx20/libplatform.a' has modification time in the future (1277143414 > 1277050339)
*** Warning: Clock skew detected. Your build may be incomplete.
... and many more of that warnings ...
gmake: *** Warning: Clock skew detected. Your build may be incomplete.

Hi Frank, they are warnings not errors, they would not prevent compilation from succeeding.

(you always get those warnings, EWAVR once asked how do you get rid of them).

What are the first few ERRORS reported ?

David

« Previous Page Next Page »