kopia lustrzana https://github.com/espressif/esp-idf
feat(bootloader): add the possibility to ignore extra components
Omar Chebib
rodzic
2253d3fe83
commit
c98d1f1619
|
|
@ -124,13 +124,20 @@ idf_build_get_property(sdkconfig SDKCONFIG)
|
|||
idf_build_get_property(python PYTHON)
|
||||
idf_build_get_property(extra_cmake_args EXTRA_CMAKE_ARGS)
|
||||
|
||||
# We cannot pass lists are a parameter to the external project without modifying the ';' spearator
|
||||
string(REPLACE ";" "|" BOOTLOADER_IGNORE_EXTRA_COMPONENT "${BOOTLOADER_IGNORE_EXTRA_COMPONENT}")
|
||||
|
||||
externalproject_add(bootloader
|
||||
SOURCE_DIR "${CMAKE_CURRENT_LIST_DIR}/subproject"
|
||||
BINARY_DIR "${BOOTLOADER_BUILD_DIR}"
|
||||
# Modiying the list separator for the arguments, as such, we won't need to manually
|
||||
# replace the new separator by the default ';' in the subproject
|
||||
LIST_SEPARATOR |
|
||||
CMAKE_ARGS -DSDKCONFIG=${sdkconfig} -DIDF_PATH=${idf_path} -DIDF_TARGET=${idf_target}
|
||||
-DPYTHON_DEPS_CHECKED=1 -DPYTHON=${python}
|
||||
-DEXTRA_COMPONENT_DIRS=${CMAKE_CURRENT_LIST_DIR}
|
||||
-DPROJECT_SOURCE_DIR=${PROJECT_SOURCE_DIR}
|
||||
-DIGNORE_EXTRA_COMPONENT=${BOOTLOADER_IGNORE_EXTRA_COMPONENT}
|
||||
${sign_key_arg} ${ver_key_arg}
|
||||
${extra_cmake_args}
|
||||
INSTALL_COMMAND ""
|
||||
|
|
|
|||
|
|
@ -41,11 +41,18 @@ if(EXISTS ${PROJECT_EXTRA_COMPONENTS})
|
|||
list(APPEND EXTRA_COMPONENT_DIRS "${PROJECT_EXTRA_COMPONENTS}")
|
||||
endif()
|
||||
|
||||
# Consider each directory in project's bootloader_components as a component to be compiled
|
||||
if(IGNORE_EXTRA_COMPONENT)
|
||||
# Prefix all entries of the list with ${PROJECT_EXTRA_COMPONENTS} absolute path
|
||||
list(TRANSFORM IGNORE_EXTRA_COMPONENT
|
||||
PREPEND "${PROJECT_EXTRA_COMPONENTS}/"
|
||||
OUTPUT_VARIABLE EXTRA_COMPONENT_EXCLUDE_DIRS)
|
||||
endif()
|
||||
|
||||
# Consider each directory in the project's bootloader_components as a component to be compiled
|
||||
file(GLOB proj_components RELATIVE ${PROJECT_EXTRA_COMPONENTS} ${PROJECT_EXTRA_COMPONENTS}/*)
|
||||
foreach(component ${proj_components})
|
||||
# Only directories are considered as components
|
||||
if(IS_DIRECTORY ${curdir}/${child})
|
||||
# Only directories are considered components
|
||||
if(IS_DIRECTORY "${PROJECT_EXTRA_COMPONENTS}/${component}" AND NOT ${component} IN_LIST IGNORE_EXTRA_COMPONENT)
|
||||
list(APPEND COMPONENTS ${component})
|
||||
endif()
|
||||
endforeach()
|
||||
|
|
@ -53,6 +60,7 @@ endforeach()
|
|||
set(BOOTLOADER_BUILD 1)
|
||||
include("${IDF_PATH}/tools/cmake/project.cmake")
|
||||
set(common_req log esp_rom esp_common esp_hw_support newlib)
|
||||
idf_build_set_property(EXTRA_COMPONENT_EXCLUDE_DIRS "${EXTRA_COMPONENT_EXCLUDE_DIRS}")
|
||||
idf_build_set_property(__COMPONENT_REQUIRES_COMMON "${common_req}")
|
||||
idf_build_set_property(__OUTPUT_SDKCONFIG 0)
|
||||
project(bootloader)
|
||||
|
|
|
|||
|
|
@ -141,6 +141,9 @@ An example project directory tree might look like this::
|
|||
- myProject/
|
||||
- CMakeLists.txt
|
||||
- sdkconfig
|
||||
- bootloader_components/ - boot_component/ - CMakeLists.txt
|
||||
- Kconfig
|
||||
- src1.c
|
||||
- components/ - component1/ - CMakeLists.txt
|
||||
- Kconfig
|
||||
- src1.c
|
||||
|
|
@ -160,6 +163,8 @@ This example "myProject" contains the following elements:
|
|||
|
||||
- "sdkconfig" project configuration file. This file is created/updated when ``idf.py menuconfig`` runs, and holds the configuration for all of the components in the project (including ESP-IDF itself). The "sdkconfig" file may or may not be added to the source control system of the project.
|
||||
|
||||
- Optional "bootloader_components" directory contains components that need to be compiled and linked inside the bootloader project. A project does not have to contain custom bootloader components of this kind, but it can be useful in case the bootloader needs to be modified to embed new features.
|
||||
|
||||
- Optional "components" directory contains components that are part of the project. A project does not have to contain custom components of this kind, but it can be useful for structuring reusable code or including third-party components that aren't part of ESP-IDF. Alternatively, ``EXTRA_COMPONENT_DIRS`` can be set in the top-level CMakeLists.txt to look for components in other places.
|
||||
|
||||
- "main" directory is a special component that contains source code for the project itself. "main" is a default name, the CMake variable ``COMPONENT_DIRS`` includes this component but you can modify this variable. See the :ref:`renaming main <rename-main>` section for more info. If you have a lot of source files in your project, we recommend grouping most into components instead of putting them all in "main".
|
||||
|
|
@ -210,6 +215,8 @@ These variables all have default values that can be overridden for custom behavi
|
|||
|
||||
- ``COMPONENTS``: A list of component names to build into the project. Defaults to all components found in the ``COMPONENT_DIRS`` directories. Use this variable to "trim down" the project for faster build times. Note that any component which "requires" another component via the REQUIRES or PRIV_REQUIRES arguments on component registration will automatically have it added to this list, so the ``COMPONENTS`` list can be very short.
|
||||
|
||||
- ``BOOTLOADER_IGNORE_EXTRA_COMPONENT``: A list of components, placed in ``bootloader_components/``, that should be ignored by the bootloader compilation. Use this variable if a bootloader component needs to be included conditionally inside the project.
|
||||
|
||||
Any paths in these variables can be absolute paths, or set relative to the project directory.
|
||||
|
||||
To set these variables, use the `cmake set command <cmake set_>`_ ie ``set(VARIABLE "VALUE")``. The ``set()`` commands should be placed after the ``cmake_minimum(...)`` line but before the ``include(...)`` line.
|
||||
|
|
@ -672,6 +679,39 @@ The linker will provide a new symbol named ``__real_function_to_redefine`` which
|
|||
|
||||
This mechanism is shown in the example :example:`build_system/wrappers`. Check :idf_file:`examples/build_system/wrappers/README.md` for more details.
|
||||
|
||||
Override the default Bootloader
|
||||
-------------------------------
|
||||
|
||||
Thanks to the optional ``bootloader_components`` directory present in your ESP-IDf project, it is possible to override the default ESP-IDF bootloader. To do so, a new ``bootloader_components/main`` component should be defined, which will make the project directory tree look like the following:
|
||||
|
||||
- myProject/
|
||||
- CMakeLists.txt
|
||||
- sdkconfig
|
||||
- bootloader_components/ - main/ - CMakeLists.txt
|
||||
- Kconfig
|
||||
- my_bootloader.c
|
||||
- main/ - CMakeLists.txt
|
||||
- app_main.c
|
||||
|
||||
- build/
|
||||
|
||||
|
||||
Here the ``my_bootloader.c`` file becomes source code for the new bootloader, which means that it will need to perform all the required operations to set up and load the ``main`` application from flash.
|
||||
|
||||
It is also possible to conditionally replace the bootloader depending on a certain condition, such as the target for example. This can be achieved thanks to the ``BOOTLOADER_IGNORE_EXTRA_COMPONENT`` CMake variable. This list can be used to tell the ESP-IDF bootloader project to ignore and not compile the given components present in ``bootloader_components``. For example, if one wants to use the default bootloader for ESP32 target, then ``myProject/CMakeLists.txt`` should look like the following::
|
||||
|
||||
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
|
||||
|
||||
if(${IDF_TARGET} STREQUAL "esp32")
|
||||
set(BOOTLOADER_IGNORE_EXTRA_COMPONENT "main")
|
||||
endif()
|
||||
|
||||
project(main)
|
||||
|
||||
It is important to note that this can also be used for any other bootloader components than `main`. In all cases, the prefix `bootloader_component` must not be specified.
|
||||
|
||||
See :example:`custom_bootloader/bootloader_override` for an example of overriding the default bootloader.
|
||||
|
||||
.. _config_only_component:
|
||||
|
||||
Configuration-Only Components
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@
|
|||
|
||||
(See the README.md file in the upper level for more information about bootloader examples.)
|
||||
|
||||
The purpose of this example is to show how to override the second stage bootloader from a regular project.
|
||||
The purpose of this example is to show how to override the second-stage bootloader from a regular project.
|
||||
|
||||
**NOTE**: Functions called during the loading stage of the bootloader are expected to be placed in the iram_loader_seg to avoid being overwritten during loading. If you are overriding functions which are called during this stage then special care needs to be taken to avoid issues, e.g. by providing your own linkerscript which places the required functions in the correct sections.
|
||||
**NOTE**: Functions called during the loading stage of the bootloader are expected to be placed in the iram_loader_seg to avoid being overwritten during loading. If you are overriding functions that are called during this stage then special care needs to be taken to avoid issues, e.g. by providing your linker script which places the required functions in the correct sections.
|
||||
|
||||
## How to use example
|
||||
## How to use this example
|
||||
|
||||
Simply compile it:
|
||||
```
|
||||
|
|
@ -21,17 +21,17 @@ And flash it with the following commands:
|
|||
idf.py flash
|
||||
```
|
||||
|
||||
This custom bootloader does not do more than the older bootloader, it only prints an extra message on start up:
|
||||
This custom bootloader does not do more than the older bootloader, it only prints an extra message on startup:
|
||||
```
|
||||
[boot] Custom bootloader message defined in the KConfig file.
|
||||
```
|
||||
|
||||
## Organisation of this example
|
||||
## Organization of this example
|
||||
|
||||
This project contains an application, in the `main` directory that represents a user program.
|
||||
It also contains a `bootloader_components` directory that, as it name states, contains a component that will override the current bootloader implementation.
|
||||
It also contains a `bootloader_components` directory that, as its name states, contains a component that will override the current bootloader implementation.
|
||||
|
||||
Below is a short explanation of files in the project folder.
|
||||
Below is a short explanation of the files in the project folder.
|
||||
|
||||
```
|
||||
├── CMakeLists.txt
|
||||
|
|
@ -48,5 +48,24 @@ Below is a short explanation of files in the project folder.
|
|||
└── README.md This is the file you are currently reading
|
||||
```
|
||||
|
||||
As stated in the `README.md` file in the upper level, when the bootloader components is named `main`, it overrides
|
||||
As stated in the `README.md` file in the upper level, when the bootloader components are named `main`, it overrides
|
||||
the whole second stage bootloader code.
|
||||
|
||||
## Conditionally override the bootloader
|
||||
|
||||
In case you only want to override the bootloader under a certain condition (target-dependent, KConfig option, etc...), it is possible to let the bootloader project know that the `bootloader_components/main` component shall be ignored.
|
||||
|
||||
For example, if the custom bootloader shall not be compiled for ESP32-C3 targets, which should use the default ESP-IDF one, the `CMakeLists.txt` file in this current example must look like this:
|
||||
```
|
||||
cmake_minimum_required(VERSION 3.16)
|
||||
|
||||
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
|
||||
|
||||
if(${IDF_TARGET} STREQUAL "esp32c3")
|
||||
set(BOOTLOADER_IGNORE_EXTRA_COMPONENT "main")
|
||||
endif()
|
||||
|
||||
project(main)
|
||||
```
|
||||
|
||||
It is important to note that this can also be used for any other bootloader components than `main`. In all cases, the prefix `bootloader_component` must not be specified.
|
||||
|
|
|
|||
|
|
@ -311,10 +311,11 @@ function(__project_init components_var test_components_var)
|
|||
if(EXISTS ${component_dir}/CMakeLists.txt)
|
||||
idf_build_component(${component_dir})
|
||||
else()
|
||||
idf_build_get_property(exclude_dirs EXTRA_COMPONENT_EXCLUDE_DIRS)
|
||||
# otherwise, check whether the subfolders are potential idf components
|
||||
file(GLOB component_dirs ${component_dir}/*)
|
||||
foreach(component_dir ${component_dirs})
|
||||
if(IS_DIRECTORY ${component_dir})
|
||||
if(IS_DIRECTORY ${component_dir} AND NOT ${component_dir} IN_LIST exclude_dirs)
|
||||
__component_dir_quick_check(is_component ${component_dir})
|
||||
if(is_component)
|
||||
idf_build_component(${component_dir})
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue