Indicates if the data as given in data field is to be allocated in cache. Currently applicable only for CLEANUNIQUE and MakeReadUnique transaction. . A CLEANUNIQUE transaction is used to write partial data into the cache when the requesting RN already has the cacheline, but the cache line is in a shared state. . If this bit is set, the data as given in data field will be written into cache according to the byte-enables set in the byte_enable field. Also, the cacheline will move to a UD state. In case of CleanUnique, if the cacheline gets deleted by an incoming snoop before this transaction completes, the cacheline moves to a UDP state. In case of MakeReadUnique, if the cacheline gets deleted by an incoming Snoop before the transaction completes, the cacheine will be updated with the transaction data, given by "makereadunique_read_data" and then overriden with the data and byte_enable programmed in the transaction handle. The cacheline will move to UD state. . If this bit is unset, the data given in the data field has no relevance. In case of CLeanUnique, if the cacheline gets deleted by an incoming snoop before this transaction completes, the cacheline moves to a UCE state. In case of MakeReadUnique, if the cacheline gets deleted by an incoming Snoop before the transaction completes, the cacheline moves to the state specified in the read data response.

This member points to a CHI transaction of barrier type (EOBarrier or ECBarrier) associated to this current transaction. When associated_barrier_xact is null, it indicates that this current transaction is not a post-barrier transaction. When associated_barrier_xact is non-null, this current transaction will wait for the response of the barrier transaction associated_barrier_xact, before this transaction can be transmitted.

Please refer to User Guide for more details on usage of this member.

Indicates the reason for VIP to issue an auto-generated transaction.
Applicable only for Active RN. Applicable only when is_auto_generated bit is set to 1.
When this field is set to:

• NOT_AUTO_GENERATED: This transaction is not auto generated.
• CACHE_FULL_AND_ENTRY_IN_CACHE_NEEDED: This transaction is auto-generated when the cache is full and an entry needs to be evicted from the cache.
• WRITE_TO_MEMEORY_BEFORE_CMO: This transaction is auto-generated when user supplied a cache maintenance transaction and the protocol requires that the cache line is first written into memory before sending the cache maintenance transaction.
• INVALIDATE_CACHELINE_BEFORE_ATOMIC_WITH_SNOOPME_ZERO: This transaction is auto-generated when user supplied an atomic transaction with snoopme set to zero and the protocol requires that the cache line is first invalidated before sending the atomic transaction.
• SYSCO_CACHE_CLEANUP: This transaction is auto-generated when Cache copies are invalidated/cleaned up before moving to the Coherency DISCONNECT phase
• AUTO_READ_AFTER_PARTIAL_WRITE_XACT: This transaction is auto-generated when user supplies a partial write transaction. In this case, the VIP auto-generates a full cacheline read for the partial write transactions.

This is a read-only member and should not be modified by the user.

This field defines the byte enable.
This field is applicable for write data, DVM payload.
This field is not applicable for Atomic transactions and will be ignored.
It consists of a bit for each data byte in the transaction data, which when set indicates that the corresponding data byte is valid.
For DVM, this field is always right aligned. For other transaction types, the details are described below.
When svt_chi_node_configuration :: wysiwyg_enable is set to 1: The byte_enable corresponds to all 64 bytes irrespective of data size of the transaction.

When svt_chi_node_configuration :: wysiwyg_enable is set to 0: The byte_enable value is right aligned.

• For Normal type memory transactions, this corresponds to number of bytes as per the data size of the transaction, starting from the address that is aligned to the data size.
• For Device type memory transactions, this corresponds to the addresses starting from transaction's address, upto next aligned address to the data size.

This is a flag that indicates whether the cache has been updated for the current transaction. Only applicable in case of allocation read and dataless transactions initiated from active RN-F.
This will be set internally and must not be programmed by the user.
Default value is 0.

For a Write transaction when separate comp and dbidresp responses are observed, this attribute indicates the order in which COMP and DBIDRESP are observed.

• NOT_SET_COMP_DBIDRESP_ORDER: This attribute is not set.
• COMP_DBIDRESP : First Comp respons is observed, later DBIDResp is observed.
• DBIDRESP_COMP : First DBIDResp respons is observed, later Comp is observed.
• COMP_DBIDRESPORD : First Comp respons is observed, later DBIDRespOrd is observed.
• DBIDRESPORD_COMP : First DBIDRespOrd respons is observed, later Comp is observed.
• COMBINED_COMPDBIDRESP : Combined CompDBIDResp respons is observed.

Applicable only in Active RN. This is a read-only attribute that is populated internally in the VIP and used for coverage purposes.

Defines the delay in number of cycles between COMP and DBIDResp flit in the case when COMP is sent before DBIDResp. This is only applicable for WriteNoSnp* and WriteUnique* transactions when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_COMP. The clock cycles are with respect to the TXRSPFLITV signal asserted for COMP Response.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to DBID RSP Flit is enforced to 0 and tx_flit_delay corresponding to COMP RSP flit is randomized.If the tx_flit_delay corresponding to DBID RSP flit is not enforced to zero, we will not see the actual comp_to_dbid_dlit_delay getting applied.

The reference event for this delay is reference_event_for_comp_to_dbid_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode

This is a counter which is incremented for every DAT flit transmitted for a read transaction. Applicable for CHI ICN Full-Slave mode.

This field defines the data.
This field is applicable for write data, read data and DVM payload of the transaction.
This field is not applicable for Atomic transactions and will be ignored.
For DVM, this field is always right aligned. For other transaction types, the details are described below.
When svt_chi_node_configuration :: wysiwyg_enable is set to 1: The data corresponds to all 64 bytes irrespective of data size of the transaction.
When svt_chi_node_configuration :: wysiwyg_enable is set to 0: The data value is right aligned.

• For Normal type memory transactions, this corresponds to number of bytes as per the data size of the transaction, starting from the address that is aligned to the data size.
• For Device type memory transactions, this corresponds to the addresses starting from transaction's address, upto next aligned address to the data size.

This field defines the Reserved Value defined by the user for each of the Protocol Data VC Flits associated to the current transaction.
The size of this array must be equal to the number of data VC flits associated.
The array indices correspond to the order in which the flits are transmitted/received.
Any value can be driven on this field.

This field holds the resp_err_status defined by the user for each of the Protocol Data VC Flits associated to the current transaction.
The size of this array must be equal to the number of data VC flits associated.
The array indices correspond to the order in which the flits are transmitted/received.
All valid values for Response Error status (NORMAL_OKAY, EXCLUSIVE_OKAY, DATA_ERROR and NON_DATA_ERROR) can be driven on this field.
In case of WriteEvictorEvict transaction, as the data transfer depends on the response from the completer, this field values are used and populated in DAT flits only when there is write data transfer.

The DBID policy used for DBID field value of certain RSP, DAT flit types of current transaction. Please refer to documentation of the svt_chi_common_transaction :: dbid_policy_enum for more details.

Defines the delay in number of cycles between DBIDResp and COMP flit in the case when DBIDResp is sent before COMP. This is only applicable for WriteNoSnp* and WriteUnique* transactions when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_DBIDRESP. The clock cycles are with respect to the TXRSPFLITV signal asserted for DBIDRESP response.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to COMP RSP Flit is enforced to 0 and tx_flit_delay corresponding to DBID RSP flit is randomized.If the tx_flit_delay corresponding to COMP RSP flit is not enforced to zero, we will not see the actual comp_to_dbid_dlit_delay getting applied

The reference event for this delay is reference_event_for_dbid_to_comp_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode

This variable controls enabling of interleaving for the current transaction. When set to 1, interleaving is enabled for current transaction. Currently, interleaving is not supported for Ordered transactions. Default value is 0

Applicable only for CHI ICN Full-Slave mode.

Represents the status of an exclusive access. Following are the possible status types:

• EXCL_ACCESS_INITIAL : Initial state of the transaction before it is processed by RN
• EXCL_ACCESS_PASS : CHI exclusive access is successful
• EXCL_ACCESS_FAIL : CHI exclusive access is failed

A combination of excl_access_status and excl_mon_status can be used to determine the reason for failure of exclusive store. This attribute is applicable to both exclusive load/read and store/write. excl_access_status is applicable to read/load transactions only if the exclusive load transaction get OK response instead of EXOK response which indicates the exclusive access fail and the sequence must be terminated and respective exclusive monitor needs to be reset. Please refer to the User Guide for more description.

