1 Silicon Errata Summary

When using the “Stay in RX after EOT”, there is a minor chance that subsequent receptions will fail. This happens when the internal firmware and hardware state machines fall out of sync, which disables proper signal reception due to an unintentionally set status flag.

In this condition, the system technically still detects signals, but the reception is aborted immediately after the Start of Telegram (SOT) state is reached. The standard notifications/events (WCO, SOT, and EOT) are still generated, but the receive buffer fill level remains at zero (0x00).

The system enters this suspect state if an End of Telegram (EOT) event occurs shortly before the system reaches the Start of Telegram (SOT). In other words, there is a break in the reception shortly before reaching the SOT.

The critical time window for entering this state is less than 6 μs. If the EOT occurs 6 μs or less before reaching the SOT, the software and hardware state machines may fall out of sync during the restart of the receive path. As a result, the system can no longer properly receive RF messages (payload data).

Under very specific conditions, the time window may be extended to 40 μs, specifically for very strong input signals (>−39 dBm) at the LNA input. If the input signal level varies around this threshold during EOT detection, the internal antenna‑damping state machine initiates a restart of the channel filter, resulting in additional latency before the receive path is reactivated. This can occur when the signal level crosses the threshold during the EOT event, that is, when it transitions from below −39 dBm to above −39 dBm or vice versa.