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_ahb_checker:
|
||
|
||
Execute signal level checks on the exclusive write signals
|
|
||
Execute signal level checks on the write path signals (driven by the manager)
|
|
||
Execute signal level checks on the read path signals (driven by the subordinate)
|
|
||
Execute signal level checks on the write path signals (driven by the arbiter)
|
|
||
Execute signal level checks on the write path signals (driven by the manager)
|
|
|
Check description: Checks whether control parity check signals(other than HTRANSCHK) or address parity check signal changed during BUSY.
Pass condition: Control and address phase parity check signals not changed during busy transfer Fail condition: Control and address phase parity check signals changed during busy transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that contol and address parity check singals does not change during wait state except when htrans changes from IDLE to NSEQ.
Pass condition: Control and address phase parity check signals not changed during wait state Fail condition: Control and address phase parity check signals changed during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that contol and address parity check singals does not change at the end of wait state.
Pass condition: Control and address phase parity check signals not changed at the end of wait state Fail condition: Control and address phase parity check signals changed at the end of wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that response generated for exclusive read access is correct
Pass condition: Exclusive read transfer gives expected exclusive read response Fail condition: Exclusive read transfer does not give expected exclusive read response Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's addresses matches
Pass condition: Exclusive read transfer and exclusive write transfer addresses are same Fail condition: Exclusive read transfer and exclusive write transfer addresses are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's burst lengths match
Pass condition: Exclusive read transfer and exclusive write transfer burst lengths are same Fail condition: Exclusive read transfer and exclusive write transfer burst lengths are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's burst sizes match
Pass condition: Exclusive read transfer and exclusive write transfer burst sizes are same Fail condition: Exclusive read transfer and exclusive write transfer burst sizes are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's burst types match
Pass condition: Exclusive read transfer and exclusive write transfer burst types are same Fail condition: Exclusive read transfer and exclusive write transfer burst types are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that id is generated same for exclusive read and write transactions
Pass condition: Exclusive read transfer and exclusive write exclusive thread id are same Fail condition: Exclusive read transfer and exclusive write exclusive thread id are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's number of busy cycles are zero
Pass condition: Exclusive read transfer and exclusive write transfer number of busy cycles are zero Fail condition: Exclusive read transfer and exclusive write transfer number of busy cycles are note zero Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that exclusive read transfer's and exclusive write transfer's prot type match
Pass condition: Exclusive read transfer and exclusive write transfer prot type are same Fail condition: Exclusive read transfer and exclusive write transfer prot type are different Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that response generated for exclusive write access is correct
Pass condition: Exclusive write transfer gives expected exclusive write response Fail condition: Exclusive write transfer does not give expected exclusive write response Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that manager is not permit an Exclusive transaction to be in progress at the same time as any transaction that registers that it is performing an Exclusive sequence
Pass condition: Exclusive transfer is not related to another sequence Fail condition: Exclusive transfer is related to another sequence Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: HEXOKAY must not be asserted in the same cycle as HRESP is asserted.
Pass condition: HEXOKAY is not asserted in the same cycle as HRESP is asserted. Fail condition: HEXOKAY is asserted in the same cycle as HRESP is asserted. Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: HEXOKAY must only be asserted in the same cycle as HREADY is asserted.
Pass condition: HEXOKAY is asserted when HREADY is asserted. Fail condition: HEXOKAY is asserted when HREADY is not asserted. Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks the received HRDATACHK is same as the parity calculated from HRDATA in a read transaction.
Pass condition: Received HrDATACHK is same as the parity calculated from HRDATA in the read transaction. Fail condition: Received HRDATACHK is not same as the parity calculated from HRDATA in the read transaction. Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANSCHK does not change during wait state except when htrans doesn't change.
Pass condition: HTRANSCHK not changed during wait state Fail condition: HTRANSCHK changed during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that user write data (hwdata_huser) does not change during waited writes
Pass condition: HWDATA_HUSER is stable during the waited write transfer Fail condition: HWDATA_HUSER is changed during the waited write transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that write data parity check signal (HWDATACHK) does not change during waited state
Pass condition: Write data parity check signal (HWDATACHK) does not change during waited state Fail condition: Write data parity check signal (HWDATACHK) changed during waited state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks the received HWDATACHK is same as the parity calculated from HWDATA in a write transaction.
Pass condition: Received HWDATACHK is same as the parity calculated from HWDATA in the write transaction. Fail condition: Received HWDATACHK is not same as the parity calculated from HWDATA in the write transaction. Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that user write data parit check signal (hwdata_huserchk) does not change during waited writes
Pass condition: HWDATA_HUSERCHK is stable during the waited write transfer Fail condition: HWDATA_HUSERCHK is changed during the waited write transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that write strobes (HWSTRB) does not change during waited writes
Pass condition: HWSTRB is stable during the waited write transfer Fail condition: HWSTRB is changed during the waited write transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that write strobes parity check signal (HWSTRBCHK) does not change during waited writes
Pass condition: HWSTRBCHK is stable during the waited write transfer Fail condition: HWSTRBCHK is changed during the waited write transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks whether control parity check signals(other than HTRANSCHK) changed during burst
Pass condition: Control parity check signals not changed during burst Fail condition: Control parity check signals changed during burst Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that a manager is not staring a new exclusive transaction while there is an outstanding exclusive transaction pending
Pass condition: Exclusive manager has no outstanding transaction pending Fail condition: Exclusive manager has an outstanding transaction pending Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that observed parity value as seen in *chk signals match that of calculated parity value from respective signal.
Pass condition: Observed parity value as seen in *chk signals match that of calculated parity value from respective signal. Fail condition: Observed parity value as seen in *chk signals doesn't match that of calculated parity value from respective signal. Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that control_huser (HAUSER) is not X or Z
Pass condition: CONTROL_HUSER is not X or Z Fail condition: CONTROL_HUSER is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that control_huserchk is not X or Z
Pass condition: control_huserchk does not contain any X or Z bits Fail condition: control_huserchk contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HADDRCHK is not X or Z
Pass condition: HADDRCHK does not contain any X or Z bits Fail condition: HADDRCHK contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HCTRLCHK1 is not X or Z
Pass condition: HCTRLCHK1 does not contain any X or Z bits Fail condition: HCTRLCHK1 contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HCTRLCHK2 is not X or Z
Pass condition: HCTRLCHK2 does not contain any X or Z bits Fail condition: HCTRLCHK2 contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HPROTCHK is not X or Z
Pass condition: HPROTCHK does not contain any X or Z bits Fail condition: HPROTCHK contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that hrdata_huser (HRUSER) is not X or Z
Pass condition: HRDATA_HUSER is not X or Z Fail condition: HRDATA_HUSER is X or Z Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HRDATACHK is not X or Z
Pass condition: HRDATACHK does not contain any X or Z bits Fail condition: HRDATACHK contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that hrdata_huserchk is not X or Z
Pass condition: hrdata_huserchk does not contain any X or Z bits Fail condition: hrdata_huserchk contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADYCHK is not X or Z
Pass condition: HREADYCHK does not contain any X or Z bits Fail condition: HREADYCHK contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADY_INCHK is not X or Z
Pass condition: HREADY_INCHK does not contain any X or Z bits Fail condition: HREADY_INCHK contains X or Z bits Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HRESPCHK is not X or Z
Pass condition: HRESPCHK does not contain any X or Z bits Fail condition: HRESPCHK contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HSELCHK is not X or Z
Pass condition: HSELCHK does not contain any X or Z bits Fail condition: HSELCHK contains X or Z bits Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANSCHK is not X or Z
Pass condition: HTRANSCHK does not contain any X or Z bits Fail condition: HTRANSCHK contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that hwdata_huser (HWUSER) is not X or Z
Pass condition: HWDATA_HUSER is not X or Z Fail condition: HWDATA_HUSER is X or Z Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HWDATACHK is not X or Z
Pass condition: HWDATACHK does not contain any X or Z bits Fail condition: HWDATACHK contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that hwdata_huserchk is not X or Z
Pass condition: hwdata_huserchk does not contain any X or Z bits Fail condition: hwdata_huserchk contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HWSTRB is not X or Z
Pass condition: HWSTRB is not X or Z Fail condition: HWSTRB is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HWSTRBCHK is not X or Z
Pass condition: HWSTRBCHK does not contain any X or Z bits Fail condition: HWSTRBCHK contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that resp_huser (HBUSER) is not X or Z
Pass condition: RESP_HUSER is not X or Z Fail condition: RESP_HUSER is X or Z Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that address phase is not extended by the Subordinate
Pass condition: Address phase is started by driving HREADY high when HTRANS is NSEQ Fail condition: Address phase is extended by driving HREADY low when HTRANS is NSEQ, and no extended data phase pending from a previous transaction Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that RETRY responses are not received when configured for AHB Lite
Pass condition: RETRY responses are not received when configured for AHB Lite Fail condition: RETRY responses are received when configured for AHB Lite Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that SPLIT responses are not received when configured for AHB Lite
Pass condition: SPLIT responses are not received when configured for AHB Lite Fail condition: SPLIT responses are received when configured for AHB Lite Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks for valid beat address of each beat in a transaction
Pass condition: Beat address is getting updated correctly Fail condition: Beat address not updated correctly Beat address and haddr is not same Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that resp_huserchk is not X or Z
Pass condition: resp_huserchk does not contain any X or Z bits Fail condition: resp_huserchk contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that burst transfer does not cross configured boundary limit
Pass condition: Burst transfer does not cross configured boundary limit Fail condition: Burst transfer crosses configured boundary limit Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks number of beats in a fixed length burst
Pass condition: Burst length not exceeded fixed length burst Fail condition: Burst length exceeded for fixed length burst Applicable device type: Passive Manager Additional information:
|
|
|
Check description: Checks that burst transaction was not terminated early:
Pass condition: Manager not terminated burst early after OKAY response Fail condition: Manager terminated burst early after OKAY response Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks whether control signals(other than HTRANS) or address changed during BUSY
Pass condition: Control signals and address not changed during busy transfer Fail condition: Control signals or address changed during busy transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that contol and address does not change during wait state except when htrans changes from IDLE to NSEQ
Pass condition: Control signals and address not changed during wait state Fail condition: Control signals or address changed during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that control and address does not change at the end of wait state
Pass condition: Control signals and address not changed at the end of wait state Fail condition: Control signals or address changed at the end of wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: It is required that all transfers in a locked sequence are to the same subordinate address region.
Pass condition: Manager performing a transfer to the same subordinate address region Fail condition: Manager performing a transfer to a different subordinate address region Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that manager shouldn't assert hlock in the middle of a non-locked transaction
Pass condition: Manager not asserted hlock in the middle of a non-locked transaction Fail condition: Manager asserted hlock in the middle of a non-locked transaction Applicable device type: Passive Manager Additional information:
|
|
|
Check description: Checks that HREADY output signal from bus is HIGH when reset is active
Pass condition: HREADY output signal from bus is HIGH when reset is active Fail condition: HREADY output signal from bus is not HIGH when reset is active Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADY output signal from subordinate is either HIGH or LOW when reset is active
Pass condition: HREADY output signal from subordinate is either HIGH or LOW when reset is active Fail condition: HREADY output signal from subordinate is X or Z when reset is active Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADY output from subordinate must be either HIGH or LOW when there is no data phase pending. That is, checks that the subordinate cannot request that the address phase is extended.
Pass condition: HREADY output from subordinate must be either HIGH or LOW Fail condition: HREADY output from subordinate is either X or Z Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that manager attempted transfer size greater than data bus width
Pass condition: Manager attempted transfer size is not greater than data bus width Fail condition: Manager attempted transfer size greater than data bus width Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HSPLIT is not asserted for a manager that has not SPLIT earlier.
Pass condition: HSPLIT is not asserted for a manager that has not SPLIT earlier. Fail condition: HSPLIT is asserted for a manager that has not SPLIT earlier. Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that HSPLIT is asserted for only one clock cycle
Pass condition: HSPLIT is asserted for only one clock cycle Fail condition: HSPLIT is not asserted for only one clock cycle Applicable device type: Passive Subordinate Additional information:
|
|
|
Check description: Checks that htrans does not change during wait state except when htrans changes from
Pass condition: HTRANS not changed during wait state Fail condition: HTRANS changed during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANS output signal from manager/bus is IDLE when reset is active
Pass condition: HTRANS output signal from manager/bus is IDLE when reset is active Fail condition: HTRANS output signal from manager/bus is not IDLE when reset is active Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANS changes to IDLE during second cycle of ERROR response
Pass condition: HTRANS changes to IDLE during ERROR response Fail condition: HTRANS did not change to IDLE during ERROR response Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANS changes to IDLE during second cycle of RETRY response
Pass condition: HTRANS changed to IDLE during RETRY response Fail condition: HTRANS was not changed to IDLE during RETRY response Applicable device type: Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANS changes to IDLE during second cycle of SPLIT response
Pass condition: HTRANS changed to IDLE during SPLIT response Fail condition: HTRANS was not changed to IDLE during SPLIT response Applicable device type: Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that manager drives HTRANS to IDLE or NSEQ when it does not have access to the bus
Pass condition: Manager drives HTRANS to IDLE or NSEQ when it does not have access to the bus Fail condition: Manager not driving HTRANS to IDLE or NSEQ when it does not have access to the bus Applicable device type: Passive Manager Additional information:
|
|
|
Check description: Checks that HUNALIGN output signal from manager dosenot changes its value in middle of a transfer
Pass condition: HUNALIGN is stable in a transfer Fail condition: HUNALIGN is not stable in a transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that write data does not change during waited state
Pass condition: Write data does not change during waited state Fail condition: Write data changed during waited state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks for IDLE changed to BUSY during wait state
Pass condition: IDLE not changed to BUSY during wait state Fail condition: IDLE changed to BUSY during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks for IDLE changed to SEQ during wait state
Pass condition: IDLE not changed to SEQ during wait state Fail condition: IDLE changed to SEQ during wait state Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks for illegal address transition during burst
Pass condition: Address is getting updated correctly Fail condition: Address not updated correctly Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks whether control signals(other than HTRANS) changed during burst
Pass condition: Control signals not changed during burst Fail condition: Control signals changed during burst Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that for non existent memory location default subordinate should provide ERROR response for NSEQ/SEQ transfers
Pass condition: Default subordinate giving error response for NSEQ/SEQ transfers when accessing nonexistent address location Fail condition: Default subordinate not giving error response for NSEQ/SEQ transfers when accessing nonexistent address location Applicable device type: Active/Passive Manager Additional information:
|
|
|
Check description: Checks that manager loses the bus once it gets the split response from the subordinate.
Pass condition: Manager loses the bus once it gets the split response from the subordinate Fail condition: Manager didn't lose the bus during the split response from the subordinate Applicable device type: Active/Passive Manager Additional information:
|
|
|
Check description: Checks for IDLE changed to BUSY
Pass condition: BUSY is not followed by IDLE Fail condition: BUSY is followed by IDLE Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks for IDLE changed to SEQ
Pass condition: SEQ is not followed by IDLE Fail condition: SEQ is followed by IDLE Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that if invalid HSEL is asserted for selected subordinate. This is applicable only in mutli_hsel_enable mode
Pass condition: HSEL is asserted for selected subordinate Fail condition: Invalid HSEL is asserted for selected subordinate Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that only OKAY responses are received during wait state
Pass condition: OKAY responses are received during wait state Fail condition: OKAY responses are not received during wait state Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that burst transfer does not cross 1 KB boundary
Pass condition: Burst transfer does not cross 1 KB boundary Fail condition: Burst transfer crosses 1KB boundary Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the average latency of read transactions in a given interval is not more than the configured max value
Pass condition: Average latency of read transactions in a given interval is not more than the configured max value Fail condition: Average latency of read transactions in a given interval is more than the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the average latency of write transactions in a given interval is not more than the configured max value
Pass condition: Average latency of write transactions in a given interval is not more than the configured max value Fail condition: Average latency of write transactions in a given interval is more than the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the average latency of read transactions in a given interval is not less than the configured min value
Pass condition: Average latency of read transactions in a given interval is not less than the configured min value Fail condition: Average latency of read transactions in a given interval is less than the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the average latency of write transactions in a given interval is not less than the configured min value
Pass condition: Average latency of write transactions in a given interval is not less than the configured min value Fail condition: Average latency of write transactions in a given interval is less than the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the throughput of read transactions in a given interval is not more that the configured max value
Pass condition: Throughput of read transactions in a given interval is not more that the configured max value Fail condition: Throughput of read transactions in a given interval is more that the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the latency of a read transaction is not greater than the configured max value
Pass condition: Latency of a read transaction is not greater than the configured max value Fail condition: Latency of a read transaction is greater than the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the throughput of write transactions in a given interval is not more that the configured max value
Pass condition: Throughput of write transactions in a given interval is not more that the configured max value Fail condition: Throughput of write transactions in a given interval is more that the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the latency of a write transaction is not greater than the configured max value
Pass condition: Latency of a write transaction is not greater than the configured max value Fail condition: Latency of a write transaction is greater than the configured max value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the throughput of read transactions in a given interval is not less that the configured min value
Pass condition: Throughput of read transactions in a given interval is not less that the configured min value Fail condition: Throughput of read transactions in a given interval is less that the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the latency of a read transaction is not lesser than the configured min value
Pass condition: Latency of a read transaction is not lesser than the configured min value Fail condition: Latency of a read transaction is lesser than the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the throughput of write transactions in a given interval is not less that the configured min value
Pass condition: Throughput of write transactions in a given interval is not less that the configured min value Fail condition: Throughput of write transactions in a given interval is less that the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the latency of a write transaction is not lesser than the configured min value
Pass condition: Latency of a write transaction is not lesser than the configured min value Fail condition: Latency of a write transaction is lesser than the configured min value Applicable device type: Active/Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the manager restarted an interrupted burst from the address of the aborted beat
Pass condition: Manager restarted an interrupted burst from the address of the aborted beat Fail condition: Manager not restarted an interrupted burst from the address of the aborted beat Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that the manager restarted an interrupted burst with a valid combination of bursts
Pass condition: Manager restarted an interrupted burst with a valid combination of bursts Fail condition: Manager not restarted an interrupted burst with a valid combination of bursts Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that a manager started burst with SEQ or BUSY instead of NSEQ
Pass condition: Manager started burst with NSEQ Fail condition: Manager started burst with BUSY or SEQ Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that a SEQ or BUSY trans only occur during active transaction after nseq
Pass condition: SEQ or BUSY trans occurs during active transaction after nseq Fail condition: SEQ or BUSY trans occurs not during active transaction Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HADDR is not X or Z
Pass condition: HADDR does not contain any X or Z bits Fail condition: HADDR contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HBSTRB is not X or Z
Pass condition: HBSTRB does not contain any X or Z bits Fail condition: HBSTRB contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HBURST is not X or Z
Pass condition: HBURST does not contain any X or Z bits Fail condition: HBURST contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HBUSREQ is not X or Z
Pass condition: HBUSREQ does not contain any X or Z bits Fail condition: HBUSREQ contains X or Z bits Applicable device type: Passive Manager Additional information:
|
|
|
Check description: Checks that HEXCL is not X or Z
Pass condition: HEXCL is not X or Z Fail condition: HEXCL is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HEXOKAY is not X or Z
Pass condition: HEXOKAY is not X or Z Fail condition: HEXOKAY is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HGRANT is not X or Z
Pass condition: HGRANT does not contain any X or Z bits Fail condition: HGRANT contains X or Z bits Applicable device type: Active/Passive Manager Additional information:
|
|
|
Check description: Checks that HLOCK is not X or Z on manager interface
Pass condition: HLOCK does not contain any X or Z bits Fail condition: HLOCK contains X or Z bits Applicable device type: Passive Manager Additional information:
|
|
|
Check description: Checks that HMASTER is not X or Z
Pass condition: HMASTER is not X or Z Fail condition: HMASTER is X or Z Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HMASTER value is in valid range based on SVT_AHB_MAX_NUM_MASTERS
Pass condition: HMASTER value is less than SVT_AHB_MAX_NUM_MASTERS Fail condition: HMASTER value is more than SVT_AHB_MAX_NUM_MASTERS Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HMASTLOCK is not X or Z on subordinate interface
Pass condition: HMASTLOCK is not X or Z Fail condition: HMASTLOCK is X or Z Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HNONSEC is not X or Z
Pass condition: HNONSEC is not X or Z Fail condition: HNONSEC is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HPROT is not X or Z
Pass condition: HPROT does not contain any X or Z bits Fail condition: HPROT contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that Extended_Memory_Type supporting HPROT[6:2] is having valid values
Pass condition: HPROT[6:2] value is in valid range Fail condition: HPROT[6:2] value is not in valid range Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HRDATA is not X or Z
Pass condition: HRDATA does not contain any X or Z bits Fail condition: HRDATA contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADY is not X or Z
Pass condition: HREADY does not contain any X or Z bits Fail condition: HREADY contains X or Z bits Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HREADY_IN is not X or Z
Pass condition: HREADY_IN does not contain any X or Z bits Fail condition: HREADY_IN contains X or Z bits Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HRESP is not X or Z
Pass condition: HRESP is not X or Z Fail condition: HRESP is X or Z Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that HSEL is not X or Z
Pass condition: HSEL is not X or Z Fail condition: HSEL is X or Z Applicable device type: Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HSIZE is not X or Z
Pass condition: HSIZE does not contain any X or Z bits Fail condition: HSIZE contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HTRANS is not X or Z
Pass condition: HTRANS does not contain any X or Z bits Fail condition: HTRANS contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HUNALIGN is not X or Z
Pass condition: HUNALIGN is not X or Z Fail condition: HUNALIGN is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HWDATA is not X or Z
Pass condition: HWDATA does not contain any X or Z bits Fail condition: HWDATA contains X or Z bits Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HWRITE is not X or Z
Pass condition: HWRITE is not X or Z Fail condition: HWRITE is X or Z Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that transfer type of a SINGLE burst is NSEQ
Pass condition: Transfer type of a SINGLE burst is NSEQ Fail condition: Transfer type of a SINGLE burst is not NSEQ Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that ERROR response completes in two cycles
Pass condition: ERROR response completes in two cycles Fail condition: ERROR response was not completed in two cycles Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that RETRY response completes in two cycles
Pass condition: RETRY response completes in two cycles Fail condition: RETRY response was not completed in two cycles Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that SPLIT response completes in two cycles
Pass condition: SPLIT response completes in two cycles Fail condition: SPLIT response was not completed in two cycles Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|
|
|
Check description: Checks that XFAIL response completes in two cycles
Pass condition: XFAIL response completes in two cycles Fail condition: XFAIL response does not completed in two cycles Applicable device type: Active Manager Additional information:
|
|
|
Check description: Checks that HRDATA/HWDATA byte lanes are selected corresponding to bits HBSTRB signal which have value 1
Pass condition: HRDATA/HWDATA byte lanes are selected corresponding to bits HBSTRB Fail condition: Invalid HRDATA/HWDATA byte lanes are selected corresponding to bits HBSTRB Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that HUNALIGN signal is correctly set for unaligned transfers. Based on ARMv6 AMBA Extension Spec (Document No: PR022-GENC-001011) section 3.1.2, example 3.1.2.2 in the document and ARM discussions following items are mandatory.
Pass condition: HUNALIGN is 1 for the unaligned transfer Fail condition: HUNALIGN is 0 for the unaligned transfer Applicable device type: Passive Manager and Active/Passive Subordinate Additional information:
|
|
|
Check description: Checks that IDLE and BUSY transfers receive zero wait cycle OKAY response
Pass condition: IDLE and BUSY transfers receive zero wait cycle OKAY response Fail condition: IDLE and BUSY transfers doesn't receive zero wait cycle OKAY response Applicable device type: Active/Passive Manager and Passive Subordinate Additional information:
|