• 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. RC could not find scan equivalent cell

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13789
  • 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

RC could not find scan equivalent cell

Lamech
Lamech over 14 years ago
Hi, I am a relatively new to cadence tools. I am trying to insert scan chain into my design. But getting the following error... "Could not find a scan-equivalent cell. DFT-510. I have added the test_cell group as specified in the documentation. Also I have set dont_use, dont_touch attributes to false in .lib file. In the RC tcl file I have set "set_attribute preserve false SCANFF" and "set_attribute avoid false SCANFF". I have tried both Muxed scan style and LSSD scan style with different cells. Can some one tell me what could be the problem? or any suggestions on scan chain design in cadence? Kind of show stopper in our project, so any help will be highly appreciated... Thanks in Advance, Charles
  • Cancel
  • grasshopper
    grasshopper over 14 years ago

     Hi Charles,

     seems like a library problem. if you can send the .lib for your non-scan and scan equivalent or the output of 

     ls -al [find / -libcell <scan/nonscan cell>

     we may be able to help

     You can also try the command

    Usage: set_scan_equivalent -non_scan_cell <libcell> -scan_cell <libcell> [-tieoff_pins <string>] [-pin_map <string>]

        -non_scan_cell <libcell>:
            the non-scan cell to be replaced
        -scan_cell <libcell>:
            the scan cell to map to
        [-tieoff_pins <string>]:
            a list of the form "{{<pin> <tieoff_value>} ... {<pin> <tieoff_value>}}" indicating the various scan pins and their respective active values
        [-pin_map <string>]:
            a list of the form "{{<non-scan pin> <scan pin>} ... {<non-scan pin> <scan pin>}}" indicating the equivalence between pins with different names in the scan and non-scan
            cells

    Note that, it should work out of the box so if you need to use set_scan_eq there is probably something wrong with the library or RC but it may also provide you some useful feedback as to what the root cause is

    regards,

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 14 years ago

     BTW, please post RC questions on logic design forum

     gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Lamech
    Lamech over 14 years ago
    Hi Grasshopper, Thanks for the reply. I dont know whether I can continue this thread here in this forum! I am attaching a file which has scan and non scan cell description, its not the complete .lib file though... Thanks Again, Charles
    • DFFnSCAN.txt
    • View
    • Hide
    • 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