SX110IS - howto start porting

flj

Hi, just got my sx110 and would like to help.
Not much experience in assembly but maybe there is something else to do.

fritzus

Hi all!

is there any news about this porting?
As flj and bcc139 .. I just got my SX110 and would like to help.

😀

nomi_68k

fritzus
is there any news about this porting?

Sorry for my long absence. In the last weeks I was away due to my job. And probably I will be away for the next weeks too! 🙁

However I'm still working on "boot.c". I rewrote half file at least using the original firmware of my SX110IS.
But now I'm having a problem because from this point the firmware of a SX110IS is fully different from those of A720 and SX100IS. 🙁

However I will find a way to post the results of my work and the disassembled firmware (only as a ASCII file and not like a IDA file).

Today I want to study why I can't follow (with debug) the execution of the program when arrives to the launch of the threads. 😉

However I renew my offer to transfer all my work to someone that have really a full knowledge to complete the porting. 😀
See you soon. Bye.

nomi_68k

ARGHHHHH :'(
Now when I compile my "boot.c" I have these errors:

"Error: internal_relocation (type: OFFSET_IMM) not fixed up"

in the line where I have:

"LDR R3, task_CaptSeqTask_my\n" //new FFC503B0; old FFC4CB64

Why? 😛

reyalp

should be LDR R3,=task_CaptSeqTask_my

Darthmalt

Been following this since my 540 died and I replaced it with a sx110 back in october. Just registered to say thanks for your work nomi. Wish i knew enough to help with the porting.

the1who

I'll have to say I've been following this since last Sunday when I purchased my new SX110IS as well. I was hoping I might be of help, but I don't have the training nor software background that you already have experience in to get that far. Just webpage is the extent of my programming such as PHP and a tid bit of java.

If I can be of help, I'd like to help for sure.

I am interested in remote control features, mainly for shutter control. Looking to take long exposures for some night shots and I know that my finger even if on timer is bad enough some instances. I was reading some features of the ability to use this firmware where it talks about remote control and enhanced features such as shutter control and motion detection.

Thanks for your work, it's appreciated and I hope this post is a token of my gratitude of your work.

popo_caris

Hola, perdona mi ingles, pero, quisiera saber como instalaste el firmware a la camara sx110, yo no lo puedo instalar.
Me enseñas por favor.

Muchas gracias..
_______

Hello, forgive my English, but I would like to learn how to install the firmware to the camera sx110, I can not install.
Teach me please.

Thank you very much ..

reyalp

If you mean CHDK, you can't because it doesn't exist for sx110 yet. If you mean a canon firmware update, follow the instructions that came with it.

spike

