nRF54L15-DK: Periodic "rx failed error" (1, 2, 9) in 802154_phy_test example

Hello, I am currently experiencing an issue with the 802154_phy_test example on the nRF54L15-DK board, and I would appreciate your technical support.

[ Environment ]

- Hardware: nRF54L15-DK

- SDK: nRF Connect SDK v3.3.0

- Toolchain: nRF Connect SDK Toolchain v3.3.0

- Application: 802154_phy_test example (Default configuration)

[ Symptom / Problem ]

When running the example without modification, the following error messages are continuously printed on the console log:

- "rx failed error 1!" - "rx failed error 2!" - "rx failed error 9!"

[ Additional Context ]

- The errors appear randomly without any specific pattern or constant period.

- To rule out any RF interference or multi-path fading from the surrounding environment, we conducted a test in the middle of a wide-open soccer field. However, the exact same errors occurred.

- We have not modified the core PHY test source code. Could you please provide insight into what causes these specific error codes (1, 2, and 9) during RX operations? Any suggestions on how to debug or resolve this issue would be highly appreciated. Thank you.

Parents
  • Hi

    What is the transmitter in this setup? The error messages can be read from nrf_802154_rx_error_t in nrf_802154_types.h.

    • Error 1 points to a malformed frame being received.
    • Error 2 points to a frame with an invalid checksum being received
    • Error 9 points to a frame with invalid length being received.

    So I think that the transmitted packets here aren't valid in one way or another.

    Best regards,

    Simon

Reply
  • Hi

    What is the transmitter in this setup? The error messages can be read from nrf_802154_rx_error_t in nrf_802154_types.h.

    • Error 1 points to a malformed frame being received.
    • Error 2 points to a frame with an invalid checksum being received
    • Error 9 points to a frame with invalid length being received.

    So I think that the transmitted packets here aren't valid in one way or another.

    Best regards,

    Simon

Children
No Data
Related