• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1083 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 Development Board Bricked with wrong Target Configuration

Pat We
Intellectual 305 points

Other Parts Discussed in Thread: CC3200, UNIFLASH

Hello

I made a mistake when following CC3200 first project, for some reason I fount that active Target Configuration was from the other project TM4C123..., I noticed that while program was loaded into memory and since then I can not connect the target because following errors:

What would be the pain free solution.

Thanks

Patrick

  • 0
    Guru 86865 points
    Hi,

    Do you see your CC3200 Launchpad at your Device Manager? If yes, using Uniflash format your CC3200 with settings 1 MB size, Secure and Alert option left unchecked.

    If successful format, load a example program at your CC3200 Launchpad using Uniflash. If it runs, then you have recovered your CC3200 Launchpad.

    - kel
  • 0 in reply to Markel Robregado
    Intellectual 305 points
    Hi Kel

    Thanks for your post , that gets me on the right track, I was able to upload bin files using Uniflash, but debugging is still not working.

    I just buy another dev board and see was is the problem

    Thanks

    Patrick
  • 0 in reply to Pat We
    Guru 86865 points
    Hi Pat,

    From the information you provided here regarding your problem, there is not enough reason to suspect that your CC3200 Launchpad is broken.

    As you have mentioned, you are able to load .bin file using Uniflash. If the program works at your CC3200 Launchpad then there is no problem with your CC3200 launchpad. Load blinky and see if the led at your CC3200 launchpad blinks.

    - kel
  • 0 in reply to Markel Robregado
    Intellectual 305 points
    Hi Kel

    I had the second board and was facing the same problem, I found the reason, I should be using cc3200 target config as the 3200XDS100.

    Thanks

    Patrick