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

SX260 HS Porting Thread

  • 642 Replies
  • 228075 Views
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #270 on: 27 / May / 2012, 15:49:33 »
Advertisements
yuyu, you have to comment existing "BL     capt_seq_hook_raw_here\n" and place them in other places,
compile and test.

Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: SX260 HS Porting Thread
« Reply #271 on: 27 / May / 2012, 17:32:12 »
@asm1989, @yuyu
You can also trace the case values capt_seq_task gets
Code: [Select]
"loc_FF06D6F8:\n"
      "    LDR     R0, [SP] \n"
      "    LDR     R1, [R0] \n"
"bl my_debugprint\n" // ***************** here ******************
      "    CMP     R1, #0x27 \n"
      "    ADDCC   PC, PC, R1, LSL #2 \n"where my_debugprint is a function which saves all registers, prints the value of r1 into a buffer and restores all registers (at least this is what I like to use). You can also collect keypresses in that buffer, everything with timestamps. The buffer can then be dumped onto the card either automatically or with a special button-combination. This may help deciding where to look for a new hook. Of course the split of the code paths (auto/not auto) may be elsewhere...
You can also write directly to a text file, but that will probably conflict with the jpeg-writing process.
Logged
*

Offline yuyu

  • *
  • 11
Re: SX260 HS Porting Thread
« Reply #272 on: 27 / May / 2012, 23:16:04 »
There are like 39 possible events and they do not match what is on levent table, is there any documentation on these alternate events?

I have a permanent GUI displaying last 10 event codes and slowly making sense of the whole task call graph thanks to the asserts in the code but this is slow.
« Last Edit: 27 / May / 2012, 23:17:37 by yuyu »
Logged
*

Offline Vitold

  • *
  • 3
  • Canon SX260 HS fw 1.00B
Re: SX260 HS Porting Thread
« Reply #273 on: 12 / June / 2012, 23:09:17 »
« Reply #272 on: 28 / May / 2012, 08:16:04 »

Is anybody home?
« Last Edit: 13 / June / 2012, 11:04:53 by Vitold »
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: SX260 HS Porting Thread
« Reply #274 on: 12 / June / 2012, 23:10:36 »
Quote from: Vitold on 12 / June / 2012, 23:09:17
Ia anybody home?
No  ... or yes .. or maybe.   But in the end, I think its "no".
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #275 on: 15 / June / 2012, 11:30:01 »
Vitold  looks like for now there is no developer with a SX230
Logged
*

Offline yuyu

  • *
  • 11
Re: SX260 HS Porting Thread
« Reply #276 on: 18 / June / 2012, 11:05:10 »
I have not been able to devote time to this since a couple days after last post in May but I did not find any image pixels on auto mode anywhere. If anyone needs raw on "auto" mode they will have to use Easy mode instead.

Image capture function is at address FF1BEA34 if someone else is interested and have the time.

tasq_seq_capt receives an event 0 ("framebuffer pointer housekeeping") followed by an event 1 ("image capture event"). Event 1 calls a lot of stuff but I would like to remark the following:

- Framebuffer management has a special case for "Auto mode", check return values at function FF0DD9F4. This function receives a parameter in the range 0-12 (there are 12 icons in the capture dial) and returns an special value for mode 5 (0 based, AUTO is sixth in dial). This code path is reached from Event 0 and from Event 1 right before FF1BEA34 is called (the big capture func). Quite the assumption but I was not going to reverse engineer the whole firmware.
- Pixel data is not available before entering FF1BEA34 but it is there after the function returns (except on auto mode).

Other events (2-38) are related to flash charging, Autofocus, image stabilization, movies and general housekeeping.

So, basically, asm1989 hooked the right spot but the data is not going to be there without major time investments to reverse engineer and reprogram picture taking logic. Not worth it imho.



Logged
*

Offline mcgd

  • *
  • 23
Re: SX260 HS Porting Thread
« Reply #277 on: 25 / June / 2012, 08:50:15 »
Quote from: asm1989 on 21 / May / 2012, 15:30:26
and here beta 5 for 100c

Have been keeping an eye on this thread to decide when to buy a SX260, but my old camera died on the weekend so have bought one.

I tried beta5 for 100c and got an error about an invalid file when doing the firmware update, so I think there may be a problem with this build.  I tried beta4 and that loaded fine - it's really coming along nicely!

One other minor thing I noticed was that the zip file has a vers.req file, but I found I needed a ver.req to get firmware information.
Logged
*

Offline FrankAZ

  • *
  • 5
Re: SX260 HS Porting Thread
« Reply #278 on: 28 / June / 2012, 01:53:38 »
Loaded B5 100c successfully - will have a change to play with it over the next couple weeks!
Logged
*

Offline mcgd

  • *
  • 23
Re: SX260 HS Porting Thread
« Reply #279 on: 29 / June / 2012, 00:58:04 »
I noticed that in Burst HQ continuous shooting mode, auto-bracketing settings aren't used.  I guess this is done differently from normal continuous shooting.  Are there any plans to allow auto-bracketing settings to be used with Burst HQ mode?  It would give fabulously quick HDR bracketing when moving subjects are involved!  (Sorry if this has been addressed previously.)
Logged
Pages: 1 ... 23 24 25 26 27 [28] 29 30 31 32 33 ... 65   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal