I have a few questions regarding the EERPOM structure described in this table from the wiki:
| File ID (numerical) | File ID | File address(offset) | File Size (bytes) | Real Used Size (bytes) | Parameter |
|---|---|---|---|---|---|
| 0 | NVMEM_NVS_FILEID | 0x50 | 0x1A0 | 0x1A | RF Calibration results table(generated automatically by TX Bip) |
| 1 | NVMEM_NVS_SHADOW_FILEID | 0x1F0 | 0x1A0 | 0x1A | |
| 2 | NVMEM_WLAN_CONFIG_FILEID | 0x390 | 0x1000 | 0x64 | WLAN configuration |
| 3 | NVMEM_WLAN_CONFIG_SHADOW_FILEID | 0x1390 | 0x1000 | 0x64 | |
| 4 | NVMEM_WLAN_DRIVER_SP_FILEID | 0x2390 | 0x2000 | variable | WLAN Driver ROM Patches |
| 5 | NVMEM_WLAN_FW_SP_FILEID | 0x4390 | 0x2000 | variable | WLAN FW Patches |
| 6 | NVMEM_MAC_FILEID | 0x6390 | 0x10 | 0x10 | 6 bytes of MAC address |
| 7 | NVMEM_FRONTEND_VARS_FILEID | 0x63A0 | 0x10 | 0x10 | |
| 8 | NVMEM_IP_CONFIG_FILEID | 0x63B0 | 0x40 | 0x40 | IP configuration |
| 9 | NVMEM_IP_CONFIG_SHADOW_FILEID | 0x63F0 | 0x40 | 0x40 | |
| 10 | NVMEM_BOOTLOADER_SP_FILEID | 0x6430 | 0x400 | variable | Bootloader Patches |
| 11 | NVMEM_RM_FILEID | 0x6830 | 0x200 | 0x7F | Radio parameters |
| 12 | NVMEM_AES128_KEY_FILEID | 0x6A30 | 0x10 | 0x10 | AES128 key file |
| 13 | NVMEM_SHARED_MEM_FILEID | 0x6A40 | 0x50 | 0x44 | Host-CC3000 shared memory file |
| 14 | NVMEM_USER_FILE_1_FILEID | 0x6A90 | variable | variable | 1st user file |
| 15 | NVMEM_USER_FILE_2_FILEID | variable | variable | variable | 2nd user file |
- Is the EEPROM written to (or updated) when the CC3000 is restarted by calling wlan_stop() and then wlan_start(0)?
- How often is the NVMEM_NVS_FILEID updated?
- What is the purpose of all SHADOW files?
- What is the difference between the "File Size" and the "Real Used Size"?
Thanks!
