• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 41 subscribers
  • Views 392 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220S-LAUNCHXL: Adding new files with OTA Update

Andrew5821
Genius 4565 points

Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH

Can you add new files with the OTA update or is the file system pretty much static once the image is put into flash.  My understanding is that I can at least update a file as long as I manually make the file size larger in uniflash so there is room for the file to grow.  Is my assumption correct here?  I just wasn't sure if I could use the extra free space for a new file later on that I deliver using the OTA update.

Thanks

  • 0
    TI__Mastermind 35070 points
    Hi Andrew,

    I would not consider the file system as static. Using the filesystem API, you can edit existing files or create new ones (within the bounds of available memory). This should apply to files from the OTA update too.


    Regards,
    Toby
  • 0 in reply to Toby
    Genius 4565 points

    Hi Toby,

    So if my mcuimg.bin is 2k I don't need to make the file size 4k in uniflash to allow space for it to grow as I do OTA updates to it?  That seems to conflict with the statement below

    http://www.ti.com/lit/an/swra515a/swra515a.pdf

    2.2 File System Guidelines Most of file system guidelines can be found in CC3x20 SimpleLink Network Processor Programmer's Guide (see the Design Consideration section in the File System chapter). In addition to those guidelines, system designers should also consider the following: • The file system allocation table consumes five blocks (20KB). • The serial flash storage type that the CC3x20 device supports has a minimal block size of 4096 bytes. • Each file consumes at least: – One block (4KB) for a file with no fail-safe support – Two blocks (8KB) for a file with fail-safe support • File size cannot be enlarged after the file has been created. To increase the file content during the device life cycle, the maximum size attribute should be set when the file is created (the file system reserves space). • File attributes cannot be modified after the file has been created (apart from commit and rollback attributes). • The file system does not handle fragmentation.

  • 0 in reply to Andrew5821
    TI__Mastermind 35070 points
    Apologies, I assumed that you were talking about free space within serial flash (that has not been allocated for a file) after an OTA. So if you allocate 2MB for a file, but currently that file has 1MB of valid content, you cannot use the other 1MB for a new file.

    The documentation is right (cannot enlarge file size). So if you do anticipate that a file will need to hold increasingly more content, up to a max, please set the max size for that file (section 2.4.4 of same document).