The problem with facilitating uboot errors

[Ffu.1]

When compiling the U-boot, these four commands are used:

PC $& gt; export KBUILD_OUTPUT=.. /build/stm32mp15_trusted

PC $& gt; export DEVICE_TREE=stm32mp157c-dk2

PC $& gt; make stm32mp15_trusted_defconfig

PC $& gt; make all

use the first: export KBUILD_OUTPUT=.. /build/stm32mp15_trusted, the compiler will fail, but if there is no first statement, the compiler will succeed

[Kevin HUBER]

Hello @Ffu.1​ ,

The error displayed about "make mrproper", means that your build folder is not clean and was already used with another configuration or with another build directory.

So please, run this command to clean your directory

make mrproper

Then redo the commands:

export KBUILD_OUTPUT=../build/stm32mp15_trusted

make stm32mp15_trusted_defconfig

And specify the device tree in the make all command :

make DEVICE_TREE=stm32mp157c-dk2 all

Regards,

Kevin

[Ffu.1]

This does work, but why only u-boot.bin is generated, not u-boot.stm32

[Kevin HUBER]

Hi @Ffu.1​ ,

Yes, I assume that you are using an ecosystem v3.0.0 or 3.1.0. It is normal that you do not have a u-boot.stm32.

Since the ecosystem v3.0.0, two binaries are needed from u-boot:

https://wiki.st.com/stm32mpu/wiki/U-Boot_overview#Output_files

u-boot.dtb and u-boot-nodtb.bin

The .stm32 is now a tf-a.stm32. To learn more things about the FIP, you can read the ecosystem release note: https://wiki.st.com/stm32mpu/wiki/STM32MP15_ecosystem_release_note_-_v3.0.0#OpenSTLinux_-28Cortex-C2-AE-A7-29

or this part of the TF-A overview: https://wiki.st.com/stm32mpu/wiki/TF-A_overview#FIP

The FIP can be generated automatically when you build your TF-A, please have a look to the README.HOW_TO.txt of the TF-A.

Regards,

Kevin

[Kevin HUBER]

Hello @Ffu.1​ ,

In order to give better visibility on the answered topics, please click on 'Select as Best' on the reply which solved your issue or answered your question. See also 'Best Answers'