hproject.yml a proposal for hardware project

[iomint]

The issue follows up the proposal presented by ST during Open-CMIS-Pack weekly meeting October 24th 2023 (refer to meeting minutes page to see the recording) to introduce a hproject.yml file to manage the platform (hw) dimension of an application project (csolution.yml). This proposal aims to become part of the Open-CMSIS-Pack standard

Describe The Problem To Be Solved

• Standardize a hardware project files format
  Define a hproject.yml consistent with application-level csolution.yml project and software project cproject.yml. It aims to bring some versatility in the hardware platform of an application project

• Allow for evaluation of “hconditions” present in some SW Components
  *By listing the HW Parts (expressed as OpenCMSIS objects) that are contained into a hardware project and make this hardware project known to the OpenCMSIS condition evaluation algorithm
  *Introduce the new attribute ‘hcondition’ at the element in the PDSC file to avoid confusion and complexity with existing “condition” attribute

• Automatically import BSPs to software project composition
  Implement the automatic import of BSPs components into a software project composition by using the evaluation of hconditions of software components to filter the ones that are relevant to HW Parts listed in the hardware project

Suggest A Solution
This pdf file attached presents more details both on the purpose and content of our proposal.
Hardware project mgt in Open-CMSIS proposal_public .pdf

The json file attached includes a corresponding schema proposal
hproject.schema.json

[jkrech]

Automatically import of BSP components:
Note that csolution today does not add components to the cproject/clayer.yml files, instead csolution list dependencies would list all components which should be added by the user.

Is the assumption correct that all components associated with a part should be selected and there is no "user choice" required?