MLX90363 Datasheet, PDF (29/57 Pages) Melexis Microelectronic Systems – Triaxis® Magnetometer IC With High Speed Serial Interface

MLX90363
Triaxis® Magnetometer IC
With High Speed Serial Interface
14.13. Protocol Errors Handling
Error Item
IncorrectBitCount
IncorrectCRC
IncorrectOpcode
tREFE <
tReady_mod1
tSyncFE <
tReady_mod2
tRESync Violation
tRERE_mod3 <
tReady_mod3
tREFE_mod3 <
tReady_FE_mod3
TimeOut
Error definition
Slave In Message bit count
≠ 64
Slave In Message has a
CRC Error
Invalid Slave in Message
Regular Message
Readback occurs to early
Regular Message
Readback occurs to early
Sync Pulse occurring to
early
Regular Message
Readback occurs to early
Regular Message
Readback occurs to early
Regular Message
Readback occurs to late
Condition
all modes
all modes
all modes
Trigger
mode 1
Trigger
mode 2
Trigger
mode 2
Trigger
mode 3
Trigger
mode 3
all modes
Detection
FW reads the HW bit
counter
FW computes CRC
FW
Interrupt occurring to
early +
Fw reads HW bit +
Protection interrupt
Interrupt occurring to
early +
Fw reads HW bit +
Protection interrupt
none. The Sync
pulse is pending
internally.
Protection interrupt
Protection interrupt
Timer Interrupt
Slave Actions
Ignore
Message +
Re-init Protocol
Ignore
Message +
Re-init Protocol
Ignore
Message +
Re-init Protocol
Ignore Frame +
Re-init Protocol
Ignore Frame +
Re-init Protocol
none (but the
sync pulse is
not treated
immediately)
Re-init Protocol
Re-init Protocol
MISO Frame =
NTT +
Re-init Protocol
MISO Message
Error Message
(incorrect bitcount = 1)
Error Message
(incorrect crc = 1)
Error Message
(incorrect opcode = 1)
NTT message
NTT message
Valid message. Note:
This violation can
cause a TSyncFE <
TReady_mod2
violation.
NTT message
NTT message
NTT message
Table 27 – Protocol Errors Handling (Slave standpoint)
Error Items/Events
Receive NTT
Associated Slave
Event
Receive NTT
Master recommended
actions
Protocol re-initialization
Associated
Slave Actions
Protocol re-
initialization
Receive Incorrect CRC _{undetected event Protocol re-initialization}
none
Receive Incorrect Opcode
Receive Error Message Send Error Message Protocol re-initialization
none
Receive an unexpected
DiagDetails message
Run in fail-safe mode
Protocol re-initialization
+ Slave reset
none
Next
MISO message
Error Message *
(TimeViolation = 1)
Normal message
Normal message
DiagDetails message
Table 28 – Protocol Errors Handling (Master standpoint)
Note 1: On NTT or Error messages, master should consider that the last command is ignored by the
slave, and it should therefore, either resend the command, or more generally re-initialize the protocol.
Note 2: After protocol re-initialization, master can diagnose the communication with a NOP command.
3901090363
Rev. 005
Page 29 of 57
Data Sheet
Jul/13