S90 Porting Thread

gsbergman

V4_S90_100c.zip (346.47 KB - downloaded 10 times.)

Winzip reports the file is an invalid archive. Could you please repost the 100c file.

ERR99

I also donwloaded the file and cant find any problem, winzip is opening and unpacking this file here without problem.
But if you wish, here is the 100c V4 build re-uploaded again:

gsbergman

Thank you. That one opened just fine. The other one even PKZip reported errors. Go figure?

gsbergman

FYI.

This is the log file from PKZip about the first V4 100c file. WinZip reported the archive was invalid and PKZip reported this log file.

4/20/2010 6:32:42 AM ZIP Reader Version 12.40.0005 Build 1004
4/20/2010 6:32:42 AM Extracting: C:\Documents and Settings\gbergman\Desktop\V4_S90_100c.zip
4/20/2010 6:32:42 AM Extracting C:\Documents and Settings\gbergman\Desktop\V4_S90_100c\DISKBOOT.BIN
4/20/2010 6:32:42 AM Unexpected end of compressed data for: C:\Documents and Settings\gbergman\Desktop\V4_S90_100c\DISKBOOT.BIN
4/20/2010 6:32:42 AM Extracting C:\Documents and Settings\gbergman\Desktop\V4_S90_100c\PS.FI2

Just don't want anyone to think I'm crazier than I am.

gsbergman

Just getting off work. (supported the Shuttle landing since midnight). I'll check out V4 this afternoon from home.

lsl7994

I am having s90 1.01b firmware... Is it possible to use any of the files? Thanks.

ERR99

gsbergman
FYI.
This is the log file from PKZip about the first V4 100c file. WinZip reported the archive was invalid and PKZip reported this log file.

I think you got a bad internet connection as you download the file the first time and only your copy was corrupted. I downloaded now both versions (from my first post and also the last one) and compared them binary. They are 100% identical.

ERR99

lsl7994
I am having s90 1.01b firmware... Is it possible to use any of the files? Thanks.

May be, may be not. It depends what canon has changed in compare to 1.01a or 101c.
You can simply try the 101a or 101c build. Anyway, it would be good if you can dump your 101b firmware
and post the dump on zshare or so.

To dump the firmware, you can try the G11 udumper from this post: https://chdk.setepontos.com/d/4647/330

lsl7994

ERR99
May be, may be not. It depends what canon has changed in compare to 1.01a or 101c.
You can simply try the 101a or 101c build. Anyway, it would be good if you can dump your 101b firmware
and post the dump on zshare or so.

To dump the firmware, you can try the G11 udumper from this post: https://chdk.setepontos.com/d/4647/330

I am trying to dump the firmware now. Will upload it later. Thanks. 😀

lsl7994

Not sure whether I have done it right. Here is the zshare link for the firmware 1.01b.

http://www.zshare.net/download/75182953a66f941d/

mercurio

101c v4 works great. thanks for all your work err99 😁

ERR99

@lsl7994:
You extracted the pure strings from the firmware dump, but for a port a complete dump of the firmware is necessary.
It is usally a *.bin file and the size is ca. 8MB. So please check if you got such a .bin file during your dumping process with cardtricks.

ERR99

mercurio
101c v4 works great. thanks for all your work err99 😁

Thats good to hear. 😉
Did you also test optical zoom and af-scan in moviemode with the 101c V4 build, does it work as expected?

mercurio

ERR99

mercurio
101c v4 works great. thanks for all your work err99 😁

Thats good to hear. 😉
Did you also test optical zoom and af-scan in moviemode with the 101c V4 build, does it work as expected?

@ movie mode:
i had a look at the manual but i'm not really sure what should happen if neither select nor shutter is chosen in the af mode. should the cam focus automatically or just keep the first focus?
for now with 101cv4 it just stays focussed like at the beginning of the recording. the other two options work.
one thing i just noticed is that fast movie control (pause and restart recording) hangs if the pause is longer than a few (˜3) seconds.

lsl7994

ERR99
@lsl7994:
You extracted the pure strings from the firmware dump, but for a port a complete dump of the firmware is necessary.
It is usally a *.bin file and the size is ca. 8MB. So please check if you got such a .bin file during your dumping process with cardtricks.

I will check again then. 😀

edited: I have a .dum file which is about 10MB. Is that the one?

whim

@lsl7994

Yes it is ... with CardTricks detecting the card that has the 'empty.dum' file, just press 'Clean' -
that will remove the leading and trailing zeroes, then prompt you to save under a new name.
The resulting file is what you want to upload, ERR99 should be able to analyse it with IDA

hth,

wim

an0n

@whim,

I'm sorry this is off topic, but, whim if you see this, I've sent you a PM.

lsl7994

whim
@lsl7994

Yes it is ... with CardTricks detecting the card that has the 'empty.dum' file, just press 'Clean' -
that will remove the leading and trailing zeroes, then prompt you to save under a new name.
The resulting file is what you want to upload, ERR99 should be able to analyse it with IDA

hth,

wim

Thanks. The card is not with me now. I will upload it to zshare later for analysis. 😀

ERR99

In case you have still trouble creating the cleaned/stripped file, then simply upload the empty.dum file after dumping in the camera.
I can also strip it later by my self with cardtricks.

ERR99

mercurio
@ movie mode:
i had a look at the manual but i'm not really sure what should happen if neither select nor shutter is chosen in the af mode. should the cam focus automatically or just keep the first focus?
for now with 101cv4 it just stays focussed like at the beginning of the recording. the other two options work.
one thing i just noticed is that fast movie control (pause and restart recording) hangs if the pause is longer than a few (˜3) seconds.

To trigger a new AF-Scan during videomode, you have to assign a key for af-retriggering in the CHDK Video menu (select SHUTTER or SET button). Then, during video record, you can trigger a AF-scan with one of this buttons. There is no automatic permanent AF scan.

The CHDK feature "fast movie control" also causes a crash/shutdown on the 101a FW and is also present on the G11 CHDK port. So this is not a 101c specific problem. But the CHDK manual has also a special note for this feature: "Only works on a few cameras. Has bugs, needs further development.", so i dont care so much about this feature. But when i have time, i will take a look at the crash log. 😉

« Previous Page Next Page »