XMC7000: OTW firmware upgrade

MCUboot is an open-source library enabling the development of secure bootloader applications for 32-bit MCUs. MCUboot is the primary bootloader in popular IoT operating systems, such as Zephyr and Apache Mynewt.

DFU middleware library protocol is a middleware library provided by Infineon. This protocol supports a serial interface to upgrade the image.

This example demonstrates a firmware upgrade for the XMC7000 using the edge protect bootloader and DFU. It bundles two applications:

Edge protect bootloader application: It consists of a MCUboot-based bootloader application run by the CM0+ core. The bootloader handles DFU application image authentication and upgrades. When the image is valid, the bootloader will boot the DFU image by using the starting address of the primary slot.

Flash boot: It handles the edge protect bootloader image authentication. When the image is valid, flash boot will boot the bootloader image. Flash boot can be configured to run in secure mode (Secure protection state) or in normal mode (Normal protection state):
- Normal protection state: Flash boot will boot the bootloader without authentication.
- Secure protection state: Flash boot will boot the bootloader once authentication is successful. If the bootloader image is found to be invalid or corrupted, the device will enter a DEAD protection state and stay in the DEAD protection state until the device is reset.

DFU application: It consist of a DFU middleware library-based DFU application run by the CM7 core. The DFU application downloads the image and stores it in the secondary slot (flash memory) via serial interface.

DFU Host Tool: It is a GUI-based tool that will send the image via serial interface to the device.

This application can be built-in one of the following ways:
- BOOT mode: The application image is built to be programmed into the primary slot. The bootloader will simply boot the application on the next reset.
- UPGRADE mode: The application image is built to be programmed into the secondary slot. Based on user input, the bootloader will copy the image into the primary slot and boot it on the next reset.

View this README on GitHub.

Provide feedback on this code example.

Requirements

ModusToolbox™ v3.4 or later (tested with v3.4)
Board support package (BSP) minimum required version: 2.3.0
Programming language: C
Associated parts: XMC7000 MCU
CySecureTools: v5.0.0
Other tools: Python v3.8.10 or later

Supported toolchains (make variable 'TOOLCHAIN')

GNU Arm® Embedded Compiler v11.3.1 (GCC_ARM) – Default value of TOOLCHAIN

Supported kits (make variable 'TARGET')

XMC7200 Evaluation Kit (KIT_XMC72_EVK, KIT_XMC72_EVK_MUR_43439M2) – Default value of TARGET
XMC7100 Evaluation Kit (KIT_XMC71_EVK_LITE_V1)

Hardware setup

XMC7000
- UART (KitProg3): To get the debug log messages
- I2C (KitProg3): For DFU transport
MiniProg4
- UART/SPI: For DFU transport
PCAN-USB Pro FD
- CAN FD: For CAN FD transport

This example uses kit's default configuration. See the kit user guide to ensure that the board is configured correctly.

Software setup

See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.

Install a terminal emulator if you don't have one. Instructions in this document use Tera Term.
Install the Python interpreter and add it to the top of the system path in environmental variables. This code example is tested with Python v3.8.10.

Using the code example

Create the project

The ModusToolbox™ tools package provides the Project Creator as both a GUI tool and a command line tool.

Use Project Creator GUI

Open the Project Creator GUI tool.

There are several ways to do this, including launching it from the dashboard or from inside the Eclipse IDE. For more details, see the Project Creator user guide (locally available at {ModusToolbox™ install directory}/tools_{version}/project-creator/docs/project-creator.pdf).
On the Choose Board Support Package (BSP) page, select a kit supported by this code example. See Supported kits.

Note: To use this code example for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work.
On the Select Application page:

a. Select the Applications(s) Root Path and the Target IDE.

Note: Depending on how you open the Project Creator tool, these fields may be pre-selected for you.

b. Select this code example from the list by enabling its check box.

Note: You can narrow the list of displayed examples by typing in the filter box.

c. (Optional) Change the suggested New Application Name and New BSP Name.

d. Click Create to complete the application creation process.

Use Project Creator CLI

The 'project-creator-cli' tool can be used to create applications from a CLI terminal or from within batch files or shell scripts. This tool is available in the {ModusToolbox™ install directory}/tools_{version}/project-creator/ directory.

Use a CLI terminal to invoke the 'project-creator-cli' tool. On Windows, use the command-line 'modus-shell' program provided in the ModusToolbox™ installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ tools. You can access it by typing "modus-shell" in the search box in the Windows menu. In Linux and macOS, you can use any terminal application.

The following example clones the "mtb-example-xmc7000-otw-firmware-upgrade" application with the desired name "xmc7000-otw-firmware-upgrade" configured for the KIT_XMC72_EVK BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id KIT_XMC72_EVK --app-id xmc7000-otw-firmware-upgrade --user-app-name xmc7000-otw-firmware-upgrade --target-dir "C:/mtb_projects"

The 'project-creator-cli' tool has the following arguments:

Argument	Description	Required/optional
`--board-id`	Defined in the field of the BSP manifest	Required
`--app-id`	Defined in the field of the CE manifest	Required
`--target-dir`	Specify the directory in which the application is to be created if you prefer not to use the default current working directory	Optional
`--user-app-name`	Specify the name of the application if you prefer to have a name other than the example's default name	Optional

Note: The project-creator-cli tool uses the git clone and make getlibs commands to fetch the repository and import the required libraries. For details, see the "Project creator tools" section of the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Open the project

After the project has been created, you can open it in your preferred development environment.

Eclipse IDE

If you opened the Project Creator tool from the included Eclipse IDE, the project will open in Eclipse automatically.

For more details, see the Eclipse IDE for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_ide_user_guide.pdf).

Visual Studio (VS) Code

Launch VS Code manually, and then open the generated {project-name}.code-workspace file located in the project directory.

