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.

Error connecting to the target on LAUNCHXL-F28069M

Other Parts Discussed in Thread: MOTORWARE, TMS320F28027, LAUNCHXL-F28069M, BOOSTXL-DRV8301

Tried to program lab 01. Using CCS 6.1 and motorware_1_01_00_14. I looked through old messages and found a similar problem with the control version of the F28069

Solution for that problem did not help. The d5 diode on the booster pak is lit and the D4 diode on the LaunchXL is lit. I checked the USB connection before setting up the booster pack. I got the TI logo to come through the USB to serial converter and the PUTTY.

So I have power and I have a good connection. What else can I check?

Error message is below:

C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 5.1.641.0)
C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 5.1.641.0)

  • Also I get a compiler warning:

    Description Resource Path Location Type
    This project was created using a version of compiler that is not currently installed: 6.2.3 [C2000]. Another version of the compiler will be used during build: 6.4.4. Please go to <a href="liveaction:OpenAppCenter">CCS App Center</a> to install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties. proj_lab10c properties

    Do I need to downgrade to 6.2.3?

    I went to the CCS App Center, but there is nothing there about adding a new compiler -strange message.

    I tried setting up a new target configuration file, but no luck. I followed step 4 in the forum section post by Barbara Brown.

    I selected the XDS100v2 Debug Probe and the TMS320F28027 Device. 

    Why is there no Launchpad Board option?

    I have the same problem with both the F28027 and F28069 launchPadXL.

    The Test Connection result says 

    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    Thanks 

    -Chuck

  • the warning is not a problem. You can right click on the project, go to properties, and choose the compiler you have installed.

    The error says you aren't able to connect USB-JTAG to the device. Typically because it is not powered.

    Are you powering through the BoosterPack Vbus or through the USB cable? Depending on which one you will have to se the jumpers appropriately.

    The ReadMeFirst outlines the settings if you are powering through the BoosterPack:
    LAUNCHXL-F28069M
    i. Remove Jumpers 1 and 2 to isolate USB and power from BOOSTXL-DRV8301
    ii. S1 set to ON-ON-ON
    iii. JP3, 6, 7 ON
    iv. JP4, 5
    a. ON-ON: if just using bottom BoosterPack headers J5-J8
    b. OPEN-OPEN: if using top BoosterPack headers J1-J4 or using both BoosterPack headers J1-J4 & J5-J8;
    c. Provide DC bus at any attached BoosterPack
  • I haven't seen anyone else report these errors.

    Assuming you are using correct power for the jumpers you have set I'm really not sure what else could be the problem...considering it happens with both boards...and I assume you have imported the correct set of projects for each...it must be a CCS installation issue.
  • Chris,
    It was an installation problem as you suggested. When I installed CCS6, I got messages complaining about the anti-virus scan. I had seen this message before when I installed CCS 5 a few months ago. At that time I had ignored anti-virus warning messages and the install went just fine. This time it turns out the Kapersky anti-virus scan did mess up the install -maybe. Or it was just a "microsoft fix", i.e., just the act of rebooting and re-installing everything fixed the problem. But I did install CCS6 twice, so I think it was the anti-virus. We will never really, truly, know.

    Thanks,
    -Chuck