Represents the status of RN exclusive monitor. Following are the possible status types:

• EXCL_MON_INVALID : RN exclusive monitor does not monitor the exclusive access on the cache line associated with the transaction
• EXCL_MON_SET : RN exclusive monitor is set for exclusive access on the cache line associated with the transaction
• EXCL_MON_RESET : RN exclusive monitor is reset for exclusive access on the cache line associated with the transaction

A combination of excl_access_status and excl_mon_status can be used to determine the reason for failure of exclusive store. This attribute is applicable to both read/load and write/store exclusive transactions. This attribute is programmed to 'EXCL_MON_RESET' on completion of the exclusive transactions. It is programmed to 'EXCL_MON_SET' only if the exclusive load/read is successful else it is marked as 'EXCL_MON_RESET'. Please refer to the User Guide for more description.

Flag to indicate update cache for successfull excl store when the transaction is dropped and the cache line is already present in unique state at the RN.

This enum represents the value for conditions under which the RN coherent exclusive transactions are dropped. Conditions are based on the values of excl_mon_status and excl_access_status. Combination of these attributes causes the transaction to drop.

Following are the possible status types:

• EXCL_MON_FAILURE_COND_DEFAULT_VALUE_XACT_DROPPED : Default value.
• EXCL_MON_RESET_ACCESS_FAIL_XACT_DROPPED : set if the exclusive transaction is dropped as the excl_mon_status is reset and the exclusive_access_status is failed
• EXCL_MON_SET_ACCESS_FAIL_XACT_DROPPED : set if the exclusive transaction is dropped as the excl_mon_status is set and the exclusive_access_status is failed as unexpected INVALID cache line status encountered
• EXCL_MON_SET_ACCESS_PASS_XACT_DROPPED : set if the exclusive transaction is dropped as when RN has a cacheline for which CU is generated, excl_mon is set for the same cacheline address and the cacheline state is unique, which means this is a RN speculative transaction to a cacheline present in it's own cache. In such scenario, do a silent write into the cache and drop the transaction. Need not issue this transaction.
• EXCL_MON_RESET_SNOOP_INVALIDATION_XACT_DROPPED : set to indicate that exclusive sequence needs to restart as the exclusive monitored RN cache has been invalidated by the incoming invalidating snoop request from different lpid or due to the normal coherent store[CU] transactions.
• EXCL_MON_RESET_STORE_WITHOUT_LOAD_XACT_DROPPED : set if the exclusive transaction is dropped as the excl_mon_status is invalid and exclusive_access_status is failed. This occurs when store without Load/Read is issued by the RN or there was an intervening Store/Write before the current exclusive store/write transaction.
• EXCL_MON_INVALID_MAX_EXCL_ACCESS_XACT_DROPPED : set if the exclusive transaction is dropped when the maximum number of active exclusive acessses exceeds 4.

This field indicates the final state of the cache line for this transaction.

• Applicable for RN-F agent in active mode.
• Used by the functional coverage related to cache states.
• Updated when the cache line is updated.

HN Node Index to which transactions need to be sent to. This variable is not used by the VIP, but can potentially be used by users in sequences.

This field indicates the initial state of the cache line for this transaction.

• Applicable for RN-F agent in active mode.
• Used by the functional coverage related to cache states.
• Updated when the request flit is created by active RN-F agent.

Variable that holds the interleaved_group_object_num of this transaction. VIP assigns a unique number to each transaction it generates from interleaved ports.
Applicable for interleaved ports only. For normal ports it is same as obect_num.

Represents the various interleave pattern for a read transaction. The interleave_pattern gives flexibility to program interleave blocks with different patterns as mentioned below.

A Block is group of DAT flits within a transaction. RANDOM_BLOCK : Drives the blocks programmed in random_interleave_array Applicable only for CHI ICN Full-Slave mode.

Indicates if the transaction is auto generated by the VIP. Transactions are auto-generated when:

