Page 2 of 2

Re: Which pins to use for SD card acces? (SD/SPI vs HSPI/JTAG/SD vs VSPI/SPI-Mode)

Posted: Thu Jan 05, 2017 2:39 pm
by novalight
Since the schematics of devKitJ V2 have been released we were about to take this as a reference. These schematics rise two questions for me: (find schematic screenshots attached)
- R_IO13 seams to be fitted with a pullup (R156) and a pulldown (R50) at the same time that does not make any sense for me
- R_IO12 pullup (R157) is NC, is this related to the Flash Voltage issue? How does this affect SD-functionality, could we also use the ESP32 internal pullup here?

What are the experiences with devKitJ V2 so far? (Especially regarding SD and JTAG)

EDIT: Added Schematic screenshots:
jtag.PNG
jtag.PNG (70.41 KiB) Viewed 7367 times
sd.PNG
sd.PNG (106.83 KiB) Viewed 7367 times

Re: Which pins to use for SD card acces? (SD/SPI vs HSPI/JTAG/SD vs VSPI/SPI-Mode)

Posted: Mon Jan 09, 2017 9:37 am
by rudi ;-)
happy new year!

example: https://github.com/espressif/esp-idf/tr ... d#hardware
(This example doesn't utilize card detect (CD) and write protect (WP) signals from SD card slot.)

best wishes
rudi ;-)

Re: Which pins to use for SD card acces? (SD/SPI vs HSPI/JTAG/SD vs VSPI/SPI-Mode)

Posted: Mon Jan 09, 2017 4:48 pm
by rudi ;-)
a Note if you use wRover Kit for testing this example
( tested with 16 GB SDHC ( primary partion 128 MB for the first test )

best wishes
rudi ;-)

Re: Which pins to use for SD card acces? (SD/SPI vs HSPI/JTAG/SD vs VSPI/SPI-Mode)

Posted: Mon Jan 09, 2017 5:49 pm
by novalight
Great to hear its working for you Rudi!

Did you do anything about IO13 and IO12?
If you have not modified anything could you confirm that IO12 is floating (in terms of no pullup) or did enable software pullups here?
For IO13 could you confirm it's beeing pulled between GND and 3V3?

Also one note on the side: If we enable internal pullups/down in our software and a random Reset/Brownout/Watchdog-Reset etc. occurs: can this lead to dangerous behavior (e.g. booting in download mode, locking up because of wrong VDD_SDIO)? How could one handle this?