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: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.507.0)

Other Parts Discussed in Thread: TMS320F28055, CONTROLSUITE

Dear All,

I am working on a project using TMS320F28055 , i am able to create empty project ,which is compiling properly & generating .out file too.

while creating project i had used XDS100v2 USB Emmulator .but when ever i am trying to debug the same i am getting error mentioned 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. (Emulation package 5.1.507.0)

 I had gone through various post on the forum related with same error ,but its issue remains the same. i had verified my target connections too but still no luck.

Need your help to resolve the issue.

Thanks 

utpal

  • is this a custom board or a kit? Did you installed the drivers of the emulator? Are you able to download an example code (controlSuite example) to the board, assuming is a kit?
    Gastón
  • Please refer to the cCARD infosheet at:
    \controlSUITE\development_kits\~controlCARDs\TMDSCNCD28055ISO\R1_2\

    Can you make sure that the emulator is being powered via JA1?  And that the MCU is also being powered via the basedboard? 
    (two sources of power are needed to allow CCS to run code/connect to this cCARD)

    Can you make sure that SW4 is ON/ON (UP/UP)?


    Thank you,
    Brett

  • Dear Gaston,
    No its not custom board . I am using TI's EVM with TMS320F28055 on board .
    Drivers are installed properly ,i am able to see in device manager usb section once i connect the same.

    I am able to import or create a new project ,also able to compile the code ,,but whenever i am trying to download the code into EVM ,i am getting above error.

    Please help.

    Thanks & Regards :-
    Utpal
  • utpal,

              did you check the reply of Brett Larimore? 

  • HI,
    I tried everything , code is compiling properly ,but main issue is unable to debug the same in device.

    "Error connecting the target "still there.
    Please find below the test results.

    [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\Jagdish\AppData\Local\TEXASI~1\
    CCS\ti\1\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 'Feb 18 2015'.
    The library build time was '23:56:50'.
    The library package version is '5.1.641.0'.
    The library component version is '35.34.40.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]


    FTDI drivers are causing issue i guess.

    Kindly advice how to resolve the issue & move ahead.

    Thanks
    utpal
  • Utpal, if you've followed the "TMDSCNCD28055ISO-Infosheet.pdf" and still receiving this error then there's some hardware issue on the board. Can you tell us about the history of this board... was it working before and later it malfunctioned?
  • Dear Gautam
    I had verified the steps mentioned in TMDSCNCD28055ISO-Infosheet.pdf all required LED is glowing as mentioned even i am getting required voltage on MCU pins. when i am connecting the EVM using USB windows recognizing it. i am able to see XDS 100 A / B in device manager too.
    But whenever i am trying to debug ,i am getting the error mentioned in above post.this is the new board bought & I am trying the same for the first time.

    Kindly suggest ,if there is any way or should i go ahead & request for replacement.

    Thanks for your quick response Gautam\

    Regards,
    utpal
  • you check this link? 

    maybe you should try to reinstall the drivers.

    Regards

    Gastón

  • Kindly suggest ,if there is any way or should i go ahead & request for replacement.

    Please go for a replacement.

    Regards,
    Gautam
  • Hi Utpal,

    I think there is a decent chance this is a hardware issue, but I am not fully convinced.  If you suspect hardware, then feel free to request a replacement.

    I did a bit of searching on the forum (for the specific error you are seeing) and typically the driver is having some sort of problem:
    1) Have you ever gotten this kit to work?  Can you try to use the board on a different computer?  This may prove that the issue is specific to the current computer that you are using.
    2) Are you using a VM? Perhaps the latency running with a VM is causing the driver to have issues. (this was the root cause in one of the forum posts)
    3) Can you see if there are any CCS updates and, if there are some, can you install them?  

     
    Thank you,
    Brett

  • Thanks to all for your quick response & suggestions .

    I got the replacement & its working fine.
  • That's Great!

    Goodluck & Regards,
    Gautam