SPSB081 datasheet(52/137 Pages) STMICROELECTRONICS

52 / 137 page

4.4.1

Clock monitor

During communication (CSN low to high phase) a clock monitor counts the valid SCK clock edges. If the SCK

edges do not correlate with the SPI data length, an SPIE is reported with the next command and the actual

communication is rejected.

By accessing the device information registers (OpCode = ‘11’) the clock monitor is set to a minimum of 16 SCK

edges plus a multiple by 8 (for example, 16, 24, 32, …).

Providing no SCK edge during a CSN low to high phase is not recognized as an SPIE. For a SPI burst read also

the SPI data length plus multiple numbers of payloads SCK edges are assumed as a valid communication.

4.4.2

SCK polarity (CPOL) check

To detect the wrong polarity access via SCK, the internal clock monitor is used. Providing first a negative edge on

SCK during communication (CSN low to high phase) or a positive edge at last will lead to an SPI error reported in

the next communication and the actual data is rejected.

4.4.3

SCK phase (CPHA) check

To verify, that the SCK phase of the SPI master is set correctly a special device information register is

implemented. By reading this register the data must be 55H. In case AAH is read the CPHA setting of the

SPI master is wrong and a proper communication cannot be guaranteed.

4.4.4

CSN timeout

By pulling CSN low the SDO is set active and leaves its tristate condition. To ensure communication between

other SPI devices within the same bus even in case of CSN stuck at low a CSN timeout is implemented. By

pulling CSN low an internal timer is started. After timer end is reached the actual communication is rejected and

the SDO is set to tristate condition.

4.4.5

SDI stuck at GND

As a communication with data all-‘0’ and OpCode ‘00’ on address b’000000 cannot be distinguished between a

valid command and a SDI stuck at GND this communication is not allowed. Nevertheless, in case a stuck at GND

is detected the communication will be rejected and the SPIE will be set with the next communication.

4.4.6

SDI stuck at HIGH

As a communication with data all-‘1’ and OpCode ‘11’ on address b’111111 cannot be distinguished between a

valid command and a SDI stuck at HIGH this communication is not allowed. In case a stuck at HIGH is detected

the communication will be rejected and the SPIE will be set with the next communication.

4.4.7

SDO stuck at GND and HIGH

The SDO stuck at GND and stuck at HIGH has to be detected by the SPI master. As the definition of the GSB

guarantees at least one toggle, a GSB with all-‘0’ or all-‘1’ reports a stuck at error.

SPSB081

Protocol failure detection

DS14048 - Rev 3

page 52/137

SPSB081 датащи(PDF) 52 Page - STMicroelectronics

SPSB081 датащи(HTML) 52 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

датащи скачать

ссылки URL