1 / 8

SIDSC Design File Methodology

May 25, 2011. SIDSC Design File Methodology. Configure and Generate Register Content at the Device Level. Noreen McMahan based on Work by Seth Park. What is An SIDSC Design Map File?.

neil
Download Presentation

SIDSC Design File Methodology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. May 25, 2011 SIDSC Design File Methodology Configure and Generate Register Content at the Device Level Noreen McMahan based on Work by Seth Park

  2. What is An SIDSC Design Map File? Enables reuse of generic modules of register content across different devices and device families, both in block guides (module chapters) and in packages of register data targeted for board software developers. For each component in a generated publication, the SIDSC design file writes device-specific information, such as the base address of the module on the device and the number of instances of the module that are available on that device. Device-specific information is supplied only at publication time, so the component (configured for conditional processing) remains generic and available for reuse. The component references can contain conditional processing attributes to filter entire components/modules in and out of the content as different reference manuals in a family are generated.

  3. What is a Design Map File The structure of an SIDSC design map file is very simple. It is a list of component references using the <component-ref> element, just as a DITA map for a block guide is a list of topic references using the <topicref> element. Each <component-ref> element must reference exactly one component, although it may specify multiple instances of this component. Each <component-ref> contains a series of attributes and their values, most of them required and some of them optional.

  4. Attributes on a Component Reference • All of the select-atts (optional) • Base address (required) • Corresponds to the <unitAddress> element in the <componentBody> of an SIDSC component. Overwrites <unitAddress>. • href (path to component file) (required) • Instances number (optional) • Set of 4 attributes: <instancesNumber>, <instanceOffsets>, <namePattern>, <unitQualifier> to define how many instances of this component are available on a device • Register increment (optional) • IP version and IP name (required) • Must match these values in the individual component file

  5. Overview: Linking

  6. Conditional Processing: Use Case 1 Filter a module in or out of a deliverable

  7. Conditional Processing: Use Case 2 Select Number of Instances When Filter is Applied

  8. End of Presentation

More Related