SX260 HS Porting Thread - page 24 - DryOS Development - CHDK Forum

SX260 HS Porting Thread

  • 642 Replies
  • 233668 Views
Re: SX260 HS Porting Thread
« Reply #230 on: 15 / May / 2012, 21:53:55 »
Advertisements
I don't know whether this bug is specific to the SX260 or is seen on other models too.
It's not a bug.  The difference you are seeing has been the topic of discussion many times on this forum.  Just search for "market ISO vs real ISO".   Here's just one post that I found quickly that explains it :

http://chdk.setepontos.com/index.php?topic=895.msg9036#msg9036

There are many others.

Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX260 HS Porting Thread
« Reply #231 on: 15 / May / 2012, 22:39:21 »
When I say "real" ISO I just mean the value recorded in the JPEG file, so I'm not sure that's the same issue. In the test I did CHDK said it was going to force ISO 400, but the EXIF data in the image says 640 was actually used.

Re: SX260 HS Porting Thread
« Reply #232 on: 15 / May / 2012, 23:26:48 »
When I say "real" ISO I just mean the value recorded in the JPEG file, so I'm not sure that's the same issue. In the test I did CHDK said it was going to force ISO 400, but the EXIF data in the image says 640 was actually used.
From http://chdk.wikia.com/wiki/CHDK_User_Manual#Override_ISO_value :

The values entered in the ISO override are not exactly equivalent to the values in the Canon UI and exif. Canon uses different values for calculation ("real" ISO) and display ("market" ISO). The CHDK override works on "real" values. The "real" value is lower than the displayed value, so an override to 50 will result in a "market" value of around 80. The exact relationship isn't well specified.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX260 HS Porting Thread
« Reply #233 on: 16 / May / 2012, 17:48:09 »
Got it, so it seems to be working as intended. In the short term I don't think I'll be trying a lot of features other than RAW mode and ISO override (for exposures >1sec where the SX260 normally forces ISO 100), but if anyone wants me to test something specific I can do that.
« Last Edit: 16 / May / 2012, 18:03:15 by kriktsemaj99 »

*

Offline rudi

  • ***
  • 129
  • A590IS_101B, SX260HS_100B
Re: SX260 HS Porting Thread
« Reply #234 on: 18 / May / 2012, 13:56:23 »
At first, thanks asm1989 and all others for your great work to porting sx260!

Here are some changes for 100b as diff from trunk 1857 based on asm1989s sx260-100b-allsources-v9.zip:
- fix NUM_DATA from focus_len_table
- my vbatt_min in rec mode
- new bitmap palette 16
- define CAM_USB_EVENTID for play rec switching (ptp tested)
- found address for LEDDrive and set led_table, state 2 to 6 (blinking led sequences) are also useable
- some cleanup in stubs_min.S, stubs_entry_2.S, recreate stubs_entry.S
- add required defines for fi2
- disable compiler warning in gps.c

rudi

Re: SX260 HS Porting Thread
« Reply #235 on: 19 / May / 2012, 11:34:59 »
Hi all,
Does anyone have sucessfully used this CHDK port on a SX240HS (without GPS) with 1.00A firmware?

Re: SX260 HS Porting Thread
« Reply #236 on: 19 / May / 2012, 15:25:00 »
Hi all,
Does anyone have sucessfully used this CHDK port on a SX240HS (without GPS) with 1.00A firmware?
You can't use CHDK from one camera model on another model (although you can sometimes use a different firmware version on the same model).
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #237 on: 20 / May / 2012, 13:21:43 »
Thanks  rudi, this way is trunk ready!

I'm trying to figure out now why it fails if you press the shutter quickly

It hangs in DvlpSeqTask,  do you have any clue how to solve it?


*

Offline reyalp

  • ******
  • 14128
Re: SX260 HS Porting Thread
« Reply #238 on: 20 / May / 2012, 17:48:52 »
Thanks  rudi, this way is trunk ready!

I'm trying to figure out now why it fails if you press the shutter quickly

It hangs in DvlpSeqTask,  do you have any clue how to solve it?
On most (digic IV and later ?) cameras, there is a special hack in the first jumptable entry for captseq, usually something like STR     R0, [R4,#0x24]. This is the first place I would look.

If the offset is changed, it could obviously mess things up. Or perhaps the Canon code has changed, fast press seems to take a very different code path.
Don't forget what the H stands for.

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #239 on: 21 / May / 2012, 14:52:18 »
Thanks realyp

what is the override to dont do the
CMP     R0, #0

 

Related Topics


SimplePortal © 2008-2014, SimplePortal