CMSIS-Pack  Version 1.2
Delivery Mechanism for Software Packs
 All Pages
Usage and Description
Here is a list of all related documentation pages:
[detail level 123]
oPack Description (*.PDSC) Format
|o/package level
|o/package/apis level
|o/package/generators level
|o/package/devices level
||\/package/devices/family level
|o/package/boards level
|o/package/conditions level
|o/package/components level
|o/package/examples level
|oTypes
||oBoardReferenceTypeBoard description type specifies the board vendor and name. It is used as a reference to the respective board description section contained in the same file
||oBoardsBookTypeDocumentation description type containing information about various parts of the documentation for the development board
||oBoardsDeviceTypeDevice description type containing information about the board's device name and vendor
||oBoardsFeatureTypeThe board feature type contains information about the board's features and capabilities. A list of feature types is pre-defined
||oCclassTypeComponent Class name
||oCgroupTypeComponent Group names are specified by the element Cgroup. Cgroup names create categories within the specified Cclass. A Cgroup name defines a string of type xs:string which is between 3 and 32 characters long
||oCompatibleDeviceTypeDevice description type containing information about the compatible devices to the board's device. Compatible means that the user is able to generate code for the compatible device and test it on the development board
||oCsubTypeComponent Sub Group names are specified by the element Csub. Csub names create sub-categories within the specified Cclass and Cgroup. A Csub name defines a string of type xs:string which is between 3 and 32 characters long
||oComponentCategoryType
||oDebugInterfaceTypeThe debugInterface type contains information about the board's debug interface
||oExampleAttributes
||oExampleProjectA project element is a sequence of environment elements containing the name of the environment and the project file to be loaded
||oExpressionTypeExpressions are used in various places to describe one of the following:
||oFileTypeFile attributes
||oFilterTypeTypes to filter dependencies
||oGeneratorFileTypeFile attributes
||oGeneratorSelectTypeGenerator select type containing information about the device's name and vendor that has been used to generate the FPDSC file
||oImageTypeThe image type specifies the pictures of the development board
||\VersionTypeVersion formatting pattern
|\Enum Values
| oBoardFeatureTypeEnumPredefined development board feature categories
| oBoardBookCategoryEnumPredefined categories for development board documentation
| oCompilerEnumTypeCompiler names
| oDcoreEnumDevice cores
| oDendianEnumTokens for endianness
| oDeviceVendorEnumDevice Vendors
| oDfpuEnumCPU has an FPU
| oDmpuEnumCPU has an MPU
| oDeviceFeatureTypeEnumPredefined peripheral feature categories
| oFileCategoryEnumFile types
| oFileAttributeEnumFile attributes (optional)
| oMemoryIDTypeEnumMemory identification types
| oDataAccessTypeEnumData access types
| \SequenceNameEnumPredefined set of basic operations executed by the debugger
oConfiguration Wizard Annotations
\Flash Programming Algorithms
 \Algorithm FunctionsBlank Check