After some tinkering, I believe this to be a bug within the ESP-IDF framework. The code runs fine if the target is set to ESP32 or ESP32C3, but it fails (as above) for the ESP32S3. I filed an issue here: https://github.com/espressif/esp-idf/issues/15446

I've got a Docker container running ESP-IDF (for development) along with a Mosquitto server for testing MQTT messaging. I can successfully connect and pub/sub to the Mosquitto broker with open MQTT (non-TLS) in QEMU as well as on a physical device. My full application can be found here: https://gith...

I'm working on an IoT example using ESP-IDF, and I'm having trouble understanding why getaddrinfo() only returns a single result. Here is my DNS lookup function: // Perform DNS lookup esp_err_t dns_lookup(const char *host, const char *port, const int family, struct addrinfo *ip_addr) { struct addrin...

Thank you! That helps to make sense of what's going on. I moved the critical section to Core 1, and it worked as expected (as Core 0 could still update the timer variable). I also changed the toggle time to 30 ms for Core 0 so it's more noticeable on the scope. Next, I added critical section markers...

In some instances, yes, it is crashing with a "Guru Meditation Error: Core 1 panic'ed (LoadProhibited)" when I had Serial.print statements in the other core (inside a similar critical section). I didn't know that Serial usage was not allowed inside the critical sections at all, so thank you for that...

This may or may not be related to my watchdog timer issue in this thread( https://esp32.com/viewtopic.php?f=2&t=19752 ), but it seems different enough that I decided to post it here anyway. I'm working with the following demo code (for illustrating how spinlocks work). // Core definitions (assuming ...

Hi all, I'm creating a demonstration to show how spinlocks can be used to block tasks in a different core (for a video about multicore programming). I recognize that waiting in an ISR is terrible practice, but I found it useful for this particular demonstration. In the code below, I have an ISR peri...