IP-XACT Standard/D4, December 19, 200715Draft Standard for theIP-XACT meta-data and tool interfaces1015Prepared by the20Schema Working GroupofThe SPIRIT Consortium253035Copyright 2007 by the Spirit Consortium.1370 Trancas Street #184, Napa, CA 94558All rights reserved.40All rights reserved.This document is an unapproved draft of a proposed IP-XACT Standard. As such, this document issubject to change. USE AT YOUR OWN RISK!Embargoed from distribution beyond The SPIRIT Consortium reviewing membership455055

151015Abstract: The IP-XACT Standard forms the conformance checks for XML data designed to describe electronic systems. The meta data forms which are standardized include: components, systems, bus interfaces and connections, abstractions of those buses, and details of the componentsincluding address maps, register and field descriptions, and file set descriptions for use in automating design, verification, documentation, and use flows for electronic systems. The standard includesa set of XML schemas of the form described by the World Wide Web Consortium (W3C) and a setof semantic consistency rules (SCRs). The standard also provides for a generator interface that isportable across tool environments. The specified combination of methodology-independent metadata and the tool-independent mechanism for accessing that data provides for portability of designdata, design methodologies and environment implementations.Keywords: Electronic Design Automation, EDA, XML Design Meta Data, IP-XACT, XML Schema,Tight Generator Interface, TGI, Semantic Consistency Rules, SRCs, Design Environment, UseModels, Tool And Data Interoperability, Implementation Constraints, Register Transfer Logic, RTL,Electronic System Level, ESL, Bus Definitions, Abstraction Definitions, and Address Space Specification.202530354045The SPIRIT Consortium.1370 Trancas Street #184, Napa, CA 94558Copyright 2007 - 2008 by the SPIRIT Consortium.All rights reserved. Published xx month 2008. Printed in the United States of America.5055No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the priorwritten permission of the publisher.

IP-XACT meta-data and tool interfacesIP-XACT Standard/D4, December 19, 20071IntroductionThis introduction is not part of the Draft Standard for the IP-XACT meta-data and tool interfaces.5The purpose of this standard is to provide the electronic design automation (EDA), semiconductor,electronic intellectual property (IP) provider, and system design communities with a well-defined andunified specification for the meta-data which represents the components and designs within an electronicsystem. The goal of this specification is to enable delivery of compatible IP descriptions from multiple IPvendors; better enable importing and exporting complex IP bundles to, from and between EDA tools forSoC design (system on a chip design environments); better express configurable IP by using IP meta-data;and better enable provision of EDA vendor-neutral IP creation and configuration scripts (generators). Thedata and data access specification is designed to coexist and enhance the hardware description languages(HDLs) presently used by designers while providing capabilities lacking in those languages.The SPIRIT Consortium is a consortium of electronic system, IP provider, semiconductor, and EDAcompanies. IP-XACT enables a productivity boost in design, transfer, validation, documentation, and use ofelectronic IP and covers components, designs, interfaces, and details thereof. It is extensible in specifiedlocations.IP-XACT enables the use of a unified structure for the meta specification of a design, the components that isbased on manual or automatic methodologies. IP-XACT specifies the tight generator interface (TGI) foraccess to the data in a vendor-independent manner.This standardization project provides electronic design engineers with a well-defined standard that meetstheir requirements in structured design and validation and enables a step function increase in theirproductivity. This standardization project will also provide the EDA industry with a standard to which theycan adhere and which they can support in order to deliver their solutions in this area.The SPIRIT Consortium has prepared a set of bus and abstraction definitions for several common buses. It isexpected, over time, that those standards groups and manufacturers who define buses will include IP-XACTXML bus and abstraction definitions in their set of deliverable. Until that time, and to cover existing usefulbuses, a set of bus and abstraction definitions for common buses has been created.101520253035A set of reference bus and abstraction definitions allows many vendors who define IP using these buses toeasily interconnect IP together. The SPIRIT Consortium posts these for use by its members, with nowarranty of suitability, but in the hope that these will be useful. The SPIRIT Consortium will, from time-totime, update these files and if a Standards body wishes to take over the work of definition, will transfer thatwork to that body.40These reference bus and abstraction definition templates (with comments and examples) are available fromthe public area of the web site.45Notice to users50ErrataErrata, if any, for this and all other standards of The SPIRIT Consortium can be accessed at the followingURL: Users are encouraged to check this URL for errataperiodically.Copyright 2007 The SPIRIT Consortium. All rights reserved.This is an unapproved IP-XACT Standards Draft, subject to change.Embargoed from distribution beyond The SPIRIT Consortium reviewing membershipiii55

IP-XACT Standard/D4, December 19, 200715Draft Standard forInterpretationsCurrent interpretations, users guides, examples, etc. can be accessed at the following URL: 10Attention is called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith.152025303540455055ivCopyright 2007 The SPIRIT Consortium. All rights reserved.This is an unapproved IP-XACT Standards Draft, subject to change.Embargoed from distribution beyond The SPIRIT Consortium reviewing membership

