-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Maple ESP32 SD/MMC Tests failed #259
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.
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
Comments
I have checked the schematics and the board has no pull-up resistors on IOs 2, 4, 12, 13 which are connected to SD card pins. All these IOs need to be pulled up for reliable operation (even though pulling up IO2 can affect entry into download mode, and pulling up IO12 will set the internal VDD_SDIO regulator of the chip to 1.8V). (you may want to read https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card#hardware which contains some troubleshooting instructions). |
Do i need 10k pull-up or 1k pull-up? Here stands 10k https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card#hardware |
Were you able to get this working @Staubgeborener ? I am facing the same issues. |
Well, no. Not really. I integrated Arduino as a component in the esp-idf, so i could use the SPI.h and SD.h librarys (oherwise the SPI driver is currently not working). I can use my SD Card now (for example with the sd card example in the arduino IDE), but with the limitation that only D0 works for the data transfer. That's really bad for the data transfer rate. It's a compromise. But a sick one. I'm also interested how this example can work with all data pins (D0, D1, D2, D3). Maybe the following threads in the esp32.com forum can help: I will try this in the next days. If it's working on your side, please write me @melvinpmathew! |
@LordJakson |
@williamesp2015 @Staubgeborener I am using ESP32 Wroom device and was able to get the SD test work fine on SPI. It's the SD_MMC test which is not working correctly for me. The above question was related to SD_MMC. I am still getting the error (563) sdmmc_cmd: sdmmc_card_init: send_scr returned 0x109. So sure that its some electrical issue, so tried pullup resistors(10k,1k) on the suggested pins and still no progress. Only change I notice is that the error changes from 0x107 and 0x109. Any more suggestions anyone? |
I'm trying to get it to work as well, After a few tests with different resistors i get the example it working but its not very stable. It only works 40% of the time. Sometimes only parts are working and the other commands throw 107/109. Looks good:
Looks not that good:
|
Thanks. But still no success here, even with 15k pull ups. No 4-bit, even no 1-bit. Just in case, could you post a picture of your circuit @thezenox ? |
Looking at the schematic myself, maybe @williamesp2015 has the best workaround (SPI+SD) |
I am new to the SDMMC interface. |
The solution provided by wiliameps2015 works for me with Analoglamb Maple 32 board using Sandisk 512mb microSD card (that is many years old) and Sandisk 16gb Ultra microSD card that is brand new (late 2017). SPI.begin(14,2,15,13);//SCK,MISO,MOSI,ss // the rest of the setup code goes here |
@PilnyTomas This should be candidate for FAQ section but it's quite old and a bit HW specific. What do you think @P-R-O-C-H-Y? Is this something what's still good to explain? |
It is a 3rd party HW design issue, and the board is no longer available, so I don't think this should go into our documentation. |
I got recently the Maple ESP32 board from AnalogLamb.
http://www.analoglamb.com/product/maple-esp32/
It use the ESP-WROOM32 module, has an micro SD slot and a plug for a Battery.
So far as I read it the SD is connected to the Pins 2/4/12-15 Like described in the SDMMC_Test.
https://hackaday.io/project/19362-maple-esp32-esp32-wifi-bt-board-with-micro-sd
https://cdn.hackaday.io/files/19362828383808/Schematic__Maple%20ESP32%20R1.pdf
If I run the SDMMC_Test I got this response:
Is this some bug in the SD/MMC implementation or is there something other wrong
The text was updated successfully, but these errors were encountered: