I have being using TWAI (J1939) in our project for a long time with (almost (more about that later)) no issues. I have now added a deep-sleep in case of low battery and reapplying external power will wake up the ESP32 again. That all works great. However, the TWAI does NOT recover after deep-sleep w...

Ignore post, stupid mistake, I couldn't see the forest for the trees.
Problem solved, it DOES work as planned.

I have roughly this setup.
 [size=85]- common_code/ - component1/ - include/ - component1.h - Kconfig - src1.c - component2/ - include/ - component2.h - Kconfig - src2.c - Project_1/ - build/ - main/ - src3.c - src4.c - CMakeLists.txt - CMakeLists.txt - sdkconfig - Project_2/ - build/ - main/ - src5...

Thank you, I'm aware of how the FLASH_CRYPT_CNT works and how to "fix" this by adding a bit, but I don't care about saving a board. I want to know HOW and WHY this happened, so we can (if possible) make sure it doesn't happen again. The fact that it's only this single bit that has been changed in th...

We're using ESP-IDF 5.2.1 This is ONE board out of a batch of 5000 that is all ok. It was extensively tested before delivery and has been working fine in the field for some time. We do not use ANY security features like Secure Boot, Flash Encryption or anything. It complains when doing the erase_fla...

We have a few thousand ESP32-U4WDH based boards out with customers and recently got one back that had entered some kind of loop and drained batteries. When testing, there is NO data on the serial channel. Trying to re-flash the firmware worked fine, but, still no log. We then tried do an 'erase_all'...

Thank you, but not the same. This is clearly related to Espressif-IDE (or Eclipse, actually), as the program compiles and launches fine in a command line ESP-IDF environment. The silly idf5.0_py3.9 env is only used when launching in Eclipse. Building works fine. And I just cannot find WHERE it is st...

I use Espressif-IDE. I have an issue with a few of my older projects. I had been using a different ESP-IDF version. They compile fine, but when I want to flash/launch, I get the following error: Screenshot 2024-02-15 at 14.15.58.png If refers to an idf5.0_py3.9_env . However, I am using IDF 5.1 Funn...

UPDATE 2:
This is where it gets interesting.
The target switch was only needed on ONE project.
After doing that, that project as well as ALL OTHERS build normally.

UPDATE:
Found a solution to this.
Changing the target from esp32 to esp32c3 made it build.
So, after switching back to esp32, I had a working build.
This is great that there is a workaround, it's not great that this is suddenly needed on all my projects.