Data Sheet ADGS5414
Rev. 0 | Page 23 of 30
0 0 1 D7 D6 D0 C7 C6 C5 C4 C3 C2 C1 C0SDO
R/W A6 A0 D7 D6 D0 C7 C6 C5 C4 C3 C2 C1 C0
1 2 8 9 10 16 17 18 19 20 21 22 23 24
SDI
SCLK
CS
15902-038
Figure 40. Timing Diagram with CRC Enabled
SCLK Count Error Detection
SCLK count error detection allows the user to detect if an incorrect
number of SCLK cycles are sent by the microcontroller or CPU.
When in address mode, with CRC disabled, 16 SCLK cycles are
expected. If 16 SCLK cycles are not detected, the SCLK count
error flag asserts in the error flags register. When less than 16 SCLK
cycles are received by the device, a write to the register map does
not occur. When the ADGS5414 receives more than 16 SCLK
cycles, a write to the memory map still occurs at the 16th SCLK
rising edge, and the flag asserts in the error flags register. With
CRC enabled, the expected number of SCLK cycles becomes 24.
SCLK count error detection is enabled by default and can be
configured by the user through the error configuration register.
Invalid Read/Write Address Error
An invalid read/write address error detects when a nonexistent
register address is a target for a read or write. In addition, this
error asserts when a write to a read only register is attempted.
The invalid read/write address error flag asserts in the error
flags register when an invalid read/write address error occurs.
The invalid read/write address error is detected on the ninth
SCLK rising edge, which means a write to the register does not
occur when an invalid address is targeted. Invalid read/write
address error detection is enabled by default and can be disabled
by the user through the error configuration register.
CLEARING THE ERROR FLAGS REGISTER
To clear the error flags register, write the 16-bit SPI frame (not
included in the register map), 0x6CA9, to the device. This SPI
command does not trigger the invalid R/W address error. When
CRC is enabled, the user must send the correct CRC byte for a
successful error clear command. At the 16th or 24th SCLK rising
edge, the error flags register resets to zero.
BURST MODE
The SPI interface can accept consecutive SPI commands
without the need to deassert the CS line, which is called burst
mode. Burst mode is enabled through the burst enable register
(Address 0x05). This mode uses the same 16-bit command to
communicate with the device. In addition, the response of
the device at SDO is still aligned with the corresponding SPI
command. Figure 41 shows an example of SDI and SDO during
burst mode.
The invalid read/write address and CRC error checking functions
operate similarly during burst mode as they do during address
mode. However, SCLK count error detection operates in a
slightly different manner. The total number of SCLK cycles
within a given CS frame is counted, and if the total is not a
multiple of 16, or a multiple of 24 when CRC is enabled, the
SCLK count error flag asserts.
SDO
COMMAND0[15:0]
RESPONSE0[15:0]
COMMAND1[15:0]
RESPONSE1[15:0]
COMMAND2[15:0]
RESPONSE2[15:0]
COMMAND3[15:0]
RESPONSE3[15:0]
SDI
CS
15902-039
Figure 41. Burst Mode Frame
SOFTWARE RESET
When in address mode, the user can initiate a software reset.
To do so, write two consecutive SPI commands, namely 0xA3
followed by 0x05, to Register 0x0B. After a software reset, all
register values are set to default.
DAISY-CHAIN MODE
The connection of several ADGS5414 devices in a daisy-chain
configuration is possible, and Figure 42 shows this setup. All
devices share the same CS and SCLK line, whereas the SDO of a
device forms a connection to the SDI of the next device, creating a
shift register. In daisy-chain mode, SDO is an eight cycle delayed
version of SDI. When in daisy-chain mode, all commands target
the switch data register (SW_DATA). Therefore, it is not
possible to make configuration changes while in daisy-chain mode.