For more details, see the Visual Studio Code for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_vscode_user_guide.pdf).

Keil µVision

Double-click the generated {project-name}.cprj file to launch the Keil µVision IDE.

For more details, see the Keil µVision for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_uvision_user_guide.pdf).

IAR Embedded Workbench

Open IAR Embedded Workbench manually, and create a new project. Then select the generated {project-name}.ipcf file located in the project directory.

For more details, see the IAR Embedded Workbench for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_iar_user_guide.pdf).

Command line

If you prefer to use the CLI, open the appropriate terminal, and navigate to the project directory. On Windows, use the command-line 'modus-shell' program; on Linux and macOS, you can use any terminal application. From there, you can run various make commands.

For more details, see the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Operation

This example bundles two applications: the bootloader application run by the CM0+ core and the DFU application run by the CM7 core. Build and program the applications in the following order. Do not start building the applications. Follow the step-by-step instructions.

Step-by-step instructions

Connect the board to your PC using the provided USB cable through the KitProg3 USB connector.
Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud.
Install the dependent modules for the imgtool Python module for image signing and key management.

MCUboot already includes this module but not the dependent modules. Do the following:
1. Open a CLI terminal and navigate to the <mtb_shared>/mcuboot/<tag>/scripts directory.
  
  On Windows, use the command-line modus-shell program provided in the ModusToolbox™ installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ tools. You can access it by typing modus-shell in the search box in the Windows menu.
  
  In Linux and macOS, you can use any terminal application.
2. Run the following command to ensure the required modules are installed.
```
python -m pip install -r requirements.txt
```
  Note: For Linux and macOS platforms, use python3 instead of python in this command.
To ensure that you are using the correct 'CySecureTools' version, run the following command:
```
python -m pip install --upgrade cysecuretools
```
Note:
- Follow Step 5 and Step 6 to build and program the applications separately by using CLI.
- Follow Step 7 to build and program combined image for both the applications by using CLI or Eclipse IDE.
Build and program the bootloader application using the CLI.

Note: By default, the protection state is set to be secure. For authentication, in the pre-build, this code example will automatically generate the cy_si_key.c file using the default cypress-test-rsa2k.pub key. In the post-build steps, this code example will automatically generate the secure image by signing the image using the default cypress-test-rsa2k.pem key. The default cypress-test-rsa2k keys are present in the <application>/keys folder. See Generate permanent and public keys for edge protect bootloader authentication under Generating a key pair for generating a new key pair.

To change the mode to a normal protection state, set the USE_SECURE_MODE_FOR_MCUBOOT variable to '0' in the <application>/user_config.mk file.

From the terminal, go to <application>/bootloader_cm0p and execute the make program_proj -j8 command to build and program the bootloader application.

Example:
```
make program_proj -j8
```
After programming, once the bootloader has successfully booted, confirm that the UART terminal displays a message as shown in Figure 1.

Figure 1. Booting with no bootable image
Build and program the DFU application in the BOOT mode using the CLI.

Note: I2C is configured as the default DFU transport. To change the DFU transport, edit the <application>/user_config.mk file to set SELECTED_TRANSPORT=<DFU_TRANSPORT>.

To change the default DFU transport configurations according to the use case, see DFU transport configurations.

From the terminal, go to <application>/dfu_cm7 and execute the make program_proj -j8 command to build and program the application using the default DFU transport. You can specify a transport manually:
```
make program_proj -j8 SELECTED_TRANSPORT=<DFU_TRANSPORT>
```
Example:
```
make program_proj -j8 SELECTED_TRANSPORT=UART
```
After programming, the bootloader starts automatically. The bootloader validates the boot image. If the validation is successful, the bootloader will let CM7 run the DFU application. The DFU application will wait for the DFU Host Tool command. Confirm that the user LED 1 toggles approximately at a one second interval and the UART terminal displays a message as shown in Figure 2.

Figure 2. Booting with the DFU app in the BOOT mode and upgrade process is OVERWRITE

Figure 3. Booting with the DFU app in the BOOT mode and upgrade process is SWAP
Build and program the combined image for bootloader and DFU applications.
Using Eclipse IDE
1. Select the application project in the Project Explorer.
2. In the Quick Panel, scroll down, and click Build <Application name>.
In other IDEs

Follow the instructions in your preferred IDE.
Using CLI

From the terminal, go to <application> and execute the make program_proj -j8 command to build and program the application using the default DFU transport. You can specify a transport manually:
```
make program -j8 SELECTED_TRANSPORT=<DFU_TRANSPORT>
```
Example:
```
make program -j8 SELECTED_TRANSPORT=UART
```
After programming, once the bootloader has successfully booted, the bootloader validates the boot image. If the validation is successful, the bootloader will let CM7 run the DFU application. The DFU application will wait for the DFU Host Tool command. Confirm that the user LED 1 toggles approximately at a one second interval and the UART terminal displays a message as shown in Figure 4.

Figure 4. Booting with the DFU app in the BOOT mode and upgrade process is OVERWRITE
Build (Do not program) the DFU application in the UPGRADE mode.

Note: BOOT is configured as the default image type. To change the image type, edit the <application>/user_config.mk to set IMG_TYPE=UPGRADE.
Using Eclipse IDE
1. Select the 'dfu_cm7' application in the Project Explorer.
2. Edit the user_config.mk file and update the value of the IMG_TYPE variable to UPGRADE.
3. In the Quick Panel, scroll down, and click Build <Application name>.
Using CLI

