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

Description

Table 3 describes in details the meaning of each system or configuration file.

Table 3. System File Description

Artifact Description
FAT File allocation table. Created upon format operation, either from Uniflash or via Image Programming. FAT is device unique so serial flash devices cannot be cloned and used on another SimpleLink device
Reserved blocks Reserved blocks for future use
/sys/servicepack.ucf Holds firmware patches to all internal cores, Network processor, MAC layer and PHY layer.
/tmp/phy.cal Calibration file created automatically by the device. Calibration is performed sparingly, typically when coming out of Hibernate and only if temperature has changed by more than 20°C or upon power cycle
/tmp/fcon.frm Fast connect frame. Holds all beacon information of the last connected access point. Created upon successful connection to an access point
/tmp/fcon.ssid Fast connect profile. Holds selected profile information of the last connected access point, as if a profile is added by the application through API. Created upon successful connection to an access point.
/tmp/table.arp ARP table file. This file holds up to 8 entries. The table is updated upon ARP response reception to the device IP address
/sys/date_time.cfg Holds the system time and date. Mainly used with to validate expiry time of certificates during SSL connections
/sys/rxfltr.ini Holds all RX filtering information. The Rx-filters module enables you to simply define a set of rules that determine which of the received frames are transferred by the SimpleLink device to the host, and which frames are dropped. The Rx-filters can be activated during AP-connection and during promiscuous mode
/sys/infoele.cfg Holds user defined information element. The information element is transmitted when the device is either in AP mode or Peer2Peer group owner mode. The size is limited to 252 bytes
/sys/macadd.bin Holds the user defined MAC address of the device. If this file exists, the device internal MAC address is bypassed
/sys/stacfg.ini Holds device configuration when it is either in station mode or Peer2Peer client mode. The list of APIs related to stacfg.ini can be found under Host Driver mapping
/sys/ap.cfg Holds device configuration when in access point mode. The list of APIs related to ap.cfg can be found under Host Driver mapping
/sys/p2p.cfg Holds device configuration when Peer2Peer mode (client or group owner). The list of APIs related to p2p.cfg can be found under Host Driver mapping
/sys/mode.cfg Holds device general configuration, unbound to device mode. The list of APIs related to mode.cfg can be found under Host Driver mapping
/sys/pref.net Holds up to 7 stored profiles. Profiles may be stored explicitly from user application or implicitly during Smart Config provisioning. SimpleLink device scan the stored profile list only if connection policy is set to Auto mode
/sys/pmcfg.ini Holds the power policy configuration of the device. The list of APIs related to pmcfg.ini can be found under Host Driver mapping
/sys/ipcfg.ini Hold IP configuration of the device. The list of APIs related to ipcfg.ini can be found under Host Driver mapping
/sys/devname.cfg Holds the device name and URN. The list of APIs related to devname.cfg can be found under Host Driver mapping
/sys/dhcpsrv.cfg Holds DHCP server information. The list of APIs related to dhcpsrv.cfg can be found under Host Driver mapping
/sys/httpsrv.cfg Holds HTTP server information. The list of APIs related to httpsrv.cfg can be found under Host Driver mapping
/sys/mdns.cfg Holds mDNS client information. The list of APIs related to mdns.cfg can be found under Host Driver mapping
/sys/smartconfigkeys.cfg Holds Smart Config keys in case the provisioning procedure is secured (access point credentials are encrypted during provisioning).