This field defines the byte enable for a Flit.
This field is applicable for write data, DVM payload and snoop response data Flit transfers. It consists of a bit for each data byte in the DAT flit, which when set indicates that the corresponding data byte is valid.

- Indicates the replicated channel ID on which the flit is sent or received.

• This attribute is applicable only when the CHI-E replicated channels feature is enabled.
• This attribute is set for both TX and RX flits internally in the VIP driver and must not be set by users.

- Indicates the current clock cycle count.

• This attribute is incremented by 1 for each clock cycle at the posedge

- Current value of tx_flitpend_flitv_delay

• Initial value is ame as tx_flitpend_flitv_delay
• Must not be set by the users, set by VIP Link Layer driver internally
• For Protocol Flits:
  • When svt_chi_node_configuration :: tx_link_deactivation_time > 0, this variable will not be reset to tx_flitpend_flitv_delay due to link deactivation while tx_flitpend_flitv_delay is being applied
  • When svt_chi_node_configuration :: tx_link_deactivation_time <= 0, this variable will be reset to tx_flitpend_flitv_delay due to link deactivation while tx_flitpend_flitv_delay is being applied

- Current value of tx_flit_delay

• Initial value is ame as tx_flit_delay
• Must not be set by the users, set by VIP Link Layer driver internally
• For Protocol Flits:
  • When svt_chi_node_configuration :: tx_link_deactivation_time > 0, this variable will not be reset to tx_flit_delay due to link deactivation while tx_flit_delay is being applied
  • When svt_chi_node_configuration :: tx_link_deactivation_time <= 0, this variable will be reset to tx_flit_delay due to link deactivation while tx_flit_delay is being applied

This field defines the Reserved Value defined by the user for Protocol Data VC Flit.
Any value can be driven on this field.
Note that this field is not applicable when svt_chi_node_configuration :: dat_flit_rsvdc_width is set to zero.

This field defines the Opcode for Data VC Flit.

This field defines the data for a DAT flit.
This field is applicable for write data, read data, DVM payload and snoop response data Flit transfers.

This field indicates the relative position of the data chunk being transferred within the 512b cache line.
Refer to section '19.3.5.23 DataID' of AMBA CHI specification.
Below is an example explining this field usage.
Consider that the width of the data VC is 128b(16B). The data size of a transaction is 512b(64B). This transaction requires 4 data VC Flits.
|------------------------------------------------|
| Data VC Flit No | 128b slice of data | data ID |
|------------------------------------------------|
| 1 | data[127:0] | 2'b00 |
|------------------------------------------------|
| 2 | data[255:128] | 2'b01 |
|------------------------------------------------|
| 3 | data[383:256] | 2'b10 |
|------------------------------------------------|
| 4 | data[511:384] | 2'b11 |
|------------------------------------------------|

This field defines the type of the Flit.

This field defines the Opcode used for Request VC Flit.

This field indicates the error status of the response. It is applicable for RSP, DAT flits.

This field defines the Opcode for Response VC Flit.

This field defines the Opcode for Snoop VC Flit.

• In case of Link Flit:
  • When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: FLIT_AND_LCRD_AVAILABLE:
    • This attribute defines the number of clock cycles the TX***FLITPEND signal is asserted before asserting TX***FLITV signal.
  • When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: PERMANENT or svt_chi_node_configuration :: FLIT_AND_LCRD_AVAILABLE_FOR_PROT_FLIT_AND_PERMANENT_FOR_LINK_FLIT:
    • This delay is not applicable and value of this attribute is ingored.
  • Unsupported: When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: FLIT_AVAILABLE

• In case of Protocol Flit:
  • When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: FLIT_AND_LCRD_AVAILABLE or svt_chi_node_configuration :: FLIT_AND_LCRD_AVAILABLE_FOR_PROT_FLIT_AND_PERMANENT_FOR_LINK_FLIT:
    • This attribute defines the number of clock cycles the TX***FLITPEND signal is asserted before asserting TX***FLITV signal.
  • When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: PERMANENT:
    • This delay is not applicable and value of this attribute is ingored.
  • Unsupported: When svt_chi_node_configuration :: flitpend_assertion_policy=svt_chi_node_configuration :: FLIT_AVAILABLE:
    • This attribute defines the minimum number of clock cycles the TX***FLITPEND signal is asserted before asserting TX***FLITV signal.
    • As the TX***FLITPEND is aserted irrespective of L-Credit availability in this case, this delay is started along with TX***FLITPEND assertion.
    • In case the L-Credit is not available by the time this delay is completed, the TX***FLITPEND signal is continued to be asserted till the L-Credit is available and subsequently the TX***FLITV signal is asserted.
    • In case the L-Credit is available before this delay is completed, the TX***FLITPEND signal is continued to be asserted till the delay is complete and subsequently the TX***FLITV signal is asserted.
• When delays are enabled (svt_chi_node_configuration :: delays_enable = 1) this should be at least 1.
• When delays are not enabled (svt_chi_node_configuration :: delays_enable = 0), value of this field is not applicable.
• Applicable for ACTIVE mode only.

• In case of Protocol Flit: Once the TX flit is available at the Link layer and the link is active, this attribute defines the number of clock cycles required to process the TX Protocol Flit (assertion of TX***FLITPEND signal).
  • This is applicable only when svt_chi_node_configuration :: flitpend_assertion_policy is set to svt_chi_node_configuration :: FLIT_AND_LCRD_AVAILABLE or svt_chi_node_configuration :: PERMANENT.
• In case of Link Flit: Once the TX flit is available at the link layer, this attribute defines the number of clock cycles required to process the TX Link Flit (assertion of TX***FLITPEND signal).
• Non-zero value of this delay is applied only when the delays are enabled (svt_chi_node_configuration :: delays_enable = 1).
• Applicable for ACTIVE mode only.
• When svt_chi_node_configuration :: flitpend_assertion_policy is set to svt_chi_node_configuration :: PERMANENT, for a given VC, VIP Link layer driver consumes next TX FLIT from the VC sequencer only once the current TX FLIT is complete, that is, corresponding TXFLITV is sampled as HIGH by receivers.

Valid ranges constraints insure that the transaction settings are supported by the chi components.

Reasonable constraints are designed to limit the traffic to "protocol legal" traffic, and in some situations maximize the traffic flow. They must never be written such that they exclude legal traffic.

Reasonable constraints may be disabled during error injection. To simplify enabling and disabling the constraints relating to a single field, the reasonable constraints for an individual field must be grouped in a single reasonable constraint.