Connect an SD Card to your Raspberry Pi Pico Microcontroller Board using SPI
HTML-код
- Опубликовано: 25 июл 2022
- SD cards are everywhere. In phones, cameras, handheld gaming consoles and more. You can even use an SD card with a Raspberry Pi Pico. Here is a tutorial on how you can connect an SD card to a Pico and read and write to its FAT32 filesystem. Along the way we cover SPI and how to wire an SPI device to your microcontroller board.
Code: github.com/garyexplains/examp...
Let Me Explain T-shirt: teespring.com/gary-explains-l...
Twitter: / garyexplains
Instagram: / garyexplains
#garyexplains
Thank you! Finally I found a really simple explanation of how it all works. This video is great for hardware beginners like me. 👍🏻
Great explanation! I was confused on what adapter to get but this answered my questions.
I was just thinking that i needed to get sdcard support working on my pico last week. What a happy coincidence
Thank you, this made it really easy
Great Video! Worked perfectly. Thanks for sharing.
You're welcome!
とても役立ちました。ありがとう！
*GARY!!!*
Good morning Professor!
Good morning fellow classmates!
Stay safe out there everyone!
MARK!!!!
Hi, thank you for the great video!
Do we need to mount the sd card everytime we turn on the pico?
and do we have tou mount it just once? because if I run the code at min 12:29 more than once I get a "timeout waiting for response" error
Good video! Do you try use the MMBasic to do this?
Brilliant now i can store more images for animations on a display
thank you mr garyy
nice, expands the options for a pico webserver, much more local data available,
could even have more than 1 sd card reader attached, just need a specific CS pin for each, the other wires are shared.
Thanks for the help. I have an old ITDB02-2.8, 2.8inch tft lcd with 65k color 320 x 240 and touchscreen that I want to use for a midi fighter. This helps a lot.
Interesting! 🙌🏼🤔 Could the Raspberry Pi Pico be programmed to work like a Ch341a to flash bios to a laptop? Would you be able to make a video on how to do it if it’s even possible at all?
How do you determine optimal spi frequency?
Is it possible to add a pen drive usb stick as a storage medium?
Hey I would love if u would answer this question, my dad bought me a cheap piano a while ago, now it's OS has failed and I wanted to make a whole new hardware for it from raspberry pi pico, I was wondering if this will be possible, the piano has 54 keynotes which will require multiplexing based input (not analog), two speakers which should be driven by an amplifier and many customizable buttons. Please help me understand if I can implement the pico here
I see that your SD module is v1.1. I have a bunch of the 1.0 modules...Do you know what the difference is? Did they fix the issue of running MISO through the level shifter?
Great explanation, I have been into arduino but wanted to use arm for microcontroller. This is great stuff. Looking for adafruit kind of community build around your channel although I am also from software background but these things are fascinating to work on.
You might find my Arduino vs Pico video interesting. If you are looking for a microcontroller based on Arm, then look at the Pico.
hi can you connect it to a raspberry pi camera module 3?
can i connect it with jumper wires straight to the raspberry pi pico?
On the pinout diagram, there are pins that are labelled equally (eg. 2 and 7, 4 and 9). Why is that and how do I choose the right combination (or does this not matter)?
Yeah, taking a second look that diagram I used isn't the best one. The point is that the pins on the right have a minus sign in front of them. A better pinout is here: datasheets.raspberrypi.com/pico/Pico-R3-A4-Pinout.pdf
You can solder pin headers directly on top of a (full-sized) SD card, because the pitches are just correct. I often solder pin headers on Micro SD-to-SD adapters to make poor man's Micro SD card slots for my dev boards.
Wow, if only I had said that in the video 🤦♂️
@@GaryExplains You could always "PIN" his comment so that it would always be the first comment. (Pun intended)
Yeah did exactly what you told to, but get this error: OSError: no SD card
What happened to the Speed Test G channel, Sir?
I'm new to the Pico. If I don't like soldering, can I plug a (USB stick) to an (OTG USB-A to micro USB adapter), and plug that into the Pico's USB port? Is there a library that will let the Pico to read / write to it?
You can use a breadboard with jumper wires.Thats the best way to try out these schematics without soldering
@@parihar-shashwat No, I was wondering if there is code to write data to a usb flash drive?
hi, maybe an obvious question, but what is the maximum capacity that the pico can support with de sd card?
Theoretically 32GB as it needs to be formatted as FAT32, however it is possible to format cards greater than 32GB as FAT32, but you need to hack it, the default after 32gb is exFAT.
me sd card has 3.3 input which does makes things a bit easier but I don't have many SD cards spare
so we can write to a file, and read it back under the same name, but how do we get a directory of available files?
Micropython has excellent documentation. You need the "os" library.
Why are you using VCC as VBUS instead of 3V3 (out) ?
I explain that in the video.
Because the adapter he is using has a buck converter built in. If you're wiring it up directly, use the 3.3v.
Got a bit of a tan there Gary 😂
Almost as if it was summer in the northern hemisphere! 😎
I have 5 different SD cards and it does not work with 32 MB, 128 MB or 64 MB (MMC).
I get the following error: `OSError: timeout waiting for v1 card`
Although it does work with a 32 GB SD card
I found the problem, it turns out that the timeout in the function init_card_v1() of the library sdcard.py is missing, it is solved by adding this line in that function: `time.sleep_ms(50)`
The result should look like this:
```
def init_card_v1(self):
for i in range(_CMD_TIMEOUT):
time.sleep_ms(50)
self.cmd(55, 0, 0)
if self.cmd(41, 0, 0) == 0:
# SDSC card, uses byte addressing in read/write/erase commands
self.cdv = 512
# print("[SDCard] v1 card")
return
raise OSError("timeout waiting for v1 card")
```
can i add a emmc in the sdcard place
No, eMMC doesn't support SPI. Without dedicated special controller hardware it's rather painful to interface an eMMC.
What kind of speed will this offer? Can i store a movie clip and get a decent frame rate putting it to an ILI9486 TFT screen? 1 frame = w*h*bits per pixel = 340*480*2 (16bits per pixel) = 307,200 bytes per frame. So i need about 15MBps for 50fps 9.2 MBps for 30fps. Or am I just asking to turn my PICO into a tiny little cinder?
In SPI mode you will only get a few K per second, not even close to 1MBps let alone 9 or 15.
@@GaryExplains ouch, is that a limit of the sd card reader/writer? SPI on a display works way faster....
Generally, effective data rate is not really defined in the SPI protocol. You can push the clock as fast as your controller can manage, but you need to keep the clock and data lines the same length (like you would for memory or usb trace pairs or any other high frequency communications lines). Raw, full 16bit frames are out of the question, though.
I suspect most SPI libraries will limit clock frequency to speeds that will work on a breadboard, but if you're designing a board and have it manufactured, you should be able to get close to the sd card's rated speeds - and provided the controller doesn't have weird bottlenecks. Keep in mind that the filesystem functionality also has processing overhead on the controller.
For multimedia applications, DMA is a better bet - in which case you get high bandwidth between devices but are limited to the sram/dram memory size. Old microcomputers used DMA for display graphics and sounds, but the data for each frame was generated by the processor, memory only needs to contain one or two frames.
If you want to read full uncompressed frames trough SPI, and audio, that's not going to work. You need a wider throughput buss or compression, lower color, or all of them together.
Could this be implemented to create a simple MP3 player?
Sure. You might find this link useful learn.adafruit.com/mp3-playback-rp2040/pico-mp3
One thing I find annoying about these SD interfaces is that they do not provide an interrupt when the SD card is inserted so you pretty much have to boot your board with the card inserted, which is annoying if you want to do quick debugging
You can create soft interrupts on pins. Check for mount and try for writing a tmp file.
You can use a while true: try writing
I tried it but got the error "OSError: timeout waiting for v2 card" after creating the sdcard object with
CS = machine.Pin(9, machine.Pin.OUT)
spi = machine.SPI(1,baudrate=1000000,polarity=0,phase=0,bits=8,firstbit=machine.SPI.MSB,sck=machine.Pin(10),mosi=machine.Pin(11),miso=machine.Pin(8))
sd = sdcard.SDCard(spi,CS) # here the error occurs after some seconds
Any ideas what's going wrong?
Did you ever solve this problem? I am having the same one
Are the pin names in software the same as on the board hardware ?
Because on the board, pin 8 is a GND, and pin 9 is SCK not CS.
For the benefit of those of you still watching this in the 1980s,
MOSI = Master Out - Slave In, and
MISO = Master In - Slave Out.
Slave is not a racist word, it's just a word.
What will they think of next ?
the pi foundation needs *milk-giving parent boards* that are fool-proof.
impossible, humans have the ability to destroy anything ...
What I did was grab a SD to mSD adapter, and soldered the wires directly onto the contacts. Popped in a mSD card, Presto
I am sure I showed a photo of that in the video, no?
@@GaryExplains I tend to skip parts of the videos, so I must have missed that. Silly me.
Gary? This is mostly Off-topic, but I'd like your opinion on what, realistically, is keeping ARM from being more commonplace in the desktop space.
I'm pretty sure the abundance of existing software built around x86 is a big part of it, but all the major operating systems in the desktop space will run on ARM now - or have versions which will, in the case of Windows.
But the real big deal, I think, is more to do with hardware. As you go up in skill level, PC users are used to upgrading their storage, their GPU and RAM, and, eventually, their CPUs. Most ARM systems don't support this, and the ones that do are usually purpose-built for the server space. Systems that meet these qualifications and have an ATX-compatible form factor seem to just not exist.
It can't be JUST the software that's keeping the corpse, the decaying husk, the veritable flesh-rotten zombie of a CPU instruction set architecture that is x86 around... can it?
No it isn't the software. Just like with Apple's transition from x86 to Arm, Windows on Arm has a very good x86 emulator. I cover this in my review of the Surface Pro X. The biggest problem is price. I cover that in several videos including ruclips.net/video/fLYEleyXOtg/видео.html , ruclips.net/video/A4dzD9NttBA/видео.html , and ruclips.net/video/LPGaQz-_VdY/видео.html
@@GaryExplains And price of dev kits in particular, it seems. So it is a software issue, but only tangentially. The more exposure devs have to a system which can run what they're trying to develop, the more likely they are to develop for it. And to get that exposure prices would need to go way down - at least on dev systems - for the time being, at least until there is adequate competition in the desktop space to drive costs down through more... capitalistic means.
@@seancondon5572 ARM servers are built in a same manner as x86. PCI-E, DDR.., idk what you are talking about.
You clearly have no appreciation to years of experience that went into x86 progression, and now it is accelerating faster than ever. Consumer segment simply does not keep up with interface generations at this point, one becomes yesterdays news the next day after adoption..
What are you looking to gain from ARM in PC setting anyway?
@@Mr.Leeroy let me introduce you to my old friend... READING COMPREHENSION. Did you see how many times the phrase "desktop space" was used? If so, why are you bringing up servers in this context?
What I would hope to gain from not using the silicon zombie that is x86, is a simpler physical architecture... one which could be made such that it sips power... or such that it can be pushed to a limit well beyond what x86 is capable of. Honestly, I have no idea why you are having such difficulty understanding this.
@@seancondon5572 Because everything you have in desktop segment comes from R&D of enterprise server platforms. If it is not required there, you are not getting it at home, unless someone decides to fund it. Not sure where are you taking this nonsense about superiority of ARM from. It is failing to get enough attention even in server segment and is only considered for very niche use cases at large enough scales of narrow purpose compute, basically complete opposite of what desktop CPU should be.
Have you any EE/SE experience to talk BS about x86? Or you just believe things that marketing departments sell, like Apple's ARM endeavor?
Is there any error handling?
Depends at what level you are looking at, as an example the sdcard.py code raises exceptions in errors case like "no SD card present" etc.
@@GaryExplains yes - great - so you can react to write errors if the sdcard is damaged.
Yes, I am sure that write errors etc raise exceptions.
Is the Speed Test G channel officially dead now?
Where did you get this sdcard module? The github repo has been deleted
Which GitHub repo has been deleted?
7:17 _"MOSI: main In, secondary/subnode In"_ In other documents you might find Master Out, Slave In.....
Reeeeeeeeeee
Will this work with a zero? my zero's reader has died
You can't boot from this card setup.
@@GaryExplains aw damn. Thank you
Something about programming a microcontroller in python just feels horridly wrong.
Always enjoy your videos but was into this video to the point where you describe the SPI pins, where I thought “that is not what I’ve learned MOSI/MISO stand for.” What’s that, you say, you’re not wrong, just not done (explaining)? So, good on you for alluding to the prior words that ‘M’ and ‘S’ indicated and that Main and Secondary are the preferred, evolved terms. As someone in technology, I have observed some absolutely mental shouting matches through all communication channels when the C-level said “we ARE changing our terms to be more inclusive.” Acronyms are a huge pet peeve of mine especially when they can mean multiple things even within the same company, but the fact is they are all-wait for it-arbitrary and often time-specific. By that, I mean that it doesn’t matter WHAT we call something, only that at any given point in time we agree upon common terms to describe the same thing(s) for the purposes of articulating thoughts and ideas and to collaborate/compete across known landscapes. If at a point in time someone points out “hey, there is a better way to say X,” then that is just some of the change we are all promised to see throughout our careers and I am all for it as long as the messages of the change are widely disseminated and regarded, so that we can continue to communicate, collaborate, and compete. That some want to hold on to old ideas, words, acronyms, and backronyms, well those are issues for them to sort out while the rest of us continue forward.
I don't decide these things, I am just trying to help people understand SPI and how to use an SD card with the Pico.
I see that you have completely misunderstood the problem and in fact you are part of the problem. You see if I called them master/slave then I would get loads of comments about how the preferred names are now different. If I try to be as open as possible and at least mention what is going on I get people like you commenting. In other words, me, a RUclipsr, who just wants to make a video about SPI I have to waste my time reading and replying to comments like yours. Dude, I am here for the tech, I don't decide what is left or right or fashionable or acceptable or whatever. I am not here to make a statement of support for one view or another. I am here for the tech, I has hoping that you were here for the tech as well. But clearly you aren't.
🤦♂️
@@GaryExplains You say 'preferred' but who is doing the preferring here? You have in fact made an implicit statement of support for the 'preferred' names, not the original names.
I don't think I made a statement about which is preferred, please re-read my reply, I said the comments would say that the preferred naming is, not me. I tried to be as open as I could in the video. Trying to keep everyone happy. But there you go, I spend all that time making a video, and people are fixating on 10 seconds of video. Weird.
M=Master and S=Slave; otherwise, very good job!
Why are people so weirdly attached to that nomenclature?
@@jackroutledge352 slave means owning another person, despicable
@@jackroutledge352 See an English dictionary for "master" and "slave." This relationship exactly describes the function of the SPI protocol.
You might find the top part of this document from the Arduino team interesting docs.arduino.cc/learn/communication/spi
@@GaryExplains It is rarely used, but some peripherals can be temporary masters for peripheral to peripheral transactions.
No more "Master/Slave" what a world. LOL.
All technical literature for SPI was MOSI and MISO in the PAST. But... after research a lot of sites about this issue i see there is a movement in favor of this changes. The Open Source Hardware Association resolve to discontinue the terms for reasons of racism. In the resolution document they use PICO/POCI in contrast with CIPO/COPI as Gary Explains above. I apologize for my previous comment because i was not been well informed. This is why I edited it. In fact BLM, in 2020, ask the community to renew the scrutiny of diversity and equity in tech including its vocabulary. But this like many others things in the similar matters related to political correctness is making an atrocious messing with terminology and confusing a lot of people. I don't think that erasing terms in our history is the solution for the future generations. What is worst is a negation of terrible acts that need to be in the collective memory. But maybe i am to old.
You might find the top part of this document from the Arduino team interesting docs.arduino.cc/learn/communication/spi While Arduino has opted for different terms, the idea is the same. I guess you think the Arduino team is talking about things outside their field of expertise?
@@GaryExplains Sure is not a question of expertise. It seems to be a question of political correctness and absurdity. See my edited post below. Thanks
"No more "Bloodletting to cure gout"? What a world! LOL." - Marcus K probably
MOSI / MISO forever. Damn the wokeness.
The fact that comments appear about a tiny part of the video shows how controversial the master/slave main/secondary issue is. So rather than go with the new way which has loads of woke connotations, the best thing is to stick to the old fashioned way. Just because some shouty minority is saying something is the new and right way to say/do something doesn't make it the right way to say/do something. If Gary had stuck with master/slave no one would have said anything, no one would've noticed, and no one would've commented. Ahhhhhhh, I just worked it out, Gary deliberately said it to gain comments to help promote the video in RUclips's AI. 🤣
It isn't just me. You might find the top part of this document from the Arduino team interesting docs.arduino.cc/learn/communication/spi
@@GaryExplains That's just the Arduino team listening to the shouty minority. Its also the old appealing to authority argument fail. To properly have a term changed, everyone needs to accept it as a positive way going forward and it would happen naturally without the new term being pushed onto others. That many, if not the majority, do not accept it is what makes it controversial and therefore not a defacto term.
@John Q. Bebtelovimab DOSI??? Lol.
The _shouty minority_ are just people who think making direct references to slavery in everyday (if you're a techy person anyway) language? Well good for them, sucks to be you I guess. Everything is woke and there's nothing you can do about it 😘
Serious question, who cares?
10 minutes wasted because we can;t be clear with MASTER OUT -SLAVE IN and vise versa. What a waiste of time
I don't decide what labels the devices makers put in their devices. I have several SPI devices that don't use MOSI etc but DIN or whatever. I thought a segment in the video that clarified that would be useful not a waste of time.
I can benefit a lot from this video, and I don't think it's a waste of time.
@@GaryExplains Greg wasn't talking about that, he was referring to your use of 'Main' and 'Secondary' substituting for 'Master' and 'Slave'.
Richard, that is unclear as Greg says, "10 minutes wasted". I didn't talk about master/main for 10 minutes, barely 10 seconds. The reasons the other labels variants exist is not because of changing master to main. Some chips just use different labels like DIN or DOUT etc.
@@GaryExplains I think he's being hyperbolic, but only he could say.