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.

CC3230SF: Confirmation with CC3230SF

Part Number: CC3230SF

Hi Team,

I would like to get your help confirming the following questions of the customer for CC3230SF below:

1. Tell whether the CC3230SF wireless lan chip comes with a precompiled binary firmware update file that can be flashed by the customer?

2.  If you can install a firmware to the wireless chip any other way than through the air updates e.g. through UART.

3. Can you check if the AT commands can be send via SPI, too or only through UART?

Please let me know if you have any questions with the customer.



  • Hi Jonathan,

    I am not a TI team member but I will answer your questions.

    1. CC3230SF chip contains two parts. Application processor Cortex-M4 which is intended to execute end-user code, and network processor (called NWP). NWP runs TI proprietary firmware which is stored on ROM. NWP firmware is not end-user modifiable. Regardless we talk about QFN package or module, CC32xx devices are shipped blank without any binary inside application processor.

    2. Production programming of CC323x devices is done via uploading content of SPI flash chip (called sFlash). This can be done via UART bootlaoder of via 3rd party SPI flash programmer. All CC32xx chips requires for own function external SPI flash chip. In case of CC32xx modules, SPI flash chip is inside module.

    3. Interface between application processor with end-user application and NWP is done via SimpleLink driver which translates sl_ API calls to internal SPI communication between application processor and NWP. This internal communication is not based on AT commands.

    If end-user want to control CC3220/CC3235/CC3230 via AT commands from external MCU. It can upload AT command application into application processor. This application is a part of CC32xx SDK (with source code). If it is required, end-user can rewrite this example code to use SPI instead UART. I expect that this can be relatively easy done.


  • Hi Jonathan,

    Jan's answers are accurate.

    For question 2, another resource that is useful is the production line guide:

    For question 3, the AT commands library only supports UART out of the box, but adding SPI support should be simple for the customer to do.

    Let us know if the customer has further questions on the CC3230.



  • Hi Michael and Jan,

    The customer accepts the information you shared and I am grateful for these answers.