• State TI Thinks Resolved
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 66 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CC2745R10-Q1: Channel Sounding stops receiving distance data after a long run, typically around 4 to 5 hours.

Michael Lin
Prodigy 20 points
Part Number: CC2745R10-Q1

Tool/software:

Hi,

As a follow-up to my previous post:
e2e.ti.com/.../cc2745r10-q1-channel-sounding-stops-receiving-distance-after-3000-5000-procedures-on-cc2745r10

After switching to SDK v9.11.01.19(www.ti.com/.../9.11.01.19),
Channel Sounding has become more stable, the distance reporting used to stop after around 40 minutes, but now it continues for 4–5 hours before failing.

Here’s a clue that may help: when the issue occurs, we observe the following UART data from the car_node (CC2745R10):

FE 16 00 59 90 44 00 00 00 00 00 01 07 0A D8 D6 00 00 01 00 00 03 00 00 00 01 00 9A
FE 11 00 59 90 60 00 0F 00 00 FF FF FF FF FF FF FF FF FF FF FF FF B7


As you can see, the distance, quality, and confidence fields are all FF FF FF FF, and after this, no more measurement data is received.

In normal operation, the second packet should look like this:

FE 16 00 59 90 44 00 00 00 00 00 01 07 0A D8 D6 00 00 01 00 00 03 00 00 00 01 00 9A
FE 11 00 59 90 60 00 00 00 00 00 00 00 00 82 03 00 00 64 00 00 00 5D


Power-cycling the key_node does not solve the issue, so the problem seems to lie with the car_node.

We reproduced this issue by increasing the CS procedure loop count from 100 to 100,000 and letting the system run overnight. The issue consistently occurs.

Could you please help check this behavior again?

Thanks!
Michael

  • 0
    TI__Expert 6075 points

    Hello Michael, 

    Thank you for reaching out. The UART data mentioned is expected with an error in PCT data received. 0xFF FF FF FF indicates that the data is invalid. Does 0xFF FF FF FF output indefinitely after the problem occurs? 

    I am going to run the test tomorrow starting in the morning. Can you let me know the distance you are testing at, the txPower, the antenna configuration, and the connection interval used? 

    Thanks,
    Isaac

  • 0 in reply to Isaac Larson
    Prodigy 20 points

    1. The incorrect distance data (0xFF FF FF FF) only appears once, and after that, no further distance results are received.
    2.
    Testing distance is about 2 meters
    txPower is "tx_power_delta": 0x80
    antenna configuration is 2 with Antenna Mux Bitmap = 0xC6
    "aci" = 7 and "preferred_peer_antenna" = 0b0011
    3.
    Connection Handle: 0
    Connection Role: 8
    Connection Interval: 24
    Connection Latency: 0
    Connection Timeout: 2000
    Clock Accuracy: 0

    Thanks!
    Michael

  • 0 in reply to Michael Lin
    TI__Expert 6075 points

    Hello Michael, 

    I have reproduced the issue on my end. I ran the demo for approximately 3 hours before seeing the failure. I observed one distance results return as invalid (0xFF FF FF FF). I did not receive anymore distance results after this point. 

    I am going to run the test tomorrow in debug mode, while capturing a sniffer log to see if I can get a better idea of what is failing. Additionally, I am going to report the issue to the team. 

    Is this issue critical for your current testing/development? Please let me know. 

    Thanks,
    Isaac

  • 0 in reply to Isaac Larson
    Prodigy 20 points

    Hi Isaac,

    We’re planning to demo this Channel Sounding feature to our customer around December.
    It would be great if the issue could be resolved before then.

    Thanks!
    Michael

  • 0 in reply to Michael Lin
    TI__Expert 6075 points

    Hello Michael, 

    I appreciate you letting me know. I will work to have the problem resolved. 

    I am going to close this ticket but will continue working on resolving the problem. 

    If you have any further questions, please feel free to reach out via E2E or to an FAE. 

    Thanks,

    Isaac