SWRA657 June   2020 CC3100 , CC3200

 

  1.   SimpleLink Wi-Fi CC3100, CC3200 Serial Flash
    1.     Trademarks
    2. 1  Introduction
    3. 2  How File System Content Gets to the Serial Flash
    4. 3  File System Guidelines
    5. 4  User File Mathematics
    6. 5  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. 6  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. 7  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. 8  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. 9  Recommended Best Practices
    11. 10 Implications of Data Integrity Compromise to CC3100/CC3200
      1. 10.1 Recovery
    12. 11 References

5.2.3 Minimum Flash Size

The minimum size of the serial flash is determined according to the memory space occupied by all system and configuration files.

As described earlier, you can either reserve the entire space or customize and reserve only the required space. In the latter case, extra caution should be taken since not preserving enough space may cause unexpected system behavior.

Table 7 marks the full memory consumption in case all system and configuration files are used.

Table 7. Flash Memory Consumption

CC3100 CC3200
File system artifacts (FAT, reserved blocks) 20KB 20KB
Service Pack 264KB 264KB
System and Configuration 200KB 200KB
MCU scheme with fail-safe (1) N/A 512KB
MCU scheme from OTA example (2) N/A 776KB
Total 484KB 996KB/1260KB
  1. 996KB is for MCU scheme with fail-safe option whereas 1260 KB is for MCU scheme from OTA example where all MCU images are created with no fail-safe. The decision mechanism is implemented in host.
  2. If the “Over The Air” example provided by TI is used as a reference, then the MCU application binaries need not be created as “fail safe”, as the primary and back-up images are stored as distinct files in the file system.

You have to select a flash large enough to fit the application code and required data files. Note that flash devices are available in the sizes, 8 Mbit, 16 Mbit, 32 Mbit, 64 Mbit and 128 Mbit.