A1100 IS Porting thread

[reyalp]

i used the .bin on top of this page and it works for a great part but i have some issues with raw

If it loads and runs, the issues are not likely to be related to your canon firmware version. Make sure you've read the stickies in the raw forum, and the previous posts in this thread about raw.

[Timich]

Try follow:
1. Press "play" button for ~ 2 seconds. Wait for loading.
2. Press shutter button.

Still doesn't work.

[Timich]

I have a A1100is with firmware 1.00a ( if i'm not mistaken ) is there a .bin file for this camera en development ?
and if yes where can i find it
i used the .bin on top of this page and it works for a great part but i have some issues with raw

As you may have noticed, the .bin from this thread doesn't work with my 1.00A.

Maybe you have B or C revision? You may check it, using ver.req (vers.req) as described here:

http://chdk.wikia.com/wiki/A1100IS

Or using this program http://chdk.wikia.com/wiki/CameraVersion on a taken picture.

[xiaofeng]

still now,firmware version 1.0c works good!I have no 1.0a,1.0b.So I cant do some thing.

[Timich]

still now,firmware version 1.0c works good!I have no 1.0a,1.0b.So I cant do some thing.

As it was written here http://chdk.setepontos.com/index.php/topic,4727.msg51933.html#msg51933 your port also works with B revision.

Unfortunately I wasn't able to contact with the guy who blinked 1.00C firmware (what version of blinker did he use, etc.), so probably I'll have to experiment with the blinker myself.

[Timich]

xiaofeng, can you upload an unencoded (no 'dancing bits') bootdisk.bin?

[xiaofeng]

xiaofeng, can you upload an unencoded (no 'dancing bits') bootdisk.bin?

I do not understand your question clear?
Sorry for my bad english.

[Timich]

After compilation diskboot.bin is encoded using 'dancing bits' technique. This process is controlled by "NEED_ENCODED_DISKBOOT=X" directive located in <...>/platform/a1100/sub/100c/makefile.inc file.

To compile an unencoded diskboot you should remove "NEED_ENCODED_DISKBOOT=X" directive from makefile.inc and recompile chdk.

Currently there is "NEED_ENCODED_DISKBOOT=2" in makefile.inc

So, can you recompile diskboot.bin without "NEED_ENCODED_DISKBOOT=2" and upload it?

[xiaofeng]

what is the use of it?
the unencode  bin file need another file to run.
Am I right?
If so how to do it?

[Timich]

Thanks!

I will convert it to "ps.fi2" using this tool: http://chdk.setepontos.com/index.php/topic,2995.0.html and upload here in a few hours.

If someone can do it faster, it is really appreciated.)

Then, camera owners will be able to test it using "Firmware update..." feature.

Theoretically, encoding unencoded diskboot.bin to ps.fi2 using tool mentioned above, should work.

I compiled blinker without any dancing bits encoding, then converted it to ps.fi2 and it works well (another question, that I had problems with finding fast photodiode).

[Timich]

Chdk version for manual (via "Firmware update" option) load.

For 1.00C and probably 1.00B

Converted from unencoded xianofeng's diskboot using fi2 encoder and 31C3 P-ID (for A1100 IS)

Please test and see how it works.

[hha1]

Chdk version for manual (via "Firmware update" option) load.

For 1.00C and probably 1.00B

Converted from unencoded xianofeng's diskboot using fi2 encoder and 31C3 P-ID (for A1100 IS)

Please test and see how it works.

It does not work with Firmware 1.00C.
No flashing blue light. indicating bootup.
A1100 reports that SD card is locked.

xiaofeng's diskbboot May 11, 2010 build does work (within limits)
using the review button to power up.

hha

[xiaofeng]

I test it.It does not work.
1.press playback button
2.press menu button.
3.press update firmware.
4.the screen trun black.-- ------>camera trun off automatic.



some suggestion?

[hha1]

Xiaofeng:

Good news for the A1100 porting. Some parts of the scripting work.
The following interval script works using CHDK 0.9.9 Date Jun 23 2010  FW 100C

rem Author - Keoeeit
rem a1100 LCD screen OFF  hha 20100721
@title a1100 Intervalometer
@param a Delay 1st Shot (Mins)
@default a 0
@param b Delay 1st Shot (Secs)
@default b 0
@param c Number of Shots (0=inf)
@default c 0
@param d Interval (Minutes)
@default d 0
@param e Interval (Seconds)
@default e 0
n=0
t=d*60000+e*1000
if c<1 then let c=0
if t<100 then let t=100
do
  click "display"
  get_prop 105 s
until (s=2)
g=(a*60)+b
if g<=0 then goto "interval"
for m=1 to g
 sleep 930
next m
:interval
  n=n+1
  if c=0 then print "Shot", n else print "Shot", n, "of", c
  shoot
  if n=c then end
  sleep t
  goto "interval"


With zero delays and with 1/50 sec exposure (selected by the A1100 in P-mode) and C=5,
the a1100 produces shots at  1.4, 3.7, 5.9, 8.2, and 10.6 seconds after pressing the shutter button,
with the images saved as normal quality 5 Mp jpeg.
The 2.3 seconds mean separation between shots is the time save one image.
get_prop 105 turns the LCD OFF and decreases the mean battery current from 560 mA to 420 mA.
This is less than I expected, probably because the software timing loop keeps the CPU clock speed high.
The red and green LED flashes to show activity.
Curiously the "Shot n " etc messages still flashes up for an instant.
With c=0 and 15 sec exposure in SCN=Night Mode and dark-frame subtract, the a1100 shot 102 pictures of the night sky
in one hour, when I stopped the sequence.

Some other features of CHDK are not working, maybe because the a1100 has no Manual mode,
or because some variables or memory locations have been switched around.
  
hha

[hha1]

We all know that the CHDK software updates the CCHDK.cfg file in the CHDK directory on the SD card just before the camera is powered OFF. This file gets occasionally corrupted, presumably when exploring incorrectly implemented CHDK menu options or function calls. In that case, when turning the power ON using the review button, the blue light blinks (=success), then the camera turns the LCD and everything else OFF and responds to nothing. I never needed to do this on my a530, so I presume this is an indication that the pre-beta release of diskboot ( CHDK 0.9.9 Date Jun 23 2010  FW 100C) is not stable.

It seems like I was trying different auto-iso settings or shutter speed over-ride. Has anybody else noticed this and was able to correlate this with any specific action?

The solution is to replace the CCHDK.cfg file with the last good version. Then all returns to normal. If no computer is near, change the SD card to "unlock".

hha