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.

CCS/TMS320F28027: TMS320F28027

Part Number: TMS320F28027
Other Parts Discussed in Thread: CONTROLSUITE,

Tool/software: Code Composer Studio

Hi,

I tried connecting the TMDSHVPFCKIT with XDSv2 JTAG emulator on CCSv4 and CCSv6. I am running the sample program of HVPFC2Phil from controlSuite. But on connecting target it gives the message as shown below.

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

I did the target configuration.But still i can't resolve this.

Please help me in resolving these error of connecting target..

Regards,

Kalpesh 

  • Kalpesh

    Check out this wiki with helping to resolve this: processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    Best Regards
    Chris
  • Hi,
    I looked into the page and did the necessary like checking the device manager,changing the Jtag USB,creating new target configuration .But none of this is solving my problem.
    I have a similar processor TMS320F28027 launchpad the program in this get debuuged. But on this TMDSHVPFCKIT it is giving me Debug connectivity error.
    I am attaching the test connection result.

    [Start: Texas Instruments XDS100v2 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


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

    C:\Users\KK\AppData\Local\TEXASI~1\CCS\ti\
    0\0\BrdDat\testBoard.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'.
    The library build date was 'Jul 27 2016'.
    The library build time was '18:31:37'.
    The library package version is '6.0.407.3'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

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

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    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).

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-150' (0xffffff6a).
    The title is 'SC_ERR_FTDI_FAIL'.

    The explanation is:
    One of the FTDI driver functions used during
    configuration returned a invalid status or an error.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]

    So please suggest me how to resolve this connectivity problem.



    Regards,
    Kalpesh

  • Kalpesh

    Did you review/try what is mentioned in the section regarding this specific error?
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    Best Regards
    Chris
  • Yes sir i reviewed the page and took necessary action for the errors,but still it gives the same error.Are there any different configuration for TMDSHVPFC kit apart from TI manual that i should know for connecting target.

    Regards,
    Kalpesh
  • Alright. I'm in the process of having someone more familiar with the board and/or JTAG to review this post.

    Best regards
    Chris
  • Hi Kalpesh,

    This project was developed with CCSv4. It should work with this CCS version without any issues. Is this the first time this board is being powered up? This project also comes with a GUI that uses isolated serial communications. Have you tried connecting to the board using the GUI?

    You will find HVPFC2PHIL-GUI-QSG.pdf  inside the docs folder. This document provides a step by step guide to running this board using the GUI. The HVPFC2PHIL.pdf document provides implementation details  and a similar step by step guide to work with the CCS project.

    I hope this helps.

    Hrishi

  • I tried with ccsv4 and i don't want to use the GUI,I just want to run the existing HVPFC2PHIL program from controlsuite in it using CCSv4. I have a same processor (TMS320F28027) launchpad ,running the program in that launchpad was successful.

    I don't understand why i can't connect target and run the same in this kit. Is there some different procedure apart from the HVPFC2PHIL manual that i need to follow .Please suggest me.

    I have a question, What if i want to use different control logic and use to run using CCSv4?


    I tried changing the cable and the board.I also ran the EEPROM test and DEBUG JTAG GUI test as suggested in one of your thread(e2e.ti.com/.../1514372

    Regards,
    KAlpesh

  • Kalpesh,

    The fact that you were able to run the code on a 28027 Launchpad suggests that this issue is related to the on-board JTAG emulation circuit of the controller card. This is why I suggest connecting the GUI first because the isolated comms uses the same USB interface. If the GUI is not able to connect to the controller we can be sure the emulator is at fault or needs to be programmed.

    Is this a new board that you recently received from TI? You mention that you changed the board. I believe you mean the small controller card. These controller cards were designed specifically for this kit and were only shipped with the kit (not sold separately). If you have a 2nd controller card, you must also have a corresponding 2nd base board. You can try that combination (2nd controller card + 2nd base board) as well.

    Hrishi

  • Hrishi,

    I tested the GUI and it works fine and yes i have 2 kits and both of them are giiving the same error while connecting target.

    If GUI is connected that means emulator is not at fault then is this due too control card? and also will it run if i modify the code and debug in the control card?

    Regards,
    Kalpesh