SX40HS porting thread - page 24 - DryOS Development - CHDK Forum  

SX40HS porting thread

  • 258 Replies
  • 89774 Views
*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #230 on: 21 / March / 2013, 11:23:07 »
Advertisements
> FAT16 on the 4G and FAT32 on the 8G ) ?

Yes, the 4GB is formatted FAT16. The 8GB FAT32.

If it isn't this it could be chdk booting code.
 

>And finally, does the cam start faster without CHDK using the same card?

I need to check this.


Thanks srsa_4c and waterwingz.


Re: SX40HS porting thread
« Reply #231 on: 21 / March / 2013, 11:34:59 »
You could also experiment with formatting the 4G card as FAT32 and see if it slows down?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #232 on: 21 / March / 2013, 11:58:43 »
No chdk, on both cards, they both boot about the same.

8GB card formatted FAT32 and using chdk, I get a slow boot.

4GB card formatted FAT16 and using chdk, I get a fast boot.

4GB card formatted FAT32, no chdk, I get a fast boot.



Re: SX40HS porting thread
« Reply #233 on: 21 / March / 2013, 12:35:47 »
No chdk, on both cards, they both boot about the same.

8GB card formatted FAT32 and using chdk, I get a slow boot.

4GB card formatted FAT16 and using chdk, I get a fast boot.

4GB card formatted FAT32, no chdk, I get a fast boot.

What about 4G card formatted FAT32 with CHDK ?
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline lapser

  • *****
  • 1093
Re: SX40HS porting thread
« Reply #234 on: 21 / March / 2013, 12:44:44 »
4GB card formatted FAT32, no chdk, I get a fast boot.
Did you try the 4GB card formatted FAT32 WITH CHDK?

I wonder if it's related to the block size. Do you know the block size when you format the cards?

How slow is slow, compared to fast, in seconds approximately?
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #235 on: 21 / March / 2013, 13:17:56 »
>What about 4G card formatted FAT32 with CHDK ?

Slow

>I wonder if it's related to the block size. Do you know the block >size when you format the cards?

Not sure, I have used sdminste.exe and fat32format.exe. No option for block size as far as I know with those two.


>How slow is slow, compared to fast, in seconds >approximately?

about 1 sec.

When I use the old-slow-cheapo 4GB card and I press the power button, the SX40HS is ready for action fast :)

Another one, do you guys think it has to do with a delay in the power button when starting in play mode?


*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #236 on: 21 / March / 2013, 14:28:33 »
I just formatted the 4GB card FAT16 with CardTricks144.
So I'm back to a fast boot.
I like pressing the power button and being ready to take
a picture as quick as possible. I don't know if using FAT16 will slow down the DNG's writing process,
but I haven't noticed much difference when using FAT32.
I'll keep experimenting with the FAT32 8GB card.

I hope the booting code for the SX40SH(i) can be optimized if needed.


*

Offline reyalp

  • ******
  • 13439
Re: SX40HS porting thread
« Reply #237 on: 21 / March / 2013, 23:38:08 »
I hope the booting code for the SX40SH(i) can be optimized if needed.
Unlikely. For cameras like the SX40 where the Canon firmware can boot for FAT32 (rather than requiring multiple partitions) CHDK doesn't do anything different based on the card format.

You could perhaps figure out where the time is being spent using LEDs.

If core_spytask_can_start didn't get called, that would slow things down, but I don't see how that would depend on the card format.
Don't forget what the H stands for.


Re: SX40HS porting thread
« Reply #238 on: 22 / March / 2013, 00:19:34 »
If core_spytask_can_start didn't get called, that would slow things down, but I don't see how that would depend on the card format.
So if init_file_modules_task gets running prior to spytask then spytask would clear "spytask_can_start" after init_file_modules_task had set it - invoking a four second startup delay?

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 13439
Re: SX40HS porting thread
« Reply #239 on: 22 / March / 2013, 00:56:19 »
If core_spytask_can_start didn't get called, that would slow things down, but I don't see how that would depend on the card format.
So if init_file_modules_task gets running prior to spytask then spytask would clear "spytask_can_start" after init_file_modules_task had set it - invoking a four second startup delay?
That wasn't really what I had in mind, but I guess might be theoretically possible on dryos cameras. If that was a problem, core_spytask doesn't actually need to set spytask_can_start=0, global initialization will happen much earlier.

wrapping the spytask_can_start loop with led on/off would tell you if any significant time was being spent there.
Don't forget what the H stands for.

 

Related Topics