Configuration space decoding, 1 mandatory definitions, 2 mandatory module functions – Teledyne LeCroy Summit T3-16 PCIe Multi-lane Protocol Analyzer User Manual User Manual
Page 249: Appendix a: configuration space decoding, Appendix a
![background image](/manuals/353586/249/background.png)
Summit T3‐16 PCI Express Multi‐Lane Protocol Analyzer User Manual
237
Appendix A
Configuration Space Decoding
The decoded capability structures in the Configuration Space Viewer and Editor are based
on programmed definitions in the PETracer software and on Configuration Space Decode
Scripts.
Configuration Space Decode Scripts are tools to define capability structures and instruct
the Configuration Space Viewer or Editor how to decode them. These scripts are in the
\CfgSpaceScripts sub‐directory below the \Scripts directory in the application directory.
You can write Configuration Space Decode Scripts using the CATC Scripting Language (CSL).
See the Teledyne LeCroy Analyzers File Based Decoding Manual for reference.
PCI Express Configuration Space Decode Scripts have the file extension .pecfgdec.
12.1 Mandatory
Definitions
Configuration Space Decode Scripts must set the following reserved variables.
CapabilityName: Name of the capability structure
CapabilityID: ID of the capability structure
ExtAddSpace: Set to 1 if Extended Configuration Space. Else, set to 0 for PCI.
12.2 Mandatory
Module Functions
Modules are collections of functions and data dedicated to decoding a specific capability
structure. Each module has one primary Configuration Space Decode Script file
(extension .pecfgdec) and optionally has include files (.inc).
A module function is an entry‐point into a decoding module. To help display a
capability structure, the application calls a module function.
The Configuration Space Editor and Viewer support only the DecodeRegister(offset) and
GetSize( ) functions.