• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 261 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: sleep and usleep not implies standby current consumption

Selvam Krishnan
Prodigy 210 points
Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Good day TI team,

Summary: We are expecting one example to test and utilize the standby current consumption. 

Details:

Our application requires overall current of 30uA. 

We choose CC2340R52RKP as it looks consume current in nA.

Our application will active for 1-3 ms and then sleep around 997ms.

We tried sleep and usleep with the example simplelink_lowpower_f3_sdk_9_12_00_19\examples\nortos\LP_EM_CC2340R5\drivers\empty using CC2340R5-LP.

We measured the current but looks oscillating.

  1. While first time measuring using DMM,

Sleep implies 0.22uA

LED ON implies 1540uA

  1. After adding I2C on top of this , oscillating up to 270uA without LED ON.

Here sleep looks consumes 270uA. 

Please clarify that is sleep = standby or not?

 

And then 

From CC2340Rx datasheet – page 53,

Understanding is there is no timer based standby mode, come out from standby mode via LP-COMP or pin reset.

Moreover, sleep and usleep is based on vTaskDelay() functionality , it looks RTOS based.

So that got confused that

Whether sleep or usleep is actually standby or not?

 

Also,

Please suggest one example without RTOS to test standby mode or any other low power mode example.

 

Thanks

Selvam

 

  • 0
    Prodigy 210 points

    Part Number: CC2340R5

    Good day TI team,

    Summary:

    Please suggest about location of operating fequency and peripherals say I2C, ADC frequency in sys config file .

    Details:

    our application requires overall current counsumtion of 30uA.

    For reduce the current consumption,

    Initially we tried to change the MCU operating freqency for the example simplelink_lowpower_f3_sdk_9_12_00_19\examples\nortos\LP_EM_CC2340R5\drivers\i2ccontroller

    via its sysconfig file - i2ccontroller.syscfg

    But not able to locate the location of current operating frequency of MCU as well as I2C clock/operating frequency in GUI of i2ccontroller.syscfg. 

    Shall we get the guidance to find the current operating frequency of MCU as well as I2C clock/operating frequency in GUI of sys config file - i2ccontroller.syscfg.?

    Thanks

    Selvam

     

  • 0
    TI__Guru**** 219337 points

    Hi Selvam,

    1. The no-RTOS empty TI Driver is a suitable example of standby power consumption, and with no radio activity you should observe less than 1 uA.  Check the device datasheet.
    2. sleep and usleep APIs allow the device to enter standby so long as no other active tasks are being performed which require clock activity
    3. To reduce power consumption, remove LED functionality and make sure that I2C is not actively transferring or that the Display is not being written (consider removing).  Fairly similar conditions exist for the ADC (i.e. if not actively using peripherals then you will minimize power consumption).
    4. The main MCU clock is 48 MHz and sources the I2C, neither of these are configurable but multiple I2C bit rates are supported by the TI Driver.

    typedef enum
{
    I2C_100kHz  = 0, /*!< I2C Standard-mode. Up to 100 kbit/s. */
    I2C_400kHz  = 1, /*!< I2C Fast-mode. Up to 400 kbit/s. */
    I2C_1000kHz = 2, /*!< I2C Fast-mode Plus. Up to 1 Mbit/s. */
    I2C_3330kHz = 3, /*!< I2C High-speed mode. Up to 3.4 Mbit/s. Mantained for backwards compatibility. */
    I2C_3400kHz = 3, /*!< I2C High-speed mode. Up to 3.4 Mbit/s. */
} I2C_BitRate;

    Regards,
    Ryan