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.

CC3200: CC3200

Guru 13485 points
Part Number: CC3200
Other Parts Discussed in Thread: UNIFLASH

Hi

Got below question:

In our CC3200 app, we have an upgrade SW procedure via WiFi we implemented.

 

In the last batch of PCBs including this chip, this procedure has stopped working.

The procedure includes file-system operations on the SFLash, manipulating the *.bin file.

It seems something in the file-system operations is failing, as the SW fails to load after executing this upgrade procedure. Saying this, we do not get any error returned from any of the TI FS APIs

 

I thought it might be related to the service-pack installed on the chip, and tried different versions, but still it fails.

We can only recover using UniFlash to burn the wafer with USB.

 

Any idea what changed?

 

  • We use sl_Fs* APIs, which are removed in the latest programmer’s-guide. What does it mean? Was it removed? Is it not working anymore?
  • Hi,

    I haven't any information about removal support for sl_ file system API at CC3200. There are no changes in this area in CC3200 SDK 1.3.0. Actually I use fs API without any problem. Can you give me number of document?

    - Do you have mcuimg.bin set as fail safe file?
    - Can you list files in Unfilash? Do you see anything suspicious?
    - Do you use same type sFlash chip?
    - Can you closely investigate issue at debugger? I really think that there need to be some error from sl_ filesystem API.
    - Can you upload simple code by JTAG and read mcuimg.bin file?

    Jan
  • I haven't any information about removal support for sl_ file system API at CC3200. There are no changes in this area in CC3200 SDK 1.3.0. Actually I use fs API without any problem. Can you give me number of document?[>>>>>)  http://www.ti.com/lit/ug/swru369c/swru369c.pdf

    - Do you have mcuimg.bin set as fail safe file?
    [>>>>>>]  - don’t know what that means
    - Can you list files in Unfilash? Do you see anything suspicious?
    [>>>>>>>]  only mcuimg.bin
    - Do you use same type sFlash chip?
    [>>>>>]  yes
    - Can you closely investigate issue at debugger? I really think that there need to be some error from sl_ filesystem API.
    [>>>>>>]  - no errors
    - Can you upload simple code by JTAG and read mcuimg.bin file?
    [>>>>>]  it works with UniFlash

  • Hi,

    I am not aware about any information about fielsystem API at previous versions of SWRU369 document. Inside revision history of SWRU369 is not mentioned that type of changes.

    - Fail-Safe - please read ( www.ti.com/.../swru368 at chapter 14 - see COMMIT flag)
    - you want to say that you see by file list by Uniflash only mcuimg.bin? This not make sense. There need to be files like phy.cal, etc.
    - by Uniflash you cannot read mcuimg.bin, please read this code by JTAG uploaded code

    Jan