Unable to program CC3200

Hi,

Can you please reply with the followings:

1. screenshot of the COM ports in the device manager (while the board is connected to the PC)
2. The dump/log on Uniflash Console screen (bottom screen)

During flashing, it is only the SOP2 jumper that needs to be connected. In operational mode, you need to remove the jumper.

Shlomi

Hi Shlomi,

The Daul port device is shown as com21, see screenshot below

With SOP2 shorted, the following is provided in the log

[14:58:33] Begin Format operation.
[14:58:33] INFO: > Executing Operation: Connect
[14:58:34] DEBUG: waiting and clearing uart rx buffer
[14:58:36] INFO: setting break signal
[14:58:36] INFO: --- please restart the device ---
[14:58:36] DEBUG: wait for ack
[14:58:51] DEBUG: UART timeout
[14:58:51] DEBUG: --- COM Port timeout on ACK read
[14:58:51] ERROR: ---reading ACK signal failed---
[14:58:51] DEBUG: disconnecting from device . . .
[14:58:51] DEBUG: --- Connection failed trying to reconnect... (1 attempt)
[14:58:51] DEBUG: waiting and clearing uart rx buffer
[14:58:53] INFO: setting break signal
[14:58:53] INFO: --- please restart the device ---
[14:58:53] INFO: Cancel button pressed
[14:58:53] DEBUG: disconnecting from device . . .
[14:58:53] FATAL: --- Can't connect to device !! ---
[14:58:53] FATAL: Error connecting to the device. Please check your COM port settings. Error code: -2
[14:58:53] INFO: > Executing Operation: Disconnect
[14:58:53] DEBUG: disconnecting from device . . .
[14:58:53] Operation Canceled: Process<Format> canceled.

I pressed the reset button on the board when requested without effect.

Hi,

The COM port looks OK. Please make sure no terminal emulation or other program is occupying the COM port. This message indicates either of the followings:

• wrong COM port is used
• COM port is occupied by another program
• SOP2 jumper is not connected
• other jumper settings is incorrect
• other HW connection issues between the FTDI chip and the UART lines going into CC3200 chipset

Can you tell what CC3200 launch pad you are using? the revision should appear on silk label.

Also, it might be that the jumper settings is incorrect. Can you send me a picture of your board settings?

Regards, Shlomi

Hi,

I double checked the com-port (21) and if I select a different one it never gets this far.
 Therefore it does look like I am connecting to the comport.

The board rev is 3.2.

I have attached i photo of the PCB.

Thanks

Well, it looks OK.

I thought that the J6-J7 that are not populated correctly as these jumpers define where the FTDI UART lines are connected to (in your case it is directed to CC3200 chipset).

The jumpers setting is working fine on my setup so this is not the issue.

The only thing that remains is to probe the UART lines. I do not see any other option.

Do you have this capability?

If so, the UART lines should be P55 and P57. It should be accessible via the BP interface. More specific, P55 appears on P2, pin #9. P57 appears on P3, pin #3. P55 should be FTDI_RX and P57 should be FTDI_RX.

The first thing you need to observe is a break signal (logical low) on the line going into CC3200 when you apply any operation on Uniflash (i.e. format, program, service pack update or get version). The break signal should be sensed by CC3200 which in return should send an ACK signal.

Regards,

Shlomi

Hi,

I connected a logic to the tx and rx line as suggested. They remain logical high the entire time. I also probed pins below J6 and J7 with the same result. I also don't see a response from the device when i remove . J6 and 7 and manually apply the logix low to the line.

KR

Regardt

In this case it looks broken.

You should see the line going from FTDI to CC3200 asserted (going down, indicating a break signal). This is why you cannot get into flashing mode.

Is it possible for you to test with another board?

Hi,

No unfortunately not, I only ordered the one to test if it is feasible to replace our current BLE based radios with lowish-power Wifi.

Thanks for your help, As someone that works for an ic/semiconductor company i know how difficult it is to provide remote support. Is there anyway we can get hold of an replacement ic, and swap it out ourselves? Or an replacement board? It is a bit of a pain to go through the import from US distributor path?

