the sx10 porting thread

alliance

Hi friends, do you have any news about CHDK for firmware 1.01B. How i can help some developer to start working on it ? Let me know if i can do something. Ciao

Random5

Hello everyone! And thank you for this nice add-on for my camera!

The manual states that zoom buttons can be used to operate MF. As we all know, the MF ring in SX10 sucks big time, so I began searching the menu for this particular option. However, I couldn't find it. Is there such option in the first place and how do I enable it if it exists?

And second question: is there some other topic for this sort of questions regarding this camera?

Thanks!

fe50

Hello & welcome, Random5 !

Random5
The manual states that zoom buttons can be used to operate MF. As we all know, the MF ring in SX10 sucks big time, so I began searching the menu for this particular option. However, I couldn't find it. Is there such option in the first place and how do I enable it if it exists?

It works like described here: CHDK wikia: Special Short-cut Keys

- enable the cameras MF mode with the UP / MF button (don't forget: MF is not available in the cameras "Auto" mode, so use e.g. P mode)
- enter <Alt> mode (with the shortcut/print key or whatever key you have defined as ALT key in CHDK menu)
- you'll see SD😖xx and FACTOR: xxx on the OSD
- to enable / disable the CHDK control just set the FACTOR to 0 (disabled) or 1/10/100/1000 (enabled)
- use the keys like described in the wikia article (UP: inf / DOWN: HF / LEFT or RIGHT: set factor)

And second question: is there some other topic for this sort of questions regarding this camera?

Since this is the porting thread from the CHDK development section: for "general" questions about using CHDK, the General Help and Assistance on using CHDK stable releases would be the right place...

...you'll find also some hints for the SX10 on the SX10 wikia page and some links on my user page

Have fun with your SX10 !

Matiss

Hello everyone. One of the reasons why I bought my Canon SX10, was because it is possible to set CHDK on PowerShot cameras like this one. Unfortunately I have 1.01b version and since October 2008 when this camera was released, there have been ported only one firmware and I have no hope that there will be any updates in next months, see also how it is also written in SX10 page - "CHDK is ONLY available for version 1.01A and at this time no developer is working on any other firmware revisions" so it seems really pessimistic for me 🙁

Of course nothing will happen if no one aren't doing anything, so I wonder could we donate for developers, so they could be interested in porting some of these firmwares? There is a lot of SX10 owners just like me, who could donate a little bit money through Paypal or something like that, so developer could get a little bit of donations for his job, and we could get a lot of fun using CHDK 😀

If it is allowed and somebody is interested in it, please let us know.

reyalp

Matiss
If it is allowed and somebody is interested in it, please let us know.

Please read: https://chdk.setepontos.com/d/2 along with the earlier responses in this thread to people asking about other firmware versions.

chdkess

Hi, I am trying to work out the missing functions in the stubs_entry_2.S on the SX10 (1.01A).

I'm starting with Mount_FileSystem by looking for references to WriteSDCard (0xFF92A9A4) because in cameras for which Mount_FileSystem has been found, the routine contains a reference to WriteSDCard (.e.g. https://chdk.setepontos.com/d/2903/2).

I've disassembled the source code and the only 2 references to the WriteSDCard address I've found are listed below and the routines do not resemble the Mount_FileSystem routine in the linked post above. Could anyone give me any hints about what to look for and perhaps what the second code listing does? Also, what is "mounter.c"? Is this something that might mount the file system?

Many thanks.

[tt]
ROM:FFC4A5C8 sub_FFC4A5C8 ; CODE XREF: sub_FFC4AB08+Cp
ROM:FFC4A5C8 ; sub_FFC4AC18+28p
ROM:FFC4A5C8 LDR R1, =0x2A70
ROM:FFC4A5CC LDR R1, [R1,#0x10]
ROM:FFC4A5D0 CMP R1, #0
ROM:FFC4A5D4 CMPEQ R0, #0
ROM:FFC4A5D8 BXNE LR
ROM:FFC4A5DC MOV R1, #0
ROM:FFC4A5E0 LDR R0, =0x1A784
ROM:FFC4A5E4 STR R1, [R0,#0x34]
ROM:FFC4A5E8 STR R1, [R0,#0x38]
ROM:FFC4A5EC MOV R1, #3
ROM:FFC4A5F0 STR R1, [R0,#0x3C]
ROM:FFC4A5F4 LDR R1, =0xFF92A7C4
ROM:FFC4A5F8 STR R1, [R0,#0x4C]
ROM:FFC4A5FC LDR R1, =0xFF92A9A4
ROM:FFC4A600 STR R1, [R0,#0x50]
ROM:FFC4A604 BX LR
ROM:FFC4A604 ; End of function sub_FFC4A5C8
[/tt]

and

[tt]
ROM:FFC4A698 ; -- -------------------------------------------------------------------------
ROM:FFC4A69C dword_FFC4A69C DCD 0x2A70 ; DATA XREF: sub_FFC4A138+1Cr
ROM:FFC4A69C ; sub_FFC4A1D0+8r ...
ROM:FFC4A6A0 dword_FFC4A6A0 DCD 0x10B4 ; DATA XREF: sub_FFC4A138+30r
ROM:FFC4A6A4 dword_FFC4A6A4 DCD 0x1A784 ; DATA XREF: sub_FFC4A18C+10r
ROM:FFC4A6A4 ; sub_FFC4A1D0+68r ...
ROM:FFC4A6A8 dword_FFC4A6A8 DCD 0x1A7E0 ; DATA XREF: sub_FFC4A18C+14r
ROM:FFC4A6A8 ; sub_FFC4A1D0+4r ...
ROM:FFC4A6AC aBootdisk DCB "BOOTDISK",0 ; DATA XREF: sub_FFC4A284+204o
ROM:FFC4A6B5 DCB 0
ROM:FFC4A6B6 DCB 0
ROM:FFC4A6B7 DCB 0
ROM:FFC4A6B8 aScript DCB "SCRIPT",0 ; DATA XREF: sub_FFC4A284+220o
ROM:FFC4A6BF DCB 0
ROM:FFC4A6C0 dword_FFC4A6C0 DCD 0xFF92A7C4 ; DATA XREF: sub_FFC4A5C8+2Cr
ROM:FFC4A6C4 dword_FFC4A6C4 DCD 0xFF92A9A4 ; DATA XREF: sub_FFC4A5C8+34r
ROM:FFC4A6C8 aMounter_c DCB "Mounter.c",0 ; DATA XREF: _sub_FFC4A608__Mounter.c__824+70o
ROM:FFC4A6C8 ; _sub_FFC4A6D4__Mounter.c__0+150o ...
ROM:FFC4A6D2 DCB 0
ROM:FFC4A6D3 DCB 0
ROM:FFC4A6D4
ROM:FFC4A6D4 ; =============== S U B R O U T I N E =======================================
ROM:FFC4A6D4
ROM:FFC4A6D4 ; LOCATION: Mounter.c:0
[/tt]

reyalp

According to my notes Mount_Filesystem is normally nullsub for dryos cams.

chdkess

Yes, it is true that in every DryOS camera stubs_entry_2.S file that I have seen Mount_Filesystem is a null stub but I am hoping I can find a place where it _does_ exist - there is no particular reason why it shouldn't; I would like to implement a JPEG2000 encoder for CHDK to allow the option of saving in this format but I keep coming up against write-caching problems (perhaps this could eventually be extended to re-encode video in a different format too).

If I use Unmount_Filesystem followed by Mount_Filesystem I can force the camera to save my JPEG2000 to disc before the next JPEG image gets a chance to overwrite the JPEG2000 from the previous photo.

Any ideas?

ewavr

chdkess
Yes, it is true that in every DryOS camera stubs_entry_2.S file that I have seen Mount_Filesystem is a null stub

Because this function currently not used in CHDK for DRYOS cameras.

Any ideas?

My idea for SX10 1.01A:
FF85AB08 Mount_FileSystem

edit: and probably FF85ABD0 Unmount_FileSystem

chdkess

Because this function currently not used in CHDK for DRYOS cameras.

I see - I will have to do some #define hunting to see why this is.

My idea for SX10 1.01A:
FF85AB08 Mount_FileSystem

edit: and probably FF85ABD0 Unmount_FileSystem

Thanks for your input - before I try the functions can I ask how you found these addresses? In the disassembly I can find no references to the 2 memory locations you gave. I'm concerned I have a bad firmware dump so are you able to tell me the locations in the firmware dumps where the references to these 2 locations are?

ewavr

chdkess
Thanks for your input - before I try the functions can I ask how you found these addresses? In the disassembly I can find no references to the 2 memory locations you gave. I'm concerned I have a bad firmware dump so are you able to tell me the locations in the firmware dumps where the references to these 2 locations are?

Starting point is InitFileModules task (SX10 1.01A):

ROM:FF884A54 task_InitFileModules ; DATA XREF: taskcreate_InitFileModules+24
ROM:FF884A54 STMFD SP!, {R4-R6,LR}
ROM:FF884A58 BL sub_FF879F78
ROM:FF884A5C LDR R5, =0x5006
ROM:FF884A60 MOVS R4, R0
ROM:FF884A64 MOVNE R1, #0
ROM:FF884A68 MOVNE R0, R5
ROM:FF884A6C BLNE PostLogicalEventToUI
ROM:FF884A70 BL sub_FF879FA4
ROM:FF884A74 CMP R4, #0
ROM:FF884A78 MOVEQ R0, R5
ROM:FF884A7C LDMEQFD SP!, {R4-R6,LR}
ROM:FF884A80 MOVEQ R1, #0
ROM:FF884A84 BEQ PostLogicalEventToUI
ROM:FF884A88 LDMFD SP!, {R4-R6,PC}

Then goto sub_FF879FA4:

ROM:FF879FA4 sub_FF879FA4 ; CODE XREF: task_InitFileModules+1C
ROM:FF879FA4 STMFD SP!, {R4,LR}
ROM:FF879FA8 BL Mount_FileSystem
ROM:FF879FAC BL nullsub_66
ROM:FF879FB0 LDR R4, =0x58CC
ROM:FF879FB4 LDR R0, [R4,#4]
ROM:FF879FB8 CMP R0, #0
....

In VxWorks (a710):

ROM:FFD99138 InitFileModulesTask ; DATA XREF: ROM:off_FFD991F4o
ROM:FFD99138 STMFD SP!, {R4,LR}
ROM:FFD9913C BL sub_FFEE1D70
ROM:FFD99140 SUBS R4, R0, #0
ROM:FFD99144 MOV R0, #0x5000
ROM:FFD99148 MOV R1, #0
ROM:FFD9914C ADD R0, R0, #6
ROM:FFD99150 BEQ loc_FFD99158
ROM:FFD99154 BL PostLogicalEventToUI
ROM:FFD99158
ROM:FFD99158 loc_FFD99158 ; CODE XREF: InitFileModulesTask+18j
ROM:FFD99158 BL sub_FFEE1D9C
ROM:FFD9915C MOV R0, #0x5000
ROM:FFD99160 CMP R4, #0
ROM:FFD99164 MOV R1, R4
ROM:FFD99168 ADD R0, R0, #6
ROM:FFD9916C LDMNEFD SP!, {R4,PC}
ROM:FFD99170 LDMFD SP!, {R4,LR}
ROM:FFD99174 B PostLogicalEventToUI

ROM:FFEE1D9C sub_FFEE1D9C ; CODE XREF: InitFileModulesTask:loc_FFD99158p
ROM:FFEE1D9C STR LR, [SP,#-4]!
ROM:FFEE1DA0 BL Mount_FileSystem
ROM:FFEE1DA4 LDR R3, =0xAF68
ROM:FFEE1DA8 LDR R2, [R3]
ROM:FFEE1DAC CMP R2, #0
ROM:FFEE1DB0 BNE loc_FFEE1DD8
....

chdkess

Thanks for that; I can now see that the source of my confusion over addresses is that my IDA dump has this as its first line of task_InitFileModules:

[tt]ROM:FFC74A54 task_InitFileModules ; DATA XREF: taskcreate_InitFileModules+24o[/tt]

but you have:

[tt]ROM:FF884A54 task_InitFileModules ; DATA XREF: taskcreate_InitFileModules+24[/tt]

I have followed the instructions at http://chdk.wikia.com/wiki/DryOS_Porting to load the dump to IDA and it does say

Rom Start address: 0xFFC00000

and

Loading address: 0xFFC00000

so I am confused why you have not done this with your dump. I assume you have left the starting address as whatever it comes up as when you first load the binary into IDA?

ewavr

chdkess
I have followed the instructions at http://chdk.wikia.com/wiki/DryOS_Porting to load the dump to IDA and it does say
Rom Start address: 0xFFC00000
and
Loading address: 0xFFC00000

On this page:

S/SD/G-Series start address is 0xFF810000

or just look:

ROM:FF810130 LDR R0, =unk_FFB9B27C ; <---absolute constant
ROM:FF810134 LDR R1, =0x1900
ROM:FF810138 LDR R3, =0x10A50

chdkess

On this page:
Quote
S/SD/G-Series start address is 0xFF810000

Ok, but the page did not say "SX". Anyway, I changed the start address and loading address to 0xFF810000 and the disassembly matches yours now 😁.

Also, your predictions of Mount_FileSystem at 0xFF85AB08 and Unmount_FileSystem 0xFF85ABD0 were correct and I no longer have write-caching problems!

I am well impressed by how you spotted those functions especially the Unmount_FileSystem one. I think I will have to study a book on ARM assembly to unravel this mystery a bit more.

muppetman

Is anyone working on CHDK for sx10 Firmware version 1.00c? if not can anyone direct to "how to" and i'll get to work....

reyalp

muppetman
Is anyone working on CHDK for sx10 Firmware version 1.00c? if not can anyone direct to "how to" and i'll get to work....

http://chdk.wikia.com/wiki/SX10
http://chdk.wikia.com/wiki/For_Developers

ewavr

Some *.S files for 1.01B firmware for future developers - http://ewavr.nm.ru/chdk/trash/sx10-101b.zip
Sorry, I can't continue this work.

fe50

ewavr
Some *.S files for 1.01B firmware for future developers - http://ewavr.nm.ru/chdk/trash/sx10-101b.zip.
Sorry, I can't continue this work.

Could you upload it somewhere else ?

alliance

Hello, i am not a developer but let me know how can i help, ciao

ewavr

fe50
Could you upload it somewhere else ?

Sorry, link was broken
http://ewavr.nm.ru/chdk/trash/sx10-101b.zip

« Previous Page Next Page »