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

Terminal Messages

The terminal can also be used for debug messages. The default configuration is 115200 bps, 8 bits, no parity, and 1 stop bit. Most of the debug messages are self-explained. For better tracking, each message is preceded by the task and module generating the message enclosed in brackets.

Table 3 lists some common messages to help users track the application status.

Table 3. Terminal Messages

Message What Does it Mean?
[Provisioning task] Provisioning Started. Waiting to be provisioned..!! The CC3220 is in provisioning mode. The user must use the SimpleLink Wi-Fi Starter Pro application to provision the device.
[ProvisioningEvent] Connection to AP succeeded During provisioning, the CC3220 managed to decode the AP credentials and connect to it successfully.
[ProvisioningEvent] Confirmation Success! During provisioning, the CC3220 supplied feedback to the SimpleLink Wi-Fi Starter Pro application.
[Provisioning task] Provisioning completed successfully..! Provisioning completed successfully.
[ProvisioningEvent] Provisioning stopped Provisioning is stopped, which may indicate the following:
  • Successful provisioning
  • Inactivity time-out elapsed
  • General error
[Provisioning task] committing new OTA download... Upon end of OTA procedure, indicates a new software package is being committed.
[Provisioning task] commit succeeded New OTA software package committed successfully.
[Provisioning task] Rollback error sl_FsCtl New OTA software package failed its validation testing (connect to AP while in Station mode or initialize while in AP mode), reverting to previous software package.
[Provisioning task] failed to commit new download, reverting to previous copy by resetting the device New OTA software package failed to commit, reverting to previous software package.
Return To Factory Image successful. Do a power cycle (POR) of the device using switch SW1-Reset After a return-to-factory is triggered and the device is up, a manual reset is required from the user to complete the operation.
Connection Success (feedback to Smartphone app failed) During provisioning, the CC3220 connected to the AP successfully, but failed to supply feedback to the SimpleLink Wi-Fi Starter Pro application.
[Link local task] HTTP GET Request Indicates client HTTP GET request. For details see Table 4.
[Link local task] characteristic is: During HTTP request, indicates the relevant resource.
[Link local task] HTTP POST Request Indicates client HTTP POST request. For details see Table 4.
[Link local task] value is: During HTTP request, indicates the value of the resource.
[Link local task] HTTP PUT Request Indicates client HTTP PUT request. For details see Table 4.
[Link local task] Received OTA filename Archive filename received during the OTA update. Filename and file size follows.
[Link local task] OTA filename is in *.tar format Archive filename received during the OTA update is not in tar format.
[Link local task] OTA bundle version file does not exist OTA version file does not exist on the file system. This is informative, not an error.
[OtaArchive_CheckVersion] accept the new version OTA version file does not exist on the file system. New version is accepted. Version number follows.
[OtaArchive_CheckVersion] newer version update New OTA version is newer than the stored version.
[OtaArchive_CheckVersion] older version update New OTA version is older than the stored version.
[OtaArchive_RunParseTar] Create/Open for write file File is updated on file system during the OTA update. Filename follows.
[OtaArchive_RunParseTar] Downloading File Completed File has been downloaded and updated on file system successfully during the OTA update.
[OTA report task] OTA progress The status of the progress bar displays in percentages during the OTA update.
[Link local task] sl_extLib_OtaRun: — Download file completed OTA procedure completed successfully.
[Link local task] sl_NetAppRecv error Error in communication with the client during the OTA update. Error code follows.
[Link local task] OtaArchive error Error in the archive module during the OTA update. Error code follows. For details refer to the OtaArchive.h header file.
[Control task] switching to AP mode The CC3220 is switching to AP mode.
[Control task] device not started in AP role Configuring the CC3220 as AP failed.
[Control task] device started in AP role, rebooting device... Switching to AP mode succeeded, rebooting application.
[Control task] device cannot start in AP mode, please reset the board Switching to AP mode failed. Manual reset is required.
[ERROR] - FATAL ERROR Fatal error occurred. Manual reset is required.