Open-CMSIS-Pack Technical Meeting 2022-03-08

\uD83D\uDDD3 Date

08 Mar 2022

Error rendering macro 'viewpdf' : Failed to find attachment with Name 22wk10_Open-CMSIS-Pack_TM.pdf

Data Model Gaps by NXP

Error rendering macro 'viewpdf' : Failed to find attachment with Name Gaps_between_NXP_Data_Model_public.pdf

#20/#71

RK: Input to Handlebars should be in json format

FR: This is possible if doesn’t need to be human readable

RK: Generator-owned components - could be hidden. Generator owned and invisible attributes proposed to be merged - any issues?

JK: Could be a passed through component without being generator owned.

FR: For a better name need to understand the usecase.

RK: Refer to issue #100 attribute “invisible”.

FR: Are we defining primary and secondary components?

ED: What is the purpose of the invisible component? If something goes wrong, how would you present it to the user?

EF: Isn’t it a way to have a meta component or one encapsulated in another?

RK: In principle yes. For the USB example makes no sense unless you have components which use the USB controller.

MD: “Selected by context” rather than “invisible” is preferable

EF: We need to think about it before confirming.

#171

FR: Why can’t csolution do this?

VG: SCI won’t be aware of yaml stuff

RK: cprj is standalone description. Propose to keep cprj file.

FR: Not sure why yaml is out of SCI.

RK: yaml file is more flexible. Depends on setup of environment.

EF: Re alternative path - ST believes the user should be able to define the directory structure

LM: For packs

Holt Sun’s presentation

JK: Let’s continue the discussion re project path and we’ll look at it.

CMSIS Annual Update Webinar next week, so no Open-CMSIS-Pack Technical Meeting.