SWRA659A March   2020  – June 2020 CC3100 , CC3100MOD , CC3200 , CC3200MOD

 

  1.   CC3x00 Power Management Optimization and Measurements
    1.     Trademarks
    2. 1 Introduction
      1. 1.1 Getting Started
        1. 1.1.1 For CC3100
        2. 1.1.2 For CC3200
    3. 2 Prerequisites
      1. 2.1 For CC3100
    4. 3 Basic System Power Modes for CC3X00
      1. 3.1 Hibernate State
        1. 3.1.1 Measurement Tool
        2. 3.1.2 Expected Results
      2. 3.2 LPDS State
        1. 3.2.1 Measurement Tool
        2. 3.2.2 Expected Results
        3. 3.2.3 Active (Rx and Tx) States
          1. 3.2.3.1 Configuration Parameter
          2. 3.2.3.2 Expected Results
    5. 4 Power Profiles Use Cases
      1. 4.1 Use Case 1: Always Connected
      2. 4.2 Configuring Options
        1. 4.2.1 Expected Results
      3. 4.3 Use Case 2: Intermittently Connected
        1. 4.3.1 Configuration Options
        2. 4.3.2 Expected Results
      4. 4.4 Use Case 3: Transceiver Mode
        1. 4.4.1 Configuration Options
          1. 4.4.1.1 Expected Results
    6. 5 Power Management Application Bench Mark
      1. 5.1 How to Use
      2. 5.2 Example Usage for CC3200
      3. 5.3 Example Usage for CC3100
    7. 6 Current Consumption Measurements Setup
      1. 6.1 Current Measurement for Profiles and Active States
      2. 6.2 Oscilloscope With Current Probe
        1. 6.2.1 Tools Needed
        2. 6.2.2 FW Needed
        3. 6.2.3 Pre-Requisites / Things to Consider
        4. 6.2.4 Procedure
      3. 6.3 Mobile Communications DC Source
        1. 6.3.1 Tools Needed
        2. 6.3.2 FW Needed
        3. 6.3.3 Pre-Requisites /Things to Consider
        4. 6.3.4 Procedure
      4. 6.4 Static Current Measurements
        1. 6.4.1 Tools Needed
        2. 6.4.2 FW Needed
        3. 6.4.3 Pre-Requisites/Things to Consider
        4. 6.4.4 Procedure
    8. 7 References
  2.   Revision History

4.1 Use Case 1: Always Connected

The always connected profile deals with situations where the device must stay connected to the access point (AP) at any time. Staying connected may cause a high power consumption due to periodic beacon functionality. In this profile, the system will enter LPDS mode between wakeups for activity since the system state needs to be kept and low latency is required.

swra659-use-case-1-always-connected.gifFigure 3. Use Case 1: Always Connected

To optimize your use case please implement below configurations:

  • LSI (Long Sleep Intervals) – A configuration that enable to wake the device up only on every n-th beacon thus providing longer Sleep periods.
    • Implementation: Use the sl_WlanPolicySet and configure SL_POLICY_PM to LSI. Can be added to the “configureSimpleLinkToDefaultState” function” in the main.c file.
  • mDNS - Upon connection to an AP, NWP automatically starts advertising itself by sending mDNS packets. Stop the mDNS feature when it is not required by the system application for power optimization.
    • Implementation: Stopping the mDNS feature is done using the sl_NetAppStop API, and can be done once as an indication is stored in NVMEM. Can be updated in the “configureSimpleLinkToDefaultState” function” in the main.c file.

A good representation of a code for such case is:

//Configurations - This section is done once sl_start(0,0,0); sl_WlanPolicySet(...); // configure the time interval between wakeups sl_socket(); sl_SetSocketOpt(); // configure UDP/TCP Secured or not sl_bind(); // Sending/Receiving Data - Done when packet need to be sent or received while (1) { sl_Send(); // can be UDP/TCP and/or secure connection sl_Recv(); // can be UDP/TCP and/or secure connection Delay(); }