https://docs.espressif.com/projects/esp ... le-project

Alternatively, EXTRA_COMPONENT_DIRS can be set in the top-level CMakeLists.txt to look for components in other places.

We are trying to generate a PWM of ~50Hz on an ESP32-S3.

Is there a way to configure the LEDC for such a low frequency?
If not, which other peripherals are best suited for this task?

Did you stop the WiFi before trying to deinit?

We generally only call `stop` if we got an event that the WiFi was started. Maybe we didn't get that event, or there is a race condition.
I will look into that.

I have some code that has a weird error after it couldn't establish a connection. It gets error 0x3014 when trying to deinit. So far I have only seen this error with the ESP32S3. E (3697) wifi_init: Failed to deinit Wi-Fi driver (0x3014) The error code reference seems to indicate that this error is ...

Are you using the USB-JTAG-Serial for monitoring?

No. We use the serial port's TX (pin 43 iirc).

One of our projects uses an ESP32S3. Sometimes we see the message `pro cpu reset by JTAG` during boot, and the device then stops shortly after. It manages to execute some instructions but it runs less than a second. This is semi-reproducible. If we wake up from sleep it happens maybe once every 20? ...

According to https://github.com/espressif/esp-idf/blob/master/docs/en/migration-guides/release-5.x/5.0/tools.rst esp-idf monitor now uses the custom console baud-rate (CONFIG_ESP_CONSOLE_UART_BAUDRATE) by default instead of 115200. I looked through the sources and couldn't find how it was doing that...

Is the ESP32 Qemu build supposed to be able to simulate a deep sleep? When I call 'esp_sleep_start' I get the following crash: Guru Meditation Error: Core 0 panic'ed (LoadStorePIFAddrError). Exception was unhandled. Core 0 register dump: PC : 0x40097560 PS : 0x00060a33 A0 : 0x80088c1f A1 : 0x3ffbbe5...

Another batch of tutorials for the Toit language have been published today.

The new tutorials cover:
- OTA
- Supabase
- AWS MQTT
- HTTP (file) server
- Toit Services

Enjoy!

Looks like we were missing a call to 'esp_wifi_stop'. That is, we were calling 'esp_wifi_start' for the espnow part of our program; then shutting down espnow (but missing the 'esp_wifi_stop'), followed by calling 'esp_wifi_start' again in the WiFi part of our program. We now call 'esp_wifi_stop' whe...