• 1) The cache is full and an entry needs to be evicted from the cache.
• 2) User supplies a cache maintenance transaction and the protocol requires that the cache line is first written into memory before sending the cache maintenance transaction.
• 3) User supplies an atomic transaction with snoopme set to zero and the protocol requires that the cache line is first invalidated before sending the atomic transaction.
• 4) Cache copies are invalidated/cleaned up before moving to the Coherency DISCONNECT phase.
• 5) User supplies a partial write transaction. In this case, the VIP auto-generates a full cacheline read for the partial write transactions.

This is a read-only member, which VIP uses to indicate whether the transaction is auto generated. It should not be modified by the user.

Applicable for ACTIVE RN only.

Indicates if the transaction ended because the requested data was already available in the cache. This bit is set by the master, no action is taken if the user sets this bit. A transaction with this bit set was not sent out on the bus and therefore other components in the testbench will not detect this transaction.

This is a read-only member, which VIP uses to indicate whether the requested data was cached. It should not be modified by the user.

Applicable for ACTIVE RN only.

This bit is set by RN if a cache line is reserved for the transaction. Thie field is used by task which unreserves the cache line at the end of transaction to filtering. This is to ensure only command that reserved cache line should unreserve cache line.

Applicable for ACTIVE RN only

This field indicates if the request is cancelled after receiving a retry response.

Indicates if COMP has been received

Indicates if DBID has been received

For a requester, this field indicates if the PcrdGrant is received.
For a completer, this field indicates if the PcrdGrant is transmitted.

For a requester, this field indicates if the PcrdGrant is received before the RetryAck.
For a completer, this field indicates if the PcrdGrant is sent before the RetryAck.

This bit is set by SN if the read is performed to a memory location that was not writtent to earlier. This should not be programmed by user. Applicable for SN only

Indicates if the transaction is retried with original qos of original request or not. In case of active RN, based on this field, RN driver decides to use original qos or any random qos for the retried transaction.

Indicates if the transaction is retried with original req_rsvdc of original request not. In case of active RN, based on this field, RN driver decides to use original req_rsvdc or any random req_rsdvc for the retried transaction. This is applicable only when svt_chi_node_configuration :: chi_spec_revision is not set to ISSUE_A.

Indicates if the transaction is retried with original tgt_id of original request or not. In case of active RN, based on this field, RN driver decides to use original tgt_id or the remapped tgt_id for the retried transaction, when svt_chi_system_configuration :: expect_target_id_remapping_by_interconnect is set to 1.

Indicates if the transaction is retried with original txn_id of original request or not. In case of active RN, based on this field, RN driver decides to use original txn_id or any random txn_id for the retried transaction.

Indicates if the tgt_id is remapped by Interconnect, to a different value other than the tgt_id field sent in the request flit by RN.

Indicates if a transaction is dropped because the start state of the corresponding cache line is not as expected before transmitting the transaction. The expected start states for each of the transaction types are given in Table 6-1 of the specification.
This will be set automatically by the RN driver based on the initial cache state validity check. If the user wishes to drop transactions based on any additional/custom rules or transaction fields, they can set this attribute to 1 in svt_chi_rn_protocol_callback :: post_initial_cache_state_check that is invoked before the request flit is scheduled for a given transaction. Applicable for ACTIVE RN only.

For every instance of link deactivation that happens while the transaction is outstanding, indicates if the deactivation was initiated by the local or the remote node.

For every instance of link reactivation that happens while the transaction is outstanding, indicates if the reactivation was initiated by the local or the remote node.

This field indicates the number of data Flits required to transfer the data based on the data width of the interface and the data size attribute of the transaction.
Consider the example that the data size is 64 Byte and data width of the interface is 16 Byte. In this case, the num_dat_flits will be 4.

Captures the value of original_tgt_id, that is tgt_field of the associated request flit.

Defines the delay in number of cycles between RetryAck and PcrdGrant RSP flits in the case RetryAck is sent before PcrdGrant(svt_chi_transaction :: is_p_crd_grant_before_retry_ack = 0), when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_RETRYACK. The clock cycles are with respect to the RSPFLITV signal asserted for RetryAck response.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to PcrdGrant RSP Flit is enforced to 0. This is reqired to ensure that actual pcreditgrant_to_retryack_flit_delay getting applied. Note that tx_flit_delay corresponding to RetryAck RSP flit is still randomized. The reference event for this delay is reference_event_for_pcreditgrant_to_retryack_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

