The elf file will be there once you have built your project. If you run "make" (or "make -j4" to speed things up) in your project directory, then one of the last few lines of the output will look like: LD build/blink.elf This means that the elf file was generated. The name of the .elf file may be di...

If i put a esp_logi inside the function task I can see log during sleep. No, this most definitely should not be happening. If you see the logs being printed, this means that the chip is not in light sleep. All peripherals are clock gated in light sleep, so no UART output can be produced in this sta...

The simplest option is to call esp_partition_erase_range function to erase the entire partition. Then initialize WL and FATFS. This will result in the filesystem being formatted.

The ELF file should be your application ELF file, it has the same name as your project (PROJECT_NAME set in Makefiile).

Regarding the first error, could you please post the partition table you are using?

It's mostly because in C language, writing into a destination buffer without knowing how large it is is unsafe. You may know the buffer size today, but then it is not uncommon for some parameters in the application to change so that the size of the destination buffer becomes insufficient. Without ex...

Hi dacitt, you might have run into a bug of some sort. Can you share your project (e.g. via a PM) so that we can reproduce the issue on our end?

No, you need to initialize "required_size" variable with the amount of space available in the destination buffer. Currently the variable is uninitialized, and contains garbage. If you want to know what is the size required to store the result, you can first call nvs_get_str with NULL instead of the ...

How are you starting OpenOCD when debugging on the custom board (what are the arguments) and what is the voltage of the flash chip used on the custom board?

If it is 3.3v the you need to use esp-wroom32.cfg instead of esp32-wrover.cfg.

Ho do you implement nvs_read_str function?

Could you please open idf_monitor ("make monitor") before you start programming the board over JTAG, and observe the console output which is generated at the time when OpenOCD prints "Core 0 was reset". If you see something like "flash read err, 1000", then it is likely that the chip is not bootstra...