PowerShot SX210 IS - Porting Thread - page 21 - General Discussion and Assistance - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 16 17 18 19 20 [21] 22 23 24 25 26 ... 59   Go Down

PowerShot SX210 IS - Porting Thread

  • 589 Replies
  • 301591 Views
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #200 on: 09 / September / 2010, 12:47:04 »
Advertisements
-Blurry image

Looks like is in the call to apex2us , maybe this cam has a diferent behaivour????

Code: [Select]
int  apex2us(int apex_tv){
#if CAM_EXT_TV_RANGE
short tv;
tv = shooting_get_tv96();
if (tv<-576 || tv!=apex_tv) return 1000000.0*pow(2.0, -tv/96.0);
else return _apex2us(apex_tv);
#else
return 0;
#endif
}
« Last Edit: 09 / September / 2010, 12:59:41 by asm1989 »
Logged
*

Offline HarpoMa

  • ***
  • 218
Re: PowerShot SX210 IS - Porting Thread
« Reply #201 on: 09 / September / 2010, 13:47:21 »
I will take a look tonight.
Logged
Canon Models - SD300, SD780, & SX210
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #202 on: 09 / September / 2010, 14:34:05 »
Quote
I will take a look tonight.

Thanks Jason,

The crash on taking picture, I traced it back to here

Code: [Select]
"BL      sub_FF972EFC_my\n"  if restored to rom's sub_FF972EFC, it dosnt crash in the same conditions

This is my reviewed code from my todays debug:

Code: [Select]
//ASM1989 DONE
void __attribute__((naked,noinline)) sub_FF972EFC_my(){ //
 asm volatile(
                 "STMFD   SP!, {R0-R8,LR}\n"
                 "MOV     R4, R0\n"
                 "BL      sub_FF973E70\n"
                 "MVN     R1, #0\n" // Original code 0xFFFFFFFF why 0 ?
                 "BL      sub_FF888E34\n"
                 "LDR     R5, =0x75B0\n" //SX200 : 0x6AD8
                 "LDR     R0, [R5,#0xC]\n"
                 "CMP     R0, #0\n"
                 "BNE     loc_FF972F4C\n"
                 "MOV     R1, #1\n"
                 "MOV     R0, #0\n"
                 "BL      sub_FF83A3D0\n"
                 "STR     R0, [R5,#0xC]\n"
                 "MOV     R3, #0\n"
                 "STR     R3, [SP]\n"
                 "LDR     R3, =0xFF972A5C\n"
                 "LDR     R0, =0xFF973138\n"        //"ShutterSoundTask"
                 "MOV     R2, #0x400\n"
                 "MOV     R1, #0x17\n"
                 "BL      sub_FF83A39C\n" //KernelCreateTask
"loc_FF972F4C:\n"
                 "MOV     R2, #4\n"
                 "ADD     R1, SP, #0x8\n"
                 "MOV     R0, #0x8A\n"
                 "BL      sub_FF891070\n" //PT_GetPropertyCaseString
                 "TST     R0, #1\n"
                 //DEBUGIN 09.09.10 Detected some registry diferences
                 "MOVNE   R1, #0x3F4\n" //SX200:0x3AE
                 "LDRNE   R0, =0xFF972CF4\n" //aSscaptureseq_c ; "SsCaptureSeq.c"
                 "BLNE    sub_FF81EB14\n" //DebugAssert
                 "LDR     R6, =0x3A678\n" //SX200:0x1550C\
                 "LDR     R7, =0x3A5AC\n" //SX200:0x15448
                 "LDR     R3, [R6]\n"  //missing
                 "LDRSH   R2, [R6,#0xC]\n" //New sx210
                 "LDRSH   R1, [R6,#0xE]\n"
                 "LDR     R0, [R7,#0x90]\n" //SX200:0x8C
                 "BL      sub_FF93938C\n"
                 "BL      sub_FF866E94\n" //LOCATION: Thermometer.c:0
                 "LDR     R3, =0x75B8\n" //SX200:0x6AE0
                 "STRH    R0, [R4,#0xA4]\n" //SX200:0x9C
                 "SUB     R2, R3, #4\n"
                 "STRD    R2, [SP]\n"
                 "MOV     R1, R0\n"
                 "LDRH    R0, [R7,#0x5C]\n"
                 "LDRSH   R2, [R6,#0xC]\n"
                 //END DEBUGIN 09.09.10 Detected some registry diferences
                 "SUB     R3, R3, #8\n"
                 "BL      sub_FF975A14\n"
                 "BL      wait_until_remote_button_is_released\n"
                 "BL      capt_seq_hook_set_nr\n"                     // +
                 "B       sub_FF972FB0\n"                             // continue function in firmware
 );
}
Logged
*

