SWRA657
June 2020
CC3100
,
CC3200
SimpleLink Wi-Fi CC3100, CC3200 Serial Flash
Trademarks
1
Introduction
2
How File System Content Gets to the Serial Flash
3
File System Guidelines
4
User File Mathematics
5
System and Configuration Files
5.1
Description
5.2
Memory Consumption
5.2.1
CC3200 Use Case
5.2.2
Host Driver Mapping
5.2.3
Minimum Flash Size
6
Implementing File System Features From Host Processor
6.1
Overview
6.2
File Listing
6.2.1
Requirements
6.2.2
Procedure
6.3
Free/Occupied Space
6.3.1
Requirements
6.3.2
Procedure
6.4
File Appending
6.4.1
Requirements
6.4.2
Procedure
7
Factors to Consider in Designing With Serial Flash
7.1
Serial Flash Vendor and Part Number Selection
7.2
Supported Flash Types
7.3
Frequent Write Operations
7.3.1
Serial Flash Access by the Wi-Fi System"
7.3.2
Seral Flash Access by the WiFi System
7.3.2.1
System Files
7.3.2.2
User Files
7.4
Sudden Power Off (power removal during a write/erase phase)
7.4.1
Battery Powered Systems
7.4.2
Line Powered Systems
8
Design Recommendations for Ensuring the Integrity of the Power Supply to the Serial Flash
8.1
Overview
8.2
Key Points
8.3
Brown-Out Mitigation Techniques for New Self-Hosted CC3200 Designs
9
Recommended Best Practices
10
Implications of Data Integrity Compromise to CC3100/CC3200
10.1
Recovery
11
References
6.2.1
Requirements
Keep and maintain a list of all user filenames created from host
Full list of all system and configuration filenames is required. For more information, see
Section 5
.
If allocated, size per file is also required:
Keep and maintain for each user file its allocated size (either the size of the content or the maximum size argument)
Full list of all system and configuration file sizes is required. For more information, see
Section 5
.
Knowledge of how to accurately calculate the occupied memory space per file. For more information, see
Section 4
.