SD card status check bug #6081

FrankBoesing · 2021-12-28T17:54:02Z

Board

WT32-SC01

Device Description

ESP-Wrover-Kit

Hardware Configuration

SD Slot

Version

latest master

IDE Name

Platformio

Operating System

Windows 10

Flash frequency

80MHz

PSRAM enabled

no

Upload speed

115200

Description

Enabled log shows many many SD- CRC Failures, reading is not possible wit 2.0.2

After revert the mentioned change, SD starts working again.

Sketch

-----
Any that uses SD.h

Debug Message

-----

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

I confirm I have checked existing issues, online documentation and Troubleshooting guide.

The text was updated successfully, but these errors were encountered:

AppsByDavideV · 2021-12-29T07:43:44Z

I can confirm there is an issue with SD and core 2.02:
Core 2.01 reading text file from sd, to be sent to client took 15 ms
Core 2.02 , same task, took 6000+ ms
Needed to go back to 2.01

SD works very slow in 2.02

FrankBoesing · 2021-12-29T08:07:30Z

@AppsByDavideV: It is OK to just remove these lines: f32c0da

AppsByDavideV · 2021-12-29T09:24:58Z

@AppsByDavideV: It is OK to just remove these lines: f32c0da

Yes, it works fine now with core 2.02, thanks

schreibfaul1 · 2021-12-29T10:29:12Z

Likewise, if the lines in f32c0da are removed, SD works in V2.0.2, tested with PlatformIO, thanks to @FrankBoesing

VojtechBartoska · 2022-01-04T08:38:02Z

Hello @FrankBoesing, we will take a look on this issue. Thanks for reporting.

VojtechBartoska · 2022-01-04T10:40:03Z

Related to #6078. These 2 issues can be validate and tested together, @P-R-O-C-H-Y.

edouardreg · 2022-01-06T13:15:43Z

Hello, the same here : SD read and write very slow since 2.0.2. Speed was around 400-500 ko/s before, now 4 ko/s after 2.0.2 upgrade. Thanks

tobozo · 2022-01-06T13:42:59Z

getting random [sd_diskio.cpp:186] sdCommand(): token error [23] 0x4 and [sd_diskio.cpp:174] sdCommand(): no token received under heavy load too.

During a screen capture test, 6 files out of 256 failed to write to SD with an average size of 40kb, this is after applying @FrankBoesing's fix.

P-R-O-C-H-Y · 2022-01-10T10:20:02Z

Hello, can you try editing sd_diskio.cpp as PR #6103 and test it?
It should fix the bug.
Thanks

tobozo · 2022-01-10T10:51:45Z

@P-R-O-C-H-Y confirmed unbroken SD after applying this PR

[edit] as pointed out by @Vigeant unbroken state isn't persistent, goes back to broken after a power cycle :-(

edouardreg · 2022-01-10T15:26:52Z

Hello, Yes it is OK after romvind lines in d_diskio.cpp Thanks

…

