
_________________________________________________PSB 7110
Siemens Aktiengesellschaft
Page 55
3.3.3.2
Buffer General Status Event (ISAR
→
Host)
If a data path is online and the associated write buffer has space available for a new message, the
status event message “buffer available” is generated to request new data from the host.
The IO-buffer control unit generates write buffer status event messages that cover information about
all buffers, thus the IIS register contains a general code (IIS = 0). In this way the load for transfering
messages is decreased significantly, as a single message may request data for more than one
datapath. It is the responsibility of the host to dispatch RDMx to the controller routines of the relevant
datapath.
7
6
5
4
3
2
1
0
DPS
MSC
MDS
IIS
0
0
0
0
0
0
0
0
15
0
14
0
13
0
12
0
11
10
9
8
CTRL MSB
RDM3
RDM2
RDM1
RDM0
7
6
5
4
3
2
1
0
CTRL LSB
0
RDM3, RDM2, RDM1, RDM0 ... Request for next Data Message from Channel 2, 1 or 0
If bit RDM2, RDM1 or RDM0 is set, the corresponding channel 0, 1 or 2 requests for a new
data message from the host.
RDM3 is currently not supported but reserved for further use.
A status event is generated by the control unit and indicated to the host when
at least one of the write buffers changes its state from "not enough free space" to "enough free
space for another data message", or when
at least one of the write buffers has still enough free space for another message immediately after
a new message was written into this buffer.
Only when either of these two states is met, the status event message is generated. If the request is
not serviced by the host, the ISAR will not generate a new status event message to request data for
that path.
It should be noticed that the corresponding bit for that buffer remains not set in the control register
each time another buffer generates an interrupt to request new data.
However a status request message (see 3.3.1) can force the generation of an indication for buffer
available for a certain buffer.
The general proceeding for data transfer from the host to the transmit buffer would be:
after Reset the ISAR will release an initial status event message with
RDM0=RDM1=RDM2=RDM3=1
the host configures buffer, data pump, IOM-2 interface and SART
the host writes the first message to the buffer (buffer is empty after reset)
if the remaining buffer space is greater than the programmed message length, there will be an
immediate interrupt to the host, who in turn can transfer the next message.
if the remaining buffer space is smaller than the programmed message length, there will be no
interrupt to the host until data is transmitted from the buffer and enough space is available to
accept one complete message.
if there is a request for message to the host and the host has no new message to send, the host
should store the request information, so for new data it can immediately continue with transfering
it to the buffer.
the host can force the generation of an indication for buffer available for a certain buffer (see
3.3.1).