[Tobias]

Hi,
about the Debian distri that is what I meant about not suiting your requirements.
Mixing tfa/uboot/kernel from different versions is most likely not booting (if I remember correctly there are some problems with the security parts).
But the rootfs is more or less just a yocto based distribution.
What you can do is leaving all parts except of the rootfs and use only the rootfs from a newer yocto or buildroot environment.

Edit:
forgot to mention probably you need some manual altering for the linux kernel modules when you have problems with modprobe it is possible the modules matching your kernel are missing and you have to make them present

• This reply was modified 4 years, 1 month ago by Tobias.

[Tobias]

Hello,
from our point of experience what you try is not working out of the box.
But if you manually alter the dts/dtsi files you can use the minimal example compiling and running on your board using SDK 2.
As an alternative to this approach you can simply replace only the rootfs of your linux.
If you leave all the boot stuff as it is and only depend on a new python version you can use a “normal” distribution like Debian on arm (Debian armhf is the corresponding armv7 you need) and just copy the minimal rootfs on the partition (make sure you leave ALL uid and gid settings e.g. by copying on linux using cp -rpf) and use it like a normal linux distribution.
The second idea is easier to use and with less implementation time possible but maybe it does not fit your requirements.

[Tobias]

Perfect thank you this was exactly what I was looking for.

[Tobias]

I found that one but I had several problems with it.
First this seems to be incompatible with SDK 2.0.
Second i wanted strictly to avoid manual device tree configuration (except some entries that seem to cause problems e.g. sound).
Some I am missing at the moment.

[Tobias]

You forgot to copy the github repo!

Arm Trusted Firmware
https://github.com/STMicroelectronics/arm-trusted-firmware
48 forks.
30 stars.
0 open issues.

Recent commits:

• feat(stm32mp1): update ST version for SSPUpdate ST_VERSION in SSP file to r2.0-ssp.Change-Id: Ib02e2a8525fdd53a0fb4ec0177469472e3e45d16Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/388736ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>, Yann GAUTIER
• build(st): update ST versionUpdate ST version to v2.0.Signed-off-by: Yann Gautier <yann.gautier@st.com>Change-Id: I24eea59f5f2cf1b7fbc2ca1809449ec2626de40aReviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/388484ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>Tested-by: Yann GAUTIER <yann.gautier@foss.st.com>Domain-Review: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>Reviewed-by: Yann GAUTIER <yann.gautier@foss.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>Reviewed-by: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>, Sebastien PASDELOUP
• fix(stm32mp2): correct USB security settingsWhen setting secure and privileged right for USB, the whole SECCFGRand PRIVCFGR were written whereas we should have only written the bitcorresponding to the peripheral. Use % instead of / to determine thebit to be changed for the given peripheral, and use mmio_setbits_32()instead of mmio_write_32().Change-Id: I0e4253355de52baf4df39d35d1da5dc7c03f7963Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/385532Reviewed-by: Gatien CHEVALLIER <gatien.chevallier@st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>, Sebastien PASDELOUP
• fix(stm32mp2-fdts): keep ommanager for hyperflashWhen compiling device tree for hyperflash boot, the DT nodeommanager@40500000 should be kept, it should then be under flag.The node spi@40430000 should also be removed in that case.Change-Id: I08a116c36476f021fc0b0da8830b3674a3925a3fSigned-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/384378ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>Domain-Review: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>Reviewed-by: Maxime MERE <maxime.mere@foss.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>, Sebastien PASDELOUP
• feat(st-crypto): add initialisaton check in HASHThis patch add the capability to not initialize hash peripheral if thisone is already done.Signed-off-by: Maxime Méré <maxime.mere@foss.st.com>Change-Id: Ie585a61ee92253c1d008f25d204c21a2a66e57adReviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/379746Reviewed-by: Yann GAUTIER <yann.gautier@foss.st.com>ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>Domain-Review: Yann GAUTIER <yann.gautier@foss.st.com>, Sebastien PASDELOUP

you can find the file in the directories:
include/dt-bindings/soc

[Tobias]

CubeMX prior to version 6 seems to be incompatible to openstlinux-5-4-dunfell-mp1-20-06-24.

What I did is using CubeMX 6.0 install the SDK and the mentioned sources.
After that I extracted the compressed tarballs in the source folder.
Then I cloned the git projects from st and copied the files to the source folder.
Added the board filename to the Makefile and compiled it.

That worked with the exception of das U-Boot which will not boot if I exchanged the original one.

EDIT: I use Linux and the dd command to directly write the stm32 files to sd card

• This reply was modified 4 years, 3 months ago by Tobias.
• This reply was modified 4 years, 3 months ago by Tobias.

[Tobias]

Have you cloned the corresponding git repos?

Arm Trusted Firmware
https://github.com/STMicroelectronics/arm-trusted-firmware
48 forks.
30 stars.
0 open issues.

