I agree that it looks like an error and should be removed, this message is misleading and not helpful at all.

I checked the clock pin with a probe and it never outputs that pulse with length set to 1, but with length set to 2 it works.
Any ideas?

I'm trying to run libswd-esp32 on esp32-s3 and it freezes at the first SPI transaction, which has length of 1 bit.

Here is a code I used to reproduce it separately, it works on ESP32, but freezes on ESP32-S3.
It only freezes when the transaction length is set to 1.



static spi_device_handle_t ...

This is a 220V AC powered device. It contains an AC to DC converter and should fall into a deep sleep when AC power is disconnected. There is a tested schematic, which generates a signal when AC voltage disappears to go to sleep, and generates signal to wake up when AC voltage is back. But sometimes ...

Aha, now I understand the problem from the hardware side. So may it be somehow solved by software with no hardware changes? Maybe some efuse?
Also how from the hardware side would it be correct to provide deep sleep on a super capacitor? I can't generate a reset signal at every wake up, otherwise ...

Here is a simplified schematic. IO9 is pulled up with 5.1k. ESP_EN is pulled up with 5.1k + capacitor to add delay for enable signal. IO8 and IO2 may have undefined states at startup in my schematic, as IO2 is used for analog measurements and IO8 for LED control.

P.S. I've tried this, but it didn't ...

I know that the battery was discharged and why BROWNOUT_RST was triggered. But later I've connected normal voltage and got stuck in forever loop: rst:0x3 (RTC_SW_SYS_RST),boot:0x0 (USB_BOOT)
This is potentially dangerous situation, when device will hang with power connected.
The question is why it ...

I have a custom board on ESP32C3, with possibility to fall into a deep sleep by external signal. As a source for power in deep sleep a 0.22F super capacitor is used. But sometimes when ESP goes out of a deep sleep when it's powered from super capacitor only, it falls into a forever loop on the next ...

Hi. I use timer interrupts to make dynamic indication on 7-segment indicators (interrupt period 1000us for show time and 50us for delay between periods to give time for LEDC to change state). To make variable brightness I use LEDC on common pins of the indicator (40kHz 4bit). It works well until ...

I've found the reason of pull down after going to deep sleep, it is in esp_deep_sleep_wakeup_prepare() function, which is called from esp_deep_sleep_start(). For some reason when i disable pulldown of the wake up pin the chip started to wake up much better. I think that function esp_deep_sleep_start ...