• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 325 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.

CC3220SF: Using Cheetah SPI programmer

Connie Lu1
Intellectual 2130 points
Part Number: CC3220SF
Other Parts Discussed in Thread: UNIFLASH

Hi Experts,

My customer is using CC3220SF module,  they have been using simplelink dev board to load software to the module.

Now they want to use Cheetah SPI programmer to load hex file generated with uniflash to load software in manufacturing. 

The problem they have is that after SPI programmer loaded the software hex file successfully, the software is not starting after power cycle. 

They use SOP pins to roll back to backup image with a button, the setting of the SOP pins seem to be critical.

Are they missing something?

Thanks,

Connie

 

  • 0
    TI__Mastermind 38980 points

    Hi Connie,

    It sounds like your customer is using the UART pins to program the CC3220 device from UniFlash instead of generating a gang image and programming the SPI serial flash directly.

    Please see the CC3220 Production Line Guide for instructions on the SOP pin requirements for programming.

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    TI__Intellectual 2130 points

    Hi Sarah,

    Could you elaborate why you think my customer may be using UART instead of programming SPI correctly? 

    Here are their observations (note they are using CC3220SF Module):

    1. With some device, after SPI programming, power off the device, power up the device, no sign of starting in 30 seconds, then all the sudden the device started.
    2. With other device, after SPI programming, power off the device, power up the device, no sign of starting forever.

     

    Comments:

    Item1, there are starting up activities in the module, similar to backup image recovery process, or restore to manufacturing image, taking 30 seconds

    Item2, the internal boot process seemed to not find a way to boot the programmed software,

     

    Looks like they got SPI programming working successfully with right setup of SPI connection to device (after waiting for 30 seconds?).

    Are they missing some setup here in SPI programming or setup in uniflash while generating gang programming hex file?

    They programmed the same hex file with UART bins, no problem starting up, why not SPI?

     

    The whole thing seems related to root setup by programmer while programming if any.

     

    Thanks,

    Connie

  • 0 in reply to Connie Lu1
    TI__Mastermind 38980 points

    Hi Connie,

    Programming a gang image will take some time on first boot, since the device has to build its file system from the gang image. What behavior are you seeing when the device is not booting as expected?

    Can you verify what module pins they are using for SPI programming, plus SOP and reset pin positions? Please also have them verify their custom board with the MOD tab of the hardware design checklist: www.ti.com/.../swru462

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    TI__Intellectual 2130 points

    Hi Sarah,

    The checklist was able to resolve their problem. Thank you!

    Connie