Other Parts Discussed in Thread: CC3120, CC3235SF, CC3235S, CC3135, UNIFLASH, CC3120BOOST
I am trying to get some clarity of several things about the CC3120.
Regarding swru455, section 4.3, it shows countries US, EU, JP, then says "The CC3135, CC3235S, and CC3235SF support a wider set... The full list of supported countries could be found in Appendix C" Is that list for the CC3120? Or only for CC3135/CC3235 (meaning the CC3120 only supports 3 country codes)?
When a new CC3120 is installed with a new empty FLASH memory, what happens? Clearly the file system cannot be "rolled back", per section 3.2.6 of swra509b since the flash is empty.
For example... when we are putting in perhaps 10,000 NWPs as an option in a production of 50,000 devices, and this is being done on the other side of the planet, how will the NWP RAM get initially programmed? According to doc swra509, section 3.2 the cloning protection would prevent a block of flash RAMs from all being programmed if the file system is encrypted and tied to a key that is unique to each device.
Do we tell the manufacturer to Install each on a EMUBOOST board? (not likely) Or we have to embed the UCF into our firmware to instruct it to load the NWP if it's empty? How would the host know the NWP has a blank RAM?
On the file system:
Per swra509 section 3.2.3 and forward, the "secure-and-authenticate" flag is the signature? So the file must be signed by something that can chain up the CA list. If a file is attempted to be stored SL_FS_CREATE_SECURE, and without SL_FS_CREATE_NOSIGNATURE, then which is the root CA that it must be signed with?
And does table 10 in section 3.2.9 of swra509b "Secure-and-Authenticate file" mean a file which is "signed"?
These are a start to determining the effort of adding this NWP as an option to a product.