SX260 HS Porting Thread - page 25 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 20 21 22 23 24 [25] 26 27 28 29 30 ... 65   Go Down

SX260 HS Porting Thread

  • 642 Replies
  • 233728 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: SX260 HS Porting Thread
« Reply #240 on: 21 / May / 2012, 15:15:16 »
Advertisements
You have a bug around the mentioned place in capt_seq_task

Code: [Select]
"loc_FF06D7A8:\n"
//PATCH BEGIN
        "BL      shooting_expo_iso_override\n"
//PATCH END
      "    BL      sub_FF06DF5C \n"
//PATCH BEGIN
        "BL      shooting_expo_param_override\n"
//PATCH END
      "    BL      sub_FF06AA24 \n"
//PATCH BEGIN
//      "    LDR     R0, [R4, #0x28] \n"
//      "    CMP     R0, #0 \n"
//      "    BLNE    sub_FF1BF284 \n" // 100c change
        "MOV     R0, #0\n"
        "STR     R0, [R5,#0x28]\n"  // fixes overrides  behavior at short shutter press
//PATCH END
      "    B       loc_FF06D9E8 \n"
You used STR R0, [R5,#0x28] instead of STR R0, [R4,#0x28]
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #241 on: 21 / May / 2012, 15:29:38 »
Thanks srsa_4c, I find It too, It solves the quick press !!

attached beta5 for  100b

Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #242 on: 21 / May / 2012, 15:30:26 »
and here beta 5 for 100c
Logged
*

Offline rudi

  • ***
  • 129
  • A590IS_101B, SX260HS_100B
Re: SX260 HS Porting Thread
« Reply #243 on: 21 / May / 2012, 16:08:09 »
Yes, thanks srsa_4c!

I explored EXMEM today.
Code: [Select]
MAXRAMADDR=0x4FFFFFFF #asm1989 Found at FF07B064 0x50000000 -1        Sx230 -> @FF086CE0 48000000 - 1is wrong. 0x50000000 is the value with 'uncached' memory bit (0x40000000). We should use still MAXRAMADDR=0x0FFFFFFF from stubs_entry.S (0x50000000 - 0x40000000 - 1). I found not enough unused memory for using EXMEM (especially on video recording). I think we don't need that.

The trunk patch for sx260-100b, 100c is attached.

rudi
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #244 on: 21 / May / 2012, 16:17:42 »
Thanks Rudi,
I also dont find too much use for exmem.

Less things are left now:
1.- other unsolved thing is remove the timelimit for hd video, I solved it for slowmotion movies but hangs with hd. ( and maybe use magiclantern code for diferent fps setings)
2.- also gps stuff , I use genie sx230 code but may need some refurbishing

Could someone please load rudis patch to the trunk?
Logged
*

Offline StealthTaffer

  • *
  • 26
Re: SX260 HS Porting Thread
« Reply #245 on: 22 / May / 2012, 17:34:37 »
                    Please do not forget the rear thumbwheel/ring change!

The CHDK thumbwheel/ring response is OPPOSITE to what Canon uses on their Menus.

CHDK: Clockwise (CW) moves menu UP!
Canon: Clockwise (CW) moves menu DOWN!

Confusing & NON-intuitive!


** Fabulous work asm1989 & contributors, MANY THANKS!! **
Logged
*

Offline jacobo

  • *
  • 2
Re: SX260 HS Porting Thread
« Reply #246 on: 23 / May / 2012, 15:08:33 »
Thanks very much for the hard work so far.

We're new to CHDK with the SX260 HS and trying to try out the beta. We've found that some of the installation documentation seems in conflict and are not sure which set of instructions to follow. We're using Mac. Any suggestions of where to start?
« Last Edit: 23 / May / 2012, 17:50:57 by jacobo »
Logged
*

Offline yuyu

  • *
  • 11
Re: SX260 HS Porting Thread
« Reply #247 on: 23 / May / 2012, 17:52:22 »
RAW file generation is corrupted on my sx260 (firmware B), both as CRW and DNG. Generated files contain junk bytes in place of actual pixel colors so it must be dumping wrong memory address.

DNG headers and metadata is ok, so it is just the actual pixel buffer that is wrong. The junk bytes are different for each shot but have a similar structure if you look at them on a hex editor, they kind of look similar on every pic even if they are actually different byte streams.

The generated JPGs are fine, is just the raw file that shows garbage.

I have checked two different SD cards and both beta5 and beta4 versions. Same behaviour everytime.

Here is a link to a ZIP file containing both the DNG and the JPG files for a sample photo.
http://dl.dropbox.com/u/81185573/bad_DNG_and_good_JPG.zip

Here is ver.req output (using "-----" to separate sucessive screens):
Code: [Select]
-----
Canon PowerShot SX260 HS
P-ID:3244 PAL D


Firmware Ver GM1.00B (1.0.0.0)
Adj Ver.005.011
Serial No. XXXXXXXXXXXX
-----
Build: Jan 6 2012  17:07:27
NoError
-----
Mecha Firm Ver. 3.00
MechaDSP Ver. 0.00
-----

EDIT:
I have dumped my firmware just in case:
http://dl.dropbox.com/u/81185573/firmware_dump.zip

Oh, and beta5 doesnt fix the full shutter press crash, I still have to half press first or I will get a crash if I go all the way down on a quick single button press.
« Last Edit: 23 / May / 2012, 18:30:17 by yuyu »
Logged
*

Offline StealthTaffer

  • *
  • 26
Re: SX260 HS Porting Thread
« Reply #248 on: 24 / May / 2012, 00:33:25 »

yuyu:

I believe what your DNG shows is what occurs when CHDK crashes the sx260. I saw 1 of these for every crash I had before we determined it was due to 'fast shutter' causes.

I think it is due to crashing while writing to the sd card, yours was worse than any of mine though as I always got partial picture. My sd cards faster than yours or ??

I have never gotten a corrupt DNG NOT associated with a crash.

Of course my experience, but I think others will attest to the same.

I also have yet to get a 'fast shutter' crash with beta5, I have done multiple 'fast shutter' shots, even to the point of no good focus, and no crashes. But maybe others have seen it crash in beta5.

Reload beta5 onto your card & retry.


Thanks & Good Luck!
Logged
*

Offline reyalp

  • ******
  • 14128
Re: SX260 HS Porting Thread
« Reply #249 on: 24 / May / 2012, 01:08:55 »
Re corrupted raw/dng:
Some cameras have multiple raw buffers and alternate between them under some circumstances.

Also some reduced resolution modes (usually special high ISO or fast shooting modes) don't produce a valid raw buffer at all.

If it crashed while saving raw, then the filesize should be wrong.
Logged
Don't forget what the H stands for.
Pages: 1 ... 20 21 22 23 24 [25] 26 27 28 29 30 ... 65   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal