Sd library problem

[bugi]

Hi,

I want to use sd library with 18F46K20 with pll 64 Mhz.

But it doesn't work with 64 Mhz.
I use, this config: SD_Init_MSSP SD_SPI_FOSC_04

It works 40 Mhz but I want to use max. speed because I use color GLCD ST7735.
At the same time I will use LES' wav player but I don't know his sd routines will be able to work at this speed.

Hi, its great to see you visiting our forum. Why not try Proton Compiler for FREE? Download the FREE version of Proton Compiler, Its called Amicus18 and its available from HERE Already using proton Compiler??? Get rid of these pesky messages... get LICENSED USER STATUS

What can I do for this issue?


Regards.

[TEEGEE]

HI

work fine , same pic , same speed

SDIN = SD_Init_FS_MSSP SD_SPI_FOSC_16
if SDIN = 1 Then ...... CARD OK

[bugi]

Hi,

work fine , same pic , same speed

SDIN = SD_Init_FS_MSSP SD_SPI_FOSC_16

But I want to use SD_Init_FS_MSSP SD_SPI_FOSC_04

Regards.

[normnet]

Hi,

I want to use sd library with 18F46K20 with pll 64 Mhz.

But it doesn't work with 64 Mhz.
I use, this config: SD_Init_MSSP SD_SPI_FOSC_04

It works 40 Mhz but I want to use max. speed because I use color GLCD ST7735.
At the same time I will use LES' wav player but I don't know his sd routines will be able to work at this speed.



What can I do for this issue?


Regards.

You have probably seen PIC iPod wav player
It is both a wav player and a GLCD.

I found SD card/SPI requires medium speed at 64 MHz.


Norm

[normnet]

You can go fast speed SPI however with a 48 MHz PIC.


Norm

[bugi]

Thanks Norm,

Now it works at 64Mhz and FOSC/4. But Les explane to me, there is a fatal flaw in most 18fxxKxx micro's MSSP module.
So, I will think about that. So I have a lot of these micros.

Regards.

Bugra

[normnet]

Thanks Norm,

...there is a fatal flaw in most 18fxxKxx micro's MSSP module...

Bugra

Interesting!
The PIC18F26K20 is what I speed tested 64 MHz with.

Norm

[Les]

They may have corrected this anomaly with the latest 18FK devices, but the 18F25Kxx and 18F45Kxx series certainly had this problem, however, they may have had a silicon update. But it is something to remember.