SWRU558 June 2020 CC3100 , CC3100MOD , CC3200 , CC3200MOD
Following is a file system breakdown:
Table 3 describes all configuration files.
Filename | Description | Fail-Safe | #Blobks |
---|---|---|---|
/sys/macadd.bin | MAC address | true | 2 |
/sys/stacfg.ini | Station configuration | true | 2 |
/sys/ap.cfg | AP configuration | true | 2 |
/sys/p2p.cfg | Peer2Peer configuration | true | 2 |
/sys/mode.cfg | WLAN Mode | true | 2 |
/sys/pref.net | Preferred networks | true | 4 |
/sys/pmcfg.ini | Power Management | true | 2 |
/sys/ipcfg.ini | IP configuration | true | 2 |
/sys/devname.cfg | Device Name | true | 2 |
/sys/dhcpsrv.cfg | DHCP Server configuration | true | 2 |
/sys/httpsrv.cfg | HTTP Server configuration | true | 2 |
/sys/mdns.cfg | mDNS configuration | true | 2 |
/sys/smartconfigkeys.cfg | SmartConfig Keys | true | 2 |
TOTAL | 28 |
It is highly important to realize that not all system and configuration files are mandatory for a proper device operation. It is use case dependent. While it is easier to understand whether a configuration file is eventually used ot not, it is less obvious with system files. This is the reason why it is mandatory to keep the entire 22 blocks space for system files. Actually, this space is allocated as part of the Image creation procedure and cannot be altered by the user.