----- Mail original ----- De: "P-R-O-C-H-Y" ***@***.***> À: "espressif/arduino-esp32" ***@***.***> Cc: "edouardreg" ***@***.***>, "Comment" ***@***.***> Envoyé: Lundi 10 Janvier 2022 11:20:14 Objet: Re: [espressif/arduino-esp32] SD card status check bug (Issue #6081) Hello, can you try editing sd_diskio.cpp as PR #6103 and test it? It should fix the bug. Thanks — Reply to this email directly, view it on GitHub , or unsubscribe . Triage notifications on the go with GitHub Mobile for iOS or Android . You are receiving this because you commented. Message ID: <espressif/arduino-esp32/issues/6081/1008725333 @ github . com>

Vigeant · 2022-01-14T03:47:43Z

Well, after upgrading to 2.02 and applying the fix from PR #6103 as suggested by @P-R-O-C-H-Y my sketch worked for a while and I could read the card again. However, when I resumed work today, it would fail again in the sd_diskio.cpp in the sdWait()<-sdSelectCard() trace. I tried reloading and resetting many times and it would always fail to mount. I reverted my esp32 library back to 1.06 as I had to do before to fix my sd card mounting issues and my card mounted fine. Once the card mounted, I could re-update to 2.02 and apply the PR #6103 fix and my card would keep working. Not sure what happens in the card but it seems like something happens to the card that makes the sdWait() fail in 2.02 that is simply ignored or fixed in 1.06. When running a diff between the 1.06 and 2.02 sd_diskio.cpp you see that the sdSelectCard() is slightly different. In 1.06 it logs that sdWait() failed and keeps going and it still mounts successfully (and fixes the card somehow). In 2.02, if this sdWait fails, it deasserts the ss and errors out stopping the initialization of the card. All that to say that there seem to be more to it than just the PR #6103. There seem to be a fail condition that 1.06 handles better than 2.02 during initialization. Any help from a dev here would be appreciated.

P-R-O-C-H-Y · 2022-01-17T15:19:51Z

Status check bug fix is merged now so this issue gets automatically closed.

Working on reported issues with mounting sd cards :)
Thanks @Vigeant for report.

P-R-O-C-H-Y · 2022-01-18T13:45:22Z

@Vigeant @tobozo Can you try removing(commenting) these 2 lines from sd_diskio.cpp in function sdSelectCard?
This can be the issue you are getting. I cannot reproduce the issue so I will be glad if you or someone can test that.

bool sdSelectCard(uint8_t pdrv)
{
    ardu_sdcard_t * card = s_cards[pdrv];
    digitalWrite(card->ssPin, LOW);
    bool s = sdWait(pdrv, 300);
    if (!s) {
        log_e("Select Failed");
        //digitalWrite(card->ssPin, HIGH);     comment these 2
        //return false;             
    }
    return true;
}

These 2 lines are not in 1.0.6.
Please let me know :) Thanks

tobozo · 2022-01-18T14:15:02Z

@P-R-O-C-H-Y this seems to solve the SD mounting issue on ESP32-Wroom and ESP32-S2 and the fix persists across power cycles \o/

P-R-O-C-H-Y · 2022-01-18T14:21:54Z

@P-R-O-C-H-Y this seems to solve the SD mounting issue on ESP32-Wroom and ESP32-S2 and the fix persists across power cycles \o/

Thanks @tobozo for testing. Will look why it was added and if its necessary to have these lines.

Vigeant · 2022-01-18T14:57:25Z

Hi @P-R-O-C-H-Y , This is what I am running with since my post and haven't had problems mounting. This seems to be the issue.

Vigeant · 2022-01-20T15:28:06Z

not sure. Here is the trace on the first reboot that fixes the card:

10:26:38.516 -> [   434][W][sd_diskio.cpp:104] sdWait(): Wait Failed
10:26:38.516 -> [   434][E][sd_diskio.cpp:126] sdSelectCard(): Select Failed
10:26:38.516 -> [   434][W][sd_diskio.cpp:180] sdCommand(): crc error
10:26:38.610 -> [   537][W][sd_diskio.cpp:180] sdCommand(): crc error
10:26:38.845 -> SD Card Type: SDHC
10:26:38.892 -> SD Card Size: 30436MB

Vigeant · 2022-01-20T15:29:52Z

Do you want me to try and configure my CS pin with a pullup before I start my spi bus and sd card? well the begin configures it as output itself. want me to change this to OUTPUT_OPEN_DRAIN?

P-R-O-C-H-Y · 2022-01-20T15:36:06Z

Try that on MOSI pin according to this: sdspi-espidf

Vigeant · 2022-01-20T15:52:25Z

hmm Guess I would need to set MOSI to OUTPUT_OPEN_DRAIN and add a physical 10k pullup.
Mod needs to be on line 230 of espressif/arduino-esp32/blob/master/cores/esp32/esp32-hal-spi.c.
Cannot try this ATM. Does your setup have an external 10k pullup? There is no such thing as OUTPUT_PULLUP...

