2022-08-08 03:39 AM
I have a custom build on the stm32mp157f dk2.
stm TF-A v2.6-r1 or vanilla TF-A v2.7, using sp_min.
stm U-boot 2020.10-r2 or vanilla Barebox-2022.06.
I've also tried U-boot 2021.10-r1, but that one crashes the kernel even earlier.
Kernel: vanilla 5.18/vanilla 5.19.
FSBL starts fine.
Both v2.6 and v2.7 starts just fine. sp_min too.
Both TF-A versions load and executes BL33 (stm u-boot or vanilla barebox) just fine.
But when I use stm TF-A v2.6 kernel crashes when started from BL33.
Works fine with vanilla TF-A 2.7 all other components being equal.
I can see the kernel decompression but stops executing directly after that.
This happens regardless if I do the fip manually or if TF-A puts it together.
Kernel 5.18 or 5.19 doesn't matter. But when I use vanilla TF-A both kernels boot.
TF-A is configured exactly the same using the variable configuration.
2022-09-01 02:51 AM
Hi @milkylainen ,
Sorry to come late in the thread.
First do you still have issue or did you manage to fix it by yourself ?
Thanks,
Olivier
2022-09-01 03:46 AM
Hi Olivier.
Np. I am still having this issue.
I have a hard time mixing parts of the ecosystem with vanilla.
So the only configuration I have gotten to a working userland is
vanilla tf-a 2.7, stm u-boot 2020.10, vanilla kernel 5.18+.
If I go to stm tf-a 2.6-r1, kernel crashes.