SWRU473A February   2017  – August 2018 CC3120MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF

 

  1.   SimpleLinkrep%#8482; Wi-Fi® CC3220 Out-of-Box Application
    1.     Trademarks
    2. 1 Introduction
    3. 2 Download and Installation
    4. 3 Installation for Basic Users
      1. 3.1 UniFlash
      2. 3.2 SimpleLink™ Wi-Fi® Starter Pro Mobile Application
      3. 3.3 Serial Terminal
      4. 3.4 XDS110 Driver Installation
    5. 4 Building the Setup
    6. 5 Flashing the Out-of-Box Project
    7. 6 Getting Started With the OOB Demonstration
      1. 6.1 Connecting to the CC3220
        1. 6.1.1 CC3220 Provisioning
        2. 6.1.2 CC3220 as AP
      2. 6.2 Browse Onboard Website
        1. 6.2.1 Local Network Demo
        2. 6.2.2 OTA Update
        3. 6.2.3 Advanced Settings
      3. 6.3 Using the Mobile Application
        1. 6.3.1 Connect to the CC3220
        2. 6.3.2 Local Network Demo
        3. 6.3.3 OTA Update
          1. 6.3.3.1 Local OTA When CC3220 is in AP Mode
      4. 6.4 Returning to Factory Image
    8. 7 Troubleshooting
      1. 7.1 Red LED Legend
      2. 7.2 Extra Debugging
      3. 7.3 Terminal Messages
    9. 8 Limitations and Known Issues
    10. 9 Out-of-Box for Advance Users
      1. 9.1 Installations for Advance Users
        1. 9.1.1 CC3220 Software Development Kit (SDK)
        2. 9.1.2 Service Pack
        3. 9.1.3 CCS IDE
          1. 9.1.3.1 Add CCS Support for FreeRTOSv9
          2. 9.1.3.2 Product Settings Verification
      2. 9.2 Source Files Briefly Explained
      3. 9.3 Building the OOB Project Using CCS
        1. 9.3.1 Executing in Debug Mode
        2. 9.3.2 Program a User Modified OOB Binary
  2.   Revision History

Program a User Modified OOB Binary

When working in debug mode, the application binary is not programmed to the serial flash and is volatile. The compiled binary can be added to the project and create an image that is programmable to the device; this way, the application binary is programmed to the serial flash and becomes non-volatile.

For secured devices, users must add their own certificate chain (the TI private key which pairs the certificate cannot be shared). Nevertheless, to simplify the procedure TI also provides the option to use a self-signed certificate store (playground).

To have all out-of-box content such as the service pack, web pages, and other system and configuration files, a UniFlash project is required so the image can be programmed into the device. The UniFlash projects are available under the following locations according to the connected CC3220 flavor.

  • For CC3220S secured device:
  • <SDK install dir>\examples\rtos\CC3220S_LAUNCHXL\demos\out_of_box\uniflash\OOB_RS_tirtos.zip

    <SDK install dir>\examples\rtos\CC3220S_LAUNCHXL\demos\out_of_box\uniflash\OOB_RS_freertos.zip

  • For CC3220SF secured device:
  • <SDK install dir>\examples\rtos\CC3220SF_LAUNCHXL\demos\out_of_box\uniflash\OOB_SF_tirtos.zip

    <SDK install dir>\examples\rtos\CC3220SF_LAUNCHXL\demos\out_of_box\uniflash\OOB_SF_freertos.zip

Follow these instructions to program the image into the device (the first four steps are identical to ‎Section 9.3.1, but are listed again here for completeness).

  1. Open the UniFlash utility to create and program the OOB image.
  2. Choose the CC3120/CC3220 device and then click the Start Image Creator button (see ).
  3. Click the Manage Projects button and then click Import project from ZIP file button. Locate the OOB project according to the connected CC3220 device. Projects already imported should appear on the list of available projects.
    • For CC3220S secured device:
    • <SDK install dir>\examples\rtos\CC3220S_LAUNCHXL\demos\out_of_box\uniflash\OOB_RS_tirtos.zip

      <SDK install dir>\examples\rtos\CC3220S_LAUNCHXL\demos\out_of_box\uniflash\OOB_RS_freertos.zip

    • For CC3220SF secured device:
    • <SDK install dir>\examples\rtos\CC3220SF_LAUNCHXL\demos\out_of_box\uniflash\OOB_SF_tirtos.zip

      <SDK install dir>\examples\rtos\CC3220SF_LAUNCHXL\demos\out_of_box\uniflash\OOB_SF_freertos.zip

  4. Browse to see all files under Files → User Files on the left side tree. As shown in Figure 42, a dummy-root-ca-cert certificate is used in case an MCU image is added to the project.
  5. root_certificate_Uniflash_project.pngFigure 42. Root Certificate in UniFlash Project
  6. Create the MCU image for the project by making code modifications and recompiling.
  7. Add the created application binary to the Image Creator project (see Figure 43):
    1. Browse to Files → User Files on the left side tree. The dummy-root-ca-cert certificate must be used if an MCU image is added to the project.
    2. Choose Select MCU Image from the Action drop-down menu and click the Browse button.
    3. Locate the compiled binary from Step 5 and select it.
    4. Because the MCU image is secured, the certificate and signature must be configured.
      1. To choose the certificate, choose dummy-root-ca-cert under the Certification File Name drop-down menu.
      2. To create a signature, leave the default Private Key File Name from the drop-down, click the browse button, and choose the dummy-root-ca-cert-key key which matches dummy-root-ca-cert-key and click the Write button. UniFlash automatically creates the signature. The key file is located on the SDK under <SDK install dir>\tools\certificate-playground
  8. NOTE

    For secured flash devices (CC3220SF), the default MCU image size is automatically set to 524288 bytes. This size is too large for the image (there are many other files as well). Set it to 262144 bytes.

    Uniflash_add_secured_MCU_image.pngFigure 43. UniFlash Add Secured MCU Image
  9. Browse to General → Settings on the left side tree and configure the image mode to either Production or Development, either works (choosing Development enables debugging).
  10. Ensure the CC3220 LaunchPad is connected and click the Connect button. Users can see the device information of the connected device with their device MAC address.
  11. Save the project and click on the Generate Image icon on the right.
  12. Finally, click on the Program Image (Create & Program) button. The image is now programmed to the device.

Upon successful programming, the application starts running.