P-R-O-C-H-Y · 2022-01-20T16:00:12Z

I have this SD SPI module image
It seems that the module have 10k resistors on pins. (there are 4 10K resistors)

Vigeant · 2022-01-20T16:18:25Z

ok I am using https://www.sparkfun.com/products/13743
so I do not seem to have a 10k on MOSI.
https://cdn.sparkfun.com/datasheets/BreakoutBoards/Shifting_microSD_v10.pdf

Vigeant · 2022-01-20T16:29:50Z

Added 10k pullup on my SD card and no luck. It still wont survive a power cycle.

P-R-O-C-H-Y · 2022-01-21T09:38:56Z

Do you have 5V power to the microSD board? Seems that 10k pull-up resistor does not help..
I'm actually getting out of any ideas why its not working for you. It has to be HW related when I don't have any issue on any ESP boards..

tobozo · 2022-01-21T11:47:27Z

@P-R-O-C-H-Y removing the timeout in sdWait created an endless loop, it waits forever.

Tried SD.end / SD.begin in a loop with various delays with no effect.

It feels like something (SPI driver?) is setting up the pins in a way that persists across reboots.

I'm out of ideas.

P-R-O-C-H-Y · 2022-01-21T11:52:32Z

Yeah it seems the problem is with SPI driver, but more weird is that I can't reproduce any issue on official ESPs Devkits boards (tried on ESP32 and ESP32S2).
It has to be HW related. Even more weird is that ignoring the sdWait() failure makes the SD card to fully work right?

AppsByDavideV · 2022-01-21T12:20:10Z

Even CS pin should have a 10K pull-up tied to 3.3V

P-R-O-C-H-Y · 2022-01-21T12:39:16Z

One more thing to try @tobozo, @Vigeant.
Can you try same test with 2 different SPI speeds? Read somewhere that some cards don't like this freq for init.
Change in file SPI.cpp SPICLASS _freq

SPIClass::SPIClass(uint8_t spi_bus)
    :_spi_num(spi_bus)
    ,_spi(NULL)
    ,_use_hw_ss(false)
    ,_sck(-1)
    ,_miso(-1)
    ,_mosi(-1)
    ,_ss(-1)
    ,_div(0)
    ,_freq(1000000) <----- can you try higher speed 16000000 (16Mhz) and lower speed 300000 (300kHz)
    ,_inTransaction(false)
{}

tobozo · 2022-01-21T12:43:20Z

I can't reproduce any issue on official ESPs Devkits boards

@P-R-O-C-H-Y maybe enable USBCDC at boot and don't use the hardware serial?

[edit] my board settings

However I got some freezes when using USBSerial.setDebugOutput(true), maybe it's unrelated, maybe it's part of the problem, but I recommend to not enable it and use occasional USBSerial.printf statements instead.

tobozo · 2022-01-21T12:54:43Z

@P-R-O-C-H-Y commenting out does not help it just fails on the next transaction.

P-R-O-C-H-Y · 2022-01-21T12:55:35Z

@P-R-O-C-H-Y commenting out does not help it just fails on the next transaction.

Yes failed for me too.
Can you try changing the SPI speed?

tobozo · 2022-01-21T13:21:03Z

tried a few speeds from 16, 27, 40MHz, even 400KHz, using FSPI, HSPI, constructor, pointer, all fail with sdWait, all succeed when I comment out the return false in sdSelectCard.

So if the problem on ESP32-S2 is SPI related, it's probably wrapped between some #if CONFIG_IDF_TARGET_ESP32S2 macros (maybe even with an extra || CONFIG_IDF_TARGET_ESP32) right?

P-R-O-C-H-Y · 2022-01-21T13:26:32Z

Thanks for testing that out.
My esp32s2 is working :) I think its not a driver think. More will be a SD card stuff.
Gonna look if there is something "missing or wrong" with macros in SPI.

Another test for you :)

