Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Pin 5 for SD Chip select does not work. #14

Open
FreddyVRetro opened this issue Nov 12, 2023 · 5 comments
Open

Use Pin 5 for SD Chip select does not work. #14

FreddyVRetro opened this issue Nov 12, 2023 · 5 comments

Comments

@FreddyVRetro
Copy link

Hi,

Thanks a lot for your code, I use it in the PicoMEM Board.
Il the previouis Board I di redo a PIO driver because 2 of my PIN (TX/RX) Were reversed, classical.
But this did work on a few SD only.

Now, I try with this code and I have problem:

I want to use Pin5 for CS, but it does not move.
In fact it move, but before we do mount.

After initialisation, I have one uSD Working, With CS Always down. (Strange it is working)

Do you use Pin5 for something else somewhere ?
@FreddyVRetro
Copy link
Author

FreddyVRetro commented Nov 12, 2023 •
edited
Loading

I used the wrong GPIO... Pin 5 is GPIO 3

It is working better, on more SD than before.

I have a PNY 32Gb that fail :
sd_spi_go_low_frequency: Actual frequency: 398089
V2-Version Card
R3/R7: 0x100
CMD8 Pattern mismatch 0x1aa : 0x100

@carlk3
Copy link
Owner

carlk3 commented Nov 12, 2023

I can't think of any use of Pin5 in particular. Someone else had a problem with pin 25, due to that being the PICO_DEFAULT_LED_PIN and some code in no-OS-FatFS-SD-SDIO-SPI-RPi-Pico\src\sd_driver\SPI\spi.h that used the LED as a drive activity indicator, but I have disabled that code by default. But, you might see what pins are used in pico-sdk\src\boards\include\boards\pico.h.

@carlk3
Copy link
Owner

carlk3 commented Nov 12, 2023

...
I have a PNY 32Gb that fail : sd_spi_go_low_frequency: Actual frequency: 398089 V2-Version Card R3/R7: 0x100 CMD8 Pattern mismatch 0x1aa : 0x100

Are you trying to use that with SPI or SDIO? Be aware that once a card is switched to SPI mode, the only way to get it back to SD mode is to power cycle it.

CMD8 is supposed to determine the voltage range supported by the SD card, but it is an early command and the card might be rejecting it for something else it is unhappy about. Most often, this is due to something it doesn't like about the Vdd or GND or the CLK.

You're getting R3/R7: 0x100, which is 0b100000000, so bit 8 is on.

image

Bit 8 says "2.7 - 3.6V":

image

so that much is good.

image

The "check pattern" was expected to be 0xAA but you got 0x00, so the card is unhappy about something. I suspect an electrical problem.

@FreddyVRetro
Copy link
Author

FreddyVRetro commented Nov 12, 2023 via email

@carlk3
Copy link
Owner

carlk3 commented Nov 13, 2023

I did not add pull up as well.

I don't really use pull ups anymore. Modern SD cards all have push-pull outputs, so the old thing about needing one on the card's DO doesn't seem to apply anymore. I think it was, or maybe still is, required for MMC cards, but I never use those.

These days, I'm more interested in serial source terminating resistors. I find these effective for running at higher speeds while also reducing noise (radiated EMI as well as local noise coupled into the power supply, etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@carlk3 @FreddyVRetro