SWRU558 June   2020 CC3100 , CC3100MOD , CC3200 , CC3200MOD

 

  1.   SimpleLink Wi-Fi CC3100, CC3200 UniFlash
    1.     Trademarks
    2. 1  Introduction
      1. 1.1 Overview
    3. 2  Installation
      1. 2.1 Linux
        1. 2.1.1 Limitations
        2. 2.1.2 During Installation
        3. 2.1.3 Running UniFlash
        4. 2.1.4 C++ Dependencies
        5. 2.1.5 COM Port
        6. 2.1.6 Porting Between Windows and Linux
    4. 3  Prerequisites
      1. 3.1 Software
      2. 3.2 Hardware
    5. 4  Uniflash Block Diagram
    6. 5  Session Support
      1. 5.1 Overview
      2. 5.2 Session Conversion
      3. 5.3 Creating a Session
        1. 5.3.1 Session Content
        2. 5.3.2 Creation Procedure
        3. 5.3.3 Relative Path Support
      4. 5.4 Saving a Session
      5. 5.5 Loading a Session
    7. 6  Secured File System Support
    8. 7  GUI Interface
      1. 7.1 Main Screen
      2. 7.2 Target Connection
      3. 7.3 Format
      4. 7.4 Get Version
      5. 7.5 File Programming
        1. 7.5.1 General
        2. 7.5.2 Non-Secured File Programming
        3. 7.5.3 Secured File Programming
      6. 7.6 Service Pack Programing
        1. 7.6.1 General
        2. 7.6.2 Procedure
      7. 7.7 Adding a New File to the Device
      8. 7.8 Erasing Existing File From the Device
      9. 7.9 Removing Existing File From the Template
    9. 8  CC3200 Support
      1. 8.1 Overview
      2. 8.2 Configuration and Programing
    10. 9  Command Line Support
      1. 9.1 Overview
      2. 9.2 Programming
        1. 9.2.1 Command Line Syntax
        2. 9.2.2 Help Manual
      3. 9.3 Available Options
        1. 9.3.1 Available Operations
        2. 9.3.2 Legend
        3. 9.3.3 Programming Example
    11. 10 Configuration File Support
      1. 10.1 Overview
      2. 10.2 Configuration Groups – Parameters’ Description
        1. 10.2.1 Device Role
        2. 10.2.2 Station
        3. 10.2.3 Access Point (AP)
        4. 10.2.4 Peer 2 Peer (P2P)
        5. 10.2.5 Profiles
        6. 10.2.6 HTTP Server
        7. 10.2.7 DHCP Server
        8. 10.2.8 mDNS Client
        9. 10.2.9 Smart Config
      3. 10.3 Configuration Groups – GUI Interface
        1. 10.3.1 Device Role
          1. 10.3.1.1 Restore to Default
          2. 10.3.1.2 Programming
          3. 10.3.1.3 Generation of Binary Templates
          4. 10.3.1.4 Configuration
        2. 10.3.2 Station
          1. 10.3.2.1 Restore to Default
          2. 10.3.2.2 Programming
          3. 10.3.2.3 Generation of Binary Templates
          4. 10.3.2.4 Flow
          5. 10.3.2.5 Configuration
        3. 10.3.3 Access Point (AP)
          1. 10.3.3.1 Restore to Default
          2. 10.3.3.2 Programming
          3. 10.3.3.3 Generation of Binary Templates
          4. 10.3.3.4 Flow
          5. 10.3.3.5 Configuration
        4. 10.3.4 Peer 2 Peer (P2P)
          1. 10.3.4.1 Restore to Default
          2. 10.3.4.2 Programming
          3. 10.3.4.3 Generation of Binary Templates
          4. 10.3.4.4 Flow
          5. 10.3.4.5 Configuration
        5. 10.3.5 HTTP Server
          1. 10.3.5.1 Restore to Default
          2. 10.3.5.2 Programming
          3. 10.3.5.3 Generation of Binary Templates
          4. 10.3.5.4 Flow
          5. 10.3.5.5 Configuration
        6. 10.3.6 DHCP Server
          1. 10.3.6.1 Restore to Default
          2. 10.3.6.2 Programming
          3. 10.3.6.3 Generation of Binary Templates
          4. 10.3.6.4 Flow
          5. 10.3.6.5 Configuration
        7. 10.3.7 mDNS Client
          1. 10.3.7.1 Restore to Default
          2. 10.3.7.2 Programming
          3. 10.3.7.3 Generation of Binary Templates
          4. 10.3.7.4 Adding/Deleting a Service
          5. 10.3.7.5 Flow
          6. 10.3.7.6 Configuration
        8. 10.3.8 Profiles
          1. 10.3.8.1 Restore to Default
          2. 10.3.8.2 Programming
          3. 10.3.8.3 Generation of Binary Templates
          4. 10.3.8.4 Adding/Deleting a Profile
          5. 10.3.8.5 Flow
          6. 10.3.8.6 Configuration
        9. 10.3.9 Smart Config
          1. 10.3.9.1 Restore to Default
          2. 10.3.9.2 Programming
          3. 10.3.9.3 Generation of Binary Templates
          4. 10.3.9.4 Flow
          5. 10.3.9.5 Configuration
    12. 11 Image Creation and Programming
      1. 11.1 Overview
      2. 11.2 Basic Concept and Operation
      3. 11.3 Image Creation – Supported Commands
        1. 11.3.1 Overview
        2. 11.3.2 General Settings
        3. 11.3.3 Format Storage Command
        4. 11.3.4 Write Service Pack Command
        5. 11.3.5 Write File Command
        6. 11.3.6 Write Gang Image Command
        7. 11.3.7 Start Logger Command
      4. 11.4 Image Creation – GUI Interface
        1. 11.4.1 Image Programming Summary Window
        2. 11.4.2 Image Programming Buttons
          1. 11.4.2.1 Add
          2. 11.4.2.2 Remove
          3. 11.4.2.3 Move
          4. 11.4.2.4 Program
          5. 11.4.2.5 Export
          6. 11.4.2.6 Settings
      5. 11.5 Image Programming to Target
      6. 11.6 How to Build an Image Guide
      7. 11.7 Serial Flash usage and Design
        1. 11.7.1 Overview
        2. 11.7.2 File System Guidelines
        3. 11.7.3 Memory Usage
          1. 11.7.3.1 Device Generic
          2. 11.7.3.2 Image Specific
      8. 11.8 Image Creation – Troubleshooting
    13. 12 Troubleshoot/Debugging
    14. 13 Limitations
    15. 14 References
  2.   A UART Connection
    1.     A.1 UART Connection