From the terminal, go to <application>/dfu_cm7 directory and execute the following command to build the application using the default toolchain to the default target:
```
make build_proj -j8 IMG_TYPE=UPGRADE
```
Perform the Device Firmware Upgrade using the DFU Host Tool:
1. Open the DFU Host Tool. Connect to the board using the transport configured.
2. Select dfu_cm7.hex. By default, it is generated in the <application>/dfu_cm7/build/UPGRADE/<TARGET>/<CONFIG> directory on a successful build.
3. Select an appropriate port based on the transport (SELECTED_TRANSPORT) configured in the DFU application. I2C is the default transport configuration. Select 400 kHz speed, set the address to 12, and then click Program.
4. Observe the image download progress status on the progress bar and wait for the download to complete.
  
  Note: See DFU Host Tool documentation for further details on selecting a port and configuring it for communication based on the transport enabled in the bootloader.
  
  Figure 5. Downloading the application using the DFU Host Tool
  
  After a successful download, the DFU application will do a soft reset.
After a soft reset, the bootloader starts automatically. The bootloader validates the upgrade image and upgrades the image by copying the image from the secondary slot to the primary slot. Then the bootloader lets CM7 run the upgraded image.
1. For an overwrite-based upgrade, confirm that the user LED 2 toggles approximately at the one second interval and the UART terminal displays the message as shown in Figure 6.
  
  Figure 6. Booting the DFU app in the UPGRADE mode after successful OVERWRITE operation
2. For a swap-based upgrade, enter 'Y' in the UART terminal to make the upgrade image as the permanent primary image or enter 'N' to revert back to the boot image. In case of the 'N' response, confirm that the boot image boots on the next reset. Confirm that the user LED 1 or 2 toggles approximately at the one second interval according to your response, and the UART terminal displays the message as shown in Figure 7.
  
  Figure 7. Booting the DFU app in the UPGRADE mode after successful SWAP operation with response YES
  
  Figure 8. Booting the DFU app in the UPGRADE mode after successful SWAP operation with response NO

Note: Once the secure protection state is implemented on the device, the device will boot only the secure image. If you want to switch to the normal protection state, erase the TOC2 structure and public key content on the flash. For erasing, run OpenOCD script on the device and set the variable USE_SECURE_MODE_FOR_MCUBOOT to '0' in the <application>/user_config.mk file, and then build and program the edge protect bootloader on the device.

Note: You can build the combined image for bootloader and DFU applications using the make build CLI command in the <application> directory but during the linking stage there might be an error stating multiple definitions of symbols for DFU application for BOOT and UPGRADE image. Currently, the solution to the problem has been addressed in the following code section of the <application>/dfu_cm7/Makefile which ignores the build artifacts of the other IMG_TYPE. For example, If BOOT is selected as IMG_TYPE then <application>/dfu_cm7/build/UPGRADE build directory artifacts will be ignored during the compilation and linking of the BOOT image.

  ```
  ifeq ($(IMG_TYPE), BOOT)
  CY_IGNORE+=build/UPGRADE
  else
  ifeq ($(IMG_TYPE), UPGRADE)
  CY_IGNORE+=build/BOOT
  endif
  endif
  ```

For programming the individual builds of the bootloader and DFU applications, use the make program_proj CLI command as shown in the preceding steps.

Debugging

You can debug the example to step through the code.

In Eclipse IDE

Use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.

In other IDEs

Follow the instructions in your preferred IDE.

Design and implementation

Overview

This code example consists of DFU middleware which downloads (secondary slot) the image through serial interface via DFU Host Tool and reset the device. During reset, the bootloader authenticates the downloaded image and moves it into the primary slot to boot the image.

Boot sequence

Figure 9 shows how the CM0+ operation starts from reset. After reset, CM0+ starts executing from ROM boot. ROM boot validates the SFlash. After the validation, execution jumps to flash boot and configures DAP as required by the protection state. Notice the color coding that depicts the memory type where the data and code resides.

Flash boot then validates the first application listed in TOC2 and jumps to its entry point if validated. In the secure protection state, the first user application is the secure image. After the secure image configures the hardware to secure the system, it validates the main user application if required.

If the SFlash or secure image is found to be invalid or corrupted, the device enters into a DEAD protection state and stays in the DEAD protection state until the device is reset.

Note: If the device enters into the DEAD protection state, it cannot transition to the RMA lifecycle stage. Failure analysis cannot be performed in such cases. TOC2 is an area in the SFlash used to store pointers to two application blocks: the secure image and the main user application. It also contains some boot parameters that can be set by the system designer.

Figure 9. Boot sequence flow

MCUboot basics

MCUboot library helps implement secured bootloader applications for 32-bit MCUs. The MCUboot repo on GitHub also includes two applications, MCUbootApp and BlinkyApp for XMC7000 devices.

MCUboot works by dividing the flash into two slots per image: primary and secondary. The first version of the application is programmed into the primary slot during production. A firmware update (DFU) application running in the device receives the upgrade image over an I2C, UART, SPI of CAN FD serial communication interface and places it in the secondary slot. This slot-based partition helps in read/write-protecting the primary slot from a less-privileged application.

Typically, a bootloader application executes in secured mode and is privileged to access the primary slot, while a less-privileged application, such as an upgrade application, cannot access the primary slot but can access the secondary slot.

MCUboot always boots from the primary slot and copies the image from the secondary slot into the primary slot when an upgrade is requested. The upgrade can be either overwrite-based or swap-based. In an overwrite-based upgrade, the image in the primary slot is lost and there is no way to roll back, if the new image has an issue. In a swap-based upgrade, the images are swapped between the two slots, and rollback is possible. In this case, MCUboot makes use of an additional area in the flash called the scratch area for reliable swapping. MCUboot for the XMC7000 supports both swap-based and overwrite-based upgrades.

For a swap-based upgrade, each image slot contains the metadata used by MCUboot to determine the current state and actions to take during the current boot operation. In case of an upgrade image, the img_ok field is updated by the application to make the current image permanent in the primary slot. See the image trailer for more details.

MCUboot implements reset recovery and resumes the copy operation if a reset or power failure occurs during the operation. Figure 10 shows the execution flow of the edge protect bootloader application.

