2022-08-25 08:07 AM
I'm targeting:
openstlinux-5.15-yocto-kirkstone-mp1-v22.07.27
DISTRO: openstlinux-eglfs
MACHINE: stm32mp15-disco
Image+SDK build fine. I create the raw file as usual, image SD card, and boot fails with:
NOTICE: Model: STMicroelectronics STM32MP157F-DK2 Discovery Board
NOTICE: Board: MB1272 Var4.0 Rev.C-02
INFO: PMIC version = 0x20
INFO: Reset reason (0x15):
INFO: Power-on Reset (rst_por)
INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe2000
INFO: FCONF: Reading firmware configuration information for: stm32mp_io
INFO: Using SDMMC
INFO: Instance 1
INFO: Boot used partition fsbl1
NOTICE: BL2: v2.6-stm32mp1-r1.0(debug):v2.6-dirty
NOTICE: BL2: Built : 13:14:26, Nov 23 2021
WARNING: CRC check failed on FWU metadata
WARNING: loading of FWU-Metadata failed, using Bkup-FWU-Metadata
WARNING: CRC check failed on FWU metadata
ERROR: loading of Bkup-FWU-Metadata failed
PANIC at PC : 0x2ffea213
I have no troubles using dunfell release with machine `stm32mp1-disco`.
My kirkstone CI (fails to boot):
My known working
dunfell CI (works):
https://github.com/meta-flutter/meta-flutter/blob/dunfell/.github/workflows/dunfell-stm32mp15.yml
Running the STM1 starter images of the same variant does work. So something about the image config.
Any ideas?
Solved! Go to Solution.
2022-08-26 03:24 PM
@Erwan SZYMANSKI
It was the missing metadata.bin file. I had made my tests prior to adding the metadata.bin copy. The STMProg tool was failing looking for metadata.bin, so I had copied it for that; not realizing I just solved the problem.
Thanks for looking!
2022-08-26 02:43 AM
Hello @Community member ,
Thank you for your contribution !
Regarding your logs, TF-A has troubles with the metadata check for FWU as explained in this article.
However, i see that you updated your .yml file between Dunfell and Kirkstone with taking this into consideration with copying arm-trusted-firmware/metadata.bin too.
I will investigate and try to reproduce from my side, I will let you informed.
Kind regards,
Erwan.
2022-08-26 03:24 PM
@Erwan SZYMANSKI
It was the missing metadata.bin file. I had made my tests prior to adding the metadata.bin copy. The STMProg tool was failing looking for metadata.bin, so I had copied it for that; not realizing I just solved the problem.
Thanks for looking!
2022-08-28 10:55 AM
Hi @Community member ,
Really glad to see that you were able to solve your issue !
Have a nice day !
Erwan.