• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 41 subscribers
  • Views 353 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.

Original question:

CC3220SF-LAUNCHXL: Servicepack Upgrade through Host Driver API

CC3220SF-LAUNCHXL: How to add signatures for service pack upgrade through Host Driver APIs

Vaishnavi Kumbargeri
Prodigy 70 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF, UNIFLASH

Hi Support,

I'm working on upgrading the service pack (alone, not a bundle upgrade) of the network processor in CC3220SF, through the host processor. I have gone through the below links,

SimpleLinkTm Wi-Fi® CC3x20, CC3x3x Network Processor (Rev. M) (ti.com)

BOOSTXL-CC3135: Firmware Update - Wi-Fi forum - Wi-Fi - TI E2E support forums

I have following doubts:

  1. I'm using the .ucf file provided in the SDK library <simplelink_cc32xx_sdk>\tools\cc32xx_tools\servicepack-cc3x20 for upgrade. While closing the service pack file, what should be used for the certificate file and signatures? In SimpleLinkTm Wi-Fi® CC3x20, CC3x3x Network Processor (Rev. M) (ti.com) it is mentioned that The service pack is a special file which already contains the signature. When writing the service pack by the host, the sl_FsClose() function should receive a NULL certificate name and a NULL signature. But the above discussion contradicts this. Please provide clarity on what signatures should be used while closing the service pack file.
  2. I understand that service pack upgrade can be done by using sl_FsWrite and sl_FsProgram. From the above discussion it is said that sl_FsProgram will be writing entire image. Does this mean that that the entire files system is reprogrammed by sl_FsProgram? Is this used in bundle upgrade?

Thanks for your patience,

Vaishnavi

  • +1
    Guru 79905 points

    Hi Vaishnavi,

    Answers to your questions:

    1. Signature you will find at directory next to ServicePack in SDK (e.g. sp_3.22.0.1_2.7.0.0_2.2.0.7.ucf.signed.bin) and for programming you will use sp_3.22.0.1_2.7.0.0_2.2.0.7.ucf file.

    2. API sl_FsProgram() is used for programming whole image including your firmware binary. That mean when will programming via sl_FsProgram() will failed, you will have bricked device and you will need to connect Uniflash via UART directly. It means you should NOT use sl_FsProgram() for any kind of remote update.

    Jan

  • 0 in reply to Jan D
    Prodigy 70 points

    Hi Jan,

    Thanks for your quick reply,

    1. That means the .ucf.signed.bin file should be read into a buffer and passed to the sl_FsClose() method and certificate path should be passed as NULL, is my understanding correct?

    Thanks a lot,

    Vaishnavi

  • 0 in reply to Vaishnavi Kumbargeri
    Guru 79905 points

    Hi Vaishnavi,

    Yes, that this correct.

    Jan