How to configure U-Boot for your board

This page explains how to configure the U-Boot source for your board.

Many existing ressources [1][2] explain the porting of U-Boot on a new board, this page is only a basic guideline for STM32MP1 Series products.

To summarize, you need to configure U-Boot for your <VENDOR> <BOARD> with the following steps:

  1. add your board device tree: arch/arm/dts/<board>.dts and <board>-u-boot.dtsi
  2. create your own board support directory: board/<vendor>/<board>
  3. add TARGET_<VENDOR> _<BOARD> in Kconfig
  4. create your board defconfig: defconfig/<board>_defconfig
  5. add your configuration file : include/configs/<board>.h

1 Device tree[edit]

Add the board device tree files <board>.dts and <board>-u-boot.dtsi in arch/arm/dts , following the steps below:

  • Copy the Linux kernel device tree in the directory arch/arm/dts : <board>.dts
 dtb-$(CONFIG_STM32MP15x) += \
  • Add a U-Boot addon device tree for your board in the arch/arm/dts directory: <board>-u-boot.dtsi
    This file is automatically included during <board>.dts processing.
    It includes the <soc>-u-boot.dtsi file provided by STMicroelectronics (arch/arm/dts/stm32mp15-u-boot.dtsi for example) and add all the properties on nodes needed by U-Boot (node /config, attibute u-boot,dm-pre-reloc / u-boot,dm-pre-proper).

At this point you can use the generic ST defconfig with the ST board directory, but with your board device tree.

The board-specific features are not correctly managed, but should be sufficient for a simple board derived from ST designs.

For example, on STM32MP15x lines More info.png, you can use the ST stm32mp1 board with your device tree as follows:

 PC $> make stm32mp15_trusted_defconfig
 PC $> make DEVICE_TREE=<board> all

The next steps are required if the ST-generic board does not comply with all of the expected behavioral aspects for your board (for example MAC address not located in OTP, specific PMIC, specific boot command).

1.1 Config node[edit]

Some properties in the 'config' node are also used to dynamically configure the U-Boot behavior in the board device tree as follows:

  • Generic U-Boot configuration, managed in generic code:
    • u-boot,mmc-env-partition = name of partition used to save U-Boot environment
  • Some ST properties only managed in ST board code (in line with LEDs and buttons on STM32 MPU boards); they can only be used if your board reuses this ST board code
    • u-boot,boot-led = name of boot-progress indicator LED
    • u-boot,error-led = name of error indicator LED
    • st,adc_usb_pd = ADC channels used to check USB power supply
    • st,stm32prog-gpios = GPIO used to force STM32CubeProgrammer mode
    • st,fastboot-gpios = GPIO used to force Android Fastboot mode

For example in arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi

   	config {
   		u-boot,boot-led = "heartbeat";
   		u-boot,error-led = "error";
   		u-boot,mmc-env-partition = "ssbl";
   		st,adc_usb_pd = <&adc1 18>, <&adc1 19>;
   		st,fastboot-gpios = <&gpioa 13 GPIO_ACTIVE_LOW>;
   		st,stm32prog-gpios = <&gpioa 14 GPIO_ACTIVE_LOW>;

2 Board subdirectory[edit]

Create your own board support subdirectory = board/<vendor>/<board> and add a Makefile file.

You can add any source files needed for your board.

In this Makefile, you can compile the ST files (in board/st/stm32mp1 or in board/st/common) or just copy them as starting point then modify them.

For example board/dhelectronics/dh_stm32mp1/Makefile uses ST files in ../../st/stm32mp1 directory and local file "board.c"

 obj-y += ../../st/stm32mp1/spl.o

 obj-y += ../../st/stm32mp1/board.o board.o

3 Kconfig[edit]

You need to support your board in Kconfig with a new configuration flag: TARGET_<VENDOR>_<BOARD>

3.1 Arch Kconfig: arch/arm/mach-stm32mp/Kconfig [edit]

  • Select the required option (soc for example : CONFIG_STM32MP15x)
  • Include your board Kconfig in arch one (source "board/<vendor>/<board>/Kconfig")
 	prompt "STM32MP15x board select"
   	bool "<vendor> <board> board"
   	select STM32MP15x
 		target the <vendor> <board> board with SOC STM32MP15x
 		managed by board/<vendor>/<board>
  source "board/st/stm32mp1/Kconfig"
  source "board/dhelectronics/dh_stm32mp1/Kconfig"
  source "board/<vendor>/<board>/Kconfig"

3.2 Board Kconfig: board/<vendor>/<board>/Kconfig[edit]

The mininimal content of this file is:

 config SYS_BOARD
 	default "<board>"
 config SYS_VENDOR
 	default "<vendor>"
 	default "<config>"

See for example board/dhelectronics/dh_stm32mp1/Kconfig .

SYS_CONFIG_NAME is used to select the used configuration file: include/configs/SYS_CONFIG_NAME.h

4 Defconfig[edit]

Add a new defconfig for your board in configs .

  • copy configs/stm32mp15_trusted_defconfig to your "<vendor>_<board>_defconfig"
  • select your new defconfig: make <vendor>_<board>_defconfig"
  • use make menuconfig to change your defconfig
    • remove CONFIG_TARGET_ST_STM32MP15x
    • change CONFIG_DEFAULT_DEVICE_TREE from "stm32mp157c-ev1" to the name of the board device tree: "<board>"
  • save the updated defconfig: make savedefconfig
  • verify and copy the file "defconfig" in configs/<vendor>_<board>_defconfig

See for example the file configs/dh_stm32mp1/stm32mp15_dhcom_basic_defconfig .

5 Configuration file[edit]

The configuration file is the include file in include/configs directory selected in Makefile.autoconf by CONFIG_SYS_CONFIG_NAME .

This file defines the CONFIG_ flags of boards that are not defined with Kconfig.

For example, in this configuration file, you can choose the initial U-Boot environment with CONFIG_EXTRA_ENV_SETTINGS, including the boot command.

For ST boards, CONFIG_SYS_CONFIG_NAME = stm32mp1; the configuration file is include/configs/stm32mp1.h .

This ST configuration file can be:

  • used in your project (with CONFIG_SYS_CONFIG_NAME="stm32mp1")
  • included in your board configuration file (#include "stm32mp1")
  • can be used a starting point for your configuration file (copy and update it).

6 References[edit]