Recent commits:

• feat(stm32mp1): update ST version for SSPUpdate ST_VERSION in SSP file to r2.0-ssp.Change-Id: Ib02e2a8525fdd53a0fb4ec0177469472e3e45d16Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/388736ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>, Yann GAUTIER
• build(st): update ST versionUpdate ST version to v2.0.Signed-off-by: Yann Gautier <yann.gautier@st.com>Change-Id: I24eea59f5f2cf1b7fbc2ca1809449ec2626de40aReviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/388484ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>Tested-by: Yann GAUTIER <yann.gautier@foss.st.com>Domain-Review: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>Reviewed-by: Yann GAUTIER <yann.gautier@foss.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>Reviewed-by: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>, Sebastien PASDELOUP
• fix(stm32mp2): correct USB security settingsWhen setting secure and privileged right for USB, the whole SECCFGRand PRIVCFGR were written whereas we should have only written the bitcorresponding to the peripheral. Use % instead of / to determine thebit to be changed for the given peripheral, and use mmio_setbits_32()instead of mmio_write_32().Change-Id: I0e4253355de52baf4df39d35d1da5dc7c03f7963Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/385532Reviewed-by: Gatien CHEVALLIER <gatien.chevallier@st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>, Sebastien PASDELOUP
• fix(stm32mp2-fdts): keep ommanager for hyperflashWhen compiling device tree for hyperflash boot, the DT nodeommanager@40500000 should be kept, it should then be under flag.The node spi@40430000 should also be removed in that case.Change-Id: I08a116c36476f021fc0b0da8830b3674a3925a3fSigned-off-by: Yann Gautier <yann.gautier@foss.st.com>Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/384378ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>Domain-Review: Sebastien PASDELOUP <sebastien.pasdeloup-ext@st.com>Reviewed-by: Maxime MERE <maxime.mere@foss.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>, Sebastien PASDELOUP
• feat(st-crypto): add initialisaton check in HASHThis patch add the capability to not initialize hash peripheral if thisone is already done.Signed-off-by: Maxime Méré <maxime.mere@foss.st.com>Change-Id: Ie585a61ee92253c1d008f25d204c21a2a66e57adReviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/379746Reviewed-by: Yann GAUTIER <yann.gautier@foss.st.com>ACI: CITOOLS <MDG-smet-aci-reviews@list.st.com>ACI: CIBUILD <MDG-smet-aci-builds@list.st.com>Domain-Review: Yann GAUTIER <yann.gautier@foss.st.com>, Sebastien PASDELOUP

For example this one I used to compile the tf-a.

[Tobias]

I upgraded my CubeMX to version 6 today.
Now I can compile everything and it is working with the exception of “das U-Boot”.
If I write my new stm32 file to partition 3 I got the u-boot output:

CPU: STM32MP157CAC Rev.B
Model: STMicroelectronics STM32MP157C eval daughter on eval mother
Board: stm32mp1 in trusted mode (st,stm32mp157c-ev1) !!!why ev1 I double checked I selected dk2 in CubeMx?
Board: MB1272 Var2 Rec.C-01
DRAM: ERROR: Illegal access to 0xfdafffb0 in:
ERROR: Non-Secure
ERROR: Privilege
ERROR: Read
PANIC at PC: 0x2ffefeb5

Exception mode=0x00000016 at: 0xfffffffc

I do not know why I am getting an error corresponding to ev1 board and not dk2 board which I selected as a basis in CubeMX.
Also I just selected the default values and just exported the dts and dtsi files.
Are there any ideas what I did wrong and more important how to fix this?

[Tobias]

On the ST Download area there is an ComboBox where you can select the version if you don’t want the current version.

[Tobias]

Is there an update on this question?

• This reply was modified 4 years, 3 months ago by Tobias.

[Tobias]

Thank you so far this part of starting a customized linux and fsbl is working now.

Next part I am troubling with is getting the tf-a compiled with current SDK.
After adding the dts/dtsi files from CubeMX to the TFA-SOURCE/fdts dir and appending
“stm32mp157c-osd32mp157c-512m-baa_minimalconfig-mx” to the Makefile.sdk TFA_DEVICETREE variable I get:
fdts/stm32mp157c-osd32mp157c-512m-baa_minimalconfig-mx.dts:21:10: fatal error: dt-bindings/power/stm32mp1-power.h: No such file or directory
21 | #include <dt-bindings/power/stm32mp1-power.h>

There is a debug-tf-a-stm32mp157c-osd32mp157c-512m-baa_minimalconfig-mx-trusted.stm32 file in ../build-trusted/ folder but I miss the release file and I am not sure neither the error “can be ignored” nor how to fix it.

Is there any solution not downgrading the SDK and sources?

[Author]

Posts