• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 409 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.

CC2640R2L: Timer power consumption issues.

Nick Sun
Intellectual 2265 points
Part Number: CC2640R2L

Hi team,

Here's a request from customer:

When customer was doing the broadcast packet cutting test, he found that the power consumption of the timer was high, which affected his experimental results.

The figure above is a waveform without any processing of the timer event, the working time of the timer is close to 3ms, and the current reaches about 4mA.

The SDK is simplelink_cc2640r2_sdk_4_30_00_08 and the example is modified by C:\ti\simplelink_cc2640r2_sdk_4_30_00_08\examples\rtos\CC2640R2_LAUNCHXL\ble5stack\simple_peripheral.

Can you help for checking this point?

Thanks and Regards,

Nick

  • 0
    TI__Expert 5150 points

    Hi Nick,

    Could you ensure me that they used the right method of measurement on the scope.

    You can check the AppNote below for details: in section §6.

    https://www.ti.com/lit/an/swra478/swra478.pdf

    Does the scope shot is corresponding to the Bluetooth LE advertisement event ?

    regards,

  • 0 in reply to Guillaume
    TI__Intellectual 2265 points

    Hi Guillaume,

    Here's the further reply from customer:

    The instrument customer used in the test is a current analyzer, the test method is right, the scope shot he took corresponds to the waveform of the timer event without any processing.

    Can you test the code sent from customer, which the timer is used to switch the broadcast?

    TestDemo.rar

    Thanks and Regards,

    Nick

  • 0 in reply to Nick Sun
    TI__Mastermind 40200 points

    Hi Nick,

    Are they running this code on a LaunchPad or on a custom board? Can they show us a diagram or a picture of how they are connecting their test equipment to their DUT?

    Best Regards,

    Jan

  • 0 in reply to Jan
    TI__Intellectual 2265 points

    Hi Jay,

    Here's the further reply from customer:

    Both on the LaunchPad and on a custom board caused similar results.

    Here is the connection diagram:

    Thanks and Regards,

    Nick

  • 0 in reply to Nick Sun
    TI__Mastermind 40200 points

    Hi Nick,

    I am surprised to see the diagram provided. I would have expected the current analyzer to be in series between the DC power supply and the VCC pin of the launchpad. Something along the lines of what is shown below:

    In the diagram provided in your reply, I would not expect accurate measurements as there is not return path for the current to come back from the current analyzer and the current is being split between going to the analyzer and the launchpad. 

    Best Regards,

    Jan

  • 0 in reply to Jan
    TI__Intellectual 2265 points
    Hi Jay,

    Here's the further original reply from customer:

    What's the difference, and back to the topic, my question is the high power consumption caused by the current and duration of the timer, why did it become how to measure the current in the end?

    I simply string the current analyzer between the current source and the device under test, and the test results also have corresponding screenshots.

    And I also sent the code I used to test, you can use this code to test, test in the way you think is right, at least you should give me a conclusion, instead of the problem of testing methods.

    3326.TestDemo.rar

    Thanks and Regards,

    Nick

  • 0 in reply to Nick Sun
    TI__Mastermind 40200 points

    Hi Nick,

    Understood. I will try to run the measurement on my side tomorrow. I will update you with any results I may find.

    Best Regards,

    Jan

  • 0 in reply to Jan
    TI__Intellectual 2265 points

    Hi Jan，

    Are there any updates for this post?

    Thanks and Regards,

    Nick

  • 0 in reply to Nick Sun
    TI__Mastermind 40200 points

    Hi Nick,

    My apologies for the delay here. I have no updates at this time. I will work with the team to get this tested sometime early next week. My apologies for the inconvenience.

    Best Regards,

    Jan

  • 0 in reply to Jan
    TI__Mastermind 40200 points

    Hi Nick,

    We are still trying to find time to test this on our side and again I apologize for the delay. I did find time to look over the code and I see a large amount of timers set up each doing some work. Are all of these timers running simultaneously? If so, then what happens when we only use a single timer? If not, then can you specify which of these timers is running?

    Best Regards,

    Jan