Other Parts Discussed in Thread: ENERGYTRACE
I want to use EnergyTrace to measure the energy consumption of a custom board that uses NB-IoT technology (board fed by 3.3V and GND pin on measurement side of Launchpad).
I have used EnergyTrace like this in the past with an MSP432 Launchpad board to measure the current consumption of some LoRaWAN devices, as these stay under the 110mA limit of EnergyTrace while transmitting.
But as NB-IoT has peaks of over 110 mA (around 300-500mA) this resulted in all my EnergyTrace measurements being halted.
I have bought the LAUNCHXL-CC2642R1 board in the hope that I could use embedded EnergyTrace HDR to also be able to measure peaks up to 800mA, which I read was an embedded option on the CC26X2R1 on https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_energytrace.html#energytrace-hdr
When I try to measure current with my new CC26 Launchpad, the data is very noisy and also still halts my measurement when a peak happens (during data transmission).
The feedback I get from the EnergyTrace window is: "Bad energy trace data was detected in the trace stream", see image below.
The CC26 Launchpad is also not able to succesfully power the external device, as the NB-IoT modem shuts down (assuming due to some current restriction or process halt in the supply line).
I have selected the higher current range in the ET-HDR Range Selector in CCS and I am using a USB 3.0 connection from my PC that should be able to deliver 900mA
(both XDS110 COM ports are D0 rated in Windows Device Manager).
What am I doing wrong? Is there a guide to using the embedded EnergyTrace HDR on Launcpad?
Or is EnergyTrace HDR just not compatible with measurements on external boards/devices.
