supplierdeeply

S95 Porting Thread

  • 1000 Replies
  • 168192 Views
*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: S95 Porting Thread
« Reply #40 on: 11 / October / 2010, 22:08:35 »
Advertisements
@Fernando

Have you also read this ?
(Mac's frequently refuse to make downloaded files executable)

Also, to get a 2 partition card to boot:

1) don't forget to format both partitions after creation

1.5)  the small FAT16 partition must be 'bootable-for-CHDK' which means it has to have
       the string BOOTDISK written to sector 0 at offset 64 decimal / 0x40 hex

2) only DISBOOT.BIN should be on the small FAT16 partition, all others (CHDK folder !) on the large FAT32

3) the small partition should be active, and the card locked; CHDK should then boot on camera start,
    and should automatically 'see' the large partition and use it to store pics


HTH,

wim

[edit: forgot 1.5 ]
« Last Edit: 11 / October / 2010, 22:22:04 by whim »

Re: S95 Porting Thread
« Reply #41 on: 12 / October / 2010, 02:42:15 »
1. If you mean what version of the trunk it was derived from, that is shown on the splash screen.
2. On zShare, click Download Now, wait a little while, click the word "here".

Waldo, thanks again buddy.

Yes, I found it. I first downloaded the zshare Source link and couldn't find it, then found it in the zshare binaries folder.

With regards to loading a previous version of CHDK and swapping the DISKBOOT.BIN and PS.FI2 files would that refer to an earlier version for the S90 CHDK?

I just sold my S90 and picking up my S95 tomorrow and excited to try some timelapse scripts out with the S95.

A million thanks again Waldo.

Cheers.

Re: S95 Porting Thread
« Reply #42 on: 12 / October / 2010, 10:51:35 »
Hello Hollywood,

With regards to loading a previous version of CHDK and swapping the DISKBOOT.BIN and PS.FI2 files would that refer to an earlier version for the S90 CHDK?

I assumed Waldo has worked with some recent CHDK trunk, so I downloaded one of the full S90 builds. I think the chosen build does not matter since the device dependant part has to be overwritten with Waldo's files.
On splash screen, CHDK displays version 0.9.9-938.

@Fernando : I haved used na SDHC card, formatted it from within the S95, simply added CHDK files then Waldo's, and did not bother creating several partitions etc. Hope that helps you.


Sorry Waldo, I wish I could help you find out how to make the overrides work  :( . The only thing I can say is by focusing on an other subject, one can find the solution of the problem he was trying to solve.
« Last Edit: 12 / October / 2010, 10:56:44 by m4mmon »

Re: S95 Porting Thread
« Reply #43 on: 12 / October / 2010, 17:34:25 »
whim:
Thank you for the tips , I'll check

m4mmon:
I'll try that (I assume you are using a >4GB card not being forced to use partitions)
But my S95 formats in FAT32, incl the 4GB card...

Thank you all, I'll try again soon
« Last Edit: 12 / October / 2010, 17:37:08 by Fernando »


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: S95 Porting Thread
« Reply #44 on: 13 / October / 2010, 04:57:56 »
waldo , for the overrides check out the sx210 port,
propset3 is no longer valid for new cams

it may help

*

Offline waldo

  • ***
  • 238
Re: S95 Porting Thread
« Reply #45 on: 13 / October / 2010, 08:38:57 »
waldo , for the overrides check out the sx210 port,
propset3 is no longer valid for new cams

Yes, my source uses different values for every prop case higher than 149.  I did not create a new propsetX.h to avoid confusion where several people might simultaneously create a new propset5.h or propset6.h, each different for different cameras.  Personally, I think propsets belong in the platform directory, not the include directory.

*

Offline reyalp

  • ******
  • 11031
Re: S95 Porting Thread
« Reply #46 on: 14 / October / 2010, 12:39:46 »
waldo , for the overrides check out the sx210 port,
propset3 is no longer valid for new cams

Yes, my source uses different values for every prop case higher than 149.  I did not create a new propsetX.h to avoid confusion where several people might simultaneously create a new propset5.h or propset6.h, each different for different cameras.  Personally, I think propsets belong in the platform directory, not the include directory.
If every new camera turns out to be different, something will have to be done. It's not clear that this is the case though. My wild guess would be it goes with canon OS releases, so r43 has one set, r45 has another.

Have a copy for each camera would be maintenance nightmare.
Don't forget what the H stands for.

Re: S95 Porting Thread
« Reply #47 on: 15 / October / 2010, 03:24:36 »
Waldo,

I have something strange running the beta and running the Canon firmware.
My camera overexposes as it takes too slow shutter speed.

Night shots seem almost like day and light points are clipping.
:'(

I feel that (sensor) calibration data has been altered or something similar.

No matter what I do and no matter how many times I reset in the menu. No change.

I just want to warn you guys this might happen. Have to send mine in for a check at Canon's.

Is there a way to give the camera a true hard reset or do I really have to send it to Canon?

Johan


« Last Edit: 15 / October / 2010, 03:26:09 by jnmaessen »


Re: S95 Porting Thread
« Reply #48 on: 15 / October / 2010, 05:57:50 »
Hello,

where have you bought your S95 with 100E?
Do you think I have a Chance to get one in Germany or San Francisco?

Thanks

genervi

*

Offline reyalp

  • ******
  • 11031
Re: S95 Porting Thread
« Reply #49 on: 15 / October / 2010, 12:32:18 »
Waldo,

I have something strange running the beta and running the Canon firmware.
My camera overexposes as it takes too slow shutter speed.

Night shots seem almost like day and light points are clipping.
:'(

I feel that (sensor) calibration data has been altered or something similar.

No matter what I do and no matter how many times I reset in the menu. No change.

I just want to warn you guys this might happen. Have to send mine in for a check at Canon's.

Is there a way to give the camera a true hard reset or do I really have to send it to Canon?

Johan



You are saying this happens without CHDK ?

Can you post an example picture, with exposure data ?

In general, it is extremely unlikely that CHDK would cause any permanent changes, and calibration wouldn't turn night into day.

@genervi
There is no way to know which firmware version you will get, short of checking it while in the store. FWIW porting new variants is much less difficult than making a whole new port, so there is a fair chance other flavors will be supported eventually.
Don't forget what the H stands for.

 

Related Topics