• State
  • Locked Locked
  • Replies 13 replies
  • Subscribers 42 subscribers
  • Views 2586 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Cannot Connect to CC3200 Launchpad

Eric Evenchick
Prodigy 50 points
Other Parts Discussed in Thread: CC3200, UNIFLASH

Hello,

I'm having a similar to this thread, where I cannot flash the CC3200. I have the SOP jumper set to 100, and when shorting the FTDI_RX and FTDI_TX pins, I am able to get a serial loopback, so it appears the FTDI chip is working properly.

With a logic analyzer connected and trying to do a Get Version in Uniflash, I see no activity on the CC3200's TX line and the error messages:

[18:39:38] INFO: --- please restart the device ---

[18:39:53] ERROR: ---reading ACK signal failed---

[18:39:56] INFO: setting break signal

etc...

The only thing I've attempted to do with this board is flash the SSL demo from the examples. After that, I was unable to continue working due to this error. I do not have another CC3200 Launchpad to test with.

At this point, it seems to me that the CC3200 side of the Launchpad is dead. Is there anything else I can do to verify this? Anything else I should test out on my end? Otherwise, can I get an RMA for this board?

Thanks,

Eric Evenchick 

  • 0
    TI__Guru 56345 points

    Hi,

    Just to make sure and align on the basic setup, can you please attach to this post the followings:

    • a picture of your board settings
    • a snapshot of your device manager when connected to the board
    • make sure no other utility is occupying the COM port and SOP2 is connected
    • Windows you are using?

    From your description it looks as the UART port is connected fine to FTDI as you get echo back. The only thing I can think of is the power to the CC3200 itself.

    Would be a good think if you can test the following to verify the logic level of the TX and RX lines:

    1. disconnect the jumpers on RX and TX
    2. connect logic probes as described below
    3. test RX line (going from FTDI to CC3200). It should be LOW
    4. test TX line (going from CC3200 to FTDI). It should be HIGH
    5. repeat steps #3,#4 with the reset button pressed

      1. test RX line (going from FTDI to CC3200). It should be LOW

      2. test TX line (going from CC3200 to FTDI). It should be LOW

     

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 50 points

    For the basic setup:

    Picture of board:

    Screeshot of device manager:

    No other device is using the COM port. I have tried doing a full reboot and ensuring Uniflash is the only open application.

    This is on Windows 7 SP1 x64

    With a logic analyzer attached as shown, both pins are always logic high, regardless of the state of the reset switch.

    Also, when powered, the green and orange LEDs on the CC3200 (GPIO 10 and 11) are illuminated, as well as the power LED (D4) and the RESET LED (D1). 

  • 0 in reply to Eric Evenchick
    TI__Guru 56345 points

    The setup looks fine but the test I requested indicates that the TX line from CC3200 is not going LOW when reset is pressed and hold. Also, since the FTDI is disconnected from CC3200, I would expect to have the RX LOW all the time.

    Just to make sure, when you reset the board, does D1 goes off and then on?

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 50 points

    Yes, pushing the reset button does toggle D1.

    On another note, I connected a logic analyzer to the SFLASH and noticed there was no activity. The CC3200 does not appear to be communicating with the SFLASH at boot.

    Thanks,

    Eric

  • 0 in reply to Eric Evenchick
    TI__Guru 56345 points

    In this case, let me involve an HW engineer and see if there are other tests we can do and if not, we will contact you offline to replace the board.

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 50 points

    Great, thank you for your help Shlomi.

  • 0
    TI__Guru 56345 points

    Eric,

    We will contact you offline via Email to get you a new board.

    I'm closing this thread.

    Shlomi

  • 0
    TI__Guru 56345 points

    Fernando,

    It does look as if you have similar issues as few other users where the CC3xxx chip is not powered on.

    Just to complete the picture and make sure this is the case, can you please try to work in debug mode (i.e. with JTAG) and try to download any binary to the device?

    Thanks,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Intellectual 310 points

    Shlomi,

    Everything was working one day, and one day after I got this error on CCS, so I went investigate the problem. Follow the picture you request.

    Best regards,


    F.A.Stock

  • 0 in reply to Fernando Almeida Stock
    TI__Mastermind 27095 points

    Hi Fernando,

    Regarding this faulty board, may we contact you at the email address you provided in your E2E profile?

    Thanks & Regards,
    Raghavendra

  • 0 in reply to Raghavendra Shenoy
    Intellectual 310 points

    Raghavendra, good morning,


    Yes, you can.

    Thanks a lot. Best regards,

    F.A.Stock

  • 0 in reply to Shlomi Itzhak
    Prodigy 80 points
    Is then any solution for this problem? I have the same problem with my LAUCHXL rev 4.1 today, after a week running smoothly. I've restarted my PC, uninstall and reinstall the driver, check the jumps carefully, it's still the same.
  • 0 in reply to Shlomi Itzhak
    Prodigy 200 points
    Hello Shlomi,

    Thank you for posting an initial testing workflow. I have been facing a similar problem like Eric from this thread and have observed similar results to all tests on 2 of my launchpad boards.

    Key differences in my specific case:
    Using Win10 64 bit
    Using a Rev. 4.1 Board instead of 3.1
    for one board: Rx Line always low, Tx line high by default and low when reset button is pressed (matches the expected behavior)
    For other board: Rx and Tx lines are both always low

    What should my next steps be?

    (Additionally, I have tested with a separate, working board and have found that the software on my computer is not the source of the issue as it is capable of communicating with and programming that other board.)

    Thank you for your help