When the interleave_pattern is set to RANDOM_BLOCK, the user would program this array with blocks. There are default constraints, which the user can override and set their own block patterns. Applicable only for CHI ICN Full-Slave mode.

Defines a reference event from which the comp_to_dbid_flit_delay should start. Following are the different reference events:

TXRSPFLITV_FOR_COMPTODBID_VALID: Reference event is TXRSPFLITV signal assertion for the current write request.

Defines a reference event from which the dbid_to_comp_flit_delay should start. Following are the different reference events:

TXRSPFLITV_FOR_DBIDTOCOMP_VALID: Reference event is TXRSPFLITV signal assertion for the current write request.

Defines a reference event from which the pcreditgrant_to_retryack_flit_delay should start. Following are the different reference events:

RSPFLITV_FOR_PCREDITGRANT_TO_RETRYACK_VALID: Reference event is RSPFLITV signal assertion for the current request.

Defines a reference event from which the req_to_comp_flit_delay should start. Following are the different reference events:

TXREQFLITV_FOR_COMP_VALID: Reference event is TXREQFLITV signal assertion for the current write request.

Defines a reference event from which the req_to_compdata_flit_delay should start. Following are the different reference events:

TXREQFLITV_FOR_COMPDATA_VALID: Reference event is TXREQFLITV signal assertion for the current write request.

Defines a reference event from which the req_to_compdbid_flit_delay should start. Following are the different reference events:

TXREQFLITV_FOR_COMPDBID_VALID: Reference event is TXREQFLITV signal assertion for the current write request.

Defines a reference event from which the req_to_dbid_flit_delay should start. Following are the different reference events:

TXREQFLITV_FOR_DBID_VALID: Reference event is TXREQFLITV signal assertion for the current write request.

Defines a reference event from which the req_to_pcreditgrant_flit_delay should start. Following are the different reference events:

REQFLITV_FOR_PCREDITGRANT_VALID: Reference event is REQFLITV signal assertion for the current request.

Defines a reference event from which the req_to_retryack_flit_delay should start. Following are the different reference events:

REQFLITV_FOR_RETRYACK_VALID: Reference event is REQFLITV signal assertion for the current request.

Defines a reference event from which the retryack_to_pcreditgrant_flit_delay should start. Following are the different reference events:

RSPFLITV_FOR_RETRYACK_TO_PCREDITGRANT_VALID: Reference event is RSPFLITV signal assertion for the current request.

Time at which this transaction was accepted by the completer recorded as a realtime value. This represents the timestamp at which a ReadReceipt/Comp/CompData response was seen for the transaction.

This member indicates the ID of the request order stream to which this transaction belongs to. Active RN agent orders the requests within a stream without any ordering dependency to the transaction that belong to other streams.

Applicable to only active RN agent. The value should be inside [0:(svt_chi_node_configuration :: num_req_order_streams-1)]

Defines the delay in number of cycles between Write REQ flit and Comp flit. This is applicable for all write, CMO and other control (DVM,Barrier) transactions when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_COMP. The clock cycles are with respect to the TXREQFLITV signal assertion for the current request.

This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the RSP flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to COMP RSP Flit is enforced to 0.

The reference event for this delay is reference_event_for_req_to_comp_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

Defines the delay in number of cycles between Read REQ flit and COMPDATA flit. This is only applicable for ReadNoSnp and ReadOnce transactions when svt_chi_sn_transaction :: xact_rsp_msg_type is set to RSP_MSG_COMPDATA. The clock cycles are with respect to the TXREQFLITV signal assertion for the current request.

This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the DAT flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to COMPDATA DAT Flit is enforced to 0. The reference event for this delay is reference_event_for_req_to_compdata_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode

Defines the delay in number of cycles between Write REQ flit and COMPDBIDResp flit. This is only applicable for WriteNoSnp* and WriteUnique* transactions when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_COMPDBIDRESP. The clock cycles are with respect to the TXREQFLITV signal assertion for the current request.

This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the RSP flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to COMPDBIDRESP RSP Flit is enforced to 0.

The reference event for this delay is reference_event_for_req_to_compdbid_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode

