• 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. PAD connections in Encounter

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 93
  • Views 15485
  • 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

PAD connections in Encounter

naderi
naderi over 16 years ago

 Hello everyone, 

I have manually modified synthesized RTL to include pad cells and their connections, then, fed them to Encounter v6.2 for place and route. After place and route, I realized vdd and gnd net are not connected to any pin.

I am wondering if I have to remove pad cells from input RTL.

Also, other IOs are connected to the associated pads by a metal layer that has the minimum width. What is the best way to define width of metal layer for connecting to the pads.

Thanks,

Ali 

  • Cancel
Parents
  • Willbe
    Willbe over 16 years ago

    Dear all,

     I have a problem. I define in my verilog file Pin and and I/O and connect them together. I define in the abc.io the Pin and Pad,  an d load the design in encounter. The pins a placed but not the Pad due to some errors. 

    Verilog File abc.v:

    module abc(clk, spi_sck_BU12P, spi_sdi_BU12P, spi_sdo_ICP, spi_chip_select_BU12P

    , led_BU12P, switch_ICP, reset_ICP, flash_reset_i_ICP, cc_vreg_en_BU12P

    , cc_reset_BU12P, cc_fifo_ICP, cc_fifop_ICP, cc_cca_ICP, cc_sfd_ICP

    , lcd_d_BBT16P, lcd_rs_BU12P, lcd_rw_BU12P, lcd_e_BU12P);

     

    BU12P spi_chip_select_2_Inst_BU12P(.A(spi_chip_select_pad[2]), .PAD(spi_chip_select_BU12P[2]));

    BU12P spi_chip_select_1_Inst_BU12P(.A(spi_chip_select_pad[1]), .PAD(spi_chip_select_BU12P[1]));

    BU12P spi_chip_select_0_Inst_BU12P(.A(spi_chip_select_pad[0]), .PAD(spi_chip_select_BU12P[0]));

    ICP flash_reset_i_Inst_ICP(.PAD(flash_reset_i_ICP), .Y(flash_reset_i_pad));

     ---------

    -------

    endmodule

     

    Reading IO assignment file "abc.io" ...

    **Warn: ignored IO file "spi_top.io" line 14: Pad: flash_reset_i_Inst_ICP N

    Reason: unable to determine object from name.

    **Warn: ignored IO file "spi_top.io" line 17: Pad: spi_chip_select_0_Inst_BU12P N

    Reason: unable to determine object from name.

    .........

    Can anyone tell what it does mean?

    Thanks,

     

    Eric

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Willbe
    Willbe over 16 years ago

    Dear all,

     I have a problem. I define in my verilog file Pin and and I/O and connect them together. I define in the abc.io the Pin and Pad,  an d load the design in encounter. The pins a placed but not the Pad due to some errors. 

    Verilog File abc.v:

    module abc(clk, spi_sck_BU12P, spi_sdi_BU12P, spi_sdo_ICP, spi_chip_select_BU12P

    , led_BU12P, switch_ICP, reset_ICP, flash_reset_i_ICP, cc_vreg_en_BU12P

    , cc_reset_BU12P, cc_fifo_ICP, cc_fifop_ICP, cc_cca_ICP, cc_sfd_ICP

    , lcd_d_BBT16P, lcd_rs_BU12P, lcd_rw_BU12P, lcd_e_BU12P);

     

    BU12P spi_chip_select_2_Inst_BU12P(.A(spi_chip_select_pad[2]), .PAD(spi_chip_select_BU12P[2]));

    BU12P spi_chip_select_1_Inst_BU12P(.A(spi_chip_select_pad[1]), .PAD(spi_chip_select_BU12P[1]));

    BU12P spi_chip_select_0_Inst_BU12P(.A(spi_chip_select_pad[0]), .PAD(spi_chip_select_BU12P[0]));

    ICP flash_reset_i_Inst_ICP(.PAD(flash_reset_i_ICP), .Y(flash_reset_i_pad));

     ---------

    -------

    endmodule

     

    Reading IO assignment file "abc.io" ...

    **Warn: ignored IO file "spi_top.io" line 14: Pad: flash_reset_i_Inst_ICP N

    Reason: unable to determine object from name.

    **Warn: ignored IO file "spi_top.io" line 17: Pad: spi_chip_select_0_Inst_BU12P N

    Reason: unable to determine object from name.

    .........

    Can anyone tell what it does mean?

    Thanks,

     

    Eric

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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