Add instructions for debugging ARM with VSCode+BMP.

[tzarc]

Description

Adds some documentation to the VSCode documentation page to describe a method do debug ARM MCUs using cortex-debug and a Black Magic Probe.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[stale]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[stale]

Thank you for your contribution!
This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.

[drashna]

Aside from that, tested this out and it works well.

Though, would it worth be adding a section for adding tasks to vscode, especially for the prelaunchtask? Not here necessarily, but just in general.

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[KarlK90]

LGTM, just a little note on the compiler flags

[KarlK90]

How about OPT = g as this provides good debug ability and still adds a little bit of optimization. Debug information is generated by default for all binaries, but it would be better to default to -g3 by adding DEBUG = 3.

[tzarc]

For me, no real preference; if you want to make a suggestion on the PR for what it should look like I'll be more than happy to commit it.