Wrapper for FSBL images

Revision as of 18:12, 17 April 2020 by Registered User (Replaced content with "==Article purpose== This article provides the basic information needed to start using the application tool '''stm32wrapper4dbg'''. It explains how to use the tool to wrap...")

1. Article purpose[edit source]

This article provides the basic information needed to start using the application tool stm32wrapper4dbg.

It explains how to use the tool to wrap an existing FSBL image and create a debug image, suitable for attaching a debugger at boot.

This article covers also the case of device secured.


2. Introduction[edit source]

The following table provides a brief description of the tool, as well as its availability depending on the software packages:

Yes: this tool is either present (ready to use or to be activated), or can be integrated and activated on the software package.

No: this tool is not present and cannot be integrated, or it is present but cannot be activated on the software package.

Tool STM32MPU Embedded Software distribution STM32MPU Embedded Software distribution for Android™
Name Category Purpose Starter Package Developer Package Distribution Package Starter Package Developer Package Distribution Package
stm32wrapper4dbg Debugging tools The tool stm32wrapper4dbg wraps a STM32 FSBL image to allows a debugger to halt the boot at the first executable instruction of FSBL.
No* Yes No** No No No
* Cross compile gdb and openocd binaries are required and only available from Developer Package.
** It is recommended to use the Developer Package to run the gdb debug session, which provided all dependencies


3. Installing the stm32wrapper4dbg tool[edit source]

The tool is installed on the host PC as part of the Developer Package.

Note: the tool is also part of the Distribution Package, which automatically creates a wrapped FSBL each time a new FSBL is built.


4. Getting started[edit source]

This chapter describes the two ways for debugging OpenSTLinux BSP components (TF-A, U-Boot and Linux kernel including external modules), Linux applications and Cortex-M4 firmware: by using GDB commands or by using a GDB user interface such as gdbgui, DDD or IDE.

4.1. Prerequisites[edit source]

The target board is up and running.


5. References[edit source]