the EP was received and was found correct, and that no
conflict was detected on the bus (excluding Attention
Request - see Section 1.3.5 "Attention Request
Transaction"). A write transfer is considered "completed"
only when the ACK bit is generated. A transaction that was
not positively acknowledged is not considered complete
by the LM40 (i.e. internal operation related to the
transaction are not performed) and the following are
performed:
—The BER bit in the LM40 Device Status register is set;
—The LM40 generates an Attention Request before, or
together with the Start Bit of the next transaction
A transaction that was not positively acknowledged is also
not considered "complete" by the master (i.e. internal
operations related to the transaction are not performed).
The transaction may be repeated by the master, after
detecting the source of the Attention Request (the LM40
that has a set BER bit in the Device Status register). Note
that the SensorPath protocol neither forces, nor
automates re-execution of the transaction by the master.
The values of the ACK bit are:
—1: Data was received correctly;
—0: An error was detected (no-acknowledge).
20068410
FIGURE 6. Write Transaction, master write data to LM40
1.3.4 Read and Write Transaction Exceptions
This section describes master and LM40 handling of special
bus conditions, encountered during either Read or Write
transactions.
If an LM40 receives a Start Bit in the middle of a transaction,
it aborts the current transaction (the LM40 does not "com-
plete" the current transaction) and begins a new transaction.
Although not recommend for SensorPath normal operation,
this situation is legitimate, therefore it is not flagged as an
error by the LM40 and Attention Request is not generated in
response to it. The master generating the Start Bit, is respon-
sible for handling the not "complete" transaction at a "higher
level".
If LM40 receives more than the expected number of data bits
(defined by the size of the accessed register), it ignores the
unnecessary bits. In this case, if both master and LM40 iden-
tify correct EP and ACK bits they "complete" the transaction.
However, in most cases, the additional data bits differ from
the correct EP and ACK bits. In this case, both the master and
the LM40 do not "complete" the transaction. In addition, the
LM40 performs the following:
•the BER bit in the LM40 Device Status register is set
•the LM40 generates an Attention Request
If the LM40 receives less than the expected number of data
bits (defined by the size of the accessed register), it waits in-
definitely for the missing bits to be sent by the master. If then
the master sends the missing bits, together with the correct
EP/ACK bits, both master and LM40 "complete" the transac-
tion. However, if the master starts a new transaction gener-
ating a Start Bit, the LM40 aborts the current transaction (the
LM40 does not "complete" the current transaction) and begins
the new transaction. The master is not notified by the LM40
of the incomplete transaction.
1.3.5 Attention Request Transaction
Attention Request is generated by the LM40 when it needs
the attention of the master. The master and all LM40s must
monitor the Attention Request to allow bit re-sending in case
of simultaneous start with a Data Bit or Start Bit transfer. Refer
to the "Attention Request" section, Section 1.2.4 in the "Bit
Signaling" portion of the data sheet.
The LM40 will generate an Attention Request using the fol-
lowing rules:
1. A Function event that sets the Status Flag has occurred
and Attention Request is enabled and
2. The "physical" condition for an Attention Request is met
(i.e., the bus is inactive), and
3. At the first time 2 is met after 1 occurred, there has not
been an Attention request on the bus since a read of the
Device Status register, or since a Bus Reset.
OR
1. A bus error event occurred, and
2. the "physical" condition for an Attention Request is met
(i.e., the bus is inactive), and
3. At the first time 2. is met after 1 occurred, there has not
been a Bus Reset.
All devices (master or slave) must monitor the bus for an At-
tention Request signal. The following notes clarify the intend-
ed system operation that uses the Attention Request
Indication.
•Masters are expected to use the attention request as a
trigger to read results from the LM40. This is done in a
sequence that covers all LM40s. This sequence is referred
to as "master sensor read sequence".
•After an Attention Request is sent by an LM40 until after
the next read from the Device Status register the LM40
does not send Attention Requests for a function event
since it is guaranteed that the master will read the Status
register as part of the master sensor read sequence. Note
that the LM40 will send an attention for BER, regardless
of the Status register read, to help the master with any
error recovery operations and prevent deadlocks.
•A master must record the Attention Request event. It must
then scan all slave devices in the system by reading their
Device Status register and must handle any pending event
in them before it may assume that there are no more
events to handle.
Note: there is no indication of which slave has sent the re-
quest. The requirement that multiple requests are not sent
allows the master to know within one scan of register reads
that there are no more pending events.
13 www.national.com
200684 Version 5 Revision 3 Print Date/Time: 2011/09/24 07:49:02
LM40