S100 porting thread

asm1989

thanks whim, It worked fine

we have to resolve why new cams fail to load the FI2,

I mean manualy loading you can allways use canon firmaware with outoload you need another sd card.

c10ud

asm1989
@c10ud

Where you able to load chdk usign the FI2 file, via fimware update menu?

I think s100 & sx260 have the same issue with this, and blocks the use of sd cards greater than 32Gb.

No, but i never tested it.

But i saw other people testing this and reported it failing. I'm not really into this FI2 thing (i find diskboot much better) so i don't know what to say..

roy.weinberg.52

Hi c10ud,
Following this thread closely as I can't wait to use CHDK on my S100! 😀

When can we expect an official release?
And can I participate in the beta?

c10ud

Hello, you can find the s100 beta build in the autobuild website already:
http://www.mighty-hoernsche.de/trunk/

beware this is not a stable release

colon247

I wish I could code so that I could help more. Except for the battery levels being wrong issue, this build is pretty solid so far. I personally used EOScard 1.2 to make my SD card bootable, loaded my CHDK files on the card, then locked my card. I can now just turn on my camera by pressing and holding the play or on/off button. (no FI2 file needed) 😁

I searched the internet for specific information about this build and could not find any. So I will write the specific information for anybody who is looking for it.

Features I have tested and work (so far):
* ISO override from 50 to 7500
* shutter speed override from 1/5000 to 2048 (34 minutes 😛 )
(I actually set a timer and returned just in time to here here the shutter close. 1 Picture took about an hour total an completely drained the battery)

* Aperture seem to stay within specs 2 to 8 (override higher than 8 seems to nothing)

* USB remote features all work well using a simple remote (could not test Ricoh CA-1)

I don't have a lot of time because of work. In my spare time I have been testing out this build of CHDK. I will write more as I get a chance.

EDIT:
hey c10ud.....when you try and choose a script from shooting mode it brings up the file browser but nothing gets highlighted so you can't really see what your are choosing. I mean it is minor since in play mode the browser is a bit different and it does highlight things. Kind of weird but just noticed it.

waterwingz

colon247
hey c10ud.....when you try and choose a script from shooting mode it brings up the file browser but nothing gets highlighted so you can't really see what your are choosing. I mean it is minor since in play mode the browser is a bit different and it does highlight things. Kind of weird but just noticed it.

Welcome to the world of Canon color palettes. Canon changes the palette it uses as it enter different modes ( playback, shooting, setup, video etc). CHDK currently has no good way to track this so the menu and OSD colors change as the Canon mode changes. Careful selection of colors can help but a good fix has not been worked out for this ( although philmoz has implemented a specialized fix for a few cameras).

colon247

I finally figured out I don't need to know coding that much using one of the gui's . So my question is what would I have to do to make things better.

For example how do I find battery max and min?
how do I help with circle of confusion?
....ect?

I dont have all the time in the world but with a little guidance maybe I can really help.

waterwingz

colon247
I finally figured out I don't need to know coding that much using one of the gui's . So my question is what would I have to do to make things better.

Probably the biggest thing you could do to help is test each version that you see released here. Especially the changes. Feedback from users is really really valued by the CHDK developers !

For example how do I find battery max and min? how do I help with circle of confusion?
....etc? I dont have all the time in the world but with a little guidance maybe I can really help.

I really hate to "rain on your parade" here, but by the time someone walks you through what it takes to make these sort of changes, they can make the changes themselves and post patches. However, just testing what works and does not work AND POSTING YOUR RESULTS is a really important thing - the devs do fixes and mostly hope nothing else breaks. Feedback helps a lot.

Update : okay, if you really want to try out making a change, compiling it and seeing it take effect, then to change the values for battery min and max at the bottom of the main.c file in trunk/platform/s100/main.c.

long get_vbatt_min()
{
    return 3000;     // 3 volts
}

long get_vbatt_max()
{
    return 4100;    // 4.1 volts
}

Play with the values until they work well for the S100.

asm1989

colon247 ,

for Circle Of Confusion
using exiftool-8.90 on a JPG taken by your cam will get something like this:
......
"Circle Of Confusion : 0.005 mm"
....