Can you do this change in DSTATUS ff_sd_initialize(uint8_t pdrv) in sd_diskio.cpp.
Changed that it will try 10 times to switch card to idle state before it will fail.

    uint8_t go_idle_count = 0;

    while (sdTransaction(pdrv, GO_IDLE_STATE, 0, NULL) != 1) {
        log_w("GO_IDLE_STATE failed");
        go_idle_count++;
        if(go_idle_count == 10)
        {
            goto unknown_card;
        }
    }

tobozo · 2022-01-21T13:51:28Z

this fails too, I'm already hammering the SD card in a 10x loop so there was 100 failed attempts instead of 10 :-)

Returning true on the first error only confirms the sdWait only fails once:

bool sdSelectCard(uint8_t pdrv)
{
    ardu_sdcard_t * card = s_cards[pdrv];
    digitalWrite(card->ssPin, LOW);
    bool s = sdWait(pdrv, 300);
    static int failures = 0;
    if (!s) {
        if( failures++ == 0 ) {
            log_w("SD Card initial selection failed, mocking success");
            return true;
        }
        log_e("Select Failed");
        digitalWrite(card->ssPin, HIGH);
        return false;
    }
    return true;
}

P-R-O-C-H-Y · 2022-01-21T13:55:18Z

OK so the SDwaits fails only once, when the Go idle state is called. Did I get that right?
After that the SDwait is working fine ?
Can you print the response in the SDWait() from the SPItransfer?

tobozo · 2022-01-21T14:14:31Z

Can you print the response in the SDWait() from the SPItransfer?

it only prints resp=0x00 on failure, which is to be expected (sdWait returns (resp > 0x00))

Vigeant · 2022-01-21T14:32:12Z

I confirm sdWait() only fails once. I put in @tobozo's snipet in mine:

bool sdSelectCard(uint8_t pdrv)
{
    ardu_sdcard_t * card = s_cards[pdrv];
    digitalWrite(card->ssPin, LOW);
    bool s = sdWait(pdrv, 300);
    static unsigned int failcount = 0;
    if (!s) {
		if (failcount == 0){
			log_e("Select Failed on first attempt!!!");
			//digitalWrite(card->ssPin, HIGH);
			//return false;
		} else {
			log_e("Select Failed");
			digitalWrite(card->ssPin, HIGH);
			return false;
		}
		failcount ++;
    }
    return true;
}

P-R-O-C-H-Y · 2022-01-24T14:00:42Z

Hi @tobozo, @Vigeant
According the facts we found out, sdWait fails only one before the GO_IDLE_STATE command.
Made new commit to the PR - #6162 where I added to ignore the sdWait in the init phase before that cmd.

For me, it works same as before :D so if you can't test the changes, I will be thankful :)

tobozo · 2022-02-03T13:05:41Z

@P-R-O-C-H-Y this implementation works for me but ignores the sdWait every time although we know it's only blocking on first access.

Ignoring this error every time could make the underlying problem more difficult to solve.

One of the effects of this is that if a write timeout occurs after mounting the drive, it'll be silently ignored and eventually result in a corrupted file without even producing a warning.

ifrew · 2022-06-05T18:06:51Z

