• 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. How to make FPGA symbol for schematic

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 167
  • Views 19350
  • 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

How to make FPGA symbol for schematic

Leeya
Leeya over 11 years ago

Hi, I saw people make schematic symbol for a complex FPGA(almost 400 pins), and that schematic break one FPGA into many different pages. Like bank1 at the first page, bank 2 at the second page,etc.How to build a multi symbols FPGA?

Thanks 

  • Cancel
  • redwire
    redwire over 11 years ago

     Go with what works best for your design flow.  I have found that it is useful in many circumstances to make a separate symbol for each bank and include the VCC/GND for that bank in that block.  More than 50-75 pins per block can be cumbersome on a schematic unless you have some grouped busses for example.

     

    The first thing I do is convert the datasheet pinlist to a text file using Adobe or some PDF reader.  In some circumstances the FPGA vendor will supply an Excel pinlist -- just ask.

    Once you have the pinlist you can quickly use the OrCAD spreadsheet editor to place the pins in each block.  You want to have heterogenous part selected and predetermine how many blocks you want.  In the spreadsheet editor you can choose which block the pin goes and what type of pin it is (input, output, bidir, 3state).

    Once the spreadsheet is completed you can review the symbols and move pins as required for better schematic connectivity.

     Think about how to manage pinswapping in the future --- that is a very powerful and necessary feature of FPGAs.  Read up on that.

    Hope that starts you off.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Leeya
    Leeya over 11 years ago

    Hi Redwire,

    That really helpful~~Thank you so much.

    Last Friday, I did a hand typing a 96 pins BGA. It take me a few hours and many typing errors~~

    This is very very very good idea

    Thanks 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • VincentS
    VincentS over 11 years ago

    Leeya,

     

    I do my FPGAs the same way as redwire except I put all the power and gnds in a power section to unclutter the signal sections. It is a good way to do symbols for FPGAs.

     

    Good luck.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • redwire
    redwire over 11 years ago

    VincentS said:
    I do my FPGAs the same way as redwire except I put all the power and gnds in a power section to unclutter the signal sections. It is a good way to do symbols for FPGAs.



    I have found that for multi-voltage parts such as Xilinx and Altera by placing the associated voltage / gnd pins for *that* bank with the IO pins helps to remind the design engineer (me in most cases) to put the proper voltage on that bank.  If you are dealing with a common voltage part then yes, I too have a block of vcc/gnd/vccio on a separate symbol.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Robert Finley
    Robert Finley over 11 years ago

    The only time I manually type in pin names is on something with fewer than 6 pins.

     Check out the EDABuilder app from EMA-EDA.

    Zero retyping... From either the Altera BSM file or a spreadsheet.

    Extracted the pinmap for Intel's 2011-pin Pentium package recently from their datasheet PDF.

    And, their footprint builder rocks too.  

    Only thing easier is to let the Cadence FPGA planner dynamically manage pin assignments.

    Safer to split the FPGA up by banks and include the pin-driver power of that bank. If you're dealing with a mix of 1.8v, 2.5v, and 3.3v logic, prevents goofs.

     

    • 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