S95 Porting Thread

hqasem

What Jonas is referring to is the CHDK "directory". So after successfully installing DISKBOOT.BIN and PS.FI2 on the S95 for the S95, he's *copying* the CHDK directory (from the S90 zip file) into the S95 SD card.

Jonas- the CHDK directory is identical in all cameras (for a specific CHDK build number). The readme.txt file may differ, but that does not affect the CHDK functionality in any way.

Waldo, Reyalp and David- keep up the great work. Version 8 is looking good! Thank you.

nickliu

I always fail to download S95 1.00E binaries (version 8 ):
http://www.zshare.net/download/84063783d0f10f7f/
the file is always 0byte...but 1.00H version is ok to download(331KB).
I had tried many times from version6 till now...
Could someone send me or upload again??
Pls help me,thanks!!!

fe50

nickliu
I always fail to download S95 1.00E binaries (version 8 ):
http://www.zshare.net/download/84063783d0f10f7f/
Could someone send me or upload again?

Here's a mirror (file "S95_100E_v8.zip"): http://www.box.net/shared/eietacqago

Microfunguy

@Waldo

I am having great difficulty porting this to SDM.

The camera crashes on booting when restoring CFG values.
That function also executes if there is no existing CFG file.
For conf values that have an associated conf_change_script_file() function, script_load() is called.
That calls script_scan(..) and crashes.
That code is common to all cameras.

Have you had similar problems ?

waldo

Microfunguy
@Waldo

I am having great difficulty porting this to SDM.

The camera crashes on booting when restoring CFG values.
That function also executes if there is no existing CFG file.
For conf values that have an associated conf_change_script_file() function, script_load() is called.
That calls script_scan(..) and crashes.
That code is common to all cameras.

Have you had similar problems ?

I thought I understood the problem when you posted this to the SD940 thread, but now that it is a S95 question, I'm not sure. 😉

Microfunguy

I have absolutely no idea.

I have reduced script_scan() to just do the strncmp comparison for @title.
I have just been told it crashes.

If I am told it is OK with that commented-out I will check strncmp address.

EDIT

The problem section of code loads the script parameters.
With that commented-out, scripts will run with hard-coded parameter values.

Johng

OK - I've just installed 1.00H binary (version 8 ) and all seems fine but due to my newbee status I'm not sure if the delayed bootup is normal.

When turning the camera on with a quick tap of the 'on' button it will always start into the 'review' mode.

If instead I hold the on button down for about 2 seconds it will boot into the normal shoot ready mode and the chdk displays will popup after about 6 seconds.

Do these timings seem normal from what other have seen so far?

Many thanks to all for the dedicated work behind this binary and project.

.

waldo

Johng
When turning the camera on with a quick tap of the 'on' button it will always start into the 'review' mode.

If instead I hold the on button down for about 2 seconds it will boot into the normal shoot ready mode and the chdk displays will popup after about 6 seconds.

Do these timings seem normal from what other have seen so far?

Yes, although my camera boots CHDK in about 1 second.

othalan

I just tried out CHDK on my S95 and I cannot take RAW images.

If I setup CHDK to use RAW images (CHDK RAW, not the native RAW format), the camera takes an image, pauses briefly, then turns off without closing the lens. I am guessing this means the CHDK firmware crashed.

When I power the camera back on, I find the image has not been recorded.

Original Firmware: GM1.00H
CHDK Download: S95_100H_v8.zip
Card Used: 32GB Transcend Card
CHDK Load Method: Manual & Auto-Boot (using different 32GB cards)

The S95 native RAW format works just fine. I discovered this problem trying to run the badpixel.lua script, but was able to reproduce it with a fresh memory card with only the CHDK firmware loaded (no scripts) and doing nothing other than switching to CHDK Raw mode. In case it made a difference, I loaded the firmware first on a 32GB card with a small FAT16 partition at the start of the card to auto-boot CHDK. Then on a second card, I left the original card formatting intact and loaded the firmware manually. Same result in both case.

Assuming this is a bug (rather than something I messed up which I find unlikely yet possible), is there anything I can do to help solve this? Any additional information I can provide?

othalan

FYI, I also just tried using a 1GB card I've used in other cameras and got the same result as described above.

Microfunguy

I am also interested in CHDK raw.
There are new features in SDM that require CHDK raw even on cameras that have native raw.

