SWRA657 June   2020 CC3100 , CC3200

 

  1.   SimpleLink Wi-Fi CC3100, CC3200 Serial Flash
    1.     Trademarks
    2. Introduction
    3. How File System Content Gets to the Serial Flash
    4. File System Guidelines
    5. User File Mathematics
    6. System and Configuration Files
      1. 5.1 Description
      2. 5.2 Memory Consumption
        1. 5.2.1 CC3200 Use Case
        2. 5.2.2 Host Driver Mapping
        3. 5.2.3 Minimum Flash Size
    7. Implementing File System Features From Host Processor
      1. 6.1 Overview
      2. 6.2 File Listing
        1. 6.2.1 Requirements
        2. 6.2.2 Procedure
      3. 6.3 Free/Occupied Space
        1. 6.3.1 Requirements
        2. 6.3.2 Procedure
      4. 6.4 File Appending
        1. 6.4.1 Requirements
        2. 6.4.2 Procedure
    8. Factors to Consider in Designing With Serial Flash
      1. 7.1 Serial Flash Vendor and Part Number Selection
      2. 7.2 Supported Flash Types
      3. 7.3 Frequent Write Operations
        1. 7.3.1 Serial Flash Access by the Wi-Fi System"
        2. 7.3.2 Seral Flash Access by the WiFi System
          1. 7.3.2.1 System Files
          2. 7.3.2.2 User Files
      4. 7.4 Sudden Power Off (power removal during a write/erase phase)
        1. 7.4.1 Battery Powered Systems
        2. 7.4.2 Line Powered Systems
    9. Design Recommendations for Ensuring the Integrity of the Power Supply to the Serial Flash
      1. 8.1 Overview
      2. 8.2 Key Points
      3. 8.3 Brown-Out Mitigation Techniques for New Self-Hosted CC3200 Designs
    10. Recommended Best Practices
    11. 10 Implications of Data Integrity Compromise to CC3100/CC3200
      1. 10.1 Recovery
    12. 11 References

CC3200 Use Case

CC3200 is a special case since its image (application code running on the internal processor) should be taken into account as well. The occupied space depends on the over-the-air (OTA) scheme. Table 5 illustrates two OTA schemes: MCU image with fail-safe option and OTA as taken from the OTA SDK add-on.

Table 5. CC3200-Specific System File Memory Consumption

Filename/Artifact Description Fail Safe No blocks
/sys/mcuimg.bin MCU application image running on the internal Cortex M4 host processor yes 128
Total 128
MCU boot info Boot information for image selection no 1
/sys/mcuimg.bin (MCU application bootloader) MCU application for image selection no 1
MCU image 1 1st image – the default image no 64
MCU image 2 2nd image no 64
MCU image 3 3rd image no 64
Total 194