I am running code ONLY on CPU0, and I only use the ESP_LOGx() functions.
I do call esp_log in gap_ble callbacks and wifi event handler.
How should I be logging from callbacks?
panic unhandled break instruction
Re: panic unhandled break instruction
No, these callbacks are not from ISRs (so logging there should be okay).
The backtrace actually looks very similar to a bug which we are troubleshooting now. Could you please check if you have "Run FreeRTOS on first core only" option enabled in menuconfig (Component config > FreeRTOS)? If it is not enabled, could you please try again having enabled it?
The backtrace actually looks very similar to a bug which we are troubleshooting now. Could you please check if you have "Run FreeRTOS on first core only" option enabled in menuconfig (Component config > FreeRTOS)? If it is not enabled, could you please try again having enabled it?
Re: panic unhandled break instruction
It's already Unicore. I also disabled CPU1 cache.
Code: Select all
# CONFIG_MEMMAP_SMP is not set
CONFIG_FREERTOS_UNICORE=y
Re: panic unhandled break instruction
Does this happen with one of the ESP-IDF examples? If not, can you share the code to reproduce this issue?
Re: panic unhandled break instruction
I have a hard time reproducing this problem, I will post back when I have more information or when I am able to reproduce.
Re: panic unhandled break instruction
I am able to reproduce this by generating input in idf_monitor.
Today especially I was having alot of them, maybe because I was testing alot.
Then I remembered reading https://github.com/espressif/esp-idf/issues/688
So I guess that is the cause. The uart0 rx interrupt.
Today especially I was having alot of them, maybe because I was testing alot.
Then I remembered reading https://github.com/espressif/esp-idf/issues/688
So I guess that is the cause. The uart0 rx interrupt.
Who is online
Users browsing this forum: No registered users and 86 guests