Figure 10. Edge protect bootloader application flow

Overwrite and swap-based upgrades for the XMC7000 device

There are two types of upgrade processes supported by the XMC7000 device.

For an overwrite-based upgrade, the secondary image is copied to the primary slot after successful validation. There is no way to revert the upgrade if the secondary image is inoperable.
For a swap-based upgrade, images in the primary and secondary slots are swapped. The upgrade can be reverted if the secondary image does not confirm its operation.

See the "Swap status partition description" section of the MCUbootApp documentation and MCUboot design documentation for more details.

DFU application flow

The DFU application demonstrates DFU operations based on the DFU middleware library. Figure 11 shows the execution flow of the DFU application.

Figure 11. DFU application flow

DFU interfaces

The DFU application supports I2C, UART, SPI, and CAN FD interfaces for communicating with the DFU Host Tool. See Table 1 for the default configuration details. You can change these default configurations according to the use case. However, you must ensure that the configuration of the DFU Host Tool matches the DFU application. See the DFU transport configurations to change the default DFU transport configurations according to the use case in our DFU application.

Table 1. Default DFU transport: I2C configurations

DFU transport: I2C	Default	Description
Mode	Slave	Device acts as a slave
Address	12	7-bit slave device address
Data rate	400 kbps	DFU supports standard data rates from 50 kbps to 1 Mbps

Table 2. Default DFU transport: UART configurations

DFU transport: UART	Default	Description
Mode	Standard	Standard, SmartCard, and IrDA are supported UART modes in SCB
Baud rate (bps)	115200	Supports standard baud rates from 19200 to 115200
Data width	8 bits	Standard frame
Parity	None	Standard frame
Stop bits	1 bit	Standard frame
Bit order	LSB first	Standard frame

Table 3. Default DFU transport: SPI configurations

DFU transport: SPI	Default	Description
Mode	Slave	Device acts as a slave
Shift direction	MSB first	default direction set as MSB first
Clock speed	1 MHz	DFU supports 1 MHz, 2 MHz, 4 MHz, and 6 MHz SPI clock speed
Mode	Mode 00	default mode set as Mode 00

DFU transport: CANFD

See the CAN FD section in Device Firmware Update (DFU) Middleware Library 5.2.

DFU transport configurations

How to change the configuration for DFU I2C transport

Hardware configuration

Uses the board's default configuration.

Software configuration

To change the default configuration, edit the <application>/dfu_cm7/imports/dfu/config/COMPONENT_CAT1/COMPONENT_DFU_I2C/transport_i2c.c file according to the use case.

How to change the configuration for DFU UART transport

Hardware configuration

Connect the RX and TX pins of MiniProg4 to P20_4 and P20_3 on the board respectively. Additionally, connect the VTARG and GND of MiniProg4 to 3.3 V and GND on the board respectively.

Software configuration

To change the default configuration, edit the <application>/dfu_cm7/imports/dfu/config/COMPONENT_CAT1/COMPONENT_DFU_UART/transport_uart.c file according to the use case.

How to change the configuration for DFU SPI transport

Hardware configuration

For XMC7200 kit -> KIT_XMC72_EVK and KIT_XMC72_EVK_MUR_43439M2, connect the MISO, MOSI, CLK, and CS pins of MiniProg4 to P10_0, P10_1, P10_2, and P10_3 on the board respectively. Additionally, connect the VTARG and GND of MiniProg4 to 3.3 V and GND on the board respectively.

For XMC7100 kit, connect the MISO, MOSI, CLK, and CS pins of MiniProg4 to P13_0, P13_1, P13_2, and P13_3 on the board respectively. Additionally, connect the VTARG and GND of MiniProg4 to 3.3 V and GND on the board respectively.

Software configuration

To change the default configuration, edit the <application>/dfu_cm7/imports/dfu/config/COMPONENT_CAT1/COMPONENT_DFU_SPI/transport_spi.c file according to the use case.

How to change the configuration for CAN FD transport

Hardware configuration

For XMC7200 kit, connect the CANL, CANH, and GND pins (J19) on the board to CAN-L, CAN-H, and CAN-GND pins of PCAN-USB Pro module (USB to CAN interface).

Sortware configuration

To change the default configuration, edit the <application>/dfu_cm7/imports/dfu/config/COMPONENT_CAT1/COMPONENT_DFU_CANFD/transport_canfd.c file according to the use case.

Memory map/partition

Figure 12 shows a typical memory map or partition used with MCUboot. The partitions need not be contiguous in memory as it is possible to configure the offset and size of each partition. However, the offset and the size must be aligned to the boundary of a flash row or sector. For XMC7000 MCUs, the size of a flash row is 512 bytes. The partition can only be in the internal flash (external flash is not supported at the moment).

The memory partition is described or defined through a memory map (a JSON file; see the <application>/flashmap directory for examples). It is important for the bootloader and DFU applications to agree on the memory map. This example uses an <application>/user_config.mk file between the two apps, and the memorymap.mk file is autogenerated from the memory map JSON file so that they can use the same set of memory map parameters. See configuring the default memory map for details.

Figure 12. Typical memory map

Sample memory maps

Following images illustrate the memory maps provided in this code example. The flashmap JSON files are located in the <application>/flashmap directory.

Figure 13. Primary and secondary slots in internal flash

Customizing and selecting the memory map

A memory map, for example, is selected by changing the value of the FLASH_MAP variable in the <application>/user_config.mk file to the desired JSON file name.

See the How to modify memory map section to understand how to customize the memory map to the use case.

During the pre-build stage, the memorymap JSON file is automatically parsed by the <application>/scripts/memorymap_xmc7000.py Python script to generate the following files:

memorymap.mk, memorymap.c, and memorymap.h files in the bootloader application.
memorymap.mk, memorymap.c, and memorymap.h files in the DFU application.

