• 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. Logic Design
  3. how to define scan chains in RC

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 15333
  • 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

how to define scan chains in RC

tanyacool
tanyacool over 12 years ago

 Hi, 

 How to define the scan chains in RC and how to prevent the broken chains .

Tha basic question points to on how prevent the scan inputs of the scanable flops to get not tied up to 0.

 

Thanks 

Tanyacool

  • Cancel
Parents
  • grasshopper
    grasshopper over 12 years ago

    Hi Tanvi,

    The DFTuser guide is probably the best place to get the question answered. Plenty of examples and all the details an email cannot capture. 

    As per the SI connected to 0, it will be connected to the SO/Q of another flop upon execution of connect_scan_chains if your chains are properly configured. In fact, default is loopback and not connected to 0 so an SI connected to zero may be flagging other issues in your design or scripting

     gh-

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 12 years ago

    Hi Tanvi,

    The DFTuser guide is probably the best place to get the question answered. Plenty of examples and all the details an email cannot capture. 

    As per the SI connected to 0, it will be connected to the SO/Q of another flop upon execution of connect_scan_chains if your chains are properly configured. In fact, default is loopback and not connected to 0 so an SI connected to zero may be flagging other issues in your design or scripting

     gh-

     

    • 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