Linking error with bootloader support plus (AEGHB-1244)

[EarthLord]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Chipset: ESP32S3
IDF version: 5.5.1

I have an issue where I am able to have one project compile and work successfully with bootloader support plus and another can't do the linking step in the compilation process. I am getting the below error where the new v3 header based image verification functions are not visible in the linking step. I've attached some files i thought are relevant. Please let me know if any other info is needed. Thank.s

I am attaching the build.ninja file, build process output (added .txt to attach here),

build.ninja.txt
idf_py_stdout_output_90435.txt

Files from components/bootloader_support_plus
CMakeLists.txt
idf_component.yml

Files from main folder
CMakeLists.txt
idf_component.yml

Files from bootloader_components/main
CMakeLists.txt
idf_component.yml

The folder structure is as below.

├── aws
├── bootloader_components
│   └── main
├── components
│   ├── bootloader_support_plus
│   │   ├── include
│   │   ├── ld
│   │   │   ├── esp32c2
│   │   │   ├── esp32c3
│   │   │   └── esp32c6
│   │   ├── private_include
│   │   └── src
│   ├── esp-nimble-cpp-master
│   │   ├── docs
│   │   └── src
│   └── rtc_time_manager
│       └── include
├── main
│   ├── com
│   │   ├── cellular
│   │   ├── mqtt
│   │   ├── nimble
│   │   ├── ota
│   │   └── wifi
│   ├── core
│   │   ├── data
│   │   ├── gpio
│   │   ├── log
│   │   └── state_machine
│   ├── io
│   │   ├── i2c
│   │   │   ├── adc
│   │   │   ├── bms
│   │   │   ├── dac
│   │   │   ├── gas_gauge
│   │   │   ├── gps
│   │   │   ├── imu
│   │   │   ├── rtc
│   │   │   ├── temp_sensor
│   │   │   └── usb_c_pd
│   │   └── uart
│   │       └── gps_uart
│   ├── micro
│   │   ├── excursion
│   │   ├── self_test
│   │   ├── tec_cont
│   │   ├── temp
│   │   └── ulp
│   └── storage
├── scripts
│   └── geofencing
└── tools

[WangYuxin-esp]

@EarthLord Hi, Please try testing the examples.
Note that I see you've placed the bootloader_plus component in the components directory, which may be a contributing factor to the error. The current linking mechanism appears to be implemented via a yml file, so please refer to the instructions here1 and here2. You can place the component in any local directory and specify it with the override_path command.

[EarthLord]

@WangYuxin-esp Thanks for the reply.

I have the correct path to components/bootloader_support_plus from yml files in main folder and from bootloader_components/main. The strange thing is that the same configuration of folder structure and yml file is working in another project but not in this one.

What else can be wrong to cause this issue?

[WangYuxin-esp]

@EarthLord Please check your configuration options to make sure this option is enabled.

[EarthLord]

Yes, these two are enabled

CONFIG_BOOTLOADER_COMPRESSED_ENABLED=y
CONFIG_BOOTLOADER_DECOMPRESSOR_XZ=y

[WangYuxin-esp]

Try deleting the build directory and recompiling the projects.
Try deleting the dependencies.lock file in the project and recompiling the project.
Compare the differences between the two projects during compilation and runtime.
If the .yml files, directory structure, and option configurations are identical, both should work.

[EarthLord]

This solves the problem. @WangYuxin-esp please share your thoughts?

[WangYuxin-esp]

I'm not very knowledgeable about compiler issues. However, I noticed that you're placing the component in the components directory, which I suspect may be a contributing factor to the issue. The components directory is a special directory name in esp-idf.
If both projects use the same version of esp-idf and have the same directory structure, they should both work.
So try moving the component out of the components directory, deleting the build directory and the dependencies.lock file, recompiling the project, and testing. If the issue persists, please provide a minimal project that reproduces the issue. Thanks.