I am assuming the script creates u-boot folder and the .dtb file. Correct ?/ If yes, it did not create the u-boot folder and if it needs that to complete the build, logically that does not work.
Are you using the latest tf-a repo from ECIO or git ?
A much quicker way to build TF-A than going through the whole SDK/ECO download is: (make sure the SDK is set to $ARCH=arm)
$ git clone https://github.com/STMicroelectronics/arm-trusted-firmware.git
$ cd arm-trusted-firmware
$ git checkout -b WORKING v2.8-stm32mp-r12
# Get the Makefile.sdk from the STM ECO 5.0.0 TF-A repository and put it in the root above the source (because .sdk file is missing on git)
$ export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts
$ make -f $PWD/../Makefile.sdk all
Did the whole thing again on a different drive, under the home folder. same result, no FIP_artfacts folder. attached is thelog. you can see it builds the dtb with DTC but somehow they are not in the output folders. Are you using the the latest Developer package image or git repo ?
and BTW on this page the Yocto and SDK links are reversed. https://www.st.com/en/embedded-software/stm32mp1dev.html
and BTW the wiki does not mention to first use ggzip -d en.SDK-x86_64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz
https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package#Building_and_deploying_the_TF-A_for_the_first_time
it may be a good thing if someone worked through the wiki and checks if all steps are correct.
I guess I understand now what is going on. The ECO system sources tar file contains the FIP artifacts folder already with u-boot and optee folder with the binaries. The TF-A make won't generate those binaries. that is why when the FIP_artifacts folder is deleted, the u-boot and optee binary folder and files are not generated.
The generated FIP images are available in <FIP_DEPLOYDIR_ROOT>/fip
This is now correct.
TF-A makefile.sdk does not generates any files in the output folder except for /fip. but it needs the ub-boot and optee files in that folder. So if the FIP_artifacts_u-boot or optee is deleted you need to get them again from the original ECO sources tar file. It means when building TF-A from the repo from github, it is not possible to build all files in FIP_artifacts. That means, the u-boot and optee files must be taken from the FIP_artifacts folder in the original ECO sources tar, The github and ECO tar file README should mention this, or at least point where those u-boot and optee binaries can be found for a successful build..(if by accident or other reason the files are deleted). I placed those FIP_artifact u-boot and optee folders in the ../../FIP_artifacts folder for building from the git repo and the fip's are now correctly created. The only one exception us the on failing is for my custom board dts That is due to the .bin file missing in the optee and u-boot folder.
Now my question are
1. Outside the ECO sources tar file, where can these FIP_artifacts u-boot and optee binaries be downloaded or how to generate them ?
2. For a custom board, where can the bin files for u-boot and optee be found ? Assume the u-boot and and optee binaries for the board be placed in the FIP_artifacts folder for the TF-A build ? In other words, the optee and u-boot .bin files should be build BEFORE TF-A ? I added the dtb file from a trusted u-boot build of the custom board (renamed from uboot-,dtb to the board name as in the makefile.sdk) in the u-boot folder of FIP_artifacts manually and the build the custom board .bin files are in the optee and in fip folders. It seems the TF-A script does not use the .dts file in the ftds folder to generate the dtb for the board. CubeMX generates a different .dts file for TF-A and u-boot. and I placed the dts of TF-A in the fdts folder and biuld u-boot.dtb with the u-boot dts file..
3. Did you try to delete the FIP_artifacts folder as I stated in the OP, and does the make regenerate the u-boot and optee binary files ?
