...

The default U-Boot configuration is a capable Linux bootloader so typically our customers do not require re-building and re-installing U-Boot. However, certain projects still do require customizations to the U-Boot firmware, which implies making changes to the U-Boot code, rebuilding the U-Boot binary and then updating it on the STM32H7 SOM.

1. Building U-Boot

The full U-Boot source for the Emcraft STM32H7 SOM board is included in the software distribution available from the Emcraft web site. Refer to the u-boot/ sub-directory in the software distribution tree.

...

1. On the Linux development host, activate the cross-build environment as described in TBD Installing and activating cross development environment:

   Code Block
   $ . ./ACTIVATE.sh

2. Change to the U-Boot top directory:

   Code Block
   $ cd u-boot

3. Configure U-Boot for the Emcraft STM32H7 SOM board:

   Code Block
   $ make distclean $ make stm32h7_som_nor_defconfig

4. Run make to create the u-boot.img binary:

   Code Block
   $ make -s

2. Upgrading U-Boot "Proper" via Ethernet

The U-Boot command line interface provides a special command that can be used to self-upgrade the U-Boot image on the running target. Before you can run this command, you need to load an upgrade U-Boot binary to the target via Ethernet from a TFTP host, refer to TBD Installing Linux uImage on the STM32H7 SOM for details of the network configuration.

...

Note that the self-upgrade sequence is a dangerous operation. You must be sure that you load and install a functional U-Boot image, which is always a tricky thing when you develop customizations to U-Boot. If something goes wrong, you can re-install the release U-Boot image as documented in Installing U-Boot to the STM32H7 SOM .