Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

SD card info

SD card info

2007-01-19 by David Collier

not strictly a processor specific question, sorry, ( and if anyone knows 
of a better place to ask it, please tell )

I'm trying to build some s/w to talk to a MicroSD ( previously known as 
TransFlash ) card in SPI mode.

There don't seem to be any published data sheets on the SanDisk web 
site, they just say "conforms to the specification"

But you can't get the specification without paying $oodles to join the 
interest group.

This is nonsense - I don't have this problem with other components.

My immediate need is to know what SPI clock speed it will talk to me at.

But I suppose if I have that I'll immediately need the s/w info for how 
to interact with it. I think most of that is in the filleted document 
they so graciously allow you to download.

I know a number of people around here have written stuff to talk to 
SPI-SD cards - is any of it GPL or anything so I can go get it to see 
how it's done?

TVM

Re: [AVR-Chat] SD card info

2007-01-19 by Bruce Parham

There are two SD links on SanDisk OEM manuals page @

     http://www.sandisk.com/Oem/Manuals/

Neither is complete but it's a start.

Good hunting,

Bruce


David Collier wrote:
Show quoted textHide quoted text
> not strictly a processor specific question, sorry, ( and if anyone knows 
> of a better place to ask it, please tell )
> 
> I'm trying to build some s/w to talk to a MicroSD ( previously known as 
> TransFlash ) card in SPI mode.
> 
> There don't seem to be any published data sheets on the SanDisk web 
> site, they just say "conforms to the specification"
> 
> But you can't get the specification without paying $oodles to join the 
> interest group.
> 
> This is nonsense - I don't have this problem with other components.
> 
> My immediate need is to know what SPI clock speed it will talk to me at.
> 
> But I suppose if I have that I'll immediately need the s/w info for how 
> to interact with it. I think most of that is in the filleted document 
> they so graciously allow you to download.
> 
> I know a number of people around here have written stuff to talk to 
> SPI-SD cards - is any of it GPL or anything so I can go get it to see 
> how it's done?
> 
> TVM

Re: SD card info

2007-01-21 by kernels_nz

Hi TVM,

Theres a quite a bit of information out there on interfacing to SD
Cards, when I did it a year or so ago, I found enough information on
Google to get me going. Things to watch out for:

- SD cards are not programmed byte by byte, they must be programmed in
512 byte pages. 
- The initialization must be done exactly as the datasheet describes.

If you cant find any datasheets, send me an email on
hein@andante.co.nz and ill email a few through to you.

Cheers
Hein B
Auckland, New Zealand.




--- In AVR-Chat@yahoogroups.com, "David Collier"
<from_yahooAVRchat@...> wrote:
>
> not strictly a processor specific question, sorry, ( and if anyone
knows 
Show quoted textHide quoted text
> of a better place to ask it, please tell )
> 
> I'm trying to build some s/w to talk to a MicroSD ( previously known as 
> TransFlash ) card in SPI mode.
> 
> There don't seem to be any published data sheets on the SanDisk web 
> site, they just say "conforms to the specification"
> 
> But you can't get the specification without paying $oodles to join the 
> interest group.
> 
> This is nonsense - I don't have this problem with other components.
> 
> My immediate need is to know what SPI clock speed it will talk to me at.
> 
> But I suppose if I have that I'll immediately need the s/w info for how 
> to interact with it. I think most of that is in the filleted document 
> they so graciously allow you to download.
> 
> I know a number of people around here have written stuff to talk to 
> SPI-SD cards - is any of it GPL or anything so I can go get it to see 
> how it's done?
> 
> TVM
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.