I have this same issue after upgrading to the latest esp32 ardunio core 2.0.3 and using the latest @tobozo m5stack-sd-menu code. I am running visual studio with vmicro on a m5stack gray module with no PSRAM. I have a thread going with @tobozo on this issue, see tobozo/M5Stack-SD-Updater#171 . I applied #6103 and commented out the two lines as suggested above by @P-R-O-C-H-Y but no luck. What I did find though which may help folks find the issue and be able to repro is that I have 3 SPI devices attached in my design. 1 is the M5stack display, 1 is the M5Stack TFcard and the other is a LORA communication module. All are on the same bus with different CS pins. If I remove the m5stack module from the lora board everything works perfectly. If I reattach it I get the errors below. after loading @tobozo M5Stack-sd-menu code from my main app. So I though I'd try stopping all 3 SPI busses before the software reset. This made no difference which surprised me. I'm not a SPI expert, but it would seem to be an SPI issue and some control Pin not being reset to the correct state. With this info, does this trigger any thoughts from folks on these errors?

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13732
ho 0 tail 12 room 4
load:0x40080400,len:3608
entry 0x400805f0
[ 1][D][Button.cpp:42] Button(): Button on pin 39, invert=1, debounce=10ms
[ 1][D][Button.cpp:42] Button(): Button on pin 38, invert=1, debounce=10ms
[ 4][D][Button.cpp:42] Button(): Button on �� 37, invert=1, debounce=10ms
[ 12][D][esp32-hal-cpu.c:214] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
ESP32-Chimera-Core initializing [Board=M5Stack_Core_ESP32] [Variant=m5stack_core_esp32]
[ 87][D][ESP32-Chimera-Core.cpp:93] begin(): Enabling LCD
[ 101][W][LGFX_AutoDetect_ESP32.hpp:415] _read_panel_id(): [LovyanGFX] [Autodetect] read cmd:04 = 000000e3
[ 102][W][LGFX_AutoDetect_ESP32.hpp:1237] autodetect(): [LovyanGFX] [Autodetect] M5Stack
[ 258][D][ESP32-Chimera-Core.cpp:246] sd_begin(): SD will use VSPI
[ 259][D][ESP32-Chimera-Core.cpp:258] sd_begin(): TFCARD_SPI_HOST=2, SPI_HOST=0, HSPI_HOST=1, VSPI_HOST=2 from core #1
[ 264][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x400f2810 arg=0x3ffbdda8
[ 283][D][ESP32-Chimera-Core.cpp:273] sd_begin(): SD Card Mount Success on pins scl/miso/mosi/cs 18/19/23/4 from core #1
ESP32-Chimera-Core started
ESP-IDF version is: v4.4.1-1-gb8050b365e
[ 304][V][M5StackUpdaterUI.h:512] SetupSDMenuConfig(): Attached buttonpressA
[ 304][V][M5StackUpdaterUI.h:513] SetupSDMenuConfig(): Attached buttonpressB
[ 310][V][M5StackUpdaterUI.h:514] SetupSDMenuConfig(): Attached buttonpressC
[ 317][V][M5StackUpdaterUI.h:515] SetupSDMenuConfig(): Attached buttons poller
[ 324][V][M5StackUpdaterUI.h:516] SetupSDMenuConfig(): Attached onProgress
[ 331][V][M5StackUpdaterUI.h:517] SetupSDMenuConfig(): Attached onMessage
[ 338][V][M5StackUpdaterUI.h:518] SetupSDMenuConfig(): Attached onError
[ 344][V][M5StackUpdaterUI.h:519] SetupSDMenuConfig(): Attached onBefore
[ 351][V][M5StackUpdaterUI.h:520] SetupSDMenuConfig(): Attached onAfter
[ 357][V][M5StackUpdaterUI.h:521] SetupSDMenuConfig(): Attached onSplashPage
[ 364][V][M5StackUpdaterUI.h:522] SetupSDMenuConfig(): Attached onButtonDraw
[ 371][V][M5StackUpdaterUI.h:526] SetupSDMenuConfig(): Attached onWaitForAction (button)
[ 379][D][M5StackUpdater.h:211] _fsBegin(): Checking for SD Support (pin #4)
[ 386][D][M5StackUpdater.h:217] _fsBegin(): SD Successfully mounted (pin #4)
[ 393][I][esp32-hal-i2c-slave.c:234] i2cSlaveInit(): Initialising I2C Slave: sda=22 scl=22 freq=100000, addr=0x15
[ 403][D][esp32-hal-i2c-slave.c:498] i2c_slave_set_frequency(): Fifo thresholds: rx_fifo_full = 28, tx_fifo_empty = 4
[ 414][E][Wire.cpp:260] getClock(): Bus is in Slave Mode
[ 419][E][Wire.cpp:308] beginTransmission(): Bus is in Slave Mode
[ 425][E][Wire.cpp:331] endTransmission(): Bus is in Slave Mode
[ 431][V][I2CUtil.cpp:73] writeCommand(): send to 0x08 [0x00] result:NG
[ 437][E][Wire.cpp:260] getClock(): Bus is in Slave Mode
Welcome to the M5Stack SD Menu Loader!
M5Stack SD Updater initializing...
M5StackSam loaded with 8 labels per page, max 96 items
Has PSRam: false
[ 463][I][menu.h:148] heapState():
RAM SIZE: 333.77 KB
FREE RAM: 263.60 KB
MAX ALLOC: 107.99 KB
[ 501][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 601][W][sd_diskio.cpp:180] sdCommand(): crc error
[ 701][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 801][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x11
[ 802][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 901][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1001][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1101][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x0d
[ 1101][E][sd_diskio.cpp:621] ff_sd_status(): Check status failed
[ 1103][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1208][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1308][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1407][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x00
[ 1407][W][sd_diskio.cpp:516] ff_sd_initialize(): GO_IDLE_STATE failed
[ 1408][E][vfs_api.cpp:104] open(): /sd/menu.bin does not exist, no permits for creation
[ 1416][W][menu.h:658] checkMenuTimeStamp(): Menu.bin has an obsolete time set (2022-06-05 00:27:10), will use this sketch build date to set the clock

[Hobo style] Clock set to an obsolete source (this sketch build): June 05 2022 00:27:10 (Sunday)
[ 1444][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1544][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1644][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1743][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x00
[ 1743][W][sd_diskio.cpp:516] ff_sd_initialize(): GO_IDLE_STATE failed
[ 1745][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1851][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 1951][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 2050][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x00
[ 2050][W][sd_diskio.cpp:516] ff_sd_initialize(): GO_IDLE_STATE failed
[ 2052][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 2158][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 2258][W][sd_diskio.cpp:174] sdCommand(): no token received
[ 2357][E][sd_diskio.cpp:199] sdCommand(): Card Failed! cmd: 0x00
[ 2357][W][sd_diskio.cpp:516] ff_sd_initialize(): GO_IDLE_STATE failed

ifrew · 2022-06-07T01:56:45Z

Looks like my issue was due to the LGFX graphics library doing auto detect of boards on the SPI bus and some of the boards they were looking for used the same CS pins as my SPI device that started giving issues. Details on this thread for those interested.... tobozo/M5Stack-SD-Updater#171

FrankBoesing added the Status: Awaiting triage Issue is waiting for triage label Dec 28, 2021

schreibfaul1 mentioned this issue Dec 29, 2021

[ 641][W][sd_diskio.cpp:174] sdCommand(): no token received schreibfaul1/ESP32-audioI2S#245

Closed

VojtechBartoska assigned P-R-O-C-H-Y Jan 4, 2022

VojtechBartoska added the Type: Bug 🐛 All bugs label Jan 4, 2022

VojtechBartoska added this to the 2.0.3 milestone Jan 4, 2022

VojtechBartoska removed the Status: Awaiting triage Issue is waiting for triage label Jan 4, 2022

VojtechBartoska changed the title ~~With https://github.com/espressif/arduino-esp32/pull/5988 SD is not usable~~ SD card status check bug Jan 4, 2022

VojtechBartoska added this to In Development in (Archived) Arduino Core ESP32 RoadMap Jan 5, 2022

P-R-O-C-H-Y mentioned this issue Jan 6, 2022

BUGFIX - Sd check status #6103

Merged

P-R-O-C-H-Y linked a pull request Jan 6, 2022 that will close this issue

BUGFIX - Sd check status #6103

Merged

VojtechBartoska mentioned this issue Jan 7, 2022

Extend SD card select timeout #6107

Closed

1 task

me-no-dev closed this as completed in #6103 Jan 17, 2022

tobozo mentioned this issue Jan 19, 2022

Files disappear from flash drive chegewara/EspTinyUSB#68

Open

P-R-O-C-H-Y mentioned this issue Jan 24, 2022

SD Mount Fail #6143

Closed

1 task

tobozo mentioned this issue Feb 3, 2022

SD Card Mount Failed tobozo/WUD-Ducky#5

Closed

ChristopheLaurent mentioned this issue Feb 18, 2022

SD.h - Application is not notified that file::flush() failed #6303

Closed

1 task

TheVisionariesInk mentioned this issue Mar 1, 2022

ESP32-CAM in boot loop (flash read err, 1000) #6164

Closed

1 task

zhekch mentioned this issue Sep 22, 2023

SD card mount failed #8663

Closed

1 task

SD card status check bug #6081

SD card status check bug #6081

Comments

FrankBoesing commented Dec 28, 2021

Board

Device Description

Hardware Configuration

Version

IDE Name

Operating System

Flash frequency

PSRAM enabled

Upload speed

Description

Sketch

Debug Message

Other Steps to Reproduce

I have checked existing issues, online documentation and the Troubleshooting Guide

AppsByDavideV commented Dec 29, 2021 • edited Loading

FrankBoesing commented Dec 29, 2021

AppsByDavideV commented Dec 29, 2021

schreibfaul1 commented Dec 29, 2021

VojtechBartoska commented Jan 4, 2022

VojtechBartoska commented Jan 4, 2022 • edited Loading

edouardreg commented Jan 6, 2022

tobozo commented Jan 6, 2022

P-R-O-C-H-Y commented Jan 10, 2022

tobozo commented Jan 10, 2022 • edited Loading

edouardreg commented Jan 10, 2022 via email

Vigeant commented Jan 14, 2022

P-R-O-C-H-Y commented Jan 17, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 18, 2022 • edited Loading

tobozo commented Jan 18, 2022

P-R-O-C-H-Y commented Jan 18, 2022

Vigeant commented Jan 18, 2022

Vigeant commented Jan 20, 2022

Vigeant commented Jan 20, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 20, 2022

Vigeant commented Jan 20, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 20, 2022 • edited Loading

Vigeant commented Jan 20, 2022 • edited Loading

Vigeant commented Jan 20, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 21, 2022 • edited Loading

tobozo commented Jan 21, 2022

P-R-O-C-H-Y commented Jan 21, 2022

AppsByDavideV commented Jan 21, 2022

P-R-O-C-H-Y commented Jan 21, 2022

tobozo commented Jan 21, 2022 • edited Loading

tobozo commented Jan 21, 2022

P-R-O-C-H-Y commented Jan 21, 2022

tobozo commented Jan 21, 2022

P-R-O-C-H-Y commented Jan 21, 2022 • edited Loading

tobozo commented Jan 21, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 21, 2022 • edited Loading

tobozo commented Jan 21, 2022

Vigeant commented Jan 21, 2022 • edited Loading

P-R-O-C-H-Y commented Jan 24, 2022 • edited Loading

tobozo commented Feb 3, 2022

ifrew commented Jun 5, 2022 • edited Loading

ifrew commented Jun 7, 2022 • edited Loading

AppsByDavideV commented Dec 29, 2021 •

edited

Loading

VojtechBartoska commented Jan 4, 2022 •

edited

Loading

tobozo commented Jan 10, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 17, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 18, 2022 •

edited

Loading

Vigeant commented Jan 20, 2022 •

edited

Loading

Vigeant commented Jan 20, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 20, 2022 •

edited

Loading

Vigeant commented Jan 20, 2022 •

edited

Loading

Vigeant commented Jan 20, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 21, 2022 •

edited

Loading

tobozo commented Jan 21, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 21, 2022 •

edited

Loading

tobozo commented Jan 21, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 21, 2022 •

edited

Loading

Vigeant commented Jan 21, 2022 •

edited

Loading

P-R-O-C-H-Y commented Jan 24, 2022 •

edited

Loading

ifrew commented Jun 5, 2022 •

edited

Loading

ifrew commented Jun 7, 2022 •

edited

Loading