• 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. Digital Implementation
  3. FlipChip PIO Flow: Assignment of Bumps fails, but why?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13312
  • Members are here 0
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

FlipChip PIO Flow: Assignment of Bumps fails, but why?

marten
marten over 10 years ago

Hi there,

when I try to assign signal bumps (EDI 14.12) to my IO pins, I always get this error message:

**WARN: (ENCSP-6014):    I/O pin 'DATA_IN[82]' does not connect to placed Area I/O instance or hard macro and will be ignored for bump assignment. Most likely reason is:
1. The Area I/O instance or hard macro is not placed.
2. I/O pin does not connect to I/O instance or hard macro in Verilog netlist.
[...]
**WARN: (ENCSP-6011):    There is no I/O pin to assign.
*** End Bump Assignment (cpu=0:00:00.0, real=0:00:00.0, mem=1135.2M) ***

I checked both reasons:

1.) I checked properties of the IO cells, they all have status "PLACED"

2.) I assigned the IO pins within my vhdl code, thats why all the io cells got found even without loading an IO file. And also in the synthesized netlist, they are there

According to the SoC user guide, I did the following steps:

  • init design
  • load io file, load eco file
  • load floorplan file
  • placePIO
  • ciopCreateBump
  • assignBump


So what am I doing wrong here? Why aren't the bumps got assigned?

  • Cancel
  • marten
    marten over 10 years ago
    Found the error: the used pad cells were not member of lef class "PAD AREAIO". I changed the used cells in my vhdl code, so that now cells of class "PAD AREAIO" get used.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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