Are you saying that simply enabling CHDK raw in the menu causes the camera to crash, before you take a photo ?

Microfunguy

@Waldo

In 100H capture sequence, for example, are sub_FF98AEC0 and sub_FFAF9990 required ?
They do not seem to be patched.

Should 'BL capt_seq_hook_set_nr' be inserted before 'BL wait_until_remote_button_is_released' ?

capt_seq_hook_raw_here() tells spytask that raw data is available.
spytask processes the data in memory and then simply copies the appropriate number of bytes to a file.
Even if the sensor address is incorrect, you would not expect the copying to crash the camera.
spytask then tells capt_seq_hook_raw_here() that the data has been saved and the remainder of the capture sequence can proceed.

waldo

Microfunguy
@Waldo

In 100H capture sequence, for example, are sub_FF98AEC0 and sub_FFAF9990 required ?
They do not seem to be patched.

I haven't looked at the particular functions you mentioned, but in general, functions that are not executed do not need to be in the build.

Should 'BL capt_seq_hook_set_nr' be inserted before 'BL wait_until_remote_button_is_released' ?

capt_seq_hook_raw_here() tells spytask that raw data is available.
spytask processes the data in memory and then simply copies the appropriate number of bytes to a file.
Even if the sensor address is incorrect, you would not expect the copying to crash the camera.
spytask then tells capt_seq_hook_raw_here() that the data has been saved and the remainder of the capture sequence can proceed.

I have no idea, but I can try what you suggest. What benefit should I be looking for if that change is made?

Microfunguy

Sorry, I mean your 'patched' versions of those functions, that do not seem to be patched.

I have never tested the effect of forcing Canon noise-reduction on/off so have no idea if it is any use.

It just sets a Canon variable to 0,1 or 2.

I am more interested in why raw saving does not work.

waldo

Microfunguy
I am more interested in why raw saving does not work.

Can you please explain why you need raw via CHDK?

Microfunguy

360 degree stereo panoramas using a SINGLE offset camera.
See my explanation here :-

http://stereo.jpn.org/eng/stphmkr/help/file_27.htm

'Streak' and peripheral photography creates built-up image directly in camera :-

http://sciencephotography.com/FAQ/ch4-image-stability/streakphoto-ch4b.html
http://www.streakphotography.com/

This is already working on my A620.

nickliu

fe50

nickliu
I always fail to download S95 1.00E binaries (version 8 ):
http://www.zshare.net/download/84063783d0f10f7f/
Could someone send me or upload again?

Here's a mirror (file "S95_100E_v8.zip"): http://www.box.net/shared/eietacqago

Dear fe50 ,
I can download correct file.
thanks a lot!

waldo

Microfunguy
360 degree stereo panoramas using a SINGLE offset camera.
See my explanation here :-

http://stereo.jpn.org/eng/stphmkr/help/file_27.htm

'Streak' and peripheral photography creates built-up image directly in camera :-

http://sciencephotography.com/FAQ/ch4-image-stability/streakphoto-ch4b.html
http://www.streakphotography.com/

This is already working on my A620.

That may be the answer to the question of why you would like to use Raw, but I still don't understand why you need CHDK Raw - the camera already supports Raw in the Canon firmware.

Microfunguy

The stereo panorama requires that you save two narrow raw strips each side of centre, each strip typically 150 pixels wide and saved very quickly.

The streak and peripheral option builds the image in-camera, column by column until complete.
A column can be just one pixel wide.

You cannot do the above with ANY consumer/pro camera at any price.

The feature is unique.

othalan

waldo

Microfunguy
I am more interested in why raw saving does not work.

Can you please explain why you need raw via CHDK?

Can't speak for waldo, but I was hoping to use the DNG file format, but could live without that.

If CHDK RAW & DNG are not to be supported that would actually be OK with me, but in that case they should be removed entirely, not left as a feature which causes the camera to crash.

Microfunguy
Are you saying that simply enabling CHDK raw in the menu causes the camera to crash, before you take a photo ?

You can turn on RAW mode in the menu (or using the alt/display button sequence). The camera doesn't crash until you actually press the shutter release button. At that point I hear the click of the camera taking a picture, there is a pause, then the camera apparently crashes before saving the picture.

« Previous Page Next Page »