Event Recorder  Version 1.0.0
MDK Debugger Views for Status and Event Information
 All Files Functions Macros Groups Pages
SCVD Validation, Usage, Delivery

Validation

An *.SCVD file is validated the following ways:

  1. Component_Viewer.xsd: The schema file specifies the syntax and structure of the XML-based format. XML tools use the schema file for checking the syntactical and structural correctness of an XML file that claims compliance with a certain format.
  2. Component Viewer: When displaying debug information in uVision, the parser shows warning messages in the dialog for Software Components that are not available or have syntax errors.

Usage

Objects and events defined in a *.SCVD file can be used the following way:

Delivery with *.pdsc file

Vendors or customers that create Packs can integrate and submit SCVD files within a Package Description file (*.pdsc). We recommend to write one SCVD file for each component element. This SCVD file can be added to Package Description file (*.pdsc) with the <file> element of category other.

The example adds the file Network.scvd to the component group CORE PDSC file.

// in Package Description file (*.pdsc)
<component Cgroup="CORE" Cvariant="Release" condition="CMSIS Core with RTOS">
...
<files>
...
<file category="other" name="Network/Network.scvd"/>
...
</files>
...
</component>

This entry would place the Network.scvd file in the Network folder of the \ARM\Pack\vendor\pack name\pack version directory.
The entire path would have the form: \ARM\Pack\vendor\pack name\pack version\Network\Network.scvd.
The condition states that the components get activated for applications that use the CMSIS Core with an RTOS.

For details, refer to Pack Description File.