2025-07-31 10:04 AM
Hi,
I am trying to boot an STM32MP257F with M33 master from SD-card (BOOT=0111).
I get the following error on PH4:
----------------------------------------
blockingfailure
S-0002031104084FFC
NS-0000000000000000
L-000000AE
----------------------------------------
What does it mean?
Best regards.
2025-08-01 5:51 AM
Hello @jh2 ,
Can you precise if you are working with your own design or if you work on an Evaluation / Discovery kit ?
Kind regards,
Erwan.
2025-08-04 3:33 AM
Hi @Erwan SZYMANSKI ,
I am working on a custom design. In what sense is this information relevant in decoding the error message?
Best regards,
2025-08-04 4:22 AM
Hello @jh2 ,
Very simply, to know if we could reproduce it on our side. Because if you had had this problem on an EV/DK kit, it would mean that we would have an issue on our side.
This log seems to be an error raised by the BootROM. I need to cross check with BootROM expert to know the signification, I will come back to you ASAP.
Did you try to boot in A35-TD and observed the same issue ?
Kind regards,
Erwan.
2025-08-04 4:30 AM
According to BootROM expert, this log does not give the reason of the fail, it just indicates that:
Kind regards,
Erwan.
2025-08-04 7:58 AM
Hi @Erwan SZYMANSKI ,
Ok, this is a valid reason.
I managed to boot the A35 on SD Card by setting BOOT=0001, and it worked as expected.
My problem is with M33 boot.
Best regards,
2025-08-04 8:03 AM
Thank you for these information, where can I find them on the st.com website?
Moreover, https://wiki.st.com/stm32mpu/wiki/STM32_MPU_ROM_code_overview
Mentions "STM32MP2 series developper boot, used for specific debug, it toggles opendrain at a rate of about 5 kHz (that is, the red LED light is dim)."
Do I understand this properly by assuming that developper boot is BOOT=0011, when the chip is reachable by the stlink? If yes, I never observed 5kHz on this signal. Could your BootROM experts double check this statement and fix the documentation if needed?
Best regards
2025-08-05 11:47 PM
Hello @jh2 ,
The decode message information is internal to BootROM team, and there is no documentation available about this.
Concerning your issue, I do not if you have any DK/EV board on your side, my suggestion would be to check that your binary is loaded properly on on it just to be sure that your issue does not come from your M33 firmare side (which is the most likely root cause if you use the same flash memory than your A35TD mode)
Kind regards,
Erwan.