Up!

Hi, I'm seeing that both the ESP32-C3 and the ESP32-S3 support Bluetooth mesh with TX power of +18 and +20dbm respectively, but on the IDF the maximum setting that we can choose is +9dbm. Is it currently possible to get a reliable Bluetooth mesh with this tx power or it is only currently supported b...

My particular problem was a pin staying high after a reset. Something as simple as this can reproduce it: main: delay 10s set pin_32 high abort It starts low, but then goes high and never goes back to low, both with abort, with esp_restart, and entering a critical zone so the interrupt watchdog caus...

Of course you'd use a CRC or similar to check contents on reset anyway.

I use a special 64bits key, if it is there, I know I'm dealing with data from the previous run.

I will investigate that so I can make a full restart (can I trigger the watchdog manually?). Would a full restart like the one you mention clear the RTC_NO_INIT memory? Although I should add that this might still be a bug. The UART should not break because of a restart Just for clarification, the UA...

I've witnessed this behavior 4 times in several years so it is very hard to debug: My chip is trying to read from an UART and doesn't get a response. After a while, it assumes that something is wrong and crashes, restarting again. And it happens again. And again. Either the chip is not writing (henc...

I am particularly interested in fixed (or known, but unfixed) bugs that may persist after a call to esp_restart or a crash.

It is very hard to search though.

Is there a list of known bugs + the IDF version that fixes them? For example, I discovered a bug that caused uart_wait_tx_done to never return, if someone is facing an issue it might be worth it to have that somewhere so they can check if it might be an IDF bug. My current problem: I'm stuck on IDF ...

You can reconfigure the extension with ctrl + p -> "Configure ESP-IDF extension".