The parameters generated in the memorymap.mk file are used in the DEFINES and LDFLAGS variables of the application Makefile.

Note: While modifying the memory map, make sure the primary slot, secondary slot, and bootloader application flash sizes are appropriate. This code example automatically matches the application linker script's flash memory allocation to the memorymap.c and user_config.mk files.

Customizing the RAM area of CM0+ and CM7 applications

Modify the BOOTLOADER_APP_RAM_SIZE to change the CM0+ ram size and the USER_APP_RAM_SIZE to change the CM7 ram size in the <application>/user_config.mk file.

Note: Ensure the RAM areas of the CM0+-based bootloader and the CM7-based DFU application do not overlap.

Memory (stack) corruption of CM0+ application can cause failure if SystemCall-served operations are invoked from CM7.

Configuring make variables

This section explains the important make variables that affect the edge protect bootloader functionality. Some of these variables are autogenerated from the memorymap JSON file and some variables can be updated directly in the Makefile or passed along with the make build command.

Common make variables

These variables are common to both the bootloader and DFU applications, it is configured via <application>/user_config.mk file.

Table 4. Common make variables

Variable	Default value	Description
`FLASH_MAP`	xmc7000_overwrite_single.json	Valid values: `xmc7000_overwrite_single.json`, `xmc7000_swap_single.json`. Flashmap JSON file name.
`SIGN_KEY_FILE`	cypress-test-ec-p256	Name of the private and public key files (the same name is used for both keys).
`APP_CORE_ID`	0	Bootloader designed like user application can either run on CM7_0 or CM7_1 cores. By default, the DFU application run on the CM7_0 core. Can change the core by setting the value to `1`.
`BOOTLOADER_SIZE`	Autogenerated	Flash size of the bootloader application run by CM0+. In the linker script for the bootloader application (CM0+), the `LENGTH` of the `cm0_flash` region is set to this value. In the linker script for the DFU application (CM7), the `ORIGIN` of the `flash` region is offset to this value.
`BOOTLOADER_APP_RAM_SIZE`	0x20000	RAM size of the bootloader application run by CM0+. In the linker script for the bootloader application (CM0+), the `LENGTH` of the `cm0_ram` region is set to this value. In the linker script for the DFU application (CM7), the `ORIGIN` of the `ram` region is offset to this value, and the `LENGTH` of the `ram` region is calculated based on this value.
`USER_APP_RAM_SIZE`	0x60000	RAM size of the user application run by CM7. In the linker script for the DFU application (CM7), the `LENGTH` of the `ram` region is set to this value.
`SLOT_SIZE`	Autogenerated	Size of the primary slot and secondary slot. i.e., the flash size of the DFU application run by CM7.
`MCUBOOT_HEADER_SIZE`	0x400	Size of the MCUboot header. Must be a multiple of 1024 (see the following note). Used in the following places: 1. In the linker script for the DFU application (CM7), the starting address of the `.text` section is offset by the MCUboot header size from the `ORIGIN` of the `flash` region. This is to leave space for the header that the imgtool inserts later during the post-build steps. 2. Passed to the imgtool while signing the image. The imgtool fills the space of this size with 0xFF (depending on internal or external flash) and then adds the actual header from the beginning of the image.
`MAX_IMG_SECTORS`	Autogenerated	Maximum number of flash sectors (or rows) per image slot for which swap status is tracked in the image trailer.
`MCUBOOT_IMAGE_NUMBER`	Autogenerated	The number of images supported in the case of multi-image bootloading. Multi-image bootloading is not supported at the moment for XMC7000.
`PRIMARY_IMG_START`	Autogenerated	Starting address of primary slot.
`SECONDARY_IMG_START`	Autogenerated	Starting address of secondary slot.
`USE_OVERWRITE`	Autogenerated	The value is '1' when scratch and status partitions are not defined in the flashmap JSON file. Note: These variables are defined in the memorymap.mk file.

Note: The value of MCUBOOT_HEADER_SIZE must be a multiple of 1024 because the CM7 image begins immediately after the MCUboot header and it begins with the interrupt vector table. For the XMC7000 device, the starting address of the interrupt vector table must be 1024-bytes aligned.

Number of bytes to be aligned to = Number of interrupt vectors x 4 bytes

i.e., 1024 = 256 vectors x 4 bytes (32-bit address) per vector.

Bootloader application make variables

These variables are configured via <application>/user_config.mk file.

Table 5. Bootloader application make variables

Variable	Default value	Description
`USE_SECURE_MODE_FOR_MCUBOOT`	1	By default, the protection state is a secure protection state. To change the state to a normal protection state, set the variable to '0'.
`SECURE_MODE_KEY_FILE`	cypress-test-rsa2k	Name of the private and public key files (the same name is used for both keys).
`USE_SW_DOWNGRADE_PREV`	1	Downgrade prevention, Value is '1' to avoid older firmware versions for upgrade.
`USE_BOOTSTRAP`	1	When set to '1' and Swap mode is enabled, the application in the secondary slot will overwrite the primary slot if the primary slot application is invalid.

DFU application make variables

These variables are configured via <application>/user_config.mk file.

