Home > Community > Forums > Logic Design > RTL Compiler: DFT Checks and non controllable/observable I/O

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

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

Last post Thu, Jul 19 2012 8:24 AM by moogyd. 6 replies.
Started by moogyd 31 Jan 2012 06:01 AM. Topic has 6 replies and 7117 views
Page 1 of 1 (7 items)
Sort Posts:
  • Tue, Jan 31 2012 6:01 AM

    • moogyd
    • Top 500 Contributor
    • Joined on Mon, Mar 22 2010
    • Posts 23
    • Points 385
    RTL Compiler: DFT Checks and non controllable/observable I/O Reply

    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

     

    • Post Points: 20
  • Tue, Jan 31 2012 6:16 AM

    • grasshopper
    • Top 25 Contributor
    • Joined on Fri, Jul 18 2008
    • Chelmsford, MA
    • Posts 242
    • Points 3,205
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O Reply
    Hi Steven, I believe you are looking for attribute dft_controllable as described below rc:/> get_attr -h *controllable* * attribute category: dft attribute name: controllable category: dft (controls design for test) object type: test_clock access type: read-write data type: boolean default value: false help: Whether the test clock is controllable in test mode. attribute name: dft_controllable category: dft (controls design for test) object type: pin access type: read-write data type: string default value: help: In test mode the output pin can take either the non_inverting or inverting value of the input pin. attribute name: dft_include_controllable_pins_in_abstract_model category: dft (controls design for test) object type: root access type: read-write data type: DftIncludeControllablePinsEnum default value: allmodes help: Enable writing out controllable pins in abstract model. hope this helps, gh-
    • Post Points: 35
  • Tue, Jan 31 2012 6:39 AM

    • moogyd
    • Top 500 Contributor
    • Joined on Mon, Mar 22 2010
    • Posts 23
    • Points 385
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O Reply

    Hi,

    Excellent - this is just what I'm looking for.

    Thanks for the quick feedback, Steven

    • Post Points: 5
  • Wed, Feb 1 2012 10:57 AM

    • moogyd
    • Top 500 Contributor
    • Joined on Mon, Mar 22 2010
    • Posts 23
    • Points 385
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O Reply

    Hi Again,

    Having checked further, this is not what I want.  This attribute only applies to pins, and is intended for internal black boxes.

    I need something to apply to design ports, and to indicate that a pin is not controllable (even though it is a primary input)

    Any additonal suggestions?

    Thanks, Steven

    • Post Points: 35
  • Thu, Feb 2 2012 9:54 AM

    • bmiller
    • Top 200 Contributor
    • Joined on Tue, Oct 14 2008
    • Ottawa, Ontario
    • Posts 42
    • Points 570
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O 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

     

    • Post Points: 5
  • Tue, Jun 12 2012 7:57 AM

    • Douglas Foster
    • Not Ranked
    • Joined on Wed, Nov 4 2009
    • Santa Maria, Rio Grande do Sul
    • Posts 1
    • Points 20
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O Reply

    Hi Steven,

    Did you get any solution for your trouble?

    I have a trouble that it seems very close to your.

    I need to include DFT accessibility in design but I will not have access for both input and output ports of digital circuit because they are connected to analog peripherals blocks.

    Is there any command in Encouter Test or RTL Compiler which won't take in account the use of the I/O ports for the test pattern generation? I think it isn't a recommend approach for test, but in my case I need to try it.

    BR,

    Douglas Foster

    Douglas Camargo Foster Digital Integrated Circuit Designer Santa Maria Design House - SMDH Santa Maria, RS - Brazil www.smdh.org
    • Post Points: 20
  • Thu, Jul 19 2012 8:24 AM

    • moogyd
    • Top 500 Contributor
    • Joined on Mon, Mar 22 2010
    • Posts 23
    • Points 385
    Re: RTL Compiler: DFT Checks and non controllable/observable I/O Reply

    Hi Douglas,

    I did not find a solution other than to disable auto-identification as described by Brad.

     Steven

    • Post Points: 5
Page 1 of 1 (7 items)
Sort Posts:
Started by moogyd at 31 Jan 2012 06:01 AM. Topic has 6 replies.