• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 67 subscribers
  • Views 1435 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104649
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

sd_ant_burst_handler_request intermittency?

David Woosley

What are the conditions that can cause sd_ant_burst_handler_request(Channel_0, 8, tx_buffer, BURST_SEGMENT_END) to return NRF_ANT_ERROR_TRANSFER_SEQUENCE_NUMBER_ERROR? If I can't fix it, is there a recommendation for how to recover?

This error intermittently occurs during downloads. It can occur when downloading the directory (128 bytes), or test files (317 bytes), and occurs after the 3rd to 20th download.

I am using NRF51422-CEAA with s210_nrf51422_3.0.0_softdevice and nrf51_sdk_v5_2_0_39364. The failure usually occurs at line 882 in the nrf6310/s210/ant_fs/client/antfs.c module, but will also fail at line 833 when downloading the test files' second data group.

Thanks for helping.

  • 0

    From ant_error.h:

    #define NRF_ANT_ERROR_TRANSFER_SEQUENCE_NUMBER_ERROR  NRF_ANT_ERROR_OFFSET + TRANSFER_SEQUENCE_NUMBER_ERROR  ///< Response when sequence number of burst message or burst data segment is out of order.

    There are three burst segment identifiers:

    BURST_SEGMENT_START
BURST_SEGMENT_CONTINUE
BURST_SEGMENT_END

    If you for example use BURST_SEGMENT_CONTINUE or BURST_SEGMENT_END before you use BURST_SEGMENT_START you will get this error.

Related