How to intentionally trigger a blocking failure on STM32N6570-DK to test PG10 BootFailed output

[Jimmy7]

Hello,

I am trying to intentionally force a blocking failure on the STM32N6570-DK to observe how the system handles the error and to test the PG10 BootFailed UART output.

To do this, I have tried tampering with the FSBL header in various ways to force a failure, as well as simply erasing the OctaFlash.

However, despite my attempts, no ID code or valid UART output ever arrives on PG10.

While the Boot ROM manual (UM3234) describes what happens during a blocking failure, there are no clear notes or official procedures explaining how a blocking failure can be intentionally generated for testing purposes.

Could someone from ST or the community clarify:

How can we intentionally and reliably trigger a blocking failure on the STM32N6570-DK to test the PG10 BootFailed UART output?

Any guidance or suggestions would be greatly appreciated.

Best regards

[Saket_Om]

Hello ​@Jimmy7 

If we take serial boot as an example, we should try using a USB cable to perform a download and then unplug the USB cable in the middle of the download. That should cause a blocking failure.

[db16122]

Please refer the document below for help

Handling of soft errors in STM32 applications