• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 542 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.

CC3200 dead after flashing a few times

Michael Menzi
Prodigy 10 points
Other Parts Discussed in Thread: UNIFLASH, CC3200

Hi all,

Yesterday I got the CC3200 launchpad (Rev 3.2) and messed around a bit with the preloaded demo app. Everything worked fine. I followed the instructions in the getting started guide to set up the tool chain. I'm using ccsv6. I managed to flash and run the httpserver example so I could see the debug output in tera term. For some strange reason - I haven't connected anything to the board neither changed the jumper settings - the third or fourth time I tried to flash ccs gave me the error message "couldn't connect to target". Rebooting didn't help so I tried to do a "get version" in uniflash but without success. Uniflash prints:

[11:13:37] INFO: setting break signal
[11:13:37] INFO: --- please restart the device ---
[11:13:52] ERROR: ---reading ACK signal failed---

I saw that others are having the same problem so I followed the advices in this and this thread and could ensure that the ftdi chip is working correctly. I can see actions on the uart_rx line (J6) but no (re)actions on the uart_tx line (J7). The tx line remains low all the time. I of course quadruple-checked the jumper settings so this can't be the problem. Then I had a look on the communication lines of the sflash and since there nothing happened after a device reset (even with SOP set to 000), I have to assume my device is already in heaven.

But.. why?

Reading the threads mentioned above showed that others have broken their devices too without having any idea how and short after they got the device.

Are there any known issues with this chip (its an xcc3200hz)? Could I accidently have corrupted the bootloader in some way?

Any advice is appreciated!

Thanks in advance,

Michael

  • 0
    Guru 86755 points

    Hi Michael,

        Try this below.

    1. Close Uniflash and other serial console that uses the same COM port as your Launchpad.
    2. Power Off and On your CC3200 Launchpad. Make sure the jumper is connected at SOP2
    3. Open Uniflash and try to load program again. Make sure you set the correct COM port at Uniflash.

    - kel 

  • 0 in reply to Markel Robregado
    TI__Guru 64455 points

    Hi Michael,

    You mentioned following some of my early posts for HW debugging and that "I can see actions on the uart_rx line (J6) but no (re)actions on the uart_tx line (J7). The tx line remains low all the time."

    When J6 and J7 are connected and you are not doing anything with Uniflash, you should see on a loggic analyzer both lines high. J6 (RX) should be high as this is the output from FTDI chip to CC3200 chip. J7 (TX) should be high indicating CC3200 chip is powered up.

    The procedure with Uniflash is as follows:

    1. J6 and J7 should be high
    2. activate Uniflash with any operation, e.g. GetVersion
    3. Uniflash should assert J6 going to low (sending a break signal)
    4. restart the device
    5. CC3200 should sense the break signal and send an ACK packet (0x00 0xCC) on J7

    This is the basic start. Please report what you see when you apply this procedure. It might be that either CC3200 UART lines are damaged in some way (as you claim seeing TX always low) or it might be the FTDI chip that got broken (and thus the TX line remains low).

    Another test you can do is disconnect the FTDI chip (by disconnecting J6 and J7), then connect an external level shifter to your PC and try to activate Uniflash. This way you can isolate whether it is FTDI issue or CC3200 issue.

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    TI__Guru 64455 points

    Hi Michael,

    We will contact you offline via Email to get you a new board.
    In addition, please note that a new production Service Pack has been released (v1.0.0.1.1).
    Make sure you start using it instead of the pre-production Service Pack.

    I'm closing this thread.

    Shlomi