C++ doesn't support C99-style named initializers for structs, and g++ (the C++ compiler we use) doesn't support any way to enable them as an optional extra. You have three alternatives: Order the elements in the named initializer in the same order they're declared in the struct. The C++ compiler sho...

This is a prerelease Release Candidate of ESP-IDF V3.2. The current stable release is ESP-IDF V3.1.3. Major New Features in V3.2 Automatic Light Sleep support to reduce power consumption, including while maintaining Wi-Fi connection. (Note: Support for Light Sleep with Bluetooth will be added in a f...

mzimmers wrote: ↑

Fri Mar 15, 2019 1:46 am

I'm not sure what you mean by the full call stack. Do you mean you want me to go further with the addr2line commands?

Yes please. I'd like to know at what point vfprintf() was being called.

This certainly seems like a memory leak bug. Even if data is being received from the UART (is it?), then there will be an upper limit to the UART buffer size - it shouldn't consume all the available RAM. What ESP-IDF version are you using? You can follow the steps here to narrow down the memory leak...

It looks like allocating the lock for a printf() call failed for some reason. Can you please give us the full call stack, so we can see exactly what started this sequence of events? If you can, please pass the "-pfia" options to addr2line as well (among other things, this will include the function n...

The error looks like the application may have used more stack than that's available to the task. The task running loop() in Arduino only has 8KB of stack available. There are two ways to try and solve this. Edit your local copy of main.cpp and change 8192 to a larger number like 16384. Create a seco...

Ah, I'm sorry my replies until now were all about the build error not the abort at startup.

Are you able to decode the backtrace from the app? Can be done using idf_monitor, or addr2line (details).

Can you also post the full boot log from your app, please? (Everything from the CPU reset onwards.)

Awesome, very interesting! There is a high level overview of the ESP-IDF application startup flow (from ROM code to app) here: https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/general-notes.html#application-startup-flow Aside from this, the ESP-IDF source code for the bootloader and ...

V3.3 testing has begun. Right now final testing for the V3.2 release is still in progress.

We don't have an ETA for the V3.3 release yet, unfortunately.

Hi Marc! Well, there is a clearly a problem there, I agree, but 1) why wouldn't FreeRTOS check its allocations? It does, with an assert. When the assert fails, you get a crash with "assert failed" in the log. 2) I sure didn't use all the RAM available, not even close 3) The same program works perfec...