Specify debugger options and config file in PDSC for `<device>` and `<board>`

[ReinhardKeil]

Some debuggers may require options that are specific to a board or device. For example AVH-FVP (which is a simulation model debugger), may require the specification of certain values.

An <debug-options> element could provide such information, for example:

<device Dname="ARMCM0P">
  <processor Dcore="Cortex-M0+" DcoreVersion="r0p1" Dfpu="NO_FPU" Dmpu="MPU" Dendian="Configurable" Dclock="10000000"/>
  <compile header="Device/ARMCM0plus/Include/ARMCM0plus.h" define="ARMCM0P"/>
  <memory name="ROM" access="rx"  start="0x00000000" size="0x00040000" default="1" startup="1"/>
  <memory name="RAM" access="rwx" start="0x20000000" size="0x00020000" default="1"/>
  <debug-options name="AVH-FVP" configfile="fvp/file.fvpconf" version="1.0">
    <key name="model" value="FVP_MPS2_Cortex-M0"/>
    <key name="uart" value="fvp_mps2.UART0"/>
  </debug-options>
</device>

<debug-options>

Parents	Element Chain
family	/package/devices/family
subFamily	/package/devices/family/subFamily
device	/package/devices/family/../device
board	/package/boards/board

Attributes	Description
name	debugger name (aligned with debug-adapter.yml)
configfile	file handling identical with <debugvars>
version	config file version

Child Elements	Description
key	key name value pair

The resulting *.cbuild-run.yml file would look like:

  debugger:
    name: AVH-FVP
    model: FVP_MPS2_Cortex-M0
    uart: fvp_mps2.UART0
    configfile: ./cmsis/<solution>+<target>.fvpconf

Data processing for *.cbuild-run.yml:

1. Start with default values from debug-adapter.yml
2. Add or overwrite values using the ` key name value pairs in PDSC file.
3. Use key values from target-set: in csolution.yml

[ReinhardKeil]

Related

• [Feature]: Add support for setting custom configurations for Debuggers  cmsis-toolbox#376
• [Feature Request]: AVH Debug vscode-cmsis-debugger#190
• Support for AVH-FVP simulation model configuration ARM-software/vscode-cmsis-csolution#271