Register Specialization Workspace

Phase 1: Analysis

Goals

Identify the possible sources for the information

Investigating alignment with IP-XACT data model

Determine whether specialization is required.

Several Semiconductor/UseCases justify specializing register data

Deliverables

Description of information type

How would you describe register data?

Assumptions regarding sources and use of information type

Recommendation for addressing information type

current thought: specialize and define transforms from native source, such as IP-XACT

Use cases to support/demonstrate committee decision

Other supporting analysis data (data modeling, requirements, etc.)

Discussion Topics

Issue

Approach

Specialization type (domain vs. structural

to be discussed in phase 2

IP-XACT Structure

The following excerpt was taken by running an instance generator (in oXygen) on the memoryMap.xsd schema from SPIRIT's 1.2 release of IP-XACT. It is intended to provide an initial understanding of the data structure. The instance was generated using random selection for choice elements.

Remember, this is an instance, not a data model. To fully analyze and understand the schema, it is best to view the schema directly.

<memoryMap>
   <name>name0</name>
   <bank xmlns:ns1="http://www.spiritconsortium.org/XMLSchema/SPIRIT/1.2" ns1:bankAlignment="serial">
      <baseAddress></baseAddress>
      <bitOffset>0</bitOffset>
      <addressBlock>
         <range></range>
         <width>1</width>
          <endianness>big</endianness>
          <usage>memory</usage>
          <volatile>false</volatile>
          <access>read-only</access>
          <parameter ns1:name="name4">parameter0</parameter>
          <register>
            <name>name5</name>
            <dim>1</dim>
            <addressOffset></addressOffset>
            <size>2</size>
            <volatile>false</volatile>
            <access>read-only</access>
            <dependency>
             <registerRef>registerRef0</registerRef>
             <fieldRef>fieldRef0</fieldRef>
             <value></value>
             <mask></mask>
            </dependency>
            <reset>
             <value></value>
             <mask></mask>
            </reset>
            <field>
             <name>name6</name>
             <bitOffset>1</bitOffset>
             <bitWidth>2</bitWidth>
             <access>read-only</access>
             <description>description0</description>
             <values>
                 <value></value>
                 <description>description1</description>
                 <name>name7</name>
             </values>
             <parameter ns1:name="name9">parameter1</parameter>
             <vendorExtensions>
             </vendorExtensions>
             </field>
             <description>description2</description>
             <parameter ns1:name="name11">parameter2</parameter>
             <vendorExtensions>
             </vendorExtensions>
          </register>
         <vendorExtensions>
         </vendorExtensions>
      </addressBlock>
      <usage>memory</usage>
      <volatile>false</volatile>
      <access>read-only</access>
      <parameter ns1:name="name13">parameter3</parameter>
      <vendorExtensions>
      </vendorExtensions>
   </bank>
   <memoryRemap xmlns:ns1="http://www.spiritconsortium.org/XMLSchema/SPIRIT/1.2" ns1:state="state1">
   <bank ns1:bankAlignment="serial">
        <!-- same content allowed as //memoryMap/bank  -->
   </memoryRemap>
   <bitsInLau>2</bitsInLau>
</memoryMap>

SPIRIT IP-XACT LEON2 example:

Legacy DITA Examples

PDTi example (in unspecialized DITA) of TLC slave with IBM CoreConnect OPB interface

Data Requirements

Refer to Register Element Normalization Worksheet

Phase 2: Specialization Creation

Goals

Deliverables

Phase 3: Data Flow and Transform Considerations

Goals

For each information type, propose method of

Deliverables

Phase 4: DITA-OT Integration

Goals

Deliverables

RegisterSpecialization (last edited 2010-03-10 22:55:37 by bob_beims)