Given solution is included in MCUboot repository with purpose to demonstrate basic concepts and features of MCUboot library on Cypress (Infineon) devices. Applications are created per MCUboot library maintainers requirements. Implementation differs from conventional and recommended by Cypress Semiconductors development flow. These applications are not recommended as a starting point for development and should not be considered as supported examples.
Examples provided to use with ModusToolbox™ Software Environment are a recommended reference point to start development of MCUboot based bootloaders for Cypress (Infineon) devices.
Refer to Cypress (Infineon) github page to find examples.
There are two applications implemented:
The default flash map for PSOC6 MCUBootApp implemented is next:
The flash map can be defined in boot/cypress/platforms/memory//flashmap/.json
It is also possible to place secondary (upgrade) slots in external memory module. In this case primary slot can be doubled in size. For more details about External Memory usage, please refer to separate guiding document ExternalMemory.md.
MCUBootApp checks image integrity with SHA256, image authenticity with EC256 digital signature verification and uses either completely software implementation of cryptographic functions or accelerated by hardware - both based on Mbed TLS Library.
There is a set assets required:
Those are represented as submodules.
To retrieve source code with subsequent submodules pull:
git clone --recursive https://github.com/mcu-tools/mcuboot.git
Submodules can also be updated and initialized separately:
cd mcuboot git submodule update --init --recursive
Root directory for build is boot/cypress
This folder contains make files infrastructure for building both MCUboot Bootloader and sample BlinkyApp application used for Bootloader demo functionality.
Instructions on how to build and upload MCUBootApp bootloader application and sample user application are located in corresponding Readme files of the platforms folder.
GCC_ARM is only supported GCC compiler. It is included with ModusToolbox™ Programming Tools. The recommended version of the GCC_ARM compiler is 11.3.1.
The default installation folder is expected by the makefile build system.To use another installation folder, version of ModusToolbox™ Programming Tools or another GCC Compiler, specify the path to a toolchain using the TOOLCHAIN_PATH parameter.
Below is an example on how to set toolchain path:
make clean app APP_NAME=MCUBootApp PLATFORM=PSOC_062_2M BUILDCFG=Debug FLASH_MAP=platforms/memory/PSOC6/flashmap/psoc6_swap_single.json TOOLCHAIN_PATH=c:/Users/${USERNAME}/Infineon/Tools/mtb-gcc-arm-eabi/11.3.1/gcc
Following CLI / IDE are supported for project build:
Make - make sure it is added to system's PATH variable and correct path is first in the list;
Python/Python3 - make sure you have correct path referenced in PATH;
Msys2 - to use systems PATH navigate to msys2 folder, open msys2_shell.cmd, uncomment set MSYS2_PATH_TYPE=inherit, restart MSYS2 shell.
This will inherit system's PATH so should find Python installed in regular way as well as imgtool and its dependencies.