L99LD02 datasheet(36/66 Pages) STMICROELECTRONICS

36 / 66 page

Serial peripheral interface (ST SPI standard)

L99LD02

36/66

DS12448 Rev 3

a stuck-at-GND error is detected, the communication will be rejected and the SPIE will

be set in the next communication cycle.



SDI stuck at HIGH



As a command with all data bits set to ‘1’ and OpCode ‘11’ on address b’111111 cannot

be distinguished from an SDI stuck-at-HIGH error, this command is not allowed. In

case a stuck-at-HIGH error is detected, the communication will be rejected and the

SPIE will be set in the next communication cycle.



SDO stuck



SDO stuck-at-GND and stuck-at-HIGH errors have to be detected by the SPI master.



As the definition of the GSB guarantees at least one bit toggle, a GSB with all bits set to

‘0’ or with all bits set to ‘1’ can be considered as an SDO stuck-at error.

5.5

Implementation remarks

5.5.1

From an implementation point of view, it is guaranteed that no register change gets lost

during communication. In case a register value was changed during a communication, it will

be reported with the next communication frame.

5.5.2

GSB and payload inconsistency

Due to the internal implementation strategy, it may occur that data reported in the GSB does

not match data reported in the payload in case the data was changed during GSB shift out.

In this case, the payload data is the status quo, as it was loaded later into the SPI shift

5.6

Timings

All SPI related timings are defined in Section 6.4.4: SPI bus (CSN, SCK, SDI, SDO).

5.7

5.7.1

Control Register

CR#1: Control Register 1

Address:

0x01h

Type:

R/W

98765432

Unused

L99LD02 датащи(PDF) 36 Page - STMicroelectronics

L99LD02 датащи(HTML) 36 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

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

ссылки URL