Jump to content
Sign in to follow this  
eelcor

CCSv5 and C2000 launchpad - Debugger crashes

Recommended Posts

Hi everybody,

 

I just received my C2000 launchpad and was looking forward to experiment with it this weekend. However, I've had nothing but problems with the board. The demo runs fine and shows the temperature as well as the nice TI addition.

 

However, when I try to compile one of the demo programs, it compiles fine, but crashes when I switch to the debugger. I can start the debugger manually, but as soon as I try to connect to the target CCS crashes (the window just closes).

 

I am running Windows 7 extreme edition 64 bit and I tried both the TI FTDI drivers as well as the latest FTDI drivers. I've installed the dbjtag gui app, which doesn't do much. For instance when I run some of the tests, this is the output:

 

>>> Start output

 

 

-----[Print the board config pathname(s)]------------------------------------

 

C:\Program Files (x86)\Debug JTAG GUI\emulators\

Board_Config\TIXDS100v2.dat

 

-----[Print the reset-command software log-file]-----------------------------

 

This utility has selected a 100- or 510-class product.

This utility will load the adapter 'jioserdesusb.dll'.

 

>>> End output

 

I've been wiggling with the switches S1...S3 to no avail. I've reïnstalled CCSv5 approx 10 times on different drives, but still the same problem. I've tried 5.1 and 5.2, but still the same problem.

 

I hope someone can help me, because this is really frustrating.

 

Kind regards, Eelco

Share this post


Link to post
Share on other sites

 

I am running Windows 7 extreme edition 64 bit and I tried both the TI FTDI drivers as well as the latest FTDI drivers. I've installed the dbjtag gui app, which doesn't do much. For instance when I run some of the tests, this is the output:

I hope someone can help me, because this is really frustrating.

 

Kind regards, Eelco

 

I have 32-bit and it works for me. Trey should be able to help or someone else with a 64bit Win machine. Hang in there.

one popular tip for 64-Bit CCS is to install CCS in a different directory other than Program Files.

Share this post


Link to post
Share on other sites

64bit Win7 here, works fine using the controlSUITE examples, though I've had to make a target configuration (Texas Instruments XDS100v1 USB Emulator -> TMS320F28027) on some.

 

And... who installs things in Program Files?... I keep things installed on a secondary HD.

Share this post


Link to post
Share on other sites

And... who installs things in Program Files?... I keep things installed on a secondary HD.

You :lol: . Not sure though, when I tried to install ccs in a different folder, I got a pop-up saying upgrades might pose a problem.

Share this post


Link to post
Share on other sites

Hi everybody,

 

Thanks for the replies! My CCS is installed in the C:\ti directory (it doesn't even offer to install in program files). I will try to make a new target and see whether I am able to connect.

 

I have the feeling that the following scenario's are the most likely:

- some legacy files of older installations are bugging me. I thought I cleaned everything but maybe I forgotten some less trivial places. Any suggestions (i've had v4intalled)?

- there is a hardware malfunction preventing jtag access (serial works although. Flipping the s3 and/or s4 doesn't seem to do much with respect to debugging and connecting.

 

I will try to install ccs on a fresh machine to see whether it is one of the scenario's or something else.

 

Kind regards, Eelco

Share this post


Link to post
Share on other sites

Eelco,

 

There are no known incompatibilities...this is strange. I agree that a clean install of CCS is the right next step. I think you're hardware is fine because they are using the XDS100 on the board to program the demo application, so if the demo works your JTAG should work as well. To me this sounds like a driver issue.

 

Trey

Share this post


Link to post
Share on other sites

Hi Trey,

 

What can I do with the drivers, are there some notorious spots where I can find remains of earlier versions of CCS. I am currently running the CCS update, maybe that will help. Somehow it seems that the ftdi chip is recognized and gets a driver, but the communication between the XDS100 and the C2000 seems to be nonfunctional (at least for JTAG, as serial seems to work fine).

 

My C2000 exposes itself in three items in the device manager, two XDS100 channels (A and B) and a USB serial port. There are no reported errors, when installing. However, as I am a devkit junkie, I have several kits (such as the papilio, mbed, arduino etc.) that use the same FTDI chip for comms. Could there be a conflict?

 

Kind regards,

 

Eelco

Share this post


Link to post
Share on other sites

I suppose there could be a conflict, but I couldn't say what exactly is conflicting. The XDS100 drivers are here:

C:\TI\ccsv5\ccs_base\emulation\windows\xds100_drivers\ftdi

 

Try completely uninstalling all the XDS devices in device manager and then reinstalling with the drivers in that directory.

Share this post


Link to post
Share on other sites

I tried it, but it doesn't work. As soon as the debugger tries to connect it crashes. The dbgjtag gui doesn't yield any information. It complains when I completely disconnect the debugger, but somehow it seems that the ftdi chip cannot make the connection to the chip. The switches S1 to S3 should all be in the "up" position? I tried both combinations.

 

Kind regards, Eelco

Share this post


Link to post
Share on other sites

What is written in the User\local folder? Somehow I have the feeling that this behavior is mainly due to some remains of earlier installations (environment variables, registry etc.).

Share this post


Link to post
Share on other sites

Yup all the switches should be in the up position. Even if they were down, you would still be able to start a debug session (i.e. connect to the debugger), you however would not be able to connect to the chip.

 

Are you able to try another PC?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...