• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. RockeIO Syskit simulation using Sigxp

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 164
  • Views 15124
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RockeIO Syskit simulation using Sigxp

archive
archive over 17 years ago

We have downloaded the Virtex4_syskit for using Rocket IO buffer models. The Kit works with standalone Synopsys HSPICE simulator . To use these models in Cadence Allegro SI simulation we have encapsulated these models in Cadence native DML format. The vendor supplied encrypted HSPICE I/O models are encapsulated in a DML macromodel , as described in the document ‘ How to aSIhspice.pdf ‘ and’ Howto wrapHSPICE.pdf ‘ from Cadence support. We have also included the necessary Hspice options and parameters required for the simulation. We find that the netlist is being generated correctly. We need the clarifications for the following 1. The Hspice simulator (Synopsys) on reading the encrypted RocketIO models gives the following error while reading the included file for receiver model . **warning** unrecognizable command card. We have attached the TX and RX DML file for the reference. Please guide us for the same. 2. The example spice deck file in the sisKit has a PRBS generator included. We have included the PRBS input by a subcircuit call(This is in the stimulus directory of the Virtex4_syskit named vsource_no_jitter_2pt5_Gbps.inc) in the body of the macromodel. Parameters required for simulation are also included. The extracted topology needs a custom stimulus to be defined for the active driver , i.e. the buffer model for RocketIO Tx differential buffer. How are the two inputs , i.e. the PRBS input (subcircuit call ) and custom stimulus treated in this case? Is there any error in constructing our macromodels. 3. designname.tr0 have been generated from the HSPICE run by giving the option ‘csdf’ in hspiceoptions. Can these files be viewed in Avanwaves?


Originally posted in cdnusers.org by jaya
rocket_tx.zip
  • Cancel
  • archive
    archive over 17 years ago

    Hi Jaya,

    I'd like to suggest that you look at the Virtex II Pro Kit from Xilinx (Virtex-II Pro Signal Integrity Simulation Kit v3.7) combined together with the Xilinx RocketIO Design-in kit from Cadence (http://www.cadence.com/community/allegro/silicon_designin/kits.aspx?type=FPGA&sort=&abs=1&exclude=).

    The two kits combine together to present working examples of simulating RocketIO HSpice models in the Allegro PCB SI and SigXp environment.

    Best regards,

    brad


    Originally posted in cdnusers.org by bgriffin
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Brad,

    As per your suggestion I looked into the Virtex- II Pro kit from Xilinx.

    I could run the example simulations there.
    Also we assigned the Virtex-II pro RocketTx and RocketRx macromodels to our design , (which actually uses Virtex -4 device) . This also works fine . I guess that there is a problem in our macromodels(which use Virtex4 SPICE models) in  the way that the PWL stimulus is fed to the macromodel .

    Can I get some help regarding this?

    Regards.


    Originally posted in cdnusers.org by jaya
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Brad,

    As per your suggestion I looked into the Virtex- II Pro kit from Xilinx.

    I could run the example simulations there.
    Also we assigned the Virtex-II pro RocketTx and RocketRx macromodels to our design , (which actually uses Virtex -4 device) . This also works fine . I guess that there is a problem in our macromodels(which use Virtex4 SPICE models) in  the way that the PWL stimulus is fed to the macromodel .

    Can I get some help regarding this?

    Regards.

    -- jaya


    Originally posted in cdnusers.org by jaya
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    It appears I am running successfully the Virtex-5 FPGA RocketIO Transceiver Signal Integrity Simulation Kit (v5_rio_sis_kit_2_0) version 2.0 release date 5/14/2008. I have a SPICE license but not Avanwaves. I am using Hspui for Windows A-2008.3 Does anyone know if I can view the results in Allegro SI if I don't have an Avanwaves license? Also I have run the Virtex II Pro SI Simulation Kit 3.0 sis_kit_v2p_v3.7 and it runs good. But I now want to use it for the Virtex 5. How difficult is it to change it to run the Virtex 5?


    Originally posted in cdnusers.org by cswanson@integritysim.com
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Two ideas: First, contact Xilinx. They need to know that you want to use their models in the Allegro PCB SI environment. That will enable more collaboration between Xilinx and Cadence. Second, contact your local Cadence field application engineer. He can get you started on the steps required for Allegro PCB SI to work with HSpice models so that you can use the HSpice simulation engine option.

    brad


    Originally posted in cdnusers.org by bgriffin
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information