Defines the delay in number of cycles between Write REQ flit and DBIDResp flit. This is only applicable for WriteNoSnp* and WriteUnique* transactions when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_DBIDRESP. The clock cycles are with respect to the TXREQFLITV signal assertion for the current request.

This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the RSP flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to DBIDRESP RSP Flit is enforced to 0.

The reference event for this delay is reference_event_for_req_to_dbid_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

Defines the delay in number of cycles between REQ flit and Pcrdgrant RSP flit, when PcrdGrant is sent ahead of RetryAck (svt_chi_transaction :: is_p_crd_grant_before_retry_ack = 1). This is only applicable for all request transactions that can have PcrdGrant as a valid response, that is, with svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_RETRYACK. The clock cycles are with respect to the REQFLITV signal assertion for the current request.
This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the Pcrdgrant RSP flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to Pcrdgrant RSP Flit is enforced to 0.

The reference event for this delay is reference_event_for_req_to_pcreditgrant_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

Defines the delay in number of cycles between REQ flit and RetryAck RSP flit, when RetryAck is sent ahead of PcrdGrant (svt_chi_transaction :: is_p_crd_grant_before_retry_ack = 0). This is only applicable for all request transactions that can have RetryAck as a valid response, that is, with svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_RETRYACK. The clock cycles are with respect to the REQFLITV signal assertion for the current request.
This delay is applied after the response item is received by the interconnect from the IC SN xact sequencer before dispatching the RetryAck RSP flit to the link layer. In case the response is suspended, the response item should reach the driver in 0 time, hence the delay is still applied once the response is resumed.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to RetryAck RSP Flit is enforced to 0.

The reference event for this delay is reference_event_for_req_to_retryack_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

Time at which response was sent from the requester to the completer. This represents the timestamp at which a CompAck response was seen for the transaction.

Indicates the RespErr field of the Response flits associated to this transaction that can have a variable value for RespErr field.
Even though there can be more than one RSP flit associated to a given CHI transaction, as per section “14.4 Error Response Use By Transaction Type” of CHI 4.0 specification, only one of the response flits can have a variable value {Okay/ExOkay, Data Error/Non-Data Error} for this field. Whereas, the remaining response flits need to be transmitted only with a fixed value as described in above mentioned reference.
Consider the following example:

• In case of WriteNoSnpFull, assume that the Comp and DBIDResp are received separately.
• The DBIDResp can have only Okay value for RespErr.
• However, Comp can have any value for RespErr.
• In this case, the user interface needs to accommodate only for specifying/storing the RespErr that corresponds to Comp.

Defines the delay in number of cycles between RetryAck and PcrdGrant RSP flits in the case RetryAck is sent before PcrdGrant(svt_chi_transaction :: is_p_crd_grant_before_retry_ack = 0), when svt_chi_ic_sn_transaction:: xact_rsp_msg_type is set to RSP_MSG_RETRYACK. The clock cycles are with respect to the RSPFLITV signal asserted for RetryAck response.

The delay will have no effect in case the number of clock cycles programmed for this delay is already elapsed with respect to the reference event even before this delay is applied.

If this delay is set to a non-zero value, the tx_flit_delay corresponding to PcrdGrant RSP Flit is enforced to 0. This is reqired to ensure that actual retryack_to_pcreditgrant_flit_delay getting applied. Note that tx_flit_delay corresponding to RetryAck RSP flit is still randomized. The reference event for this delay is reference_event_for_retryack_to_pcreditgrant_flit_delay. Default value is 0. Applicable only for CHI ICN in Full-Slave mode.

Internal queue of snoop transactions which started after current transaction started

- This attribute captures the status of the transaction with respect to suspend_wr_data

• This is a read-only field for testbench, and is updated by VIP components

Byte Enable pattern for DAT flits of a write transactions.

Data pattern for DAT flits of a write transactions.

This property indicates the order in which the flits are seen for the transaction. It is populated at the end of the transaction based on the order in which the associated flits are completed. When the CHI_E replicated channel feature is enabled it is possible that multiple flits are seen on the interface at the same point in time, in such a scenario this field reflect the order in which these flits are stored in the internal queues of the transaction class. This is a read only field and is internally populated by the VIP.

This field defines the Transaction type.

Internal queue of transactions which started before current transaction started, populated only in case of RN

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