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

Original question:

CCS/LAUNCHXL-CC1352P: Build fails randomly with odd error

CCS/LAUNCHXL-CC1352P: Energytrace reports wrong current

Yvan Pearson
Intellectual 850 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software: Code Composer Studio

Energytrace seems to report the wrong current. I need to power cycle the board, or re-start energy trace a few times to get the expected current.

Steps:

1.Load hex file to board

2.start energy trace via icon near the menu

3.press the green triangle button (play button)

4.Look at mean current, reads ~0.654mA (should be ~50uA)

5.Re-start and/or power cycle launchpad

6.press the green triangle button (play button)

7.Look at mean current, reads ~0.654mA or reads 0.050mA. If it reads the former repeat process

Also sometime energytrace hangs for unknown reasons

My Setup

Ubuntu18

CCS v9.3

SDK v3.40

Any thoughts?

  • 0
    Intellectual 850 points

    PS. It would be great if energytrace would read the correct current the first time and not hang :)

    Thanks

  • 0 in reply to Yvan Pearson
    TI__Guru**** 171224 points

    Yvan,

    I am analyzing this problem, but I don't recall these issues in CCSv9.2 (when I was using ET heavily on Ubuntu). Do you have a specific application that could help reproduce this?

    One additional influence that sometimes happens with ultra-low currents is the influence of JTAG circuitry: to accurately measure sub mA currents, sometimes it is necessary to disconnect from the debug session, unplug, re-plug and then measure it. In extreme cases you need to remove the unnecessary jumpers from the launchpad kit in order to reduce leakage through the extra circuitry (the EnergyTrace "non plus" measurements can be done without any JTAG) 

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 850 points

    My Setup

    Ubuntu18

    CCS v9.3

    SDK v3.40

    Application Zstack ZED_LIGHT with defines

    Z_POWER_TEST

    POWER_TEST_POLL_DATA

    xBOARD_DISPLAY_USE_UART

    The problem seems to go away if I re-connect the USB cable before pressing the green triangle. I need my application to be in the uA range so correct readings are important

  • 0 in reply to Yvan Pearson
    TI__Guru**** 171224 points

    Yvan,

    Please apologize for the delay; I was out of the office for a few days.

    I am running the same environment as you, but I am getting a consistent current of ~8mA, even by disabling the LED PWM (as shown in this other thread) and removing all JTAG jumpers.

    I have the following questions: 

    - When defining Z_POWER_TEST, the symbol POWER_TEST_TX_PWR is undefined. Which power value did you choose? I suspect this will influence the current consumption. (sorry, I am not very familiar with the values required by this setting). 

    - Between steps 4 and 5 above, are you closing the EnergyTrace interface when disconnecting the USB cable? If not, I can see issues happening if the re-connect causes the Launchpad board to be re-enumerated by the system to a different bus and port. 

    Regards,

    Rafael