SX260 HS Porting Thread - page 4 - DryOS Development - CHDK Forum supplierdeeply

SX260 HS Porting Thread

  • 642 Replies
  • 119744 Views
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #30 on: 06 / April / 2012, 00:41:29 »
Advertisements
@philmoz , It was the way it calls it in the tasks sub in asm,

But I will use your call, thanks.

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #31 on: 06 / April / 2012, 02:26:25 »
@waterwingz

I'm using chdk-pt  and it really simplifies a lot of copy-paste for long files, very good work!!

When it finds Ram address it calls
"    BL      sub_FC68BBE4 \n"

instead of
"    BL      sub_0068BBE4 \n"

It's the same or one of them is wrong?

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #32 on: 06 / April / 2012, 05:40:59 »
More sources
http://www.4shared.com/zip/2vZD6P3k/sx260-100b-varsources-v1.html
boot.c
capt_seq.c
lib.c

-> lib.c I'm not suer of
1) If it is here +0xC or not?

Code: [Select]
char *hook_raw_image_addr()
{
if (*((int*)(0x3188 + 0xc)) != 0) //asm1989 sx260  0x3188 ( @FF071468 )  +0C Not found !!!! -RECHECK !!!
//SX230 - >  0x3F58 ( @FF07B02C ) +0xC (@FF07B0A4 )
{
return (char*) 0x4ADB54A0; //ams1989 sx260 looks like @FF056D9C   - sx230 @FF066A14
}
else
{
return (char*) 0x40DADA80;  //ams1989 sx260 looks like @FF3E6530   - sx230 at: @FF37FB7C
}
}

2) If its +0x50 Here:
Code: [Select]
void *vid_get_viewport_fb_d()
{
return (void*)(*(int*)(0x3CD0+0x50));    // asm1989 @ FF061E24 +  Not sure about 0x50 maybe 0x58
}

And the GPS stuff to deal once it boots

*

Offline srsa_4c

  • ******
  • 4228
Re: SX260 HS Porting Thread
« Reply #33 on: 06 / April / 2012, 06:34:45 »
When you find addresses like
Code: [Select]
if (*((int*)(0x3188 + 0xc)) != 0)
in the code, it usually means the original firmware code used this base pointer + offset addressing scheme (I think this usually means that the value in question is part of a structure).
The firmware code may have been something like
Code: [Select]
ldr r4, =0x3188
...
ldr r0, [r4, #0xc]

... and their VxWorks compiler used to generate code like this  :)
Code: [Select]
mov r4, #0x3100
...
add r4, r4, #0x88
...
ldr r0, [r4, #0xc]
« Last Edit: 08 / April / 2012, 06:22:04 by srsa_4c »


Re: SX260 HS Porting Thread
« Reply #34 on: 06 / April / 2012, 09:33:23 »
When it finds Ram address it calls
"    BL      sub_FC68BBE4 \n"
instead of
"    BL      sub_0068BBE4 \n"
It's the same or one of them is wrong?
I'm not sure at this point how to handle the "new" cameras that load part of their code into RAM.   Right now the dissassembler assumes all code is in a contiguous block in high memory.  So thinks like branch instructions will be dissassembled assuming they are branching to code on that area.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #35 on: 06 / April / 2012, 12:01:59 »
I'm trying to test out a version but I' cant get rid of this error

Code: [Select]
gui.c: In function 'gui_alt_mode_button_enum':
gui.c:1234:10: error: #error camera alt-buttons not defined
gui.c:1238:28: error: 'names' undeclared (first use in this function)
gui.c:1238:28: note: each undeclared identifier is reported only once for each function it appears in
gui.c:1239:39: error: 'keys' undeclared (first use in this function)

I'm using the kbd.c file from the sx230 , and it compiles right for this cam, didn't developed yet for sx260

any clue?

*

Offline srsa_4c

  • ******
  • 4228
Re: SX260 HS Porting Thread
« Reply #36 on: 06 / April / 2012, 12:20:58 »
Code: [Select]
gui.c: In function 'gui_alt_mode_button_enum':
gui.c:1234:10: error: #error camera alt-buttons not defined
any clue?
Either put #undef CAM_ADJUSTABLE_ALT_BUTTON for your camera in platform_camera.h, or define your buttons just a few lines above (in gui.c).

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #37 on: 06 / April / 2012, 12:50:38 »
thanks srsa_4c

Now seams to get stuck with focus_len_table,  it looks like it is not getting it from finsig_dryos.c

edit: manualy added to stubs_min , finsig is not getting it
« Last Edit: 06 / April / 2012, 12:55:51 by asm1989 »


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #38 on: 06 / April / 2012, 13:17:59 »
Finally it compiles and generates everything,

But get a "Update File Error" ???

keys seam ok & Verified
NEED_ENCODED_DISKBOOT=8    #asm1989  @ 0xFF5AAB0C
KEYSYS=d4c

PLATFORMID=12868

« Last Edit: 06 / April / 2012, 13:26:23 by asm1989 »

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX260 HS Porting Thread
« Reply #39 on: 06 / April / 2012, 19:23:00 »
Someone tested the new dancingbits for generating the bin & FI2 ?

Maybe the "Update File Error"  is because it dosnt reach this { 6,3,1,0,5,7,2,4 }, // spicy habenaro sx260hs (dryos r50)

Thanks for any advice!

 

Related Topics