SD940 (IXUS120) porting thread - page 12 - DryOS Development - CHDK Forum supplierdeeply

SD940 (IXUS120) porting thread

  • 542 Replies
  • 99516 Views
Re: SD940 (IXUS120) porting thread
« Reply #110 on: 20 / December / 2010, 13:27:18 »
Advertisements
it's recommended to disable the "RAW File in Dir with JPEG" setting from the CHDK RAW menu.

Good point.  The default is disable - but I did noticed the multiple folder issue when I enabled it to see what it would do.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline waldo

  • ***
  • 238
Re: SD940 (IXUS120) porting thread
« Reply #111 on: 20 / December / 2010, 13:35:01 »
It sounds like there may be some differences between the 102c and 103c code, but I'll compare the 103c files to what I have when I see them.
« Last Edit: 20 / December / 2010, 15:12:03 by waldo »

Re: SD940 (IXUS120) porting thread
« Reply #112 on: 20 / December / 2010, 14:55:12 »
DELETED

Moved to S95 thread.

« Last Edit: 20 / December / 2010, 15:19:08 by Microfunguy »

*

Offline waldo

  • ***
  • 238
Re: SD940 (IXUS120) porting thread
« Reply #113 on: 20 / December / 2010, 15:16:22 »
@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 ?

Did you notice this edit in conf.c ?

Code: [Select]
//    CONF_INFO( 63, conf.alt_mode_button,        CONF_DEF_VALUE, i:KEY_PRINT, conf_change_alt_mode_button),
// change default to Print for sd940
    CONF_INFO( 63, conf.alt_mode_button,        CONF_DEF_VALUE, i:KEY_DISPLAY, conf_change_alt_mode_button),

I guess looking at it now, the comment should say "Change default to Display"....


Re: SD940 (IXUS120) porting thread
« Reply #114 on: 21 / December / 2010, 05:04:32 »
Well, without the ps.fi2 I don't get the firmware update option in the menu, with the file I do, though a zero-byte file with the name ps.fi2 doesn't seem to load the chdk properly (camera hangs with a black screen, have to remove the battery to get it goin' again)...
I just looked at the forum thread for making the fi2.inc file needed to produce a ps.fi2 file. 
http://chdk.setepontos.com/index.php/topic,2995.0.html
Looks like more work than I have time for right now.  Did you try using the other (SD card write protect) method of booting - it does not need the ps.fi2 file.

Thanx for the hint, I got it working now with a different SD card with the writeprotect enabled, gonna do some testing

Re: SD940 (IXUS120) porting thread
« Reply #115 on: 21 / December / 2010, 09:00:13 »
Thanx for the hint, I got it working now with a different SD card with the writeprotect enabled, gonna do some testing

Latest Beta release at the start of this thread has what you were looking for. I haven't tested it so if you get a chance you might see if it works ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SD940 (IXUS120) porting thread
« Reply #116 on: 21 / December / 2010, 13:08:38 »
I spent some time on the SD940 port.
.....
I'm hoping that more than the two of us are using this.  I'm counting on others to test this, since I only rigorously test what I use, which is about 10% of the features.

waldo :  Did you try shooting RAW ?  I see people over in the S95 thread are having the same problem as me.  
http://chdk.setepontos.com/index.php?topic=5641.msg58456#msg58456
The camera locks up while trying to write a RAW file to the SD card.  Also, there is a file created but it seems to be all black when I use FastStone Image Viewer ( reported to read CHDK RAW files correctly).

UPDATE :  As per the S95 thread, I reduced hook_raw_size() to 0x4000.  Camera still hangs when creating the file - but the file is 16K instead of 8M so it used the smaller value.  Also,  the filename sequential number seems to work fine for the RAW files so the camera parameter used for that appears be okay.
« Last Edit: 21 / December / 2010, 19:09:03 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SD940 (IXUS120) porting thread
« Reply #117 on: 21 / December / 2010, 15:04:48 »
Thanx for the hint, I got it working now with a different SD card with the writeprotect enabled, gonna do some testing

Latest Beta release at the start of this thread has what you were looking for. I haven't tested it so if you get a chance you might see if it works ?

It works.


"bricked" camera ?? - solved
« Reply #118 on: 22 / December / 2010, 11:56:27 »
I think I maybe just "bricked" my SD940 working with CHDK.   I now get an error message on startup (with or without CHDK loaded) that says "Lens error, restart camera".   The green LED flashes for a while and then the camera shuts down.  Ouch.

Anybody dealt with this before ?

I've been working on getting RAW to function and chased the problems down to the call to utime() in raw_savefile() in raw.c.  If I comment out that call,  image files are written to the SD card without crashing the camera.  I noticed that utime() in wrapper.c builds differently depending on whether CAM_DRYOS_2_3_R39 is defined in camera.h or not. So I undefined it to see what would happen, rebuilt and loaded.  The camera failed to boot CHDK with that change.  So I rebuilt with CAM_DRYOS_2_3_R39 defined and discovered the lens error on restart.  CHDK will boot but once it returns control to the camera I get the error message again.

UPDATE :  solved - lens was stuck. I guess it doesn't take much to do that.  See two posts down for details.
« Last Edit: 22 / December / 2010, 12:40:34 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline c10ud

  • ***
  • 245
Re: SD940 (IXUS120) porting thread
« Reply #119 on: 22 / December / 2010, 12:15:12 »
i sometimes had that message while messing up with zooming and some random camera, but it automagically fixed itself rebooting the camera without injecting code. maybe you have some code that's calling bad firmware addresses?

 

Related Topics