Sandisk SD Card Pinout

[ddrecovery]

Anyone have some advice on the pinout for this?
Its a Sandisk Extreme PRO 128gb SD Card.
Is it similar to other Sandisk cards (14-15 pins across) with some additional N/C points?
Or an entirely new pinout?
It is not in PC3000 Flash or VNR.
Your help would be appreciated.

Attachments

[HaQue]

pretty sure it is same pinout but leftmost pin on each row not used. try and confirm it by looking at the regular pinout for this type, and VCC/GND

[Sasha Sheremetov]

Tried through adapter or using standard pinout?

[ddrecovery]

pretty sure it is same pinout but leftmost pin on each row not used. try and confirm it by looking at the regular pinout for this type, and VCC/GND

You are quite correct. Wired it up and it reading now. Many thanks.

Tried through adapter or using standard pinout?

Reading this one the old fashioned way.....

[scratchy]

I think the extra pins are used for larger capacity or 16 bit NAND .

[ddrecovery]

Update: I tried the basic pinout for this SD Card and although it ID's, the read was junk. So i sent the card to a colleague to look at who did manage to find the correct pinout, but his comment was "this is a really weird new Sandisk configuration". So if you get one, its not the standard with a few extra pins.

[Sasha Sheremetov]

Can you post a pictures of sticker? (so we can buy it)

[ddrecovery]

Here you go.

Attachments

[jeremyb]

So i sent the card to a colleague to look at who did manage to find the correct pinout, but his comment was "this is a really weird new Sandisk configuration".

It's okay Tim, you can say my name..

Notes:
Pinout is standard, as HaQue described.

Card uses 2 Col 4 Row NOT 2 Col 3 Row

Card stores a small amount of data "? possible bank map ?" in PROM accessible by 0xEC command.. Identifiable by SNDK header (IIRC). If you send EC followed by Address offset you'll see it.. On previous generation SanDisk cards all you get is 0xFF returned on the query, this one actually has data in it.

Card reads of of phase w/ RE.. First few bytes are in sync, the rest aren't which cases the reader to read everything except the header as 0x00, where as the controller can read it perfectly.. My guess is the chip requires some specific timings.

Card requires a special reset command otherwise it returns a garbage ID.

BTW, I took Don Anderson of Tri-State Data Recovery out to lunch, he said he's a friend of yours... cool dude

[jeremyb]

Typos and annotations:

Card uses 2 Col 4 Row NOT 2 Col 3 Row

The extra ROW doesn't appear to be used, atleast when I issued read commands it didn't pull anything however this may be a future feature...

Card reads of of phase w/ RE.. First few bytes are in sync, the rest aren't which cases the reader to read everything except the header as 0x00, where as the controller can read it perfectly.. My guess is the chip requires some specific timings.

Reads out of phase... eg: if I issue the same read command for the same page it returns differently depending on whether the controller issues the read command or whether the reader does.. like the setup times are wrong. If I had another reader ** cough deep discount from sasha ** I could offer more input however all I can go by is my reader in debug mode which works in 15us timing increments.

[ddrecovery]

It's okay Tim, you can say my name..

Jeremy, Jeremy, Jeremy, I feel better now....

BTW, I took Don Anderson of Tri-State Data Recovery out to lunch, he said he's a friend of yours... cool dude

I only hang with the coolest people

[Amarbir[CDR-Labs]]

So i sent the card to a colleague to look at who did manage to find the correct pinout, but his comment was "this is a really weird new Sandisk configuration".

It's okay Tim, you can say my name..

Notes:
Pinout is standard, as HaQue described.

Card uses 2 Col 4 Row NOT 2 Col 3 Row

Card stores a small amount of data "? possible bank map ?" in PROM accessible by 0xEC command.. Identifiable by SNDK header (IIRC). If you send EC followed by Address offset you'll see it.. On previous generation SanDisk cards all you get is 0xFF returned on the query, this one actually has data in it.

Card reads of of phase w/ RE.. First few bytes are in sync, the rest aren't which cases the reader to read everything except the header as 0x00, where as the controller can read it perfectly.. My guess is the chip requires some specific timings.

Card requires a special reset command otherwise it returns a garbage ID.

BTW, I took Don Anderson of Tri-State Data Recovery out to lunch, he said he's a friend of yours... cool dude

Hi Jeremyb ,
What Do You mean by 2 col and 4 row and not 2 col by 3 rows .I have seen only two variations one start starts from initial pins from left to right and one that we have to leave a pin ,I always follow what haque said above ,thats to trace vcc vss to pads

[jeremyb]

Hi Jeremyb ,
What Do You mean by 2 col and 4 row and not 2 col by 3 rows .I have seen only two variations one start starts from initial pins from left to right and one that we have to leave a pin ,I always follow what haque said above ,thats to trace vcc vss to pads

I was referring to the read command, not the pinout..

The read command is like this..

00h COL COL ROW ROW ROW ROW 30h

[Bolo]

@jerremyb: CMD 0x65 / ADDR 0x00 0x00 0x00 / CMD 0x90 / ADDR 0x00 / DATA ...... doesn't work ???

[jeremyb]

See my Notes on SoftCenter Forums..

Preconditioning #1 Fix ID
Cmd 0x5C 0xC5 0x55
Addr 0x00
Data 0x01

Cmd 0x55
Addr 0x20
Data 0xC0

Cmd 0x55
Addr 0x20
Data 0xC0

Cmd 0x65
Addr 0x00 0x00 0x00
Cmd 0xFD
Wait