• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 52 subscribers
  • Views 251 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2745R10-Q1: CC2745 Handover abnormal

Weifeng Ou
Prodigy 40 points

Part Number: CC2745R10-Q1

Hello TI,

When debugging the channel sounding + handover functionality in the simplelink_lowpower_f3_sdk_9_14_00_39 sdk car_node demo, I encountered the following problem:

1. When the mobile phone is connected to the CC2745, without performing channel sounding ranging, the Serving Node performs handover, and the Candidate Node successfully connects to the mobile phone (handover data size is 268 bytes).

2. The mobile phone connects to the CC2745, and the channel sounding ranging function is started. After obtaining the distance, the Serving Node performs the handover function, and the Candidate Node crashes (the handover data size is 1128 bytes).

3. CCS debug call stack is shown in the following figure:

img_v3_02tn_ff9b9fe3-2b32-46be-84a2-9cb03316783g.jpg

img_v3_02tn_ea13521c-2382-4b9f-bfd8-20e192b1de4g.jpg

4. Because we cannot see the code in handover_cn.c, we cannot continue to investigate the cause of the crash. Please help us solve this problem, thank you.

 

  • 0
    TI__Intellectual 1910 points

    Hello Weifeng,

    We have someone looking into it, please allow a week and we will get back to you. Thank you.

  • 0 in reply to Eshaan Tibrewala
    Prodigy 40 points

    Hello, how is the progress of this issue? I'd like to track it via email. Is your email address [email address here]? I've also emailed TI's FAE (Island, Wei) about this issue, and I'd like to CC you on this email.

  • 0
    TI__Intellectual 1910 points

    Hello Weifeng,

    The FAE will directly reach out and add me or someone from the automotive team and set up an email thread between us to track the issue. Thanks!

    Eshaan

  • 0 in reply to Eshaan Tibrewala
    TI__Intellectual 1910 points

    Hello Weifeng,

    You have to initialize channel sounding before starting handover. Currently, this is the only way to avoid the issue you are seeing. Thank you.

    Eshaan

  • 0 in reply to Eshaan Tibrewala
    Prodigy 40 points

    Hello Eshaan Tibrewala,

    I'm performing channel sounding ranging on the ServingNode. After successful ranging, I initiate a handover to the Candidate node.

    Before executing the handover on the Candidate node, I've already called `ChannelSounding_start` and initialized it.

    What does initializing channel sounding before the handover mean? What specific operations are performed?

  • 0 in reply to Weifeng Ou
    TI__Genius 9775 points

    Hello Weifeng, 

    There is currently a problem with executing connection handover after channel sounding has been initialized. To avoid sending the extra 860 bytes, and connection handover failing, you need to de-initialize channel sounding before executing connection handover. We are currently working on resolving the problem. 

    Additionally, you will need to edit the Key Node example project to enable multiple CS configurations. By default, the Key Node project only uses one CS configuration. If you want to execute CS with the serving node, and then the candidate node, you will need to do this. 

    When the problem with CS handover is resolved, you will not need to create multiple CS configurations on the Key node project. The handover will transfer the CS configuration between the serving node and the candidate node. 

    The flow for this looks like this: de-initialize channel sounding -> start SN connection handover -> handover connection to CN -> re-enable channel sounding on CN -> create new CS configuration for the CN on the key node. 

    Please try this and let me know if it works for you. 

    Thanks,
    Isaac

  • 0 in reply to Isaac Larson
    Prodigy 40 points

    Hello Isaac Larson，

    I tried calling the CS_RemoveConfig function after CS ranging is complete. After calling this function, the handover data obtained from the ServingNode is still 1128 bytes. It seems that there is no way to disable the parameter configuration related to ChannelSounding. Are there any other APIs that can disable ChannelSounding?