• 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. Scan Reorder issue

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 16980
  • 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

Scan Reorder issue

Vishnu Chada
Vishnu Chada over 15 years ago

We have a scan connection as follows :

               FF1(from Q,SDFF)   -----------BUF ---------------FF2 (to D , DFF)
                                                                                 |
                                                                                 |
                                                                                 ________(to other logic)


Scan def :

+ORDERED
        FF1 ( IN SI ) ( OUT Q )
        FF2  ( IN D ) ( OUT Q )
+FLOATING
         ---
        ---

When i do scan reordering the tool mess with the functional path which is shown in above representation.Connects that entire logic to other flop, which is caught in lec.It does not honor the ORDERED section properly.Is there any known issue where encounter has problem handling Regular Flop (with D input as part of the scan chain) in the ORDERED section instead of a ScanFlop ?

Tried using 7.1 and 8.1USR3.

Appreciate your help.

Regards,
Vishnu

  • Cancel
Parents
  • Vishnu Chada
    Vishnu Chada over 15 years ago

    I was able to bypass the above mentioned issue by adding the buffer to the ordered list.But am still facing issue when the scan chain ends it D pin of the flop.

     

    + STOP <instance> D

     Using 8.1 USR3. I think encounter inherently has problem handling scan chains where there is  D pin in the chain instead of SI.

     Would like to know from the user community or cadence personnel if this is true from there previous experiences.

     Appreciate your time.


    Regards,

    Vishnu

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Vishnu Chada
    Vishnu Chada over 15 years ago

    I was able to bypass the above mentioned issue by adding the buffer to the ordered list.But am still facing issue when the scan chain ends it D pin of the flop.

     

    + STOP <instance> D

     Using 8.1 USR3. I think encounter inherently has problem handling scan chains where there is  D pin in the chain instead of SI.

     Would like to know from the user community or cadence personnel if this is true from there previous experiences.

     Appreciate your time.


    Regards,

    Vishnu

    • 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