Murata Electronics North America DNT24 Manuel D’Utilisation
www.Murata.com
Technical support +1.678.684.2000
Page 14 of 83
© 2015 by Murata Manufacturing Co. Ltd.
E-mail:
tech_sup@murata.com
DNT24 Integration Guide – 03/04/15
The DNT24 SPI port can run at three clock rates in master mode - 125, 250 or 500 kbps. There are two
message sources available to a DNT24 SPI master, a protocol-formatted RxData message or a stored
command. The DNT24 master will clock a message from either source into its slave and return the bytes
clocked out as a protocol-formatted TxData message. The DNT24 event timer triggers sending the stored
command to the DNT24’s slave. The stored command can be up to 16 bytes in length. Figure 3.2.1
shows the required SPI master mode-signal connections, and Figure 3.2.2 shows the SPI master-mode
timing.
message sources available to a DNT24 SPI master, a protocol-formatted RxData message or a stored
command. The DNT24 master will clock a message from either source into its slave and return the bytes
clocked out as a protocol-formatted TxData message. The DNT24 event timer triggers sending the stored
command to the DNT24’s slave. The stored command can be up to 16 bytes in length. Figure 3.2.1
shows the required SPI master mode-signal connections, and Figure 3.2.2 shows the SPI master-mode
timing.
Figure 3.2.2
In SPI slave mode, the host can stream data into DNT24 at up to 250 kbps, provided the host suspends
clocking within 10 bytes following a low-to-high transition on /HOST_CTS. The host can clock data into
the DNT24 at up to 4 Mbps for data bursts of up to 50 bytes, provided the interval from the end of one
burst to the start of the next burst is at least 2 ms, and the host suspends clocking on a low-to-high transi-
tion on /HOST_CTS. See Figure 3.2.4
clocking within 10 bytes following a low-to-high transition on /HOST_CTS. The host can clock data into
the DNT24 at up to 4 Mbps for data bursts of up to 50 bytes, provided the interval from the end of one
burst to the start of the next burst is at least 2 ms, and the host suspends clocking on a low-to-high transi-
tion on /HOST_CTS. See Figure 3.2.4
Figure 3.2.3