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.

CC3135MOD: is embedded programming to CC3135MOD from third party MCU via SPI interface the same as via UART?

Part Number: CC3135MOD

Hi

I am now looking at SWPA231 CC313x Wi-Fi Embedded Programming app note which is using UART interface to program CC3135MOD Flash from third party MCU.

and I am using SPI interface between CC3135MOD and STM MCU, and trying to program/update CC3135MOD flash from MCU via SPI.

However, I could not find any related documents to use SPI interface to program CC3135MOD flash from host MCU

So, I wonder if the embedded programming from MCU via SPI interface is the same as via UART interface?

If not so, what other steps I need to take care of when using SPI interface?

Looking forward hearing the answer very soon

Thanks 

  • Hi Mark,

    Thanks for your question, I've assigned this to one of our SW experts.

  • The document you are referring is talking about the bootloader API.

    The CC31XX bootloader only supports UART. This mode is typically used during production.

    SPI interface is used by the operational firmware (UART can also be supported for the operational interface).

    To enter bootloader mode - see 5.3.1 in the "embedded programming" guide.

    When working through the SPI (i.e. with the NWP is running operational mode) - you can use "sl_FsProgram" command to format the entire flash and write the new "programming" image (see chapter 8.12 of the programmer's guide).

    The better way to update the service pack and or user files is through the standard file system API (FsOpen, FsWrite, FsClose) - see chapter 8.4. This methods adds a fail-safe protection. It is demonstrated in our over-the-air update demos, see https://www.ti.com/lit/pdf/swra510.