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 Lauchpad flash from Format to Oob

Other Parts Discussed in Thread: UNIFLASH, CC3200SDK, CC3200

Hi,

I Format the lauchpad and I have not been able to flash the OOB. I have download the servicepack_1.0.1.5.0.bin and try to follow the instruction under the UniFlash Quick Start Guide web site but I have not been able to get to the point whee OOB boot up from flash. Furthermore, after I Format the Launchpad, it seems that it also errased the MAC address for this board. 

Can you tell me the step by step from Format the Lauchpad to the point that I can get theOOB to boot from flash?  If posible, please tell it in a step proceedure wth screen capture (or better yet demonstrate it via a video for youtube).  

Back to the detail isntruction example, I show my steps which did not get the OOB to boot from flash but I list them so you can help me correct the steps as necessary:

1.  Open CCS Uniflash  (note: this latest tool does not show version under help->About). Assume I already established the COM connection

2. On the left pane, select  the top option CC31xx/CC32xx Flash Setup and Control

 On the right pane, select the following buttons:

3. Select "Format" button  -> choose 1MB -> wait till format completed

4. Selet Program button ->  do I need to do any configuration first?

5. Select "Service Pack Programming" button  -> navigate to the directory containsthe latest servicepack_x.bin  (servicepack_1.0.1.5.0.bin  as of 3/23/16)

6. Select Image Programming -> navigte to directories where oob.bin and out_of_box.ucf are stored. program them one at a time

  C:\ti\CC3200SDK_1.1.0\cc3200-sdk\example\out_of_box\ccs\Release\oob.bin

  C:\ti\CC3200SDK_1.1.0\cc3200-sdk\example\out_of_box\html\out_of_box.ucf

7.  remove the SOP2 jumper, confirm P58 jumper install fo AP mode; reboot  

As I said this proceedure did not work. So please correct what I did wrong.

 - what do I need to do next?  

 - How do I find the MAC address for the device and how do I set it up ?  

 - What do I do with the options uner CC31xx/CC32xx Config Groups?

Thank you for your help,

Sy

  • Hi Sy,

    Try these steps below. Before performing any Uniflash operations place a jumper at SOP2. You also need to set correct COM Port for your C3200 LP at Uniflash. Remove power to your CC3200 LP when placing and removing jumpers.

    1. Using Uniflash, format your CC3200 with settings 1 MB Size, Secure and Alert option left unchecked.
    2. Using Uniflash program latest Service Pack.
    3. Using Uniflash go to File->Open Configuration. Then open oob .ucf file located at "C:\ti\CC3200SDK_1.1.0\cc3200-sdk\example\out_of_box\html". Then click "Program", to program oob to your CC3200 LP Serial Flash.
    4. Remove jumper at SOP2. Place jumper at P58-Vcc. Then power cycle your CC3200 LP
    5. Test oob using your smart phone.

    - kel

  • Hi Kel,

    Thank you for your help. The instruction in step 3 was what I needed to program the OOB. I folowed your sequence and it works. I am still unclear what is the purpose of the oob.bin file? In some other discussions about the oob said that to program both but your instruction said only to program the .ucf only .

    Regards,
    Sy
  • Hi Sy,

    See, the Uniflash wiki for further clarification about .ucf files. processors.wiki.ti.com/.../CC31xx_&_CC32xx_UniFlash

    When you open the oob .ucf file at Uniflash you will see a set of files that is needed by the program. Besides the .bin file there are .html, .gif., css., .jpg and others.

    For example programs like blinky. The program does not require any other file for the blinky program to run. So to program blinky example program using Uniflash, you create a new configuration and then set the .bin file location at /sys/mcuimg.bin.

    - kel
  • Just in case, if you are still not able to boot from SFlash after following the proper flashing procedure as explained by others, then the problem might be related to the UART peripheral being used without being properly initialized.

    Are there any UART messages that are being sent before the UART is enabled? If yes then you can try to comment those UART prints until the system is successfully initialized and it is properly configured. You can check this through the LED's which are set to turn on/off/blink to indicate certain stages in the boot up/initialization. You may want to disable all UART prints and then once it boots successfully through SFlash (based on the LED status or connection to WiFi), iteratively enable the UART prints in the reverse order and see when it fails to boot. This will indicate the point prior to which UART is not initialized and thus it cannot be used.

    Regards,
    Umar C