Hi all,

I would like to use UART0 and the built-in USB-UART bridge to send a basic WLAN configuration file to the ESP32. I tried this based on the UART examples, but everytime I send the file to the ESP32, it resets. What am I doing wrong? How can I use the USB-UART bridge for my purposes? I am ...

Hi all,

I'm using IDF v5.3.1 within VS Code. I use esp32 WROOM and esp32c6 modules. I configured to save core dumps to flash memory. Reading the flash memory works fine with both module types. But I cant decode the core dump written by the esp32c6 module. Calling espcoredump (or idf.py info ...

No problem ;) It cost me several days to figure out. But this is my (quite simple) solution and it works fine.

In my project structure on disk I added a "Binaries" folder where cmake copies the required files.
Additionally, I saved a "sdkconfig.defaults.xxx" for each target architecture I use (here ...

Hi everybody!

Does anybody already tried to compile a source for target esp32c6 with IDF v5.3 (release) and core dump switched on for "flash"?
In my project the compilation failes with a "boundary violation" in the flash core dump source.

Any hints?

Greetings
Christoph

If anybody is interested: solved my problem by adding some cmake custom commands to the CMakeList.txt file in the project root folder.

Greetings
Christoph

Hi All!

I would like to know if it is possible to have one main folder with code in VS CODE, but to target to different processor types with different *.bin names. To give an example:
I have written some code primarily for the ESP32-WROOM module. Now, I would like to target an ESP32C6 module from ...

Hi Matthias,

I opened an issue in Github. Simon Cao answered very quickly that it is a known bug. Which is already fixed internally. He posted the right code and I will do so here if anybody else encounters the same problem. You just have to replace the given function:


static bool s_i2c_read ...

Hi Matthias,

I am out :D

I tried it with the function you provided... nothing. Still blocks within read part, getting resetted by task watchdog and afterwards blocked in i2c_new_master_bus ... what am I missing?
LOG is set to "VERBOSE", check of i2c log is set, but there are no significant log ...

Hi Matthias,

thanks for the hint! But unfortunately, even with "uint8_t data[1]" both read functions block until watchdog reset.
Do you use the 5.2 release branch or the 5.2 developer branch?

Greetings
Christoph

Hi All!

Consider following situation: main task creates legacy i2c driver, initializes and uses it from time to time. A second task is responsible to accept and to answer TCP connect requests. On thing to do within the TCP task is to do a full OTA update. During update an i2c connected LCD display ...