Murata Electronics North America DNT24 Manuel D’Utilisation
www.Murata.com
Technical support +1.678.684.2000
Page 15 of 83
© 2015 by Murata Manufacturing Co. Ltd.
E-mail:
tech_sup@murata.com
DNT24 Integration Guide – 03/04/15
Figure 3.2.4
The host should use the following steps to fetch data from a DNT24 SPI slave, as show in Figure 3.2.5:
1.
The host sets the /HOST_RTS signal high to allow the DNT24 to signal data available.
2.
The DNT24 sets the data available (DAV) high to signal the host it has data.
3.
The host set the /SS signal low to enable SPI operation.
4.
The host clocks in one dummy byte (ignore the output byte) and then sets /HOST_RTS low.
5.
The host begins to clock out the data, which can include several messages.
6.
The host continues to clock out data until a 0x00 byte occurs in the byte stream where a 0xFB
start-of-message would be expected.
start-of-message would be expected.
7.
The host has now clocked out all messages and the 0x00 is discarded.
8.
The host sets /HOST_RTS and /SS high to allow the DNT24 to signal DAV the next time it
has data.
has data.
Note that the DAV signal can go low before the last message is clocked out. It is not a reliable indication
that the last byte of the message(s) has been clocked out. See Section 5.2 for recommendations on con-
figuring the SPI port, and Section 7.4.4 for detailed information on SPI port configuration parameters.
that the last byte of the message(s) has been clocked out. See Section 5.2 for recommendations on con-
figuring the SPI port, and Section 7.4.4 for detailed information on SPI port configuration parameters.
Figure 3.2.5