CCS/TMS320F28379D: TMS320F28379D / Cannot connect to target

Tomas Sadilek

Part Number: TMS320F28379D
Other Parts Discussed in Thread: CONTROLSUITE, TMDSCNCD28379D

Tool/software: Code Composer Studio

I am using CCS 7 and the TMS320F28379D control card. The card is correctly set up and powered from the micro-usb connector. The debugger is properly connected.

Proper debugger is selected in project options.

Connection is verified with the "Verify" button.

The project is properly built (cpu1 flash).

However, debug results in this message: "

Texas Instruments XDS100v2 USB Debug Probe/C28xx_CPU1 : Target must be connected before loading program."

over 8 years ago

0 Gautam Iyer over 8 years ago

Guru 192875 points

Hi Tomas,

Did you go through the info sheet? You can find the same here:
C:\ti\controlSUITE\development_kits\~controlCARDs\TMDSCNCD28379D_v1_0

Regards,
Gautam

0 Tomas Sadilek over 8 years ago in reply to Gautam Iyer

Intellectual 430 points

Hi Gautam,

Yes, I have gone thru the datasheet. The JTAG boundary scan test works fine.

I have also tested CCS 6.0.1, 6.2, and 7. No success in any of these installations.

My computer seems to have an issue with this card and also the 28377D card.

Tomas

0 Tomas Sadilek over 8 years ago in reply to Gautam Iyer

Intellectual 430 points

Also,

I have installed CCS 6.2 on a different computer and the same thing happens (Cannot connect to target).

Also, I have tried the Verify Connection (without any project), selected the correct processor and hit "Test Connection". All tests succeeded.

However, CCS still reports that the debug cannot connect to the target.

Thanks,
Tomas

0 Tomas Sadilek over 8 years ago in reply to Gautam Iyer

Intellectual 430 points

I think I have found a pretty major bug.

There is a project that compiles just fine but cannot be debugged (flashed) due to the "Cannot connect to target" error on two computers and CCS versions 6.01, 6.2, and 7.0 (and a ton of different compilers).

A different project loads just fine.

However, if the "good" project is tried after the "bad" project, the same error happens.

If the "good" project is tried first, it works fine. The "bad" project still does not work and disables the debugging functionality for all subsequent debugging sessions until CCS is restarted.