• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 378 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.

LAUNCHXL-CC1352R1: CC1352R - energy trace issue

Adam Kozlowski
Expert 1805 points
Part Number: LAUNCHXL-CC1352R1


Hi,

I use:
board: Launchpad-CC1352R
SDK: 5_10

I have a simple program based on the PinStandby example from TIREX.
There is only one change. Two lines inside the main thread that are responsible for LED toggling have been removed.

I use this program to check energy trace for the simplest scenario, transition STANDBY->ACTIVE->STANDBY.

When I set standbyDuration to 1000ms, I see the following energy trace:

There are two main parts: red and blue.
The red part is a recharge pulse, and the blue is the actual transition.
In this case (period=1000ms), I can see one additional "standalone" recharge pulse between adjacent wakeups.
Everything is as expected. The energy of the recharge pulse depends on the time since the last recharge and so on.

Unfortunately, when I set standbyDuration to 100ms, I see the following energy trace:

There are three main parts: red, blue, and extra yellow.
What is this yellow part for?

Regards
Adam

  • 0
    TI__Guru* 87051 points

    I am able to see the same thing. Please allow me some time to look into this.

    BR

    Siri

  • 0 in reply to Siri
    TI__Guru* 87051 points

    First of all, I am sorry that this has taken so long.

    I spent some time trying to figure out if there were any differences in the power driver with respect to the different wake-up intervals and I also consulted R&D to discuss if the difference could be related to the re-charge algorithm, but no-one could find any reasons for the differences.

    The I saw that for the same interval (100 ms) you would actually see both the short and the long active time.

    I then suspected that we were probably both fooled by the accuracy/resolution of ET.

    I was then able to look at the current profile with a proper power analyzer and could see that the current profiles was the same always (they all have the extra yellow part).

    BR

    Siri

  • 0 in reply to Siri
    Expert 1805 points

    Hi,

    Thank you for the effort you put, and your deep investigation.
    I have a few days off, but I'll come back to the issue by the end of the following week.

    Siri said:
    I was then able to look at the current profile with a proper power analyzer and could see that the current profiles was the same always (they all have the extra yellow part).

    Would you be so kind as to post the results you got (preferably CSV file)?
    If you are concerned about sharing this, you can always send me a direct message.

    BTW
    I found a similar result in swra578b (page 19).

    Regards
    Adam

  • 0 in reply to Adam Kozlowski
    TI__Guru* 87051 points

    The measurements where done with a Keysight 14585A

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/scopedata.scp

    https://www.keysight.com/de/de/search.html/14585a

    Siri