11.8 Image Creation – Troubleshooting

If you got to this section, it means something in the process went wrong. Before debugging Gang Programming, please make sure you turn on verbose mode for maximum debugging information. Pick Window → Preferences from the top toolbar. Under Uniflash Preferences, the Print out additional debug information for the supported modules should be checked for full debug messages.

The following checklist includes the main nodes in the process and expected results:

  • Image creation: upon a successful creation, a Finished successfully!!!! message should appear on the Console window with some additional debug messages
  • Image Programming
    • Using any off-the-shelf SPI programmer (mainly before assembly on the target boards): a successful programming is tool specific.
    • Using Uniflash (via UART lines): upon a successful programming, Uniflash should not print any error messages on the Console window.
  • Image extraction: upon resetting the board, an indication from the Host MCU for successful power-up should be generated.
  • Post extraction: after image extraction is completed, user application should be executed with no issues (as if files were programmed separately).

Possible issues at each node and respective solutions:

  • Image creation
    • same filename is used
      • You should see an exclamation mark indicating this error. Please avoid using the same filename more than once.
    • Total files exceed the size of the serial flash:
      • Try to use 0 as Max file size so the minimum size is allocated (original file size)
      • Make sure you do not add the Write Gang Image File command. It reduces the size of the image
      • Try to remove some unnecessary files is possible
    • Any other error:
      • Capture the error code on the Console window. The error code is the number following the ‘Exit code >’ prefix.
  • Image Programming:
    • Using any off-the-shelf SPI programmer:
      • Make sure all SPI lines are connected properly
      • Make sure either raw binary (*.bin) or IntelHex binary (*.hex) are used properly with the tool
      • Read back image and verify
    • Using Uniflash:
      • Make sure you use the raw binary (*.bin) and not the IntelHex binary (*.hex)
      • Uniflash should not print any error messages on the Console window. For any error, please open an E2E ticket.
  • Image extraction:
    • Serial flash is not formatted:
      • Make sure Format Storage command is added to the image
    • Any other error:
      • If Start Logger command is added, try to raw read the entire content using external tools and search for the first text line of the log: "Start Log" or 617274204C6F67 in hexadecimal. Open an E2E and attach the capture
      • For help, open an E2E ticket in all other cases.
  • Post extraction
    • Experiencing issues when invoking APIs that implicitly creates files on the serial flash. These APIs creates configuration files.
    • It is possible that the free space left on the serial flash after extraction is not enough. Please try to free some space on the original image and retry
    • For help, open an E2E ticket in all other cases.