TIDUE59A May   2018  – September 2020

 

  1.   Description
  2.   Resources
  3.   Features
  4.   Applications
  5. 1System Description
    1. 1.1 Key System Specifications
  6. 2System Overview
    1. 2.1 Block Diagram
    2. 2.2 Design Considerations
    3. 2.3 Highlighted Products
      1. 2.3.1 CC3220
      2. 2.3.2 CC2640R2F
      3. 2.3.3 DRV8837
    4. 2.4 System Design Theory
      1. 2.4.1 CC3220S to CC2640R2F Interface
      2. 2.4.2 CC3220S to DRV8837 Interface
      3. 2.4.3 Software Architecture
      4. 2.4.4 Network Connection Management
      5. 2.4.5 Provisioning
        1. 2.4.5.1 AP Provisioning and SmartConfig™
        2. 2.4.5.2 Wi-Fi Provisioning Over BLE
      6. 2.4.6 Sending and Receiving Messages Through Cloud
        1. 2.4.6.1 Message Queue Telemetry Transport Protocol
        2. 2.4.6.2 MQTT Client Implementation
      7. 2.4.7 Over-the-Air Updates
        1. 2.4.7.1 HyperText Transfer Protocol
      8. 2.4.8 Security Enablers
        1. 2.4.8.1 Secure Boot
        2. 2.4.8.2 Secure Sockets
          1. 2.4.8.2.1 Hardware Accelerators
          2. 2.4.8.2.2 Simple Network Time Protocol
        3. 2.4.8.3 File System Security
          1. 2.4.8.3.1 Failsafe Files and Bundle Protection
      9. 2.4.9 Low-Power Consumption
  7. 3Hardware, Software, Testing Requirements, and Test Results
    1. 3.1 Required Hardware and Software
      1. 3.1.1 Hardware
        1. 3.1.1.1 CC3220S LaunchPad™ Development Kit
        2. 3.1.1.2 CC2640R2F LaunchPad™ Development Kit
        3. 3.1.1.3 Sensor BoosterPack™ Connections (BMI160)
        4. 3.1.1.4 DRV8837EVM Modifications and Connections
        5. 3.1.1.5 Assembling EVMs
      2. 3.1.2 Software
        1. 3.1.2.1 Getting Started With Software
          1. 3.1.2.1.1 Build simple_np Application and Flash CC2640R2F
          2. 3.1.2.1.2 Use Premade UniFlash ImageCreator Project
          3. 3.1.2.1.3 Importing Project Source Files Into CCS
        2. 3.1.2.2 User Files
        3. 3.1.2.3 Run Wi-Fi® Doorlock Demo
          1. 3.1.2.3.1 Connect CC3220 to Network
          2. 3.1.2.3.2 Networking Functions
            1. 3.1.2.3.2.1 Get Current Date and Time (SNTP)
            2. 3.1.2.3.2.2 Send and Receive Messages (MQTT)
            3. 3.1.2.3.2.3 Perform Software Update Using Dropbox (OTA Update)
    2. 3.2 Testing and Results
      1. 3.2.1 Pass or Fail Tests
      2. 3.2.2 Power Measurements
      3. 3.2.3 Test Setup
        1. 3.2.3.1 CC3220S
        2. 3.2.3.2 CC2640R2F
        3. 3.2.3.3 DRV8837
      4. 3.2.4 Test Results
      5. 3.2.5 Battery Life Estimate
  8. 4Design Files
  9. 5Software Files
  10. 6Related Documentation
    1. 6.1 Trademarks
  11. 7Terminology
  12. 8About the Author
  13. 9Revision History

3.2.3.1 CC3220S

While measuring the power consumption of the CC3220S, the CC3220S and CC2640R2F LaunchPads were not stacked, to allow the devices to be powered separately. Instead, only the signals required for the NPI were connected between the boards using jumper wires. Resistor R141 on the CC3220S LaunchPad must also be removed. R141 is used to form a pull down on the input used by one of the CC3220S LaunchPad switches (SW2 on Rev. A). The resistor must be removed when measuring the power consumption on both the CC3220S and CC2640R2F LaunchPads, because the pin used by the switch is P4, which is used by the NPI and may increase power consumption while the NPI is idle (see Figure 3-12).

GUID-9A21D174-7F50-41C1-B6E7-2A73FB212F34-low.gifFigure 3-12 R141 Location on CC3220S LaunchPad™

While powering the CC3220S LaunchPad from the DC power analyzer, the LaunchPad was configured according to the Battery Powering Only the CC3220 and U8 (Onboard Serial Flash) section of the CC3220 SimpleLink™ Wi-Fi® LaunchPad™ Development Kit Hardware User's Guide, and run standalone (flashed instead of the debugger), to let the power management policy for the MCU host stay enabled.

The power analyzer was configured with an output of 3.3-V DC while powering the CC3220S LaunchPad. A Netgear AT&T hotspot was used as the AP during the tests, with no other stations connected. Three different modes of operation that occur during normal application operation were measured, as follows:

  • TIDC-01005 idle connected to AP (not including AP keep alive messages)
  • TIDC-01005 receiving lock status request and sending lock state to cloud
  • TIDC-01005 receiving lock/unlock command from cloud and running a PWM output to control the motor driver

Note:

When using the LaunchPad configuration from the Battery Powering Only the CC3220 and U8 (Onboard Serial Flash) section of the CC3220 SimpleLink™ Wi-Fi® LaunchPad™ Development Kit Hardware User's Guide, the back-channel UART is disconnected and debug prints are not available.