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.

LAUNCHCC3220MODASF: CC3220MODASF: the shortest programming

Part Number: LAUNCHCC3220MODASF
Other Parts Discussed in Thread: UNIFLASH, CC3220SF, CC3220MOD, BEEPROG2

Hello,

Could you please advise how to get the fastest and reasonable way to program the flash?

Let me explain some:

- I would ask it to suggest a mass-production equipments to my customer.

- We would be glad if you could tell us whether TI have a PC tool for *JTAG* programming, if it is faster than UART. 

- My test report (I used the sample code "at_commands"):

  - Uniflash422: 61sec by stopwatch. 52sec from RST falling to the last TX.

  - uniflash_project_generator: 73sec by log output. 71sec from RST falling to the last TX.

  - I tried JTAG CCS740, but it was not successful.

    - Build not successful: at_commands_CC3220SF_LAUNCHXL_tirtos_ccs

    - Debug didn't start: at_commands_CC3220SF_LAUNCHXL_freertos_ccs

  - The UART baud rate was 1.08usec=925925baud.

  • Hi,

    Fastest way how to program sFlash in CC3220MOD is to use external flash programmer. For example programming by BeeProg2 programmer from Elnec can take approximately 25sec.

    Whole flash (4MB) memory MX25R3235FxxxL0 program+verify without erase at external programmer .... 22sec

    SerialFlash cannot be programmed by JTAG.

    Jan

  • Jan,
    Thank you very much for your quick reply!
  • Jan,
    Let me reconfirm.

    My target flash memory is not the sFlash(an ext. serial flash) but the XIP(embedded in the CC3220MODASF part).
    Is your reply the same?

    Or it would be glad if you mean BeeProg2 has a plan to support the CC3220MODASF.
  • Hi,

    I have no experience with programming XIP flash at CC3220SF by external flash programmer. I suppose that any kind of programmer which supports programming Cortex-M by JTAG/SWD can be used. But direct programming XIP flash by JTAG during product manufacturing is not a good idea. This way will be very impractical and your product will have significant security problems.

    JTAG/SWD is enabled only at development mode. Sell product witn CC3220SF in development mode is very bad idea from this reasons:
    - in development mode is enabled JTAG and this is a significant security risk (theoretically JTAG can be deactivated from your code, but security risk during boot still persist)
    - in development mode is possible list and read files from sFLash by Uniflash software (your secret from sFLash can be stolen)
    - you will need prepare separate image for each produced device, because in development mode is image bonded with device MAC (even if you will manage this during production, how do firmware updates in filed?)
    - you will still need program sFlash (at least upload image with development mode + ServicePack)

    More information you find at production line guide www.ti.com/.../swra568.pdf

    Jan

  • Jan,

    I would give-up JTAG. Now we think that UART is only the communication line for flash programming.

    By the way, can I ask you about the importance of the serial flash? Mandatory, recommended, or not necessary if the XIP is large enough?

    Our first candicate is CC3220MODASF as titled. Because we thought the part is good for users who preferes flash-inside uC.
    On the other hand your posts sounded to me that generally the part should have a serial flash (sFlash) even it has XIP flash internally.
  • Hi,

    UART with Embedded programming ( www.ti.com/.../EMBEDDED-PROGRAMMING ) is a reasonable way for a production programming. Serial flash is mandatory for all CC32xx and CC31xx devices including CC3220SF.

    Biggest advantage of CC3220MODASF module it that module is pre-certified and this allows decrease costs of final product certification. Module contains inside CC3220SF chip + 4MB serial flash + other components.

    Jan