Offline HarpoMa

  • ***
  • 218
Re: PowerShot SX210 IS - Porting Thread
« Reply #203 on: 10 / September / 2010, 01:04:27 »
It will take some time...I have to catch up.
Logged
Canon Models - SD300, SD780, & SX210
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #204 on: 10 / September / 2010, 14:05:27 »
yes a lot of new stuff, better look at ports from newers OS like sd980 and sx20  and sx200 for similarities

Look like the crash was due to coments in the code ???,

Here is the latest capt_seq.c  http://www.zshare.net/download/80268390076a3f6b/

with this one it dosnt crash, and it isnt blurry ,( because the code is comented as stated earlier)

overrides never worked, maybe there is something new with the props???
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: PowerShot SX210 IS - Porting Thread
« Reply #205 on: 10 / September / 2010, 21:49:36 »
Looks like your strchr address is wrong:
Code: [Select]
NHSTUB(strchr, 0xFF88FCAC)  // -> ASM1989 08.21.2010
possible address:
Code: [Select]
NHSTUB(strchr, 0xFF813FE4)
also i think this is correct:
Code: [Select]
NHSTUB(open, 0xFF81A9E4)
« Last Edit: 10 / September / 2010, 22:11:22 by pixeldoc2000 »
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #206 on: 11 / September / 2010, 04:04:12 »
Thanks Pixeldoc!!

The strchr was indeed wrong, with this one the script's run, not tested , but go through

Doing some reserch I found that there are two diferent adrress for Open and open, like in sd980

NHSTUB(open, 0xFF81A9E4)
NHSTUB(Open, 0xff836be4)

and the same for close and Close

NHSTUB(close, 0xFF81AA94)
NHSTUB(Close, 0xff836c50)
« Last Edit: 11 / September / 2010, 14:32:36 by asm1989 »
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: PowerShot SX210 IS - Porting Thread
« Reply #207 on: 11 / September / 2010, 14:57:15 »
Quote from: asm1989 on 11 / September / 2010, 04:04:12
Doing some reserch I found that there are two diferent adrress for Open and open, like in sd980

NHSTUB(open, 0xFF81A9E4)
NHSTUB(Open, 0xff836be4)

and the same for close and Close

NHSTUB(close, 0xFF81AA94)
NHSTUB(Close, 0xff836c50)
Yes, i noticed this too. SD4000 has also different open and Open.
But Open and Close on SD990 is little different.

Im using addresses from sigfinder for open, Open, close and Close for SD4000.
Looks like sigfinder Open and Close are correct for SX210 too!

BTW, do you mean ixus980_sd990 by sd980? That the one i'm talking about!
« Last Edit: 11 / September / 2010, 15:18:02 by pixeldoc2000 »
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #208 on: 11 / September / 2010, 15:18:41 »
I'm talking about ixus200_sd980
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: PowerShot SX210 IS - Porting Thread
« Reply #209 on: 11 / September / 2010, 18:07:02 »
do you have redraw issus with canon firmware before and after ALT mode (chdk menu)?

most of the time time canon firmware does not refresh screen for a while (looks like its related to canon original menu or osd) but than recovers itself..

if tested different things in vid_bitmap_refresh(), but everything it tried is doing worse..

did you test address from sigfinder for Open and Close?
« Last Edit: 11 / September / 2010, 18:09:41 by pixeldoc2000 »
Logged
Pages: 1 ... 16 17 18 19 20 [21] 22 23 24 25 26 ... 59   Go Up
« previous next »
 

Related Topics