STM32MP1 support available in SW4STM32

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4; you can download a short video showcasing this on the ac6-tools website (registration required).

System Workbench for STM32

Starting debug with too many breakpoint enable

during a debug session we can easily end up having all target breakpoint set + “main”.
At next debug session debug will fail to start with the infamous message box

“Error in final launch sequence”

The detail or openocd log make clear what’s the reason

Info : no flash patch comparator unit available for hardware breakpoint
Error: can’t add breakpoint: resource not available

Error message from debugger back end:
Warning:\nCannot insert hardware breakpoint 3.\nCould not insert hardware breakpoints:\nYou may have requested too many hardware breakpoints/watchpoints.\n

What is right because of the main tmp breakpoint requires one extra break point that target do not have is required.

I’m not sure what would be the best way to deal with this.
I kind of remenber some debuger will maintain debug perpective active and cpu under reset
but will let user disable breakpoints and give a new go after
What seam anyway better than today behaviour.

the plugin may disable all break but main wait for it and then enable all others.
That will be ok for most common use case but is’nt necessrry correct as some breakpoint may be before main ie startup/interrupt etc...

I just came to find that working on nucleo l053r8 that has only 4 bkpt that is quite not enougth.