Improve DFP and BSP Hands-on material

[ReinhardKeil]

The Problem To Be Solved

Improve the guidelines for generating packs.

Common issues that we find today are:

• Startup code is not provided as C source code.

  • Relates to UX Issues: How to distribute toolchain agnostic examples in packs #1450

• Multiple linker scripts (i.e. for RAM and ROM) are provided but usage is unclear.

  • Project templates that contain target-types: for RAM and ROM could help, do we need more?

• Component descriptions repeat the Cclass, Csub name instead of a short description.

  • Example: "HAL:ENET" with description "ENET HAL Driver" instead of "Ethernet HAL driver".

Please help to list other findings...

[ReinhardKeil]

First improvements:

• https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/pack-tools.md#hints-for-pack-creation
• https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/pack-tools.md#project-examples

This video shows at ~14:30 how pack content is used by IDEs