• 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. Allegro X Scripting - TCL
  3. connecting multiple signals to component

Stats

  • State Suggested Answer
  • Replies 4
  • Answers 1
  • Subscribers 13
  • Views 4184
  • Members are here 0
More Content

connecting multiple signals to component

mikeyam
mikeyam over 2 years ago

Hello

I need to connect multiple signals for DDR memory to FPGA component.

I have list of signals in Excel with required FPGA pins it should be connected to. 

All the memory signal go to the same part of the FPGA component.

Its more than 100 signals and i have to do it for 4 banks, so its a lot of connectivity if done manually.

Is there any way to create such connectivity more automatically?

example, if we could generate some verilog like file from excel saying which signal name goes to which pin name.

Is there anything like this existing in Orcad?

Thank you in advance,

Michael

  • Cancel
  • Sign in to reply
Parents
  • avant
    0 avant over 2 years ago

    Maybe you can generate and then import a flat netlist from a spreadsheet..

    Here's the general format: 

    $PACKAGES

    CAP0201 ! 'CAP,4.7UF' ! '4.7UF' ; C29

    $NETS

    CLK_N ; J2.1 U1.3

    $END

    'CAP,4.7UF' is the device file

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • avant
    0 avant over 2 years ago

    Maybe you can generate and then import a flat netlist from a spreadsheet..

    Here's the general format: 

    $PACKAGES

    CAP0201 ! 'CAP,4.7UF' ! '4.7UF' ; C29

    $NETS

    CLK_N ; J2.1 U1.3

    $END

    'CAP,4.7UF' is the device file

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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