SWRU558 June 2020 CC3100 , CC3100MOD , CC3200 , CC3200MOD
Session files are saved as *.usf files (UniFlash Session File) and includes information about the interface, device, and the session that you want to use. Configurations can be saved and opened in UniFlash to preserve and restore settings, and to maintain a different set of files for different devices.
Session consists of all relevant files for interaction with the target device along with other specific configurations such as target interface, COM port number, device type, and so forth. When a session is created, the following files can be found under the root session directory
Session files are saved as *.usf files (UniFlash Session File) and includes information about the interface, device, and the session that you want to use. Configurations can be saved and opened in UniFlash to preserve and restore settings, and to maintain a different set of files for different devices.
Note that upon saving a session, for example, as configname.usf, a directory named configname_session is created in the same folder. This should make it portable in that as long as the file and folder are sent together, the user should be able to open it in UniFlash.
An example of configuration file content is as follows:
#Tue Apr 28 09:14:08 IDT 2015
capacity=1MB
com=21
interface=CC31x Flash Connections
device=CC31x Flash Devices
secure=true
alert=true
CFG_GRP_ID|DHCP_Server=false
CFG_GRP_ID|Station=true
CFG_GRP_ID|mDNS_Client=false
CFG_GRP_ID|Device_Role=true
CFG_GRP_ID|Profiles=false
CFG_GRP_ID|AP=false
CFG_GRP_ID|Profile7=false
CFG_GRP_ID|Profile6=false
CFG_GRP_ID|Profile5=false
CFG_GRP_ID|Profile4=false
CFG_GRP_ID|Profile3=false
CFG_GRP_ID|mDNSClient5=false
CFG_GRP_ID|Profile2=false
CFG_GRP_ID|mDNSClient4=false
CFG_GRP_ID|Profile1=false
CFG_GRP_ID|mDNSClient3=false
CFG_GRP_ID|mDNSClient2=false
CFG_GRP_ID|mDNSClient1=false
CFG_GRP_ID|P2P=false
CFG_GRP_ID|HTTP_Server=false
CFG_GRP_ID|Smart_Config=false