Unable to flash CC3200 with uniflash

Hi Parthib,

    Try this below steps.

1. Close Uniflash and other Serial Console that have communicated with it previously like Tera Term.
2. Then power off and power on your CC3200 Launchpad.
3. Open Uniflash, and program your CC3200 Launchpad. Make sure you set the correct COM Port.

- kel

Hi

       kel

                  I appreciate your answer. But it is still not working, during the flash operation when uniflash prompted me to press reset button I did that and from that point my board stop working . Do you think that my board gone bad?

--MTR

Hi,

   There are some post here that the CC3200 Launchpad became unusable. But, most probably that is caused by human factors.

   For whatever reasons, I had past experience having trouble making the Uniflash work for a day or so. The solution was to start fresh. I uninstalled Uniflash and deleted all drivers associated with my CC3200 Launchpad at Device Manager. The drivers for CC3200 Launchpad will be re-installed automatically after refreshing the Device Manager. I installed the latest version of Uniflash and now I am able to load programs at CC3200 Launchpad using Uniflash.

   As mentioned in this forum and from my observation, you will be unable to load program to your CC3200 Launchpad using Uniflash if you have previously used a serial console like Tera Term to communicate with your CC3200 Launchpad. Take note of this. That is why I earlier advised to close Uniflash and other Serial Console.

- kel

Hi MTR,

If Markel's suggestions do not work for you, I would like to make sure the board is not broken as a result of ESD damage or any other HW reason. Can you please try to work in debug mode (using CCS/IAR) with any example code and check that it works?

Additionally, on the log that you shared it seems that flashing started (at least the format section) and then Program operation failes. Is this always reproducible? Can you tell if the following operations work:

1. GetVersion
2. Format
3. Program
4. ServicePack update

Shlomi

If you are still able to debug, the problem is most likely the FTDI COM port driver... see this link: http://energia.nu/cc3200guide/

Try the FTClean (I could not find it. so I used CDM Uninstaller 1.4 instead to uninstall the drivers) http://www.ftdichip.com/Support/Knowledgebase/index.html?ftcleanutility.htm

Then I used the CC3200-SDK\tools\ftdi\ folder to reinstall the drivers after a reboot and that fixed it for me, but it was a hassle to go through that.

Regards,

JJ

Can you give a little insight on how to use the CDM uninstaller?

It is asking for a vendor ID and product ID.

Kyle,

The GUI tool has a field for vendor ID and Product ID of the device you are trying to remove the drivers for completely.

It's been a few weeks, but I found the Vendor ID of the FTDI driver by going to Control Panel->Device Manager and locating the "CC3200LP Dual Port (COMx)" entry and searched the "Hardware Ids" property which contains the USB VendorID and ProductID fields. In this case, the string should look like "FTDIBUS\COMPORT&VID_0451&PID_C32A". The Vendor ID is "0x451" and Product ID is "0xC32A" to enter into the fields with the same names in the CDM Uninstaller GUI tool. Enter these values into the fields in the tool, and click "Add", which will create a table entry that "VID_0451 PID_C32A" into the list and you can either repeat the process (in this case, you shouldn't need to but just in case there are some products associated that I am missing causing the problem) then click "Remove Devices" to completely uninstall the driver.

This is somewhat of a hard removal, and will require you to reinstall the drivers manually. As I mentioned previously, the drivers are in the CC3200SDK tools folder under FTDI.

The tool is not entirely intuitive, but the general ID is that it seems to look for the INF entries corresponding to that VID/PID and removes them from the system. You really want to use this tool as a last resort. The failure mode I observed was that I could debug using the JTAG but I could not flash.

I hope this helps!

PS: Clicking "Generate uninstall log file" may be a good idea too.

JJ

Thanks for the help, I will give this a try.

Edit: Sadly, doesn't seem to fix my problem, but thanks for the help.