Stats

  • Locked Locked
  • Replies 20
  • Subscribers 90
  • Views 19612
  • 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

Can CTS stop tracing on hierarchical module ports?

archive

Dear community,

my clock signal is connected to the clock network on the one hand. On the other hand it is connected to a module's input. Within this module the signal is always used as a data signal (chip is switched to different mode of operation for this).

This module contains logic, therefore CTS traces through the input ports. AFAIK tracing can only stop at top level ports or leaf cell pins.

Is there any way to make CTS stop tracing at the module's input port (like ExcludedPin/ExcludedPort - which don't work)?

Many thanks in advance for your suggestions!


Originally posted in cdnusers.org by agruebl
Parents

  • Hi agruebl,

    You need the "LeafPin" command in your ".ctstch" file on the input pin of the first device(s) in your module.

    If you look at the "Encounter User Guide" (soceUG.pdf), "Synthesizing Clock Trees" (Chapter 11),
    Product Version 6.2.2 (SOC6.2), August 2007, on Page 477, you will see the following:

    LeafPin
    + pinName rising | falling
    + …


    Marks the input pin as a “leaf” pin for non-clock-type
    instances, stops tracing, and balances clock skew.
    Note: Use the LeafPin statement only with input pins.
    CTS ignores LeafPin statements that are associated
    with output pins.

    Choose one of the following:
    rising - CTS treats the input pin as a risingedge-
    triggered flip-flop clock pin.
    falling - CTS treats the input pin as a fallingedge-
    triggered flip-flop clock pin.

    Here's a real life example. These are input pins of devices where clock was stopped
    from tracing through combinational logic gates.

    LeafPin
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/a1
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/a2
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/b1
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/b2


    Regards - R.M.


    Originally posted in cdnusers.org by raul63
Reply

  • Hi agruebl,

    You need the "LeafPin" command in your ".ctstch" file on the input pin of the first device(s) in your module.

    If you look at the "Encounter User Guide" (soceUG.pdf), "Synthesizing Clock Trees" (Chapter 11),
    Product Version 6.2.2 (SOC6.2), August 2007, on Page 477, you will see the following:

    LeafPin
    + pinName rising | falling
    + …


    Marks the input pin as a “leaf” pin for non-clock-type
    instances, stops tracing, and balances clock skew.
    Note: Use the LeafPin statement only with input pins.
    CTS ignores LeafPin statements that are associated
    with output pins.

    Choose one of the following:
    rising - CTS treats the input pin as a risingedge-
    triggered flip-flop clock pin.
    falling - CTS treats the input pin as a fallingedge-
    triggered flip-flop clock pin.

    Here's a real life example. These are input pins of devices where clock was stopped
    from tracing through combinational logic gates.

    LeafPin
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/a1
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/a2
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/b1
    + i_macro/i_core/i_usb_device_top/i_usb_asyn_hand/asyn_hand_ps1/u19/b2


    Regards - R.M.


    Originally posted in cdnusers.org by raul63
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.