How to download VIP smartsearch?
DESIGNWARE_HOMEto required designware home location where VIP Smartsearch should be downloaded.
vip_smartsearch_<version>.runfile.
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>
How to install VIP Smartsearch?
Please refer to the fileVIP_Smartsearch_installation_and_usage_guide.pdfin
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>for installation steps.
Customer Support
For more details about VIP smartsearch tool, contact support_center@synopsys.com.Inheritance diagram for class svt_dti_transaction:
This is the base transaction type which contains all the physical attributes of the transaction like address, data, burst type, burst length, etc. It also provides the timing information of the transaction to the master & slave transactors, that is, delays for valid and ready signals with respect to some reference events.
The svt_dti_transaction also contains a handle to configuration object of type svt_dti_port_configuration , which provides the configuration of the port on which this transaction would be applied. The port configuration is used during randomizing the transaction.
|
|
Width of this signal is controlled through macro SVT_DTI_MAX_ADDR_WIDTH.
Default value of this macro is 64. To change the width of this variable
value of this macro needs to be changed.
Define the new value for the macro in file svt_dti_user_defines.svi, and
then specify this file to be compiled by the simulator. Also, specify
+define+SVT_DTI_INCLUDE_USER_DEFINES on the simulator compilation command
line. Please consult User Guide for additional information, and consult VIP
example for usage demonstration.
The SVT_DTI_MAX_ADDR_WIDTH macro is only used to control the maximum width
of the signal. The actual width used by VIP is controlled by configuration
parameter svt_dti_port_configuration :: addr_width.
This represents address information field of different messages. For example, 'addr' implies Input Address IA field of DTI_TBU_TRANS_REQ message 'addr' implies Output Address OA field of DTI_TBU_TRANS_RSP message |
|
|
|
|
|
It represents FAULT_TYPE field of DTI_ATS_TRANS_FAULT message. This bit indicates to the TBU how to handle the fault. 00: InvalidTranslation. 01: CompleterAbort. 10: UnsupportedRequest. 11: Reserved. Applicable for ATS protocol. |
|
|
It represents RANGE field of DTI_ATS_INV_REQ message. This field indicates the range of Virtual Addresses for invalidation. Applicable for ATS protocol. |
|
|
It represents AMA field of DTI_ATS_TRANS_RESP message. ats_memory_attribute (AMA).Applicable for DTI-ATSv2. This field indicates the translation attributes in a form that is designed for use by the PCIe ATS Memory Attributes field. For details,Refer ARM-IHI0088 version E and E.b
Applicable for ATS protocol. |
|
|
It represents ERROR field of DTI_ATS_SYNC_ACK message. This bit indicates that a PCIe error has occurred. Applicable for ATS protocol. |
|
|
It represents ATST field in DTI_TBU_TRANS_REQ. This bit indicates whether the transaction is ATS-translated. When '1' this bit indicates that this transaction was the result of a previous ATS translation request made using DTI-ATS. Applicable for TBU protocol.(applicable for DTI Edition 2 (ARM:100225_0000_02en only) Available in DTI-TBUv1. Later specification version E (DTI-TBUv2) onwards ATST has been part of new FLOW[1:0] field. FLOW[1:0] =2'b01 reflects ATST encoding. |
|
|
|
|
|
|
|
It represents COMB_ALLOC field of DTI_TBU_TRANS_RESP message. combined_allocate(COMB_ALLOC). For version DTI_TBUv2, this field indicates how translation allocation hint to be handled. It represents allocation hint. For DTI_TBUv1 - it is Reserved. 0: The allocation hints in the ATTR field override the transaction attributes. 1: The allocation hints in the ATTR field are combined with the transaction attributes.
Applicable for TBU protocol. |
|
|
It represents COMB field of DTI_TBU_TRANS_RESP message. It represents combined_memory_type.For version DTI_TBUv2, this field indicates how translation memory type and cacheability to be handled.
For DTI_TBUv1 - it is Reserved.
0: the memory type and cacheability in the ATTR field override the transaction attribute. Applicable for TBU protocol. Applicable from Spec version E onwards. Applicable for DTI-TBUv2. It is RSVD,SBZ for DTI-TBUv1 |
|
|
It represents COMB_SH field of DTI_TBU_TRANS_RESP message. combined_shareability(COMB_SH) For version DTI_TBUv2, this field indicates how translation shareability to be handled. It represents combined_shareability. For DTI_TBUv1 - it is Reserved. 0: the shareability in the SH field override the transaction attributes. 1: the shareability in the SH field to be combined with the transaction attributes.
Applicable for TBU protocol. |
|
|
It represents implementation defined field of DTI_TBU_CONDIS_ACK messages.
condis_ack_imp_def is at bit 7 of DTI_TBU_CONDIS_ACK. |
|
|
It represents implementation defined field of DTI_TBU_CONDIS_REQ messages.
condis_req_imp_def is at bit 7 of DTI_TBU_CONDIS_REQ. Applicable for TBU and ATS protocol. |
|
|
It represents STATE field of DTI messages.
This bit identifies the new channel state requested. |
|
|
|
It represents CTXTATTR field of DTI_TBU_TRANS_RESP message. This field gives IMPLEMENTATION DEFINED attributes for the translation context.
Applicable for TBU protocol. |
|
|
cxl(CXL) reflects the value set in the 'source_cxl' bit of the ATS request.
Applicable for DTI-ATSv3.
This field is the member of DTI_ATS_TRANS_RESP message.
|
|
|
It represents CXL_IO field of DTI_TBU_TRANS_RESP/DTI_ATS_TRANS_RESP message. cxl_io (CXL_IO). Used by the root ports implementing CXL. 0 - The translation response can be used be by CXL.io or CXL.cache 1 - The translation response can only be used for cxl.io translated transactions.
Applicable for TBU and ATS protocol. |
|
|
This represents the data in dti transaction. This is an 8 bit wide array which is
used by the Register access message group.
In DTI_TBU_REG_WRITE message, [7:0]data[3] represents the data to be written by the TCU.
In DTI_TBU_REG_RDATA message, [7:0]data[3] represents the data read from the TBU.
Upon receiving the response DTI_TBU_REG_RDATA message, the read request transaction DTI_TBU_REG_READ is updated with the read data.
Applicable for TBU protocol. |
|
|
|
|
|
It represents FAULT_TYPE field of DTI_TBU_TRANS_FAULT message. This bit indicates to the TBU how to handle the fault.
For spec 2.0 and 3.0 , The FAULT_TYPE is of 2 bits.
From Spec E and above this FAULT_TYPE is of 3 bits. Applicable for TBU protocol. |
|
|
It represents FLOW[1:0] field in DTI_TBU_TRANS_REQ. It represents translation flow required. This field provides the information with a transaction about the flow and TCU a hint to respond and handle the faults. If the flow value is : STALL : Indicates the translation request supports the stall fault flow. TCU may stall response. ATST : Indicates this transaction is a result of periviously translated request made by ATS. NOSTALL : Indicates the translation request doesn't support the stall fault flow. fault response must be returned. PRI : Indicates that this transaction if results in tranlsation fault will resolve issue using PRI request(PCIe End point uses this option) via DTI-ATS connection.
Applicable for TBU protocol. |
|
|
|
It represents HWATTR field of DTI_TBU_TRANS_RESP message. hw_attr(HWATTR) For version DTI_TBUv2, this field indicates how translation memory type and cacheability to be handled. It represents combined_memory_type. For DTI_TBUv1 - it is Reserved. 0: the memory type and cacheability in the ATTR field override the transaction attribute. 1: the memory type and cacheability in the ATTR field to be combined with the transaction attribute.
Applicable for TBU protocol. |
|
|
Width of this signal is controlled through macro
SVT_DTI_MAX_ID_WIDTH. Default value of this macro is 8. To change the
maximum width of this variable, user can change the value of this macro.
Define the new value for the macro in file svt_dti_user_defines.svi, and
then specify this file to be compiled by the simulator. Also, specify
+define+SVT_DTI_INCLUDE_USER_DEFINES on the simulator compilation command
line. Please consult User Guide for additional information, and consult VIP
example for usage demonstration.
The SVT_DTI_MAX_ID_WIDTH macro is only used to control the maximum width
of the signal. The actual width used by VIP is controlled by configuration
parameter svt_dti_port_configuration :: id_width.
|
|
|
identity_translation (IDENT) indicates whether an identity translation is required.
When identity translation is needed, IDENT is set to '1' and FLOW must be ATST.
When MMUV = '0' IDENT is reserved.
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_REQ message.
|
|
|
It represents implementation defined field of DTI_TBU_MASTER_IMP_DEF_TYPE1_REQ messages. imp_def_type1_mstr_req_imp_def_fields is at bit 3 to 160 of DTI_TBU_MASTER_IMP_DEF_TYPE1_REQ |
|
|
|
It represents implementation defined field of DTI_TBU_SLAVE_IMP_DEF_TYPE1_REQ messages. imp_def_type1_slv_req_imp_def_fields is at bit 3 to 160 of DTI_TBU_SLAVE_IMP_DEF_TYPE1_REQ |
|
|
|
It represents implementation defined field of DTI_TBU_MASTER_IMP_DEF_TYPE2_REQ messages. imp_def_type2_mstr_req_imp_def_fields is at bit 3 to `SVT_DTI_TBU_MASTER_IMP_DEF_TYPE2_MSG_MAX_WIDTH_1 of DTI_TBU_MASTER_IMP_DEF_TYPE2_REQ |
|
|
|
It represents implementation defined field of DTI_TBU_MASTER_IMP_DEF_TYPE2_REQ messages. imp_def_type2_mstr_req_imp_def_fields is at bit 3 to `SVT_DTI_TBU_MASTER_IMP_DEF_TYPE2_MSG_MAX_WIDTH_1 of DTI_TBU_MASTER_IMP_DEF_TYPE2_REQ |
|
|
|
It represents INC_ASET1 field of DTI_TBU_INV_REQ message. This bit indicates whether the ASET value of a translation affects its invalidation. Applicable for TBU protocol. |
|
|
It represents InD field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ. This bit indicates whether the transaction is an instruction access or data access in DTI_TBU_TRANS_REQ. When '0' : Data access. When '1' : Instruction access. This bit indicates whether execute (instruction) access is requested in DTI_ATS_TRANS_REQ. When '0' : The translation will only be used for data accesses. When '1' : The translation might be used for instruction and data accesses. Applicable for TBU and ATS protocol. |
|
|
|
It represents SIZE field of DTI_TBU_INV_REQ message. This field relates to invalidate operation. SIZE is when OPERATION is a TLB Invalidate operation. The SIZE field is DTI_TBU_INV_REQ[15:12]. It overlaps with TG, TTL and SSID[3:0]. Refer to specifcation for details. Applicable for TBU protocol. Applicable from Spec version F onwards. |
|
|
inv_comp_error(ERROR) indicates the Invalidation completion error.
Applicable for DTI-ATSv3.
This field is the member of DTI_ATS_INV_COMP message.
|
|
|
inv_tag(ITAG) indicates the Invalidation tag.
Applicable for DTI-ATSv3.
This field is the member of DTI_ATS_INV_REQ and DTI_ATS_INV_COMP message.
|
|
|
It represents Last field in DTI_ATS_PAGE_REQ message.
This field indicates last request message in a page request group.
Applicable for ATS protocol. |
|
|
Memory_encryption_context (MECID) indicates memory extension context information for RME-DA.
This is feature belongs to RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_RESPEX message.
|
|
|
It represents message type field msg_type of every DTI messages. |
|
|
MMUV.
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_REQ message.
|
|
|
It represents MPAMNS field of DTI_TBU_TRANS_RESP message. MPAMNS For version DTI_TBUv2, this field indicates information related to Memory partioning and monitoring(MPAM) security indicator. For DTI_TBUv1 - It is Reserved. For DTI_TBUv2 - It represent the MPAM NS value.
Applicable for TBU protocol. |
|
|
mpamnse (MPAMNSE) indicates extension of the security states for MPAM.
This is feature belongs to RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_REQ message.
{MPAMNSE,MPAMNS} indicates PARTID set and security state of MPAM:
|
|
|
|
It represents NO_TRANS field of DTI_ATS_CONDIS_REQ message.
This field indicates no messages for translation group, invalidation and sync group. |
|
|
It represents NS field in DTI_TBU_TRANS_REQ/DTI_TBU_TRANS_RESP. This bit indicates the security level of the transaction when in DTI_TBU_TRANS_REQ. This bit indicates the security status to be used for downstream transactions when in DTI_TBU_TRANS_RESP. Applicable for TBU protocol. |
|
|
non_secure_extension (NSE) indicates extension of the security states.
This is feature belongs to RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_REQ/RESP, DTI_TBU_REG_WRITE/READ message.
{NSE,NS} provides security state encodings:
00 - Secure.
01 - Non-Secure.
10 - Root.
11 - Realm.
|
|
|
It represents NUM field of DTI_TBU_INV_REQ message. This field relates to range invalidate operation. NUM is when OPERATION is a TLB Invalidate operation. Refer to specifcation for details. Applicable for TBU protocol. Applicable from Spec version E onwards. |
|
|
Variable that holds the object_id of this transaction
|
|
|
It represents OPERATION field of DTI_TBU_INV_REQ/DTI_ATS_INV_REQ message. This field identifies the type of invalidation operation being performed. Applicable for TBU and ATS protocol. |
|
|
It represents OAS field of DTI_TBU_CONDIS_ACK/DTI_ATS_CONDIS_ACK
It represents the output address size which is the maximum address size permitted for translated addresses. |
|
|
|
|
|
|
|
|
|
Variables used in generating XML/FSDB for pa writer
|
|
|
It represents INST (execute access) field in DTI_ATS_PAGE_REQ message. This field indicates whether execute access is requested or not. Applicable for ATS protocol. |
|
|
It represents PRIV (privileged access) field in DTI_ATS_PAGE_REQ message. This field indicates whether privileged access is requested or not. Applicable for ATS protocol. |
|
|
It represents READ (read access) field in DTI_ATS_PAGE_REQ message. This field indicates whether read access is requested or not. Applicable for ATS protocol. |
|
|
It represents resp field in DTI_ATS_PAGE_RESP message.
This field indicates response type for the page requested. Applicable for ATS protocol. |
|
|
It represents WRITE (write access) field in DTI_ATS_PAGE_REQ message.
This field indicates whether write access is requested or not.
Applicable for ATS protocol. |
|
|
It represents PARTID field of DTI_TBU_TRANS_RESP message. part_id(PARTID)
Applicable for TBU protocol. |
|
|
It represents PERM[1:0] field in DTI_TBU_TRANS_REQ. This bit indicates whether write or read access is requested. When 2'b00 : W:Write permission required. When 2'b01 : R:Read permission required. When 2'b10 : RW: Read and write permission required. When 2'b11 : SPEC: Neither permission required. The translation request is speculative and cannot cause a permission fault.
Applicable for TBU protocol. |
|
|
It represents PMG field of DTI_TBU_TRANS_RESP message. mpam pmg(PMG)
Applicable for TBU protocol. |
|
|
The port configuration corresponding to this transaction
|
|
|
|
It represents PRG_INDEX field in DTI_ATS_PAGE_REQ and DTI_ATS_PAGE_RESP message.
This field indicates Page request group index.
Applicable for ATS protocol. |
|
|
It represents PnU field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ. This bit indicates whether this transaction represents privileged or unprivileged access. When '0' : Unprivileged. When '1' : Privileged. Applicable for TBU and ATS protocol. |
|
|
It represents PROTOCOL field of DTI_TBU_CONDIS_REQ/DTI_ATS_CONDIS_REQ/DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ/DTI_ATS_PAGE_REQ messages. |
|
|
It represents VERSION field of DTI messages.
This field identifies the requested protocol version.
If DTI TBU and TCU supports V2 then ports are set accordingly.
Ex. cfg.dti_version = svt_dti_port_configuration :: DTI2_0
and svt_dti_transaction :: protocol_version will have value '1' in the DTI_TBU_CONDIS_REQ/ DTI_ATS_CONDIS_REQ. Applicable for TBU and ATS protocol. |
|
|
It represents QOS field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ. This field indicates the Quality of Service priority level. Applicable for TBU and ATS protocol. |
|
|
It represents RnW field in DTI_TBU_TRANS_REQ. This bit indicates whether write or read access is requested. When '0' : write access. When '1' : read access.
Applicable for TBU protocol.(applicable for DTI Edition 2 (ARM:100225_0000_02en only). |
|
|
reqex indicates if translation resp DTI_TBU_TRANS_RESPEX can be given.
This is feature belongs to MECID(memory encryption context) for RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_TRANS_REQ message.
when this is
0 - DTI_TBU_TRANS_RESPEX cannot be given
1 - DTI_TBU_TRANS_RESPEX can be given.
|
|
|
same_power_domain (SPD).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_CONDIS_REQ message and
indicates the same power domain of TBU and TCU.
|
|
|
|
It represents SCALE field of DTI_TBU_INV_REQ message. This field relates to range invalidate operation. SCALE is when OPERATION is a TLB Invalidate operation. Refer to specifcation for details. Applicable for TBU protocol. Applicable from Spec version E onwards. |
|
|
It represents SEC_SID field in DTI_TBU_TRANS_REQ. This bit indicates whether the StreamID is Secure. When '1' represents Secure StreamID(SID).
Applicable for TBU protocol. |
|
|
It represents SH field of DTI_TBU_TRANS_RESP message. This field indicates the shareability of the translation. When '2'b00': Non-Shareable. When '2'b01': Reserved. When '2'b10': Outer-Shareable. When '2'b11': Inner-Shareable. Applicable for TBU protocol. |
|
|
|
It represents RANGE field of DTI_TBU_INV_REQ message. This field indicates the range of SIDs or VMIDs for invalidation. Applicable for TBU protocol. |
|
|
|
It represents SPECULATIVE field in DTI_TBU_TRANS_REQ. This bit indicates whether the translation request is speculative. Applicable for TBU protocol.(applicable for DTI Edition 2 (ARM:100225_0000_02en only) Available in DTI-TBUv1. Later specification version 3.0 onwards SPECULATIVE and RnW has been combined to form PERM[1:0] where PERM[1] reflects and SPECULATIVE PERM[0] reflects RnW. SPECULATIVE encoding is when PERM[1:0]=2'b11. |
|
|
It represents S1HWATTR field of DTI_TBU_TRANS_RESP message. This field gives the IMPLEMENTATION DEFINED stage 1 hardware attributes.
Applicable for TBU protocol. |
|
|
It represents S2HWATTR field of DTI_TBU_TRANS_RESP message. This field gives the IMPLEMENTATION DEFINED stage 2 hardware attributes.
Applicable for TBU protocol. |
|
|
stages (STAGES).
Applicable for DTI-TBUv3.
This field is the member of DTI_TBU_CONDIS_REQ message and
indicates the translation stages to support RME and RME-DA .
|
|
|
It represents SID field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ/DTI_TBU_INV_REQ/DTI_ATS_INV_REQ/DTI_ATS_PAGE_REQ/DTI_ATS_PAGE_RESP. It is StreamID that is used for translation or invalidation. Width of this signal is controlled through macro SVT_DTI_MAX_STREAMID_WIDTH. Default value of this macro is 32. To change the maximum width of this variable, user can change the value of this macro. Define the new value for the macro in file svt_dti_user_defines.svi, and then specify this file to be compiled by the simulator. Also, specify +define+SVT_DTI_INCLUDE_USER_DEFINES on the simulator compilation command line. Please consult User Guide for additional information, and consult VIP example for usage demonstration. The SVT_DTI_MAX_STREAMID_WIDTH macro is only used to control the maximum width of the signal. The actual width used by VIP is controlled by configuration parameter svt_dti_port_configuration :: streamid_width. Applicable for TBU and ATS protocol. |
|
|
It represents SSID field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ/DTI_TBU_INV_REQ/DTI_ATS_INV_REQ/DTI_ATS_PAGE_REQ/DTI_ATS_PAGE_RESP. It is SubstreamID that is used for translation or invalidation. Width of this signal is controlled through macro SVT_DTI_MAX_SUBSTREAMID_WIDTH. Default value of this macro is 20. To change the maximum width of this variable, user can change the value of this macro. Define the new value for the macro in file svt_dti_user_defines.svi, and then specify this file to be compiled by the simulator. Also, specify +define+SVT_DTI_INCLUDE_USER_DEFINES on the simulator compilation command line. Please consult User Guide for additional information, and consult VIP example for usage demonstration. The SVT_DTI_MAX_SUBSTREAMID_WIDTH macro is only used to control the maximum width of the signal. The actual width used by VIP is controlled by configuration parameter svt_dti_port_configuration :: substreamid_width. Applicable for TBU and ATS protocol. |
|
|
It represents SUP_PRI field of DTI_ATS_CONDIS_ACK message.
This field indicates when register accesses are supported. |
|
|
It represents SUP_REG field of DTI_TBU_CONDIS_REQ message.
This field indicates when register accesses are supported. |
|
|
SUP_T bit indicates the granted T bit(Trusted_entity) usage in the
DTI_ATS_TRANS_REQ,DTI_ATS_INV_REQ,DTI_ATS_PAGE_REQ and DTI_ATS_PAGE_RESP messages.
This is feature belongs to RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-ATSv3.
This field is the member of DTI_ATS_CONDIS_REQ/DTI_ATS_CONDIS_ACK message.
|
|
|
|
TE bit indicates Security space of the address(OA).This is used when DTI-F, DTI-ATSv3 is supported.
This is feature belongs to RME(Relam management Extension).
Applicable for DTI-ATSv3.
This field is the member of messages DTI_ATS_TRANS_RESP,
When '0' indicates OA is Non-secure Address.
When '1' indicates OA is realm Address.
When DTI_ATS_TRANS_REQ.T is '0', TE is Reserved(SBZ).
|
|
|
It represents TOK_INV_GNT field of DTI messages. Applicable for TBU and ATS protocol. |
|
|
It represents TOK_TRANS_REQ field of DTI_TBU_CONDIS_REQ, DTI_ATS_CONDIS_REQ and
TOK_TRANS_GNT field of DTI_TBU_CONDIS_ACK, DTI_ATS_CONDIS_ACK messages. Applicable for TBU and ATS protocol. |
|
|
currently not supported yet and may undergo changes
|
|
|
|
It represents TG field of DTI_TBU_INV_REQ message. This field relates to range invalidate operation. TG is when OPERATION is a TLB Invalidate operation. Refer to specifcation for details. Applicable for TBU protocol. Applicable from Spec version E onwards. |
|
|
It represents TTL field of DTI_TBU_INV_REQ message. This field relates to range invalidate operation. TTL is when OPERATION is a TLB Invalidate operation. Refer to specifcation for details.
Applicable for TBU protocol. |
|
|
Transaction handle to be used to send DTI message over Axi4_Stream Transport layer.
User can construct the axi master transaction object in the DTI sequence with required
parameters and DTI component will use this transaction handle to send it over Axi4_Stream
interface as received with DTI message as payload.
Note: If this transaction handle is found to be null then DTI component will simply use
a new axi master transaction object with its own randomized parameters.
|
|
|
It represents IMP_DEF (implementation defined) field of DTI_TBU_TRANS_REQ message. Applicable for TBU protocol. |
|
|
It represents IMP_DEF (implementation defined) field of DTI_TBU_TRANS_RESP message. trans_resp_imp_def is at bit [159:156] of DTI_TBU_TRANS_RESP. Applicable for TBU protocol. |
|
|
It represents ATTR field of DTI_TBU_TRANS_RESP message. This field indicates the translation attributes. Refer to the specification for details. Applicable for TBU protocol. |
|
|
T bit indicates Trusted entity, used when SUP_T is supported.
This is feature belongs to RME-DA(Relam management Extension -Device assignment).
Applicable for DTI-ATSv3.
This field is the member of various messages DTI_ATS_CONDIS_REQ/DTI_ATS_CONDIS_ACK,
DTI_ATS_TRANS_REQ,DTI_ATS_INV_REQ, DTI_ATS_PAGE_REQ and DTI_ATS_PAGE_RESP message.
When '0' indicates non-secure streamID
When '1' indicates realm streamID.
|
|
|
|
It represents SSV field in DTI_TBU_TRANS_REQ/DTI_ATS_TRANS_REQ/DTI_ATS_PAGE_REQ/DTI_ATS_PAGE_RESP. This bit indicates whether a valid SubstreamID is associated with this translation. When '1' this bit indicates that SSID is valid. Applicable for TBU and ATS protocol. |
|
|
|
|
It represents nW field of DTI_ATS_TRANS_REQ message. Applicable for ATS protocol. |
|
|
This represents current status of the DTI transaction. If transaction is complete then it is updated with COMPLETE status. If transaciton is aborted then it is updated with ABORTED status. If transaction is being transported then it is updated with TRANSPORT_STARTED status. If it is yet to be processed then xact_status is set to INITIAL. Default Value: INITIAL |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|