You can also get the complete package from https://github.com/espressif/esp-bsp/re ... ine-latest — it is automatically updated for any new board.

1. Is the Flash Memory (U3) of Fig-3 marked as **External Memory** in Fig-2? Yes, it is. 2. Is FreeRTOS firmware pre-installed in "Instruction ROM Memory" of Fig-1? Which core it is -- Core0 or Core1? It's not. FreeRTOS (plus every other part of the system: heap implementation, C library, periphera...

The ota update use image version i think, i didn't know there was app version and image version. How to "automate" image version ? I'm sorry, I can't understand this part. The line of code you are pointing to uses the "version" field of esp_app_desc_t structure. This field can be set in a variety o...

It seems this change had been mentioned in the release notes of v5.1. To allocate a Freertos object in PSRAM, you have to first allocate memory for it with heap_caps_malloc(..., MALLOC_CAP_SPIRAM) and then use xQueueCreateStatic to initialize the object inside the allocated buffer. Here's an example...

Please try adding --version 2 after image_info command, then it should print the app metadata info (https://docs.espressif.com/projects/esp ... image-info)

Espflash (https://github.com/esp-rs/espflash) can also be built into a standalone binary.

We perform lazy context switching, same as for the FPU: 1. When switching the tasks, the coprocessors (FPU and PIE) are disabled 2. If the new task never used FPU or PIE, there's nothing to do 3. If the new task does try to use FPU or PIE, this triggers a "coprocessor disabled" exception. The except...

I'm afraid in this case the host tool would be unable to decide the core dump, even if it used the correct partition table offset. Both the partition table and the core dump would be encrypted, and typically the encryption key is not known on the host side. If the scenario is to use core dumps in a ...

The format is also documented in https://docs.espressif.com/projects/esp ... ormat.html

Try setting EXTRA_COMPONENT_DIRS to the parent folder of your component folder ("common"). (Or rather move "common" into a "mycomponents" folder and set the latter as a component dir.) I believe the intention is that an "EXTRA_COMPONENT_DIR", just like "components" in your project or the IDF, conta...