Stats

  • Locked Locked
  • Replies 6
  • Subscribers 63
  • Views 4019
  • 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

RTL Compiler: DFT Checks and non controllable/observable I/O

moogyd

Hi,

I am synthesizing a top level digital block that has interfaces to external pads and to a top level analog block.

When I run DFT checks, it assumes that all ports are controllable, which is not the case for the signals from the top level analog block.

Is the an attribute I can apply to these ports to indicate that they are not controllable?

Thanks,

Steven

 

Parents

  •  Steven,

     I think the only thing you can do is prevent RC from automatically identifying test clocks and test mode signals.  

     To turn off auto identifcation of test signals:

      set_attr dft_identify_test_signals false /

      set_attr dft_identify_top_level_test_clocks false /

     

    The defaults are "true".

     You will have to manually define test clocks and test mode signals (define_dft test_clock, define_dft test_mode, etc) on the ports that CAN be controlled on the tester.  Any internal clocks that cannot be controlled can have the test clock muxed on them using fix_dft_violations.

    Regards,

    Brad

     

Reply

  •  Steven,

     I think the only thing you can do is prevent RC from automatically identifying test clocks and test mode signals.  

     To turn off auto identifcation of test signals:

      set_attr dft_identify_test_signals false /

      set_attr dft_identify_top_level_test_clocks false /

     

    The defaults are "true".

     You will have to manually define test clocks and test mode signals (define_dft test_clock, define_dft test_mode, etc) on the ports that CAN be controlled on the tester.  Any internal clocks that cannot be controlled can have the test clock muxed on them using fix_dft_violations.

    Regards,

    Brad

     

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.