IXUS 100 IS (Europe) / PowerShot SD780 IS - Porting Thread

reyalp

You need to encode with the correct dancingbits version, which should be mentioned somewhere in this thread chdkess

chdkess

Hi, in the zip file in the first post the define is set for dancing bits as USE_ENCODED_DISKBOOT=2 which is the correct version of dancing bits for the IXUS 100. When I compile it even says it is using the right version:

main.c -> main.o
-> main.elf
main.elf -> main.bin
<< Leaving loader/ixus100_sd780/resetcode
entry.S -> entry.o
main.c -> main.o
blobs.S -> blobs.o
-> main.elf
main.elf -> main.bin
<< Leaving loader/ixus100_sd780
<< Leaving loader
>> Entering to CHDK
-> LUALIB/GEN/propset1.lua
-> LUALIB/GEN/propset2.lua
<< Leaving CHDK
-> PS.FI2
Saving ./bin/PS.FI2
Done
dance -> DISKBOOT.BIN ver 2
**** Firmware creation completed successfully

As I say, the PS.FI2 works fine but the DISKBOOT.BIN which is compiled at the same time isn't. Something fishy is going on with the dancingbits encoding.

Duke

Maybe i'm completely wrong, but i would guess that the source code linked in the first post is older. It says V3 and the binaries are stated as V7.
As far as i remember the diskboot method was not working back in Version 3.

chdkess

Hi Duke, thanks for your reply. That explains it. Harpoma do you need a hand in porting? If so I know C so can help out but I can't see the IXUS 100 code in trunk.

Chdkess

HarpoMa

Just been disconnected. The best thing people can do is submit bug reports on the current binaries. So far it's been very bare. I base my work on bug reports. I don't feel confident to submit to svn until I have more bug fixes.

I will post the latest source so people can rebuild if desired.

Harpo

reyalp

HarpoMa
Just been disconnected. The best thing people can do is submit bug reports on the current binaries. So far it's been very bare. I base my work on bug reports. I don't feel confident to submit to svn until I have more bug fixes.

I will post the latest source so people can rebuild if desired.

CHDK is GPL*, so in general, if you release a binary, you should release the corresponding source. This will also help in the cases where people abandon a partly finished port.

I would not worry too much about having all the bugs fixed before it goes into SVN. It's easier to collaborate when everyone can see the current source. If there are major outstanding bugs, we can leave it out of the autobuild.

* Given the nature of the source, one could argue that this isn't valid, but l don't want to get into that here. It was clearly the intent of the original authors that their own original code be under the GPL.

HarpoMa

I've read these comments of yours before on other posts. As for SVN thats more your call then mine as you can submit to SVN and I cannot. I won't argue the GPL because I agree the souce should be available I've just been lazy. If you would prefer I can delete the binary and rerelease once I have time.

Each version of the binary and souce is noted in post #1 btw. It is clear that the last binary is not from the last source. If this is unacceptable please say so and I will always make certain to keep them in sync. As I clean up the build it take more time then I like to spend doing a joint source / binary release.

Harpo

reyalp

HarpoMa
If this is unacceptable please say so and I will always make certain to keep them in sync.

I wouldn't worry to much about this. I sometimes post test builds without source for the same reason. OTOH, we have had a number of people abandon ports part way through, without posting their final source (and in some cases without posting any source at all), so I like to get people to post it as much as possible.

That said, if you set things up right, posting a source patch with each build shouldn't be much additional work. It's quite easy to generate a patch from your current working copy. Just svn add all the new source files (not the object files etc), and svn diff > patchfile. In tortoise you can right click "create patch". You can svn add even if you can't commit.

HarpoMa

--removed as I misread the prior post....

count

Hi! 😀

I've successfully gotten this CHDK running on a European Ixus 100IS (the Mac tips helped - you really have to do all of them, including deletion of extended attributes) ... looks nice!

Since this is my first CHDK try, I don't know what to test (is there something like a page with a 'Testsuite' that once can walk through to confirm everything works as expected?)

what I'm missing is the Zebra display - doesn't seem to be there.

The BASIC interpreter seems to be working, although the hdr-stack script (http://chdk.wikia.com/wiki/UBASIC/Scripts:_HDR_with_stacking) I tried seems to have problems - it's taking quite a lot of pictures, and it doesn't seem to be able to change the exposure setting after changing it the first time ...

I trigger it using ALT-Shoot with the exposure menu on screen - I guess it would be required to turn of the '<ALT>' mode, but then the script stops running. Maybe I misunderstand something - or there is still a problem. This would be my main usecase for CHDK, though 😀 I don't know what else is possible and will probably only discover later ...

I can test etc., just let me know what I shall do 😀

Please advise

count

HarpoMa

Fab. I'll add those items to the list. I hope to be back to normal schedule this week and I'll be back here again.

Harpo

srunyon1

just get USB control.. and or a timer great work!!!! thanks!!!

count

I don't get the bit about the GPL compliance required? GPL requires you to provide the sourcecode & buildscripts - is that's what 0.7b is, and nothing else? Or does it give me anything else than 0.7? A quick changelog on updates would be nice 😀 I'm basically holding my breath 😉

chdkess

In case you're interested, I think I've found the following addresses:

Mount_FileSystem    0xFF862020
Remount_FileSystem    0xFF862134

Jestik

one more question: will it be possible to fix iso in the mobie mode?

HarpoMa

@chdkess - thx I'll add them in.
@count - 0.7b is my latest build possible. As for change logs thats what post #1 is...
@jestik - I don't know what you mean really - If you expand on what is broke I'll fix it but understand that I cannot fix it if I don't know how to repeat it. If you also provide how to verify the fix that would be good too.

You will be happy to know that I'm back to this project now so you will actually see some more progress vs what has occured as of late. 😀

Harpo

Microfunguy

I think you will find the source files will not compile.
It first stops with errors caused by \platform\makefile_sub.inc :-

34: Extraneous text after 'else'
40: only one 'else' per conditional.

HarpoMa

It compiles in my environment but that certainly does not imply it will build in any other. I build on a Vista box and if I recall Vista is not supported in the build tree. I have made changes to make inc that certainly are not likely to be supported in the build tree.

But because I certainly don't want to hang my hat on memory I will build it tonight and verify. I don't suggest anyone actually use my source but since I am required to release it I have.

Harpo

Edit: Yes I looked at the file that is complaining and it's all related to Vista build. So if you want to build this build then you will want to have enough C++ knowledge to fix it. Likely a simple replacement of the .inc file from the real tree will make it work. However as this is NOT a submission to SVN i don't plan to fix it. This is a release of my build source and not for the average person to use.

Microfunguy

OK, I can get as far as compiling boot.c and then there are a couple of syntax errors.

At the bottom of the file are :-

LDR R1, [R5,#0x68] (not in quotes)

BLX R1 (not in quotes)

Are these meant to be commented-out ?

Jestik

HarpoMa
hm.. sorry for my english.
I was meant to say not "fix iso" but "set iso".
when i'm shooting video there is a lot of noise in shadows, because, as i understand, the camera is trying to use auto iso --> high iso
will it be possible to set iso manualy for example to 100 or 200?

« Previous Page Next Page »