I can't connect after BOOT_CM7 has been disabled, OB, CubeProgrammer

[Zaher]

I just tried to disable BOOT_CM7 for option-bytes using STM32CubeProgrammer and after applying, I can't connect to the MCU. I tried again with R192 shorted out, but STLink still can't connect to the MCU: "The interface firmware FAILED to reset/halt the target MCU"

This is on STM32H747-DISCO board.

[Zaher]

Please don't tell me I have bricked the board, and there's no way to recover from this!

[Zaher]

By the way, I did this as per the requirement of BootCM4_CM7GatedGated example in the Cube package.

"User Option Bytes requirement (with STM32CubeProgrammer tool)

    BOOT_CM4(BCM4) = 1                Enable cortex M4 Boot

    BOOT_CM7(BCM7) = 0                Disable cortex M7 Boot"

If there's no way to recover from this, wouldn't ST warn about it?

[Zaher · Accepted solution]

It's true Google some times is the best friend. I just don't know how I missed this article here. I spent hours trying to figure it out, shorting jumpers, connecting certain probes, and finally, my lovely H747-DISCO is back to life again!