• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 179 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2340R5: BLE MCU can't be scanned by others during low power mode

YW Lin
Intellectual 540 points
Part Number: CC2340R5
Other Parts Discussed in Thread: , LP-XDS110, SYSCONFIG

Hi TI members,

Below is my building environment:

Software

Version

Code Composer Studio

12.3.0.00005 

SimpleLink SDK

7.10.00.35

XDCtools

3.62.1.16_core

We power on a BLE MCU for 2 days in our lab, and we found the BLE couldn't be scanned after this period of time.

We would like to know:

1. Which variable decide how long will it take to enter low power mode?

2. If we would like to have our MCU be scanned by windows PC / mobile phone all the time, shall we disable low power mode, or shall we modify any of the configurations of low power mode?

Thanks.

BR,

  • 0
    TI__Mastermind 33640 points

    Hi,

    Thank you for reaching out. I have a few questions that may help us resolve this issue as efficiently as possible. Can you clarify if the CC2340R5 is on an LP-EM-CC2340R5 or a custom board? By default, the CC2340R5 in the unmodified basic_ble project should advertise indefinitely and enter standby mode between the advertisements. It should not shutdown after a period of time.

    When the device cannot be found in scans, is it still responding? Do you see UART activity if the buttons are pressed? Is the device in debug mode or not? If it is in debug mode, then can you pause the execution and share the call stack?

    Best Regards,

    Jan

  • 0 in reply to Jan
    Intellectual 540 points

    Hi,

    1. Can you clarify if the CC2340R5 is on an LP-EM-CC2340R5 or a custom board?

    -> LP-EM-CC2340R5

    2. By default, the CC2340R5 in the unmodified basic_ble project should advertise indefinitely and enter standby mode between the advertisements. It should not shutdown after a period of time.

    -> I thought the behavior didn't look like "shutdown" but looked similar to falling asleep. Does this make sense? I'm not quite sure of this.

    3. When the device cannot be found in scans, is it still responding?

    -> The device might not have connected to any other devices, so it might not have anyone to response to?

     

    4. Do you see UART activity if the buttons are pressed?

    -> No connection between device and app, so I think there couldn't be any activity.

    5. Is the device in debug mode or not?

    -> No.

    6. If it is in debug mode, then can you pause the execution and share the call stack?

    -> Sorry, it wasn't in debug mode, so I don't have this information to share with you.

    Hope the information helps.

    Thanks.

    BR,

  • 0 in reply to YW Lin
    TI__Mastermind 33640 points

    Hi,

    Thanks for the information. Can you verify what the power draw is on the device? How are you powering the device? If its by connecting it to e PC through the LP-XDS110, then you can open a UART terminal and connect via UART to see if there is any UART output and if you can operate the menu through the buttons. This will let us confirm if the device is hanging, in shutdown, or standby. 

    Best Regards,

    Jan

  • 0 in reply to Jan
    Intellectual 540 points

    Hi,

    Our CC2340 was powered on by another CPU, the GPIO of the two components were connected and the CPU provided the power to CC2340.

    We didn't use the LP-XDS110 while we met this situation.

    During our testing, we won't be using the LP-XDS110, so it's kind of hard for us to provide the information you requested.

    But we suspected that the issue was due to low power mode, will disabling the low power mode improve the situation?

    Thanks.

    BR,

  • 0 in reply to YW Lin
    TI__Mastermind 33640 points

    Hi,

    If the issue is due to low  power mode, then yes disabling the power management will resolve the behavior. However, I am not sure if it is due to low power mode. Still it is worth a test. Can you try disabling low power mode through sysconfig and retesting?

    Best Regards,

    Jan