Prototype first set of Core Peripheral dialogs based on SCVD

[jreineckearm]

As discussed in parent #239 , we should aim for creating core peripheral dialogs base don the SCVD description format for Component Viewer. See that parent for more details.

A first set of dialogs/SCVD files should be:

• SysTick
• NVIC/Interrupts (first incarnation without SVD interrupt table cross references)
• Faults
• System Config

A second iteration (possibly outside the scope of this issue) could be

• MPU
• SAU
• other dialogs we had in uVision?

• Implementations can be inspired by hand-crafted dialogs in uVision. But we are OK with accepting the limitations of SCVD/Component Viewer technology in a first incarnation. This can include currently not supported core registers or Trustzone accesses. Please collate a list of encountered problems.
• All dialogs are read-only.
• Do not plan with changing core peripheral states in a first incarnation. This particularly affects peripherals where you'd need to change region selection to read out all of them (like MPU and SAU). Instead, display information that is available with the current, unmodified state of a peripheral.
• Avoid using registers with side-effects while modelling core peripherals with SCVD.
• Create one SCVD file per peripheral. We may need architectural (v6-M/v7-M/v8-M) flavors depending on how hard it is to read out capabilities in core peripheral or CPU config/ID registers. We should, if possible, avoid making decisions based on CPUID register.

[jreineckearm]

@andbararm , can you please pick this up as discussed earlier today?

[jreineckearm]

No comments please about this issue number and potential success. 😉