KR

Regardt

Hi,

I'm less familiar with the ordering/replacement policy. I'll loop in some people internally and see how it can be resolved.

Will let you know.

Shlomi

Regardt, I will reach out to you to see how best we can support this

Regardt,

Just tested it myself to make sure.

You need to probe the jumper on J6 J7 (which I believe you did) and not the P55/P57 on the booster pack connector. When I do so, I can see the RX line goes low whenever I invoke any operation from the Uniflash, e.g. format, Program.

Shlomi

Can you perform one more test. Connect the jumpers across J6 and J7 such that the UART TX and RX from the FTDI gets shorted. [The pins of the jumpers which face towards the USB connector]

 Then open a terminal window and open the COM port (the 2nd one if you see two).

Send any command to the terminal and it should echo back. This would prove the FTDI chip is working Ok.

Hi,

So J6, J7 is connected to the Flash side? What board rate should i use?

Hi Regardt,

Works for me using the following

115200 Baud, 8 Data Bits, None Parity and 1 Stop Bit.

Glenn.

Hi,

The port opens, but no echo. FT_prog sees the device as "USB <-> JTAG/SWD" with vendor id 0451 and product id C32A

Kind Regards,

Regardt

I have done so, I will leave with our DHL shipment today

Can you let me know which application was being tried to flash on the Launchpad.

Hi,

I am travailing at the moment, so have a look when I get back to the office.

KR

Regardt

Hi Guys

Im facing the same problem Mr. Regardt had with the 3200, i.e., that Im unable to program the device. I have been using the 3200 without any issues using IAR and running the program from the RAM. But after programming the flash 4-5 times, the chip suddenly stopped working. 

I tried running the test that Mr. Shlomi Itzhak had suggested and instead of getting a high level throughout as Mr Regardt dis, I'm getting a low level throughout the operation. 

Does anybody have any idea why this is happening. This seems to be a common problem as I have heard of someone else's chip failing in a similar fashion. Could anyone from TI suggest how it can be corrected?

Hi,

Can you clarify what you mean by stopped working? It is not clear if Uniflash is not working or the programmed application is not working. Also, what do you mean by low level throughput?

If it is Uniflash, please send the scenario/steps you took and log from Uniflash.

Regards,

Shlomi

Sorry for the late response

I had been running programs with the CC3200 in the RAM using IAR workbench and the programs were working properly while so. Then I tried to run a program from the flash by programming the device using Uniflash. The first 2 times I programmed the flash, the programs worked correctly. However, after programming the device a third time, the program worked for a while, and after a couple of resets, it suddenly stopped working, i.e. the output I was observing on a UART terminal stopped. 

Then I tried to program the CC3200 again, using Uniflash. This time, Uniflash returned an error saying that there was no response from the device. I tried it a few times, checked whether the jumpers were connected properly, checked if the FTDI was working properly by shorting jumpers J6 and J7 and looping back a few characters, and tried again, to no avail. 

These are the results of running a Get Version command

[14:10:04] Begin GetVersion operation.
[14:10:04] INFO: > Executing Operation: Connect
[14:10:06] INFO: setting break signal
[14:10:06] INFO: --- please restart the device ---
[14:10:21] ERROR: ---reading ACK signal failed---
[14:10:24] INFO: setting break signal
[14:10:24] INFO: --- please restart the device ---
[14:10:39] ERROR: ---reading ACK signal failed---
[14:10:41] INFO: setting break signal
[14:10:41] INFO: --- please restart the device ---
[14:10:56] ERROR: ---reading ACK signal failed---
[14:10:58] INFO: setting break signal
[14:10:58] INFO: --- please restart the device ---
[14:11:13] ERROR: ---reading ACK signal failed---
[14:11:13] FATAL: --- Can't connect to device !! ---

Regards

Varun

Varun,

It is always better to open a new thread rather than using an existing one.

Anyway, it looks like you cannot even connect to the COM port (or to the FTDI chip).

Since you are new to it, please provide the followings:

