Elprotronic Elprotronic’s GangFlasher-ST provides convenient procedure procedures for programming custom boards with ST MPx microprocessor MPUs inside. Within this procedure called the User-Defined boards programming it is possible to automatically adapt user Device Trees (DT) memory nodes into Elprotronic bootloaders (it is provided only for single particular programming session). They provide non-recoverable peripherals and external devices as a static structure. One of GangFlasher (GF) functionalities is export of used device bootloaders. These bootloaders provide programming access to peripherals and external devices during the GangFlasher’s programming process. The bootloaders are resident only in volatile memory, so they do not affect board state after a power-cycle. One of the key functionalities of the GangFlasher-ST is the ability to run custom boards designed by the client. The GangFlasher-ST has an automatic method of integrating the custom DT into its boot process. As an alternative to this automated process, there is also the possibility for the user to control the boot DT with their own corrections. Th minimal Device Tree (DTmin) and direct user correction of used nodes via DTmin corrections can be combined using a DT configuration file. Let

As an example, let us consider one of microprocessor (MPU) Vendor example boarda 3rd party MPU board from an external vendor, in this case it will be the Karo TXMP-1570 board. This board will not boot using any default ST MPU board configurations (like DK1/DK2, EV1, etc.).

1. GangFlasher-CLI example

...

In this particular setup (environment is ST Toolkit version 4, and board Karo TXMP-1570 with STM32MP157C MPU) the problem lies in HSE configuration. Documentation could be found in STM32MP157 Reference Manual (RM0436 Rev 6, pp.526) and Trusted Firmware ARM (TFA) synchronized with ST Toolkit version 4 (Developer Package v4 TFA/plat/st/stm32mp1/bl2_plat_setup.c l. 322 provides provide details about probable problem with clock). It is quite easy to figure out where lies source of problem - in clock or uart configuration.

...