• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 43 subscribers
  • Views 2203 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 -- IAR workbench -- Unable to connect to CC3200 Launchpad

Rob Rodrigues
Mastermind 19780 points
Other Parts Discussed in Thread: CC3200-LAUNCHXL, UNIFLASH, CC3200

Hi Team,

I have an issue that I haven't found a resolution to on the forum here.

I am using a CC3200-LAUNCHXL board rev 3.2 with IAR Workbench 7.2.  I am trying to load an example program on to the Launchpad, but IAR can't connect to the Launchpad!

UniFlash has no problems, I have formatted the Launchpad and updated to the most recent service pack 1.0.0.1.0

The error happens on IAR when I try to start the debugger. The error says

"Fatal error: **ERROR**: Unable to connect - Check hardware, speed and interface selected.

Session aborted!"

I followed the steps listed in the quick start guide to the letter including replacing the driver library for lmftdi.

Regards,
 

  • 0
    Guru 86755 points

    Hi Rob,

         I am not using IAR, but, I sometimes get this error. When you connect your Launchpad at your PC, check if you see it a Device Manager. Close other tools connecting to it like Tera Term. Then power off and on your CC3200 Launchpad and try again to debug using IAR. Select the proper interface connection.

        I know these above are unusual steps, but I do this.

    - kel

  • 0 in reply to Markel Robregado
    Guru 21435 points

    In-between debug sessions, you will need to hit the reset button on the CC3200 LaunchPad. This is what I do to ensure I can run another debug session.

    Glenn. 

  • 0 in reply to Glenn Vassallo
    TI__Mastermind 19780 points

    Thanks for your suggestions, everyone.  Sadly this isn't a user error issue, as I have the Launchpads working just fine on another PC.

     

    The PCs are identical as far as I can tell, along with all the project options in IAR.  Still, IAR does not connect to the Launchpads at all.

     

    Interesting symptom: When the debugger starts in IAR on the working PC, I get 2 status bars while flashing the CC3200. One status bar says "Starting debugger session: Loading debug file"  The second bar beneath it says "TI Stellaris Driver: Downloading application ..."

    On the non-working PC, it hangs at the first status bar "Starting debugger session: Loading debug file" only and never gets to the second one.

     

    Regards,

  • 0 in reply to Rob Rodrigues
    TI__Expert 7215 points

    Hi Rob,

    Starting debugger session: Loading debug file - This is not appearing in failure case indicates that debug DLL might not be correct.

    Can you please confirm that below steps are taken care

    copy "armLMIFTDI.dll" to "C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.x.x\arm\bin" 

  • 0 in reply to Kaushal Kukkar
    TI__Expert 7215 points

    Also,

    Can you please check whether device manager shows JTAG in USB controller as shown in below picture.

  • 0 in reply to Kaushal Kukkar
    TI__Mastermind 19780 points

    Hi Kaushal,

    Here is a screenshot of the device manager.

     

     

    The device connects to UniFlash as well.  Debugging doesn't work in IAR however.

  • 0 in reply to Rob Rodrigues
    TI__Expert 5025 points

    Hi Rob,

    Were you able to resolve the issue you faced on one of the PCs or have you just moved on with the other PC?

    Best regards,

    Naveen

  • 0 in reply to Naveen Narayanan
    TI__Mastermind 19780 points

    Hi Team,

     

    We have resolved the issue with the original PC.  With help from Victor, we determined it was a device conflict that the driver isn't capable of resolving.

     

    Another FTDI device was connected to the PC at the same time as the CC3200 Launchpad, and the driver is unable to distinguish between the two different devices.

     

    Disconnecting ALL other FTDI devices from the PC solved the problem.

     

    Regards,