Add support for DISCO_L475VG_IOT01A #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 6 commits
September 2, 2021 11:43
* Update library information for bootloader and application The mcuboot.lib files now point to lambda-shuttle/mcuboot, which contains support for CMake. * Resolve include path for secondary_bd.h The path now includes the full path to this header, which lives under the flash_map_backend folder of the mbed-mcuboot port's include directory. * Update bootloader and application app configurations * Add CMakeLists.txt for target application * Add CMakeLists.txt for target bootloader * Set target application c_lib to "small" in mbed_app.json
* Update mcuboot.sh to use mbed-tools * Add DISCO_L475VG_IOT01A as option for target board * Use pyocd for flashing the target binaries The scripts now take in a -f or --flash option instead of the mount path of the board to flash the binaries. * Update clean routine to only clean when option is set * Fix target binary paths in mcuboot.sh This commit also includes a number of other fixes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the script for building the MCUboot example,
mcuboot.sh, uses the old mbed-cli (V1) to build the bootloader and primary application as the MCUboot port for Mbed OS lacks support for the newmbed-toolsand was built right before the transition. The Mock example, however, usesmbed-tools.A pull request has been issued at mcu-tools/mcuboot#1153 to add support for CMake; work on this wasn't trivial and involved generous help from @LDong-Arm to resolve. The library information file for the MCUboot example now points to this fork. Subsequently, CMakeLists.txt files were added to the bootloader and application directories of the MCUboot FOTA example to facilitate the mbed-tools build workflow.
This added support for CMake also saw a number of smaller changes (resolving header paths and updating the app configuration json file). The
mcuboot.shscript was updated to usembed-toolsand README.md files for both the repository and examples were updated accordingly. The examples have been verified to work as expected onDISCO_L475VG_IOT01A.Other notable changes include the use of
pyocdfor flashing the binaries, with the script now accepting a-for--flashoption instead of the board's mount point, and an updated clean routine that only cleans the builds and generated files when specified to do so; previously, the dependencies and generated files were automatically cleaned on a failed exit.