EspExceptionDecoder VS FreeRTOS-Transceiver

Here is the github for the tool I use and it explains how to install it. EspExceptionDecoder

It helps you to decode backtrace and find the problem https://github.com/me-no-dev/EspExceptionDecoder

Your code 'stuck' somewhere for more than 3 seconds without feeding the watchdog. The ESP Exception Decoder might tell you where it hung, although more likely it's simply a coding error which isn't obvious with the Exception Decoder. https://github.com/me-no-dev/EspExceptionDecoder

https://github.com/me-no-dev/EspExceptionDecoder Install that and dump your stack trace into it (between the cut points). We can't decode it, it needs the ELF file generated by the compile. It will help you figure out where the errors are.

There may be more messages about the crash. I would use the ESP Exception Decoder to try to find where in the code it's crashing.

Arduino: https://github.com/me-no-dev/EspExceptionDecoder Esp-idf: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-monitor.html

This. Install the exception decoder into your IDE: https://github.com/me-no-dev/EspExceptionDecoder

But there is also a way of creating two special callback functions that dynamically create a copy of the received data (even complex structures) and delete it afterwards (call right after xQueueReceive for creating a copy). Only works on heap-memory with malloc / new and free / delete for the dataAllocator/dataDestroyer callback (example) . In that way, the receiving task will own the pointers in his rx buffers

I've tried to create my first library to make data exchange between tasks + buffering of received data simpler: https://github.com/xhera83/FreeRtos-Transceiver. It is still in an early stage but works perfectly for me atm. Im much much faster with it than with the raw FreeRTOS API.