A495 porting thread

HankeyPoo

44

Re: A495 porting thread

« Reply #190 on: 02 / June / 2011, 07:53:59 »

Advertisements

Logged

waterwingz

12139

Re: A495 porting thread

« Reply #191 on: 02 / June / 2011, 08:44:36 »

Quote from: HankeyPoo on 02 / June / 2011, 07:53:59

There is a german user with said january that the beta 495f works.

Works with an earlier release of the German version of CHDK. Its a different code base. I still need to know if the build I did of the 1.00f works.

Logged

Ported : A1200 SD940 G10 Powershot N G16

waterwingz

12139

Re: A495 porting thread

« Reply #192 on: 02 / June / 2011, 12:21:57 »

Follow-up - I think I've got it down to six stubs entries that may not be correct. That's a lot more managable - I'll pick away at them over the next couple of days when I have a few minutes. For what its worth, the questionable stubs are :

Code: [Select]

kbd_read_keys_r2()  <- 1st instruction is a Branch to somewhere else 
leddrive()                 <- different code that my reference port
qsort()                     <- not a proper subroutine - will crash if called
readfastdir()             <- different code that my reference port
time()                      <- different code that my reference port
writesdcard()            <- nulsub in the A495 ports

Logged

Ported : A1200 SD940 G10 Powershot N G16

HankeyPoo

44

Re: A495 porting thread

« Reply #193 on: 02 / June / 2011, 12:45:22 »

Hi !

Hmmm - the "writesdcard" would confirm my theory about crashing when the photo is done an has to be write on the sd card.
My tests show that everything is fine - even at long exposuretimes - the crash happends when the cam tries to write the picture on the SD Card.

Logged

reyalp

14082

Re: A495 porting thread

« Reply #194 on: 02 / June / 2011, 12:58:37 »

Quote from: HankeyPoo on 02 / June / 2011, 12:45:22

Hi !

Hmmm - the "writesdcard" would confirm my theory about crashing when the photo is done an has to be write on the sd card.
My tests show that everything is fine - even at long exposuretimes - the crash happends when the cam tries to write the picture on the SD Card.

Good guess, but this isn't it, WriteSDCard is only used to write *directly* to the SD card, bypassing the canon OS. This is used for partition swapping and "make bootable" but not normal file access.

Logged

Don't forget what the H stands for.

waterwingz

12139

Re: A495 porting thread

« Reply #195 on: 02 / June / 2011, 14:20:33 »

Quote from: reyalp on 02 / June / 2011, 12:58:37

Good guess, but this isn't it, WriteSDCard is only used to write *directly* to the SD card, bypassing the canon OS. This is used for partition swapping and "make bootable" but not normal file access.

It a null_sub ( BX LR) and should not have cause a crash in any case. (yes - I understand that risk that the calling routine might have expected something back that it then operate on).

Turns out there are other routines in the A495 port also stubbed out that way - the ND filter in & out being one example. Not going to worry about that until the shooting crash gets fixed.

Logged

Ported : A1200 SD940 G10 Powershot N G16

D. Obermann

5

Re: A495 porting thread

« Reply #196 on: 02 / June / 2011, 16:42:09 »

Hi waterwingz.
Found your request for PS A 495 FW 1.00 F users today; following a hint of msl, german chdk forum.
I have a PS A 495 FW 1.00 F since 2011 May 7, working with german chdk v. 558 or 560(?), dont know exactly,
must have a look at my own pc; i am not at home yet.
Tried hasty this evening your posted version.
CHDK boot works; bad pixel.bin creation works; *.dng format works.
Have not tested anything else; what kind of function do you need to be tested?

regards

Logged

IXUS60/SD600, FW 1.00A; Powershot S95, FW 1.00H; Powershot A495, FW 1.00F;
sometimes IXUS100 IS, FW 1.00C; infrequently IXUS80 IS, FW 1.01B

waterwingz

12139

Re: A495 porting thread

« Reply #197 on: 02 / June / 2011, 17:10:05 »

Quote from: D. Obermann on 02 / June / 2011, 16:42:09

CHDK boot works; bad pixel.bin creation works; *.dng format works.
Have not tested anything else; what kind of function do you need to be tested?

If you can confirm that the version I posted for the 1.00f firmware will successfully take a regular jpg picture (i.e. not crash when you press the shutter button) then you have done everything I need !

Logged

Ported : A1200 SD940 G10 Powershot N G16

HankeyPoo

44

Re: A495 porting thread

« Reply #198 on: 02 / June / 2011, 17:29:00 »

Logged

philmoz

3450

Re: A495 porting thread

« Reply #199 on: 02 / June / 2011, 18:19:15 »

Quote from: waterwingz on 02 / June / 2011, 12:21:57

Follow-up - I think I've got it down to six stubs entries that may not be correct. That's a lot more managable - I'll pick away at them over the next couple of days when I have a few minutes. For what its worth, the questionable stubs are :
Code: [Select]
kbd_read_keys_r2() <- 1st instruction is a Branch to somewhere else leddrive() <- different code that my reference port qsort() <- not a proper subroutine - will crash if called readfastdir() <- different code that my reference port time() <- different code that my reference port writesdcard() <- nulsub in the A495 ports

I've been working on an enhanced version of finsig/gensig that is giving me very good results so far.
If you can post your platform/a495 files (and all the subs directories) I can try my signature matching algorithms and see if it picks up anything.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)