1. picture of your CC3200 jumper settings while flashing
2. picture of your device manager while connected to the board
3. version of your CC3200 chipset (should be label on the chip, either XCC3101GZ or XCC3200HZ)
4. make sure SOP2 is connected while flashing
5. make sure J6 and J7 are connected on flash

Additionally, the test I would like to to perform is to connect J6 and J7 as in the picture, open a terminal on the same COM port and type some characters. You should see what you type echoed back.

Shlomi

I am so glad that I found this forum.

I am having the exact same issue.

my cc32200 was working perfectly. I loaded an example from energia. made soem changes and then loaded it again and since then nothing?

I cant connect to the device to upgrade firmware or anything.

Jumpers are correct.

I put the suggested ins on the scope and they are both down. Might as well put the probe to ground.

This is my second dud board. First one came completely dead, and now this one seems to have stuck its finger up its nose.

I did come accross this site:

http://energia.nu/cc3200guide/

where they say this:

You may get an error message inside of Energia at compile time like “FAILED ACK”.  One thing you can try is to clean out your FTDI files using the FT Clean utilityhttp://www.ftdichip.com/Support/Knowledgebase/index.html?ftcleanutility.htm. This may help get your development back on track.

I cant find any download link for the ftdiclean util. But is there any logic behind it?

Hello Shlomi and Gagan, I also have the same problem with my CC3200 Launch-XL which I bought a few weeks ago. It has been working nicely up until today, when it suddenly became unreponsive. I was able to upload a sketch from Energia one minute, and I was unable to upload another sketch a few minutes later.

I have followed all of the indications in this forum topic, and I have the same symptoms.

When I connect with the board via USB to my notebook, it shows as COM Port 19. From Energia (using a jumper cable between TCK and SOP2), using COM Port 19 and selecting the CC3200 Board, I receive this message:

Binary sketch size: 1.976 bytes (of a 262.144 byte maximum)
Opening \\.\COM19
Read ACK failed
Failed to trigger bootloader

I tried to reflash the device with Uniflash, thinking it might perhaps fix the bootloader, but I am not able to connect from Uniflash either. I open Uniflash (with Jumper on J15 on SOP2 and J8 on TCK), select COM Port 19, create new target CC3200, Service Pack Program and select the service pack bin file, and I receive this message:

[14:51:28] Begin ServicePackProgramming operation.
[14:51:29] INFO: > Executing Operation: Connect
[14:51:31] INFO: setting break signal
[14:51:31] INFO: --- please restart the device ---
[14:51:46] ERROR: ---reading ACK signal failed---
[14:51:46] WARNING: ---seting break signal to false failed---
[14:51:48] INFO: setting break signal
[14:51:48] INFO: --- please restart the device ---
[14:52:03] ERROR: ---reading ACK signal failed---
[14:52:03] WARNING: ---seting break signal to false failed---
[14:52:05] INFO: setting break signal
[14:52:05] INFO: --- please restart the device ---
[14:52:20] ERROR: ---reading ACK signal failed---
[14:52:20] WARNING: ---seting break signal to false failed---
[14:52:22] INFO: setting break signal
[14:52:22] INFO: --- please restart the device ---
[14:52:37] ERROR: ---reading ACK signal failed---
[14:52:38] WARNING: ---seting break signal to false failed---
[14:52:38] FATAL: --- Can't connect to device !! ---
[14:52:38] FATAL: Error connecting to the device. Please check your COM port settings. Error code: -3
[14:52:38] INFO: > Executing Operation: Disconnect
[14:52:38] Operation ServicePackProgramming returned.

I have also tested UART as suggested by Prajay, by shorting the J6-J7 jumpers, and I do get an echo back, so FTDI / UART seems to work. I even reflashed the FTDI chip using FT_PROG as suggested in some other forum posts, and I was able to flash the FTDI chip.

I am guessing then that it's some kind of failure on SFLASH or on the MCU itself. 

Can you please let me know how to proceed for servicing the device.

Hello All,

Identical problem as everyone above, but using the ArduCAM CC3200 Uno Board. 

Suggestions for any type of solution would be great.