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.

CCS/LAUNCHXL-CC1310: USING LAUNCHPAD TO TEST A CC1310F64

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310, CC1352R, ENERGYTRACE

Tool/software: Code Composer Studio

Hello, 

I would like to modify the project pinStandby_CC1310_LAUNCHXL_nortos_ccs to make it work on a CC1310F64. 

To do so, I have :

- changed the general properties of my project 

- modified the memory size in the file .cmd such as : 

/*#define FLASH_BASE 0x0
#define FLASH_SIZE 0x20000
#define RAM_BASE 0x20000000
#define RAM_SIZE 0x5000*/

#define FLASH_BASE 0x0
#define FLASH_SIZE 0x10000
#define RAM_BASE 0x20000000
#define RAM_SIZE 0x4000

Then I measured the power consumption using EnergyTrace with two launchpad (CC1310 and CC1352R) and I get the following results : 

As you can see, recharge pulses are quite low and the current consumption is equal to 1.4 µA (I expected around 0.7 µA).

Do you know where this overconsumption could come from? 

Regards,

Geoffrey

  • Did you verify that the current was as expected with the out of the box example? In addition, Energy Trace may not be accurate enough to give the datasheet numbers

    What is the purpose of this software? The FW I delivered to the customer you work with giives the expected current consumption on the customer HW.

  • Hello, 

    Yes the current consumption was as expected with the out of the box example (128KB).

    No customer purpose, this is only out of curiosity. I wonder if a modification in the memory size can affect the current consumption (maybe pins being left unassigned or so on). 

    Rgds,

    Geoffrey

  • Memory size and/ or number of DIOs doesn't affect power consumption. The DIOs are set as high-z as default.

    Going to RHB mean that you need to remove all DIOs in the example that does not exist on a RHB or the code will get stuck in some error handling.