Skip to end of banner
Go to start of banner

Open-CMSIS-Pack Technical Meeting 2023-01-10

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

\uD83D\uDC65 Participants

(Can be filled from Zoom meeting report)

Slides

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

Meeting Notes

Priorities

(Slide from Nov 22)

EF: Can you point to the output file topic

RK: This is a proposal to replace the output type.

Roadmap for H1 2023

RK: Want to assign all the items that are possible in CMSIS-Toolbox 2.0

JK: We’ve been a bit flexible in making not fully compatible changes. For this baseline we’d like to avoid making disruptive changes that affect previous projects.

EF: For the spec, have a proposal related to hardware projects and have an issue in preparation.

RK: You need to tell us what needs to be in CMSIS-Toolbox as well and then we need to work out how to resource it.

Linker Script File #187

FR: Will look in the list for the DevTools issue.

RK: I will create it after this call.

TB: Is there a sketch to give more context about the proposal?

RK: There are some linker scripts. See the regions template .h file

TB: If I understand correctly the memory region .h file will mirror the uVision file. Is this the target implementation or a starting point?

RK: Don’t think we should go to the extreme.

JK: Make a separation between toolchain dependency and memory configuration.

For Review

#651

#649

RK: How urgent is this?

FR: Can consider it as review comments on the CMake chain vs recommended CMake guidelines.

#450

HS: For now it looks good.

#607

JK: Need to know if this is in or out of Toolbox-2.0.

RK: Would be an incompatible change so should be in.

#175 #176 → #186

File Category Mapping

Meeting Recording

(Zoom recording uploaded via Files & Images)

  • No labels