• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 342 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.

CC2340R5: CC2340R5 standby current problem

Nick Yao
Prodigy 30 points
Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I've mass produced 180 boards so far, and found that there are 20 or so units with high standby current, the normal standby current is around 20uA, while the high ones are ranging from 30-100+uA.

What could be the problem?

The program works in peripheral mode, broadcast interval 1s, the program is modified based on basic_ble.

The board with high standby current will work fine if I change the chip for it.

I'm not sure if it's a chip problem or a program problem.

Doubt the program, most of them are normal.

Suspect the chip, TI's chip failure rate is so high?

Seek help from TI official technical support.

  • 0
    TI__Mastermind 42250 points

    Hi,

    Thank you for reaching out. Have you had your design reviewed using https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS? I will loop in the HW team to get their thoughts as to what may be going on.

    Best Regards,

    Jan

  • +1
    TI__Expert 6520 points

    Hi Nick,

    I suspect that there may be an issue with the pin configuration. Floating inputs can lead to excess current consumption. In the case of the CC2340Rxx devices I'm aware of an issue with the SWDIO and SWDCK pins. They connect internally to the debug circuit and always act as an input and so should either be driven as an output or configured as in input with a pull-up or pull-down resistor. In the case of SWDIO/SWDCK the default reset value for the IOC register for those pins is to have a pull-up applied to SWDIO and a pull-down applied to SWDCK. The current version of the SDK when using Sysconfig resets those values and disables the pulls. You can ensure the default values are not overwritten by configuring those two pins in sysconfig and selecting the "Do Not Configure" option:

    Please try this and see if the excess power consumption issue is resolved.

    This configuration will be resolved in a future release of the SDK

    Best Regards,

    Jake

  • 0 in reply to Jake Pulliam
    Prodigy 30 points

    Thank you very much. The standby currents did all normalize after configuring as you said.