IP-XACT meta-data and tool interfacesIP-XACT Standard/D4, December 19, 20071ParticipantsThe following members and observers took part in the IP-XACT Schema Working Group (SWG) and theElectronic System Level (ESL) Working Group (EWG):Greg Ehmann, NXP Semiconductors, Chair SWGJean-Michel Fernandez, Cadence, Chair EWGGary Delp, LSI Corporation, Technical DirectorJoe Daniels, Technical Editor510ARM: Allan Cochrane, Christopher Lennard, Andrew Nightingale, Chulho Shin, Peter Grun,Anthony Berent, Sheldon WoodhouseCadence: Jean-Michel Fernandez, Giles Hall, Saverio Fazzari, Victor Berman15CoWare: Cesar A. Quiroz, Kris DekeyserDenali: Gary LippertInfineon: Wolfgang Ecker, Thomas SteiningerLSI: Gary Delp, Wayne Nation, Gary Lippert, Dave Fechser20MatiTech: Aaron BaranoffMentor: John Wilson, Gary Dare, Mark Glasser, Matthew Ballance, Mike Andrews, Ajay KumarNXP Semiconductor: Geoff Mole, Ahmed Hemani, Roger Witlox, Greg Ehmann, Maurizio Vitale,Erwin de KockProsilog/Magillem: Stephane Guntz, Cyril Spasevski25Sonics: Kamil SynekST Microelectronics: Christophe Amerijckx, Serge Hustin, Anthony McIsaac, Stephane GuenotSynopsys: Mark Noll, Bernard DeLay, John A. Swanson, Paul Wyborny30Texas Instruments: Bob T. Maaraoui, Bertrand BlancSpecial acknowledgment is given to:Mentor: Contribution of initial schema upon which the work is based35Synopsys: Contribution of constraint structureThe Board of Directors of The SPIRIT Consortium active during the release of the IP-XACT Standard:Ralph vonVignau, NXP, PresidentChristopher Lennard, ARM, Vice-PresidentLynn Horobin, Executive Secretary40John Goodenough, ARMStan Krolikoski, CadenceLuke Smithwick, Kathy Werner, FreescaleJean Bou-Farhat, Gary Delp, LSIBill Chown, Mentor GraphicsBart de Loore, NXP SemiconductorsSerge Hustin, ST MicroelectronicsPierre Bricaud, SynopsysLoic Le-Toumelin, Texas Instruments455055Copyright 2007 The SPIRIT Consortium. All rights reserved.This is an unapproved IP-XACT Standards Draft, subject to change.Embargoed from distribution beyond The SPIRIT Consortium reviewing membershipv

IP-XACT Standard/D4, December 19, 20071510152025303540455055viCopyright 2007 The SPIRIT Consortium. All rights reserved.This is an unapproved IP-XACT Standards Draft, subject to change.Embargoed from distribution beyond The SPIRIT Consortium reviewing membershipDraft Standard for

IP-XACT meta-data and tool interfacesIP-XACT Standard/D4, December 19, 20071Contents1.Overview. . 1Purpose . 1IP-XACT design environment . 11.3.1System design tool . 21.3.2Design intellectual property . 31.3.3Generators . 31.3.4IP-XACT interfaces . 4IP-XACT enabled implementations . 41.4.1Design environments . 41.4.2Point tools . 51.4.3IPs . 51.4.4Generators . 5Conventions used . 51.5.1Visual cues (meta-syntax) . 51.5.2Notational Conventions . 51.5.3Syntax examples . 51.5.4Graphics used to document the Schema . 6Use of color in this standard. 9Contents of this standard . 92.Normative references . 113.Definitions, acronyms, and abbreviations. use model . 214.14.25.Definitions. 12Acronyms and abbreviations. 185Roles and responsibilities. 214.1.1Component IP provider . 214.1.2SoC design IP provider . 214.1.3SoC design IP consumer . 224.1.4Design tool supplier . 22IP-XACT IP exchange flows. 224.2.1Component or SoC design IP provider use model . 234.2.2Generator provider use model . 234.2.3System design tool provider use model . 23IP-XACT schema. 255.1Schema overview . 255.1.1Design schema . 255.1.2Design configuration schema . 255.1.3Component schema . 255.1.4Bus definition schema . 255.1.5Abstraction definition schema . 255.1.6Abstractor schema . 255.1.7Generator schema . 26Copyright 2007 The SPIRIT Consortium. All rights reserved.This is an unapproved IP-XACT Standards Draft, subject to change.Embargoed from distribution beyond The SPIRIT Consortium reviewing membershipvii3540455055

IP-XACT Standard/D4, December 19, 200715.255.3106.Draft Standard forIP-XACT objects. 265.2.1Object interactions . 265.2.2VLNV . 275.2.3Version control . 29Design models . 295.3.1Design . 305.3.2Hierarchy represented by a design file . 305.3.3Design interconnections . 325.3.4Hierarchical connectivity . 33Interface definition descriptions . 356.16.2Definition descriptions . 35Bus definition . 356.2.1Schema . 356.2.2Description . 366.2.3Example . 366.3 Abstraction definition. 376.3.1Schema . 376.3.2Description . 386.3.3Example . 396.4 Ports. 406.4.1Schema . 406.4.2Description . 406.4.3Example . 416.5 Wire ports. 416.5.1Schema . 416.5.2Description . 426.5.3Example . 426.6 Qualifiers. 426.6.1Schema . 426.6.2Description . 436.6.3Example . 436.7 Wire port group . 446.7.1Schema . 446.7.2Description . 446.7.3Example . 456.8 Wire port ‘mode’ constraints. 456.8.1Schema . 456.8.2Description . 466.8.3Example .