generate register model from sonics ip xact

To significant gains due to the reduction of time during the assembly process.Īlthough IP-XACT 1.4, the latest version of the IP-XACT specifications, enables users to capture OCP core descriptions (such as OCP interfaces at RTL or TLM levels, ports and parameters) and OCP connections between core interfaces (including connections for OCPĭataflow and sideband signals), it does not support natively the full configurability features of an OCP interface, where a change of an OCP parameter value enables the addition of a new signal Have been automated (instead of 35 percent with the previous methodology) which directly translates connection of ports between different levels of hierarchy, based on naming conventions, for example.Īs a direct result of this approach, more than 70 percent of all connections in one particular system.connectivity checking (for example to verify that no port was left dangling beforeshipping this system to the verification team).insertion of isolation cells at multiple levels of hierarchy.Other examples of the types of automated tasks natively performed by Magillem or through VHDL netlist from the IP-XACT descriptions. Using Magillem, our IP-XACT flagship Design Environment, different engineering teams haveīeen able to exchange, integrate and build complex platforms and generate the corresponding Magillem Design Services, as a member of both OCP-IP organization and The Spirit Consortium, has brought its expertise to help this client move to this methodology for its next generation of wireless chips. Practical benefits of this OCP and IP-XACT based methodology have been recently demonstrated by a customer of Magillem Design Services, an American semiconductor company.

The IP-XACT descriptions and perform various automated tasks, such as launching checks,Ĭreating connections automatically, generating a VHDL platform netlist or dumping register lowlevel In addition, specific executables (called “generators” using IP-XACT terminology) may process WhenĬompleted, this sub-system IP-XACT description may be shipped to another team or company for integration into the full system in the same way (possibly using a different IP-XACT compliant assembly tool since they will still remain interoperable). The IP-XACT compliant configuration script may be directly launched into the same tool, and additional connections/parameterization performed. The system integrator who receives this UART can automatically import it into his IP-XACT compliant platform assembly tool and integrate it into his existing sub-system (which is also being captured in IP-XACT).

Generate register model from sonics ip xact