TMPR4955AF datasheet(77/168 Pages) TOSHIBA

77 / 168 page

Chapter 6 TX4955A System Interface

6-5

6.2.5.1

Master state and slave state

The system interface is placed in the master state when the TX4955A processor is

driving the SysAD bus and SysCmd bus. In contrast, the system interface is in the

slave state when the external agent is driving the SysAD bus and SysCmd bus.

The processor asserts the ValidOut* signal if the SysAD bus and SysCmd bus

become valid when the system interface is in the master state. The external agent

asserts the ValidIn* signal if the SysAD bus and SysCmd bus become valid when the

system interface is in the slave state.

6.2.5.2

Shifting from the master state to the slave state

The system interface remains in the master state unless it enters one of the

following states:

•

The external agent issues a request, then usage of the system interface is

granted (external arbitration).

•

The processor issues a read request and shifts into the slave mode by itself.

6.2.5.3

External arbitration

The external agent cannot issue external requests via the system interface unless

the system interface goes into the slave state. Shifts from the master state to the slave

state are arbitrated by the processor using the system interface handshake signals

ExtRqst* and Release.* This shift is performed as follows below.

1) The external agent sends notification that it would like to issue an external

request by asserting the ExtRqst* signal.

2) The processor releases the system interface and changes its state from the master

state to the slave state by asserting the Release* signal for 1 cycle.

3) The system interface returns to the master state when issuing of the external

request is complete.

6.2.5.4

Shifting to the slave state on its own

Shifting to the slave state on its own means that the shift from the master state to

the slave state is started by the processor when the processor read request is still on

hold. The Release signal is automatically asserted after the read transaction.

Self-invoked shifting to the slave state occurs either during the issue cycle of the read

request or several cycles after that.

After shifting to the slave state on its own, the processor returns to the master state

at the end of the next external request. This is made possible by a read request or

other type of external request.

The SysAd bus and SysCmd bus drives must start after the external agent confirms

that the processor autonomously shifted to the slave state. While the system interface

is in the slave state, the external agent can start making external requests without

requesting access to the system interface (without asserting the ExtRqst* signal).

The system interface returns to the master state when the external request ends.

If a processor read request is on hold after a read request is issued, the processor

automatically changes the system interface into the slave state even if the system

interface access necessary for the system agent to issue the external request has not

been requested. By shifting to the slave state in this manner, the external agent

becomes able to return read response data.

TMPR4955AF Datasheet(PDF) 77 Page - Toshiba Semiconductor

TMPR4955AF Datasheet(HTML) 77 Page - Toshiba Semiconductor

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL