I tried the ulp samples and they worked fine.
I then tried to integrate the ULP wakeup in my "regular" code, but the processor doesn't wake up completely, it just writes "ets" or "ets J", so it kinda wakes up, but then nothing more happens.
I commented out virtually all other code, except for a few ...

I have a new board, using the ESP32-S3-WROOM-2 module and have I2S connected to:

#define GPIO_I2S_MCLK GPIO_NUM_39
#define GPIO_I2S_SD GPIO_NUM_40
#define GPIO_I2S_BCK GPIO_NUM_41
#define GPIO_I2S_WS GPIO_NUM_42

I2S is not working and there are signals on all pins, except GPIO_41.
I'm aware this ...

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 ...

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 ...

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 ...

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 ...

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 ...

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 ...