• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 699 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: BLE Idle/standby current

Notozman
Expert 7536 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: UNIFLASH, ENERGYTRACE

Hi Team, 

I need to measure the CC1352 idle current. It was good in the old SDK, but now I am not getting the same results in the later SDK's with the latest devices. Pls see my results of average current below measured from Launchpads.

@3.3v SDK version  
1352 Peripheral (SDK2.3/ES1.1) 1.9uA simplelink_cc13x2_sdk_2_30_00_45
1352 Peripheral (SDK3.1/ES2.1) 62uA cc13x2_26x2_sdk_3_10_00_53
1352 Peripheral (SDK3.1/ES2.1) 62uA cc13x2_26x2_sdk_3_10_01_11

Using the simple_peripheral example I am just commenting out the adv enable lines as below - then measuring ...no other changes. Release mode build. 

//gp        status = GapAdv_enable(advHandleLegacy, GAP_ADV_ENABLE_OPTIONS_USE_MAX , 0);

//gp        status = GapAdv_enable(advHandleLongRange, GAP_ADV_ENABLE_OPTIONS_USE_MAX , 0);

Is this a known issue ? 

  • 0
    TI__Guru 57865 points

    That is odd, assigning an expert to look into it.

  • 0
    TI__Guru 56590 points

    Hello Notozman,

    Which board LP did you use?

    Can you read the chip info from uniflash?

    You did not interchange CC1352R1_LAUNCHXL and CC1352P1_LAUNCHXL?

    Is there any activity on the current trace or just a flat base line?

  • 0 in reply to Eirik V
    TI__Expert 7536 points

    Hi Eirik, 

    Used the old and new 1352R1 boards. - I only have old version for the P2 and haven't measured that one yet. 

    I havent looked at the profile since just taking the average - confirmed on both battery emulator and external XDS110. 

    Are you saying you dont see this ? 

  • 0 in reply to Notozman
    TI__Guru 56590 points

    Hello Notozman,

    I have not measured yet. I wanted to figure out which exact version you a re using as I would need to track down the same version here.

    Did you remove all the jumpers on the launchpad?

    It might be related to the "RXD<<" pin which is left floating. This could contribute to the extra 60 uA current. Can you verify that you removed all the jumper except the RXD?

  • 0 in reply to Eirik V
    TI__Expert 7536 points

    Hi Eirik. 

    I removed all jumpers as I did with the ES1.1 board where I get the correct results. I will try with the RXD jumper in-place.

    Thanks.

  • 0 in reply to Notozman
    TI__Expert 7536 points

    Looks like that is the issue ! Now I measure 1.7uA.

    Did I miss some documentation somewhere stating that the RXD line was floating ? 

    Thanks for your help !

  • 0 in reply to Notozman
    TI__Guru 56590 points

    Hello Notozman,

    It is mentioned in step 1 in section "7 EnergyTrace" of the Measuring CC13xx and CC26xx current consumption app note:

    Remove all jumpers on the LaunchPad between the XDS debugger and the device, except for the XDS110 Power, the 3V3 and RXD jumpers (see Figure 34).

    ....

    The UART driver in the SDK configures the UART RX pin without internal pull-up. To avoid current leakage in the input buffer, the pin must always be firmly pulled to a logic level

    www.ti.com/.../swra478

  • 0 in reply to Eirik V
    TI__Expert 7536 points

    Ok thanks. 

    Since I wasn't using ET, then I missed it. Was following the DC analyser steps since I am using Agilent battery emulator. Perhaps a doc update with a special highlight on this would be nice !

    Thanks again for your help.