colon247

waterwingz......thanks, I know it is a bit hard but I learn quick. I will soon try changing those numbers and see where I get. No promises but if I get somewhere with these numbers I will post.

asm1989.....thanks a lot......the circle of confusion right now in "shooting.c" is

int circle_of_confusion = 5; //TODO:

I am assuming this is wrong. So far after checking all my pictures and every picture on flickr taken with a s100 is seem that the number is .006 instead of .005

This might be a dumb question but what happens when this number is wrong?

waterwingz

colon247
This might be a dumb question but what happens when this number is wrong?

Nothing much. The calculated information for hyperfocal distance / depth of field information reported in the CHDK OSD will be slightly off - depending on how wrong the circles of confusion number is.

funnel

c10ud
as for the boot, unfortunately i've been unable to find the correct value to check during boot in order to choose between play or rec so the camera only boots in play mode and then you have to switch manually (left as a todo in notes.txt)

I found this when looking for sx260 power on button.

for s100 in boot.c it should be

*(int*)(0x26E0+0x4) = (*(int*)0xC022F48C)&4 ? 0x200000 : 0x100000;

@colon247 would be great if you could test this.

colon247

funnel

I found this when looking for sx260 power on button.

for s100 in boot.c it should be

[code]*(int*)(0x26E0+0x4) = (*(int*)0xC022F48C)&4 ? 0x200000 : 0x100000;[/code]

@colon247 would be great if you could test this.

Great news it works!!!!!! I compiled it and now I can hold my power button and it goes straight into shooting mode instead of play mode like before. 😁

Edit:
I have also had time to test the battery levels. And the correct min max are:

long get_vbatt_min() // TODO:
{
    return 3200;
}

long get_vbatt_max() // TODO:
{
    return 4050;

c10ud

Nice one funnel, how did you find the value?

I remember struggling a bit around that address and the value for a correct power on in play/rec mode but no luck 😀

funnel

how did you find the value?

ROM:FF00FE48 loc_FF00FE48                            ; CODE XREF: sub_FF00FDDC+10j
ROM:FF00FE48                                         ; sub_FF00FDDC+1Cj
ROM:FF00FE48                 MOV     R0, #0x36           ---------v Plug this value
ROM:FF00FE4C                 BL      sub_FF02BC18       <-------< down here            |

ROM:FF02BC18 sub_FF02BC18                            ; CODE XREF: sub_FF00FDDC+24p
ROM:FF02BC18                                         ; sub_FF00FDDC+34p ...
ROM:FF02BC18                 LDR     R1, =dword_FF452BDC
ROM:FF02BC1C                 LDR     R2, [R1,R0,LSL#3] //0xFF452BDC+(0x36<<3)==0xFF452D8C==0xC022F48C
ROM:FF02BC20                 LDR     R2, [R2]
ROM:FF02BC24                 ADD     R0, R1, R0,LSL#3
ROM:FF02BC28                 LDR     R0, [R0,#4]   //0xFF452D8C+0x4==0x00000004
ROM:FF02BC2C                 ANDS    R0, R0, R2
ROM:FF02BC30                 MOVNE   R0, #1
ROM:FF02BC34                 BX      LR

that's it 0xC022F48C & 0x00000004

c10ud

Got it, thanks!

colon247

WOW.....did you guys go to a university to learn this. Those two codes that funnel wrote went way over my head 😐: ....jajaja

You smart people figure out anymore codes that might work, throw them at me I will try it.

for now I will stick to the simple stuff

c10ud

sent patch for trunk: https://chdk.setepontos.com/d/650/709

colon247

was reading through c10ud's changes about Fi2 and.....

Does anybody actually know the Fi2key for the s100 yet?
If nobody has it....is it hard to find?

Will the Fi2 fix for the SX260 work for this camera?

c10ud-----if you are working on this already, let me know and I will just wait 😀

c10ud

since i don't have the camera anymore i'm not working on this, but i am confident that the fix for sx260 will apply to s100 too, just wait until it gets upstreamed or apply the patch by yourself 😉

« Previous Page Next Page »