Processor Local Bus Functional Model Toolkit User's Manual

Synch_in
Synch_out
8.6 Master Interface Checks
This section describes the PLB master interface checks performed during simulation.
8.6.1 Mn_request
The following error messages are issued for this signal:
• Error 1.1.1
An error message is issued when a master deasserts its Mn_request without any of the following
events: (that is, if any one of the following events occur then no error is flagged)
PLB_MnAddrAck is asserted
Mn_abort is asserted
PLB_MnRearbitrate is asserted
MnTimeout is asserted
• Error 1.1.2
An error message is issued when Mn_request is active and SYS_plbReset is active.
• Warning1.1.3
A warning message of possible deadlock is issued when Mn_request is not inactive for 2 clock
cycles after PLB_MnRearbitrate, Mn_request and Mn_busLock are sampled active with
PLB_Mnaddrack inactive.
• Error 1.1.4
Requesting master which has the bus locked did not deassert Mn_Request for two clocks after a
rearbitrated request.
8.6.2 Mn_priority(0:1)
No protocol checks.
8.6.3 Mn_busLock
The following error messages are issued for this signal:
• Error 1.3.1
An error message is issued when a master’s Mn_busLock is active without its Mn_request being
active unless the bus is already locked by the requesting master.
• Error 1.3.2
Table 1. Summary of PLB Signals (Continued)
Signal Name Source Description Page
72 Processor Local Bus Functional Model Toolkit Version 4.9.2