Hi to all working on the SX110IS porting, and good luck. Unfortunately I am a newbie too, so of little help with the nitty-gritty of programming and too far off learning the lingo. I too am anxious to know how to get RAW capture from my new toy (as it's all I use with my SLR) but it's looking like I wont find out until after the holiday I bought it for... never mind.

On another note, I signed up to give notice to 'the1who' and anyone else here anxious to go remote with shutter control -
I found a bit of freeware called 'cam4you'. Currently version 2.00 build0.
Although it's not yet on their list, it does now support the SX110IS. It gives a basic liveview and zoom, plus manual controls for both stills and video capture. There is no guide as yet, but a swift look around pays off. There is timestep programming and motion sensoring, so much to play with, still doing just that myself! Link below:

http://alkenius.no-ip.org/Cam4you_remote/index.html

nomi_68k

reyalp
should be LDR R3,=task_CaptSeqTask_my

Shame on me!! 😁 I was very tired.
To forgive me, I post all the functions that I found with a very high grade of confidence.
But I confirm you that there's the necessity to find someone much more experienced than me to do the porting. 🙁
However I still try to work on this job.
Bye.

trunk\platform\sx110is\sub\100b\stubs_entry.S
// !!! THIS FILE IS GENERATED. DO NOT EDIT. !!!
#include "stubs_asm.h"

NSTUB(AllocateMemory, 0xFFE08340)
NSTUB(AllocateUncacheableMemory, 0xFFC1782😎
NSTUB(Close, 0xFFC1334😎
NSTUB(CreateTask, 0xFFC0B8C0)
NSTUB(DeleteFile_Fut, 0xFFC12BF4)
NSTUB(EnterToCompensationEVF, 0xFFC1531😎 // "ExpComp On"
NSTUB(ExecuteEventProcedure, 0xFFC5B5B😎
NSTUB(ExitFromCompensationEVF, 0xFFC1535C) // "ExpComp Off"
NSTUB(ExitTask, 0xFFC0BB50)
NSTUB(Fclose_Fut, 0xFFC12D70)
NSTUB(Feof_Fut, 0xFFC12F5C)
NSTUB(Fflush_Fut, 0xFFC12F9😎
NSTUB(Fgets_Fut, 0xFFC12EC4)
NSTUB(Fopen_Fut, 0xFFC12D30)
NSTUB(Fread_Fut, 0xFFC12E1C)
NSTUB(FreeMemory, 0xFFE0833😎
NSTUB(FreeUncacheableMemory, 0xFFC1786😎
NSTUB(Fseek_Fut, 0xFFC12F10)
NSTUB(Fwrite_Fut, 0xFFC12E70)
NSTUB(GetBatteryTemperature, 0xFFC3885C)
NSTUB(GetCCDTemperature, 0xFFC387EC)
NSTUB(GetCurrentAvValue, 0xFFD0F3D4)
NSTUB(GetCurrentTargetDistance, 0xFFD0D8D4)
NSTUB(GetDrive_ClusterSize, 0xFFC44DCC)
NSTUB(GetDrive_FreeClusters, 0xFFC44E34)
NSTUB(GetDrive_TotalClusters,0xFFC44E00)
NSTUB(GetFocusLensSubjectDistance, 0xFFE047A4)
NSTUB(GetOpticalTemperature, 0xFFC388CC)
NSTUB(GetParameterData, 0xFFD3897😎
NSTUB(GetPropertyCase, 0xFFC5F2A0)
NSTUB(GetSystemTime, 0xFFE0839😎
NSTUB(GetZoomLensCurrentPoint, 0xFFD12370)
NSTUB(GetZoomLensCurrentPosition, 0xFFE02890)
NSTUB(IsStrobeChargeCompleted, 0xFFC92E0😎
NSTUB(LocalTime, 0xFFC595BC)
NSTUB(LockMainPower, 0xFFC63DA0)
NSTUB(Lseek, 0xFFC1348😎
NSTUB(MakeDirectory_Fut, 0xFFC12C6😎
NSTUB(MoveFocusLensToDistance, 0xFFE5B264)
NSTUB(MoveZoomLensWithPoint, 0xFFE0507C)
NSTUB(NewTaskShell, 0xFFC5ED4😎
NSTUB(Open, 0xFFC13320)
NSTUB(Read, 0xFFC0A13😎
NSTUB(ReadFastDir, 0xFFDF35B😎
NSTUB(Remove, 0xFFC13390)
NSTUB(RenameFile_Fut, 0xFFC12BA0)
NSTUB(SetAutoShutdownTime, 0xFFC63E14)
NSTUB(SetFileTimeStamp, 0xFFC13624)
NSTUB(SetParameterData, 0xFFD388E😎
NSTUB(SetPropertyCase, 0xFFC5F19😎
NSTUB(SleepTask, 0xFFC176AC)
NSTUB(TakeSemaphore, 0xFFC0B74C)
NSTUB(TurnOffBackLight, 0xFFC6F9FC)
NSTUB(TurnOnBackLight, 0xFFC6F9E4)
NSTUB(UIFS_WriteFirmInfoToFile, 0xFFD2D3A0)
NSTUB(UnlockMainPower, 0xFFC63CF4)
NSTUB(UpdateMBROnFlash, 0xFFC44C0C)
NSTUB(VbattGet, 0xFFC10314)
NSTUB(Write, 0xFFC133F4)
NSTUB(_log, 0xFFE90410)
NSTUB(_log10, 0xFFE8F354)
NSTUB(_pow, 0xFFE8F4C4)
NSTUB(_sqrt, 0xFFE9177😎
NSTUB(close, 0xFFC09F50)
NSTUB(closedir, 0xFFDF368😎
NSTUB(closefastdir, 0xFFDF368😎
NSTUB(free, 0xFFC03A80)
NSTUB(kbd_p1_f, 0xFFC114F4)
NSTUB(kbd_p1_f_cont, 0xFFC11500)
NSTUB(kbd_p2_f, 0xFFC10D04)
NSTUB(kbd_read_keys, 0xFFC113F0)
NSTUB(kbd_read_keys_r2, 0xFFC35D7C)
NSTUB(lseek, 0xFFC1348😎
NSTUB(malloc, 0xFFC039AC)
NSTUB(memcmp, 0xFFC0D8B4)
NSTUB(memcpy, 0xFFC74B70)
NSTUB(memset, 0xFFD8FF54)
NSTUB(mkdir, 0xFFC136EC)
NSTUB(mktime_ext, 0xFFC753DC)
NSTUB(open, 0xFFC09EA0)
NSTUB(opendir, 0xFFDF3524)
NSTUB(openfastdir, 0xFFDF3524)
NSTUB(qsort, 0xFFD9045C)
NSTUB(rand, 0xFFC0D9BC)
NSTUB(read, 0xFFC0A13😎
NSTUB(readfastdir, 0xFFDF35B😎
NSTUB(rename, 0xFFC1341C)
NSTUB(srand, 0xFFC0D9B0)
NSTUB(stat, 0xFFC13554)
NSTUB(strcat, 0xFFC74984)
NSTUB(strchr, 0xFFC74A0C)
NSTUB(strcmp, 0xFFC0D84C)
NSTUB(strcpy, 0xFFC0D834)
NSTUB(strftime, 0xFFC74DE4)
NSTUB(strlen, 0xFFC0D890)
NSTUB(strncmp, 0xFFC749C0)
NSTUB(strncpy, 0xFFC1D254)
NSTUB(strrchr, 0xFFD8FF2C)
NSTUB(strtol, 0xFFC1D48C)
NSTUB(time, 0xFFC59470)
NSTUB(vsprintf, 0xFFC0D7F😎
NSTUB(write, 0xFFC0A19😎

nomi_68k

A question about the file "stubs_entry_2.S": I collected a list of functions from the platform "SX100IS", but I can't understand wich functions are really used by CHDK, and wich functions instead are there only for other (historical?) reasons. So for now I put the address of a nullsub for every function.
But can someone tell me for wich functions of the following list I must find the true address and wich functions I can delete without any problem?
Thanks very much.

trunk\platform\sx110is\sub\100b\stubs_entry_2.S
#include "stubs_asm.h"

// !! UNKNOWN FUNCIONS ADDRESS !!
// Not found, so pointer to nullsub for immediate return
// nullsub_1: 0xFFC00940

NHSTUB(ints_disable, 0xFFC00940)
NHSTUB(ints_enable, 0xFFC00940)
NHSTUB(kbd_pwr_on, 0xFFC00940)
NHSTUB(kbd_pwr_off, 0xFFC00940)
NHSTUB(platformsub_kbd_fetch_data, 0xFFC00940)
NHSTUB(taskcreate_jogDial, 0xFFC00940)
NHSTUB(SetZoomActuatorSpeedPercent, 0xFFC00940)
NHSTUB(strstr, 0xFFC00940)
NHSTUB(UnsetZoomForMovie, 0xFFC00940)
NHSTUB(PostLEDMessage, 0xFFC00940)
NHSTUB(TurnOnMic, 0xFFC00940)
NHSTUB(TurnOffMic, 0xFFC00940)
NHSTUB(ExpCtrlTool_StopContiAE, 0xFFC00940)
NHSTUB(ExpCtrlTool_StartContiAE, 0xFFC00940)
NHSTUB(MakeAFScan, 0xFFC00940)
NHSTUB(GiveSemaphore, 0xFFC00940)
NHSTUB(dumpMemoryToFile, 0xFFC00940)
NHSTUB(RefreshPhysicalScreen, 0xFFC00940)
NHSTUB(utime, 0xFFC00940)
NSTUB(memPartAlloc, 0xFFC00940)
NSTUB(memPartFindMax, 0xFFC00940)
NSTUB(taskCreateHookAdd, 0xFFC00940)
NSTUB(taskDeleteHookAdd, 0xFFC00940)
NSTUB(taskIdListGet, 0xFFC00940)
NSTUB(taskLock, 0xFFC00940)
NSTUB(taskUnlock, 0xFFC00940)
NSTUB(Mount_FileSystem, 0xFFC00940)
NSTUB(Unmount_FileSystem, 0xFFC00940)
NSTUB(rewinddir, 0xFFC00940)
NSTUB(CreatePhysicalVram, 0xFFC00940)
NSTUB(CreateTaskStrict, 0xFFC00940)
NSTUB(DisableDispatch, 0xFFC00940)
NSTUB(DisplayImagePhysicalScreen, 0xFFC00940)
NSTUB(EnableDispatch, 0xFFC00940)
NSTUB(GetFocusLensSubjectDistanceFromLens, 0xFFC00940)
NSTUB(MakeDirectory, 0xFFC00940)
NSTUB(PhySw_testgpio, 0xFFC00940)
NSTUB(ProtectFile, 0xFFC00940)
NSTUB(chdir, 0xFFC00940)
NSTUB(ioctl, 0xFFC00940)
NSTUB(iosDevAdd, 0xFFC00940)
NSTUB(iosDrvInstall, 0xFFC00940)
NSTUB(isalpha, 0xFFC00940)
NSTUB(isdigit, 0xFFC00940)
NSTUB(islower, 0xFFC00940)
NSTUB(isspace, 0xFFC00940)
NSTUB(isupper, 0xFFC00940)
NSTUB(localtime, 0xFFC00940)
NSTUB(readdir, 0xFFC00940)
NSTUB(strpbrk, 0xFFC00940)
NSTUB(taskCreateHookAdd, 0xFFC00940)
NSTUB(taskDeleteHookAdd, 0xFFC00940)
NSTUB(taskIdListGet, 0xFFC00940)
NSTUB(taskName, 0xFFC00940)
NSTUB(taskResume, 0xFFC00940)
NSTUB(taskSuspend, 0xFFC00940)
NHSTUB(PT_PlaySound, 0xFFC00940)
NHSTUB(DoAFLock, 0xFFC00940)
NHSTUB(UnlockAF, 0xFFC00940)
NHSTUB(WriteSDCard, 0xFFC00940)

reyalp

You need:
1) every entry point which is not found correctly in stubs_entry.S (either not found at all, or found, but matching the wrong function)
2) A handful of functions that are not automatically found.
3) A few functions that must be defined in order to link, even though they don't actually exist (or have never been found) in dryos.

The exact set of functions you need depends on which features you enable in camera.h

For 2) and 3), I would just compile and add until it works. Doing that on the SD990, I ended up with

// not in sig_ref
NHSTUB(UnsetZoomForMovie, 0xFF9689EC) // string "ZoomCon_UnsetZoomForMovie"
NHSTUB(PT_PlaySound,0xFF863970) // search on PT_PlaySound
NHSTUB(PutInNdFilter,0xFFA46ED0) // string TurnOnNdFilter ? TODO!
NHSTUB(PutOutNdFilter,0xFFA46EF4) // string TurnOffNdFilter ? TODO!
NHSTUB(DoAFLock,0xFF863A80) // PT_DoAFLock 
NHSTUB(UnlockAF,0xFF863A90) // PT_UnlockAF 

// These don't exist/aren't found in dryos
NHSTUB(Mount_FileSystem,0xFF81093C) // NULLSUB
NHSTUB(Unmount_FileSystem,0xFF81093C) // NULLSUB
NHSTUB(rewinddir,0xFF81093C) // NULLSUB
NHSTUB(SetZoomActuatorSpeedPercent,0xFF81093C) // NULLSUB

As noted above, your mileage may vary depending on what features you have enabled.

Note that stubs_entry_2.s should contain NHSTUB not NSTUB.

It's a good idea to look at a few different cameras when you are trying to figure out what to do. Different people with varying levels of understanding have done different ports. You might want to refer to sd1100 100c for this one. Also beware that while many are commented like I have above, entry points have been added at the end of most of the stubs_entry_2.S files without regard to the comments 😉

hnsight

Hey Nomi ... just so you know, some of us here are lurking, and rooting for you!

I have an SX110 and periodically check here on progress. I would LOVE to see you succeed with a port, it would make this camera sooo much better!

I appreciate your effort! Keep at it!

chdkj

Hi Nomi,

I'm working on a port for the sx110 (1.00b) for a few weeks now - more or less. Anyway.. hope we will get it as soon as possible. I didn't spend all of my time for having fun with camera ports 😉

I can confirm all of the entry points for the functions mentioned in stubs_entry.S above.

It seems to me that RefreshPhysicalScreen is located at 0xFFD8FC00 (not 100% safe)--> NHSTUB(RefreshPhysicalScreen, 0xFFD8FC00). I had analyzed functions at superior levels and followed the function calls and ended up with 0xFFD8FC00.

Couldn't find code for kbd_power_off an kbd_power_on so far and I think these functions are not implemented and should be pointed to nullsubs:
NHSTUB(kbd_pwr_off, 0xFFC00940)
NHSTUB(kbd_pwr_on, 0xFFC00940)

I didn't make any changes to stubs_entry.S and put all into stubs_entry_2.S

Kind regards.

reyalp

kbd_pwr_* are missing from some other cams, so this is probably OK.

chdkj

..or even not 😉
As far as I can see kbd_pwr_* is called by kbd_read_keys only (compared to a720 as an example). In sx110 kbd_read_keys executes two functions (and more) and each calls another function. And those other functions looking alike kbd_pwr_* in a720.
Frankly, it's the same as looking into a crystal ball...

NHSTUB(kbd_pwr_on, 0xFFC3642C)
NHSTUB(kbd_pwr_off, 0xFFC36444)

chdkj

found some other functions needed by chdk compile process, partly questionable:
NHSTUB(DoAFLock, 0xFFC1504😎
NHSTUB(ExpCtrlTool_StartContiAE, 0xFFC20894)
NHSTUB(ExpCtrlTool_StopContiAE, 0xFFC209D😎
NHSTUB(GiveSemaphore, 0xFFC0B81C)
NHSTUB(MakeAFScan, 0xFFD19824) //differ from other cams
NHSTUB(PostLEDMessage, 0xFFC357C8 ) //questionable, might be wrong...
NHSTUB(PT_PlaySound, 0xffc4dcf0) //questionable, might be wrong...
NHSTUB(SetZoomActuatorSpeedPercent, 0xFFC00940) //nullsub, there are things like SetZoomActuatorSpeedPPS in fw
NHSTUB(TurnOffMic, 0xFFC36DD😎
NHSTUB(TurnOnMic, 0xFFC36DAC)
NHSTUB(UnlockAF, 0xFFC1509C)
NHSTUB(UnsetZoomForMovie, 0xFFD3E944)
NHSTUB(WriteSDCard, 0xFFD02B30)

chdkj

... compile is running straight through but the cam don't like DISKBOOT.BIN. Cam feigns death. The SD card is write protected. A few changes to DISKBOOT.BIN by a simple editor lead to a "card is write protected" message. Seems that code from DISKBOOT.BIN is terribly wrong. Checked boot.c, lib.c, main.c and others and I will do this again.

Obihoernchen

chdkj do you have akready spoken with nomi_68k ? Maybe he can give you the code and you can finish the work.

For all developers please keep this: http://chdk.wikia.com/wiki/SX110IS actual.

« Previous Page Next Page »