Variable	Default value	Description
`IMG_TYPE`	BOOT	Valid values: `BOOT`, `UPGRADE` BOOT: Use when the image is built for the primary slot. The `--pad` argument is not passed to the imgtool. UPGRADE: Use when the image is built for the secondary slot. The `--pad` argument is passed to the imgtool. Also, the DFU application defines different user LED toggles depending on whether the image is BOOT type or UPGRADE type.
`SELECTED_TRANSPORT`	I2C	Valid values: I2C, UART, SPI, CANFD The DFU supports I2C, UART, SPI, and CANFD interfaces for communicating with the DFU Host Tool. These DFU transport can be changed according to the use case.
`HEX_START_ADDR`	Autogenerated	if the image is BOOT, it will set the value as a `PRIMARY_IMG_START`and if the image is UPGRADE, it will set the value as a `SECONDARY_IMG_START`.
`APP_VERSION_MAJOR` `APP_VERSION_MINOR` `APP_VERSION_BUILD`	1.0.0 if `IMG_TYPE=BOOT` 2.0.0 if `IMG_TYPE=UPGRADE`	Passed to the imgtool with the `-v` option in MAJOR.MINOR.BUILD format, while signing the image. Also available as macros to the application with the same names. Note: These variables are configured via dfu_cm7/Makefile.mk.

Security

Edge protect bootloader application authentication

XMC7000 secure boot configuration description

Flash boot handles the edge protect bootloader image authentication. When the image is valid, flash boot boots the bootloader image. You can configure the flash boot to run either in secure (secure protection state) or normal mode (normal protection state):

Normal protection state: Flash boot boots the bootloader without authentication.
Secure protection state: Flash boot boots the bootloader once authentication is successful. If the bootloader image is found to be invalid or corrupted, the device enters a DEAD protection state and stays in the state until the device is reset.

The only difference between these two states is that the secure protection state requires additional configurations like TOC2, flash boot image header, and object trailer.

Edge protect bootloader application Makefile supports secure image build configuration for XMC7000.

To prepare a secure bootloader image, edit the variable USE_SECURE_MODE_FOR_MCUBOOT=1 in the <application>/user_config.mk file and need to configure the public key and specify the appropriate parameters for the TOC2 structure in the cy_si_config.c and cy_si_key.c files.

By default, the protection state is set to be secure. For authentication, in the pre-build, this code example will automatically generate the cy_si_key.c file using the default cypress-test-rsa2k.pub key. In the post-build, this code example will automatically generate the secure image by signing the image using the default cypress-test-rsa2k.pem key. The default cypress-test-rsa2k keys are present in the <application>/keys folder.

The XMC7000 internal flash boot module can be used in secure configuration. See AN234802 for a complete description and instructions for configuring a secure boot.

See Boot sequence for the boot sequence of the secure protection state.

This example includes a sample key pair under the <application>/keys directory. You must not use this key pair in your end product. See Generate permanent and public keys for edge protect bootloader under Generating a key pair for generating a new key pair.

DFU application authentication

Edge protect bootloader checks the image integrity with SHA256, and image authenticity with EC256 digital signature verification. The bootloader application enables ECDSA SECP256R1 (EC256) by default. MCUboot uses the Mbed TLS library for cryptography.

Note: Encryption image and hardware crypto acceleration are not supported at the moment for XMC7000.

MCUboot verifies the signature of the image in the primary slot before booting every time MCUBOOT_VALIDATE_PRIMARY_SLOT is defined. it also verifies the signature of the image in the secondary slot before copying it to the primary slot.

The bootloader application enables image authentication by uncommenting the following lines in the <application>/bootloader_cm0p/libs/mcuboot/boot/cypress/MCUbootApp/config/mcuboot_config/mcuboot_config.h file:

#define MCUBOOT_SIGN_EC256
.
.
.
#define MCUBOOT_VALIDATE_PRIMARY_SLOT

When these options are enabled, the public key is embedded within the bootloader application. The DFU application is signed using the private key during the post-build steps. The imgtool Python module included in the MCUboot repository is used for signing the image.

This code example includes a sample key pair under the <application>/keys directory. You must not use this key pair in your end product. See Generate permanent and public keys for DFU application authentication under Generating a key pair for generating a new key pair.

Generating a key pair

Command to generate permanent and public keys for edge protect bootloader authentication

Use CySecureTools to generate the keys.

Generate the permanent and public keys:

cysecuretools -t $(PLATFORM) create-key --key-type RSA2048 -o $(<application>)/keys/cypress-test-rsa2k.pem $(<application>)/keys/cypress-test-rsa2k.pub --format PEM

Use the following command to generate cy_si_key.c file:

cysecuretools convert-key -k $(<application>)/keys/cypress-test-rsa2k.pub -o $(mtb_stared_path)/platforms/utils/XMC7000/cy_si_key.c --fmt secure_boot --endian little

Note: The command to generate the cy_si_key.c file is already implemented in the bootloader application. Basically, the cy_si_key.c file public key context automatically matches with the cypress-test-rsa2k_gen.pub file.

Command to generate permanent and public keys for DFU application authentication

You can use the imgtool Python module to generate the keys.

Generate the private key:

python $(IMGTOOL_PATH)/imgtool.py keygen -k $(<application>)/keys/cypress-test-ec-p256.pem -t ecdsa-p256

Generate the public key:
```
python $(IMGTOOL_PATH)/imgtool.py getpub -k $(<application>)/keys/cypress-test-ec-p256.pem > $(<application>)/keys/$cypress-test-ec-p256.pub
```
Note: You can create new keys by simply uncommenting the following in the PREBUILD_VAR variable present in the <application>/bootloader_cm0p/Makefile file:
```
`$(MAKE) gen_key_ecc256;` 
`$(MAKE) gen_key_rsa2k;` 
```
Important: First, run the command to generate cypress-test-ec-p256 keys, and then run the command to generate the cy_si_key.c file in the <application>/bootloader_cm0p/Makefile file, as follows:
```
```
PREBUILD_VAR=+\
$(MAKE) generate_flashmap_cm0p;\
$(MAKE) gen_key_ecc256;\
$(MAKE) gen_key_rsa2k;\
$(MAKE) gen_cy_si_key_source_file;
```
```

OpenOCD script

To recover the device from secure mode to normal mode

To erase the TOC2 structure and public key content on the flash, run the following OpenOCD script on the device:

