That actually is better in Processor Expert (it automatically add dependent components). Dependency management: I can describe that a component needs another one.Building and publishing packs could be automated (that’s not the case with Processor Expert).Processor Expert had added lately multiple repositories to deal with versions, but that did not work well. In project is it possible to ‘lock’ the version used which is important to keep things stable from a project perspective. With Processor Expert users had to download the packs manually from a server. The packs are hosted on a server used with a package manager.In Processor Expert the packs were using a special (encrypted?) format. Compressed normal archive files as package file which can reduce download bandwidth.Main features of the CMSIS-Pack approach for the McuOnEclipse components: I recommend reading through which includes nice training and tutorial material. Examples: project examples which can be used to demonstrate usage of components.Boards: describes development boards and links to information (e.g.Devices: describe the device (family, sub-family, device) with properties like processor architecture, memory, debug interface.Conditions: dependency on device, compiler and/or other components.Components: Describe software components with taxonomy (class, group, subgroup) and list of files.That XML (.pdsc, Packet Description) file describes the files and defines other attributes: In a nutshell, CMSIS-Packs are (zip) archive files with an XML description file. There are several points noted in this wiki about its current limitations. Since then, the standard has been evolved, but seems not be widely used (yet?). Two years ago ARM announced a new member of their CMSIS standard, the CMSIS-Pack: a way to package software components, device information, example projects and code templates into an open format. It is used in many university labs, research and personal projects, but as noted above: it is now time to move a vendor neutral way. But with the acquisition of that technology a few years ago by Freescale (now NXP) that technology turned into a vendor specific solution and was only available for Freescale parts.

Keil 5 framework cubemx.pdsc is missing