Download Processor Local Bus Functional Model Toolkit User`s Manual

• Error 2.5.1
An error message is issued when Sln_rearbitrate is asserted and both PLB_PAValid and
PLB_SAValid are inactive.
• Error 2.5.2
An error message is issued when Sln_rearbitrate is active while the slave is not selected. This
check depends on user defined address map.
• Error 2.5.3
A warning message is issued when Sln_rearbitrate is asserted and PLB_SAValid is active. (Not
applicable to PLB 4.x)
• Error 2.5.4
An error message is issued when more than one slave asserts Sln_rearbitrate in the same clock.
8.7.6
PLB_rd/wrpendReq
The following error messages are issued for this signal:
• Error 2.6.1/3
An error message is issued when the PLB changes this transfer qualifier from the time when a
request to transfer is made until the addressed slave asserts its Sln_addrAck, or the transfer is
terminated through Mn_abort, PLB_MnRearbitrate, or PLB_MnTimeout.
• Error 2.6.2/4
An error message is issued if this signal is active when there is no Mn_request.
8.7.7
PLB_MasterID(0:3)
The following error messages are issued for this signal:
• Error 2.7.1
An error message is issued when the PLB changes this transfer qualifier from the time when a
request to transfer is made until the addressed slave asserts its Sln_addrAck, or the transfer is
terminated through Mn_abort, PLB_MnRearbitrate or PLB_MnTimeout.
• Error 2.7.2
An error message is issued when the PLB is locked (Mn_busLock, Mn_Request, and
PLB_MnaddrAck were sampled active) and PLB_masterID does not equal the locked master’s id.
• Error 2.7.3
An error message is issued if in the cycle following a rearbitrate with PLB_busLock inactive,
PLB_PAValid is active and the current PLB_masterID is the same as in the previous cycle when
rearbitrate was asserted.
8.7.8
PLB_rd/wrpendPri(0:1)
There are currently no protocol checks for this signal.
Version 4.3
PLB Compliance Checks
77