• State
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 40 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CC2744R7-Q1: Advertising and Scanning is not starting | Channel Sounding

Vaibhav Patil
Intellectual 421 points

Part Number: CC2744R7-Q1

Hi Forum,

I am referring to the Channel Sounding car_node example. I am facing an issue when trying to start advertising or scanning.

The corresponding APIs return success, but the device neither starts advertising nor scanning when these APIs are called from anywhere other than the TERMINATE_CONNECTION event handler in app_car_node.c.

The same APIs work as expected when invoked from the TERMINATE_CONNECTION event, but not when called from other parts of the application.

Could you please let me know if there are any dependencies, state restrictions, or initialization requirements that must be satisfied before starting advertising or scanning?

Regards,
Vaibhav

  • 0
    TI__Genius 9855 points

    Hello Vaibhav, 

    Are you using the channel sounding python demo?  

    Where are you calling the API to start advertising/scanning and have you verified that the function is being executed at all? If you did verify this, what is the return code of the function?

    Additionally, what SDK are you using? 

    Thanks,
    Isaac 

  • 0 in reply to Isaac Larson
    Intellectual 421 points

    Hi Isaac,

    I am using SDK 9.14.02.16 and working with the modified example provided by TI. This implementation is completely independent of the Python demo, with all the functionality running on-chip.

    Yes, I am verifying the API execution based on its return value, which is 0x00 (success).

    I have implemented project-specific UART commands to enable or disable advertising and scanning. However, when I issue these commands, advertising or scanning does not start, even when no CS procedure is in progress. If I issue the same command again, the API returns 0x11.

    Regards
    Vaibhav

  • 0 in reply to Vaibhav Patil
    TI__Genius 9855 points

    Hello Vaibhav, 

    1. Have you verified the UART commands are being received properly?

    2. Also, can you let me know where you are calling the adv/scan start API from?

    3. What do you mean by issue the command again?

    4. Do you mean you unsuccessfully call adv/scan start, then try to start adv/scan again?

    5. How are you verifying that adv/scan is not working? 

    6. Can you output the PA/LNA and send a waveform capture of this when the problem occurs? You can do this within RCL -> RCL Observables -> Use Case -> Select PA/LNA Pins. 

    Please provide a response to these comments. I will look into testing when I receive these answers. 

    Thanks, 
    Isaac 

  • 0 in reply to Isaac Larson
    Intellectual 421 points

    Hi Isaac,

    1. Yes, I verified that the command is being received correctly, and the corresponding API is executed with a return status of 0x00 (SUCCESS).

    2. I have implemented a wrapper function outside app_car_node.c, which eventually transfers the control flow to the functions in app_car_node.c.

    3. When I issue the command to start advertising, the API returns 0x00 (SUCCESS). However, advertising does not actually start. If I issue the same command again, the API returns 0x11.

    4. I don't believe the initial API call is unsuccessful, since it returns 0x00 (SUCCESS).

    5. I verify advertising using the nRF Connect Android application. For scanning, I verify that advertising reports are received by the application.

    6. Could you clarify the relevance of this check? Since advertising and scanning work correctly in some scenarios and only fail when triggered through my external UART commands, it seems the radio itself is functioning correctly. Wouldn't that indicate the issue lies elsewhere?

    Regards

    Vaibhav

  • 0 in reply to Vaibhav Patil
    TI__Genius 9855 points

    Hello Vaibhav, 

    Understood. The 6th question was to verify that advertising/scanning was not seen through the radio layer. 

    Have you tested this on the newer SDKs (9.20 or 9.20.01)? 

    I will work on replicating the problem you are seeing. 

    Thanks,
    Isaac