• 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. Custom IC Design
  3. Cannot abut devices in Layout XL, tsAbutFunction failed...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14001
  • 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

Cannot abut devices in Layout XL, tsAbutFunction failed.

imcostanzo
imcostanzo over 5 years ago

Hello,

I am trying to abut devices in Layout XL. In the past, I have been able to either use the Chain Devices dialog available in the connectivity drop-down menu or by simply placing devices that share the same net on top of each other. However today I can't seem to do that. I get a warning that the function tsAbutFunction failed.

This is from the CIW:

*WARNING* (LX-2205): Unable to abut the following two instances:
 'M9.1' (instance of cell 'nmos2v')
 'M9.2' (instance of cell 'nmos2v')
This occurred because the abutment function (tsAbutFunction) failed
when called to adjust pcell parameters for abutment (event 2).
INFO (LX-1100): Correct tsAbutFunction and try again.
INFO (LCE-1007): The cell verifier found
INFO (LCE-1008):    671 open(s)
*Error* fix: argument #1 should be a number (type template = "n") - "iPar(\"simM\")"

Searching for tsAbutFunction doesn't turn anything up and I didn't find any information or fix in the Abutment documentation. Has anyone ran into this issue before?

Thanks,

Ian

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Ian,

    The abut function will have been defined as part of your PDK, and so tsAbutFunction will have been written by the PDK provider (probably). Without seeing that, I can't comment as to what might be wrong, other than the fact that it's clearly expecting something to be a number when it is not.

    I found some reports with similar messages - but they were quite old and so I'm not sure they are definitely the same cause (and even so, I think it was a PDK issue). Best to contact customer support so we can debug properly.

    Andrew.

    • 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