Create a file named xmc7000_flash_erase.cfg in the C:/Users/ModusToolbox/tools_<version>/openocd/scripts/interface directory and copy the below content to the xmc7000_flash_erase.cfg file. Open the command prompt in the C:/Users/ModusToolbox/tools_<version>/openocd/bin directory and run the command openocd -s ../scripts -f ../scripts/interface/xmc7000_flash_erase.cfg.

source [find interface/kitprog3.cfg]
set ENABLE_ACQUIRE 0
set ACQUIRE_TIMEOUT 2000

transport select swd
source [find target/cat1c.cfg]
cat1c sflash_restrictions 1

init; reset init;

flash erase_address     0x17007C00              0x00000200
flash erase_address     0x17006400              0x00000C00
flash erase_address     0x14030000              0x10000
flash erase_address     0x14000000              0x30000

reset;
shutdown

Pre-build and post-build steps

Bootloader application: Pre-build steps

The pre-build steps are specified through the PREBUILD variable in <application>/bootloader_cm0p/Makefile.

Generate memorymap source and memorymap.mk files from memorymap JSON file.
Generate the cy_si_key.c file; basically, the cy_si_key.c file's public key context automatically matches that of cypress-test-rsa2k.pub file.

Bootloader application: Post-build steps

The post-build steps are specified through the POSTBUILD variable in <application>/bootloader_cm0p/Makefile.

In the secure protection state, the bootloader image is digitally signed by the cypress-test-rsa2k key.

Note: In the secure protection state, flash boot checks the image's authenticity with RSA2048 digital signature verification.

DFU application: Pre-build steps

The pre-build steps are specified through the PREBUILD variable in <application>/dfu_cm7/Makefile.

Generate memorymap source and memorymap.mk files from memorymap JSON file.

DFU application: Post-build steps

The post-build steps are specified through the POSTBUILD variable in <application>/dfu_cm7/Makefile.

The DFU image will be digitally signed by cypress-test-ec-p256 key.

Note: Edge protect bootloader checks the image integrity with SHA256, and image authenticity with EC256 digital signature verification.

Design notes

Both the bootloader and DFU applications redirect the log to the serial port (UART). Both apps use the same RX/TX pins and the retarget-io driver to communicate with the USB-to-UART bridge provided by KitProg3. The bootloader application runs first, initializes the retarget-io driver, prints the messages, deinitialize retarget-io, and then boots the DFU application and enters deep sleep mode. Then the DFU application initializes the same retarget-io driver, prints messages, deinitializes retarget-io, and soft-resets the device. There is no issue since the log does not print on both the cores at the same time.
Currently, the CM0+ core supports only the PDL flash (API) driver. The edge protect bootloader application uses the PDL flash (API) driver.

Code example design

XMC7000 is a multi-core device; this code example is designed to run the bootloader on the CM0+ core and the DFU application on the CM7_0 or CM7_1 core. The bootloader on CM0+ always checks for a valid application binary. On every power cycle, it transfers control to the CM7_0 or CM7_1 core to execute the DFU application.

Flash boot always checks for a valid bootloader application binary on every power cycle to transfer control to the CM0+ core to execute the bootloader application.

Folder structure

This application has a different folder structure because it contains the firmware for CM7 and CM0+ applications as follows:

|-- <application>                   # project directory
    |-- bootloader_cm0p/            # CM0+ application folder
        |-- deps/                   # Contains application dependence middleware links
        |-- source/                 # Contains source file
        |-- Makefile                # Top-level cm0p application Makefile
    |-- dfu_cm7/                    # CM7 application folder
        |-- deps/                   # Contains application dependence middleware links
        |-- source/                 # Contains source files
        |-- Makefile                # Top-level cm7 application Makefile
    |-- flashmap/                   # Contains flashmap JSON files
    |-- keys/                       # Contains keys for bootloader and user application authentication
    |-- scripts/                    # Contains script to generate the memorymap source files and Makefile
    |-- templates/                  # Contains modified linker script for our project
    |-- common_libs.mk              # Including the MCUboot middleware source and header files
    |-- common.mk                   # Common Makefile
    |-- common_app.mk               # Common application Makefile
    |-- Makefile                    # Top-level application Makefile
    |-- user_config.mk              # User configuration Makefile

Resources and settings

Table 7. Bootloader resources

Resource	Alias/object	Purpose
UART (HAL)	cy_retarget_io_uart_obj	UART HAL object used by Retarget-IO for the Debug UART port

Table 8. DFU application resources

Resource	Alias/object	Purpose
UART (HAL)	cy_retarget_io_uart_obj	UART HAL object used by Retarget-IO for the Debug UART port
I2C (HAL)	DFU_I2C	I2C slave driver to communicate with the DFU Host Tool
UART(HAL)	DFU_UART	UART driver to communicate with the DFU Host Tool
SPI (HAL)	DFU_SPI	SPI slave driver to communicate with the DFU Host Tool
CAN FD(HAL)	DFU_CANFD	CAN FD slave driver to communicate with the DFU Host Tool
GPIO (HAL)	CYBSP_USER_LED and CYBSP_USER_LED2	User LED 1 and 2

Related resources

Resources	Links
Application notes	AN234334 – Getting started with XMC7000 MCU on ModusToolbox™ AN234023 – Smart I/O usage setup in XMC7000 family
Code examples	Using ModusToolbox™ on GitHub
Device documentation	XMC7000 MCU documents
Development kits	Select your kits from the Evaluation board finder.
Libraries on GitHub	mtb-pdl-cat1 – Peripheral Driver Library (PDL) mtb-hal-cat1 – Hardware Abstraction Layer (HAL) library
Middleware on GitHub	mcu-middleware – Links to all MCU middleware MCUboot – Open-source library enabling the development of secure bootloader applications for 32-bit MCUs DFU middleware library – Provide an SDK for updating firmware images via wired (I2C/UART/SPI) or wireless (OTA) retarget-io – Utility library to retarget STDIO messages to a UART port
Tools	ModusToolbox™ – ModusToolbox™ software is a collection of easy-to-use libraries and tools enabling rapid development with Infineon MCUs for applications ranging from wireless and cloud-connected systems, edge AI/ML, embedded sense and control, to wired USB connectivity using PSOC™ Industrial/IoT MCUs, AIROC™ Wi-Fi and Bluetooth® connectivity devices, XMC™ Industrial MCUs, and EZ-USB™/EZ-PD™ wired connectivity controllers. ModusToolbox™ incorporates a comprehensive set of BSPs, HAL, libraries, configuration tools, and provides support for industry-standard IDEs to fast-track your embedded application development.

Other resources

Infineon provides a wealth of data at www.infineon.com to help you select the right device, and quickly and effectively integrate it into your design.

For XMC™ MCU devices, see 32-bit XMC™ industrial microcontroller based on Arm® Cortex®-M.

Document history

Document title: CE237943 – XMC7000: OTW firmware upgrade

Version	Description of change
1.0.0	New code example
1.1.0	Updated to support ModusToolbox™ v3.2
2.0.0	Updated to support MCUboot middleware v1.9.1 Added support for KIT_XMC72_EVK_MUR_43439M2 and KIT_XMC71_EVK_LITE_V1 kits
2.0.1	Disabled D-cache for XMC7000 based BSPs
2.1.0	Enabled D-cache support for XMC7000 devices Added support for CAN FD transport
2.2.0	Updated to support NINJA based build flow

All referenced product or service names and trademarks are the property of their respective owners.

The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc., and any use of such marks by Infineon is under license.

© Cypress Semiconductor Corporation, 2023-2024. This document is the property of Cypress Semiconductor Corporation, an Infineon Technologies company, and its affiliates ("Cypress"). This document, including any software or firmware included or referenced in this document ("Software"), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress's patents that are infringed by the Software (as provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation of the Software is prohibited.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress shall have no liability arising out of any security breach, such as unauthorized access to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR GUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL BE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (collectively, "Security Breach"). Cypress disclaims any liability relating to any Security Breach, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any Security Breach. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this information and any resulting product. "High-Risk Device" means any device or system whose failure could cause personal injury, death, or property damage. Examples of High-Risk Devices are weapons, nuclear installations, surgical implants, and other medical devices. "Critical Component" means any component of a High-Risk Device whose failure to perform can be reasonably expected to cause, directly or indirectly, the failure of the High-Risk Device, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any use of a Cypress product as a Critical Component in a High-Risk Device. You shall indemnify and hold Cypress, including its affiliates, and its directors, officers, employees, agents, distributors, and assigns harmless from and against all claims, costs, damages, and expenses, arising out of any claim, including claims for product liability, personal injury or death, or property damage arising from any use of a Cypress product as a Critical Component in a High-Risk Device. Cypress products are not intended or authorized for use as a Critical Component in any High-Risk Device except to the limited extent that (i) Cypress's published data sheet for the product explicitly states Cypress has qualified the product for use in a specific High-Risk Device, or (ii) Cypress has given you advance written authorization to use the product as a Critical Component in the specific High-Risk Device and you have signed a separate indemnification agreement.
Cypress, the Cypress logo, and combinations thereof, ModusToolbox, PSoC, CAPSENSE, EZ-USB, F-RAM, and TRAVEO are trademarks or registered trademarks of Cypress or a subsidiary of Cypress in the United States or in other countries. For a more complete list of Cypress trademarks, visit www.infineon.com. Other names and brands may be claimed as property of their respective owners.

Name		Name	Last commit message	Last commit date
Latest commit History 6 Commits
bootloader_cm0p		bootloader_cm0p
dfu_cm7		dfu_cm7
flashmap		flashmap
images		images
keys		keys
scripts		scripts
templates		templates
.gitignore		.gitignore
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
common.mk		common.mk
common_app.mk		common_app.mk
common_libs.mk		common_libs.mk
user_config.mk		user_config.mk

License

Infineon/mtb-example-xmc7000-otw-firmware-upgrade

Folders and files

Latest commit

History

Repository files navigation

XMC7000: OTW firmware upgrade

Requirements

Supported toolchains (make variable 'TOOLCHAIN')

Supported kits (make variable 'TARGET')

Hardware setup

Software setup

Using the code example

Create the project

Open the project

Operation

Step-by-step instructions

Debugging

Design and implementation

Overview

Boot sequence

MCUboot basics

Overwrite and swap-based upgrades for the XMC7000 device

DFU application flow

DFU interfaces

DFU transport configurations

How to change the configuration for DFU I2C transport

Hardware configuration

Software configuration

How to change the configuration for DFU UART transport

Hardware configuration

Software configuration

How to change the configuration for DFU SPI transport

Hardware configuration

Software configuration

How to change the configuration for CAN FD transport

Hardware configuration

Sortware configuration

Memory map/partition

Sample memory maps

Customizing and selecting the memory map

Customizing the RAM area of CM0+ and CM7 applications

Configuring make variables

Common make variables

Bootloader application make variables

DFU application make variables

Security

Edge protect bootloader application authentication

XMC7000 secure boot configuration description

DFU application authentication

Generating a key pair

Command to generate permanent and public keys for edge protect bootloader authentication

Command to generate permanent and public keys for DFU application authentication

OpenOCD script

To recover the device from secure mode to normal mode

Pre-build and post-build steps

Bootloader application: Pre-build steps

Bootloader application: Post-build steps

DFU application: Pre-build steps

DFU application: Post-build steps

Design notes

Code example design

Folder structure

Resources and settings

Related resources

Other resources

Document history

About

Topics

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages