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.

XDS 100 V2 JTAG Emulator with TMS320F28027F

Other Parts Discussed in Thread: TMS320F28027F, CONTROLSUITE, LAUNCHXL-F28027, TMS320F28027, MOTORWARE

Hi all  :)

I made a pcb with TMS320F28027F connected to the 20-pin header for XDS 100 V2 JTAG Emulator (TMDSEMU 100V2U-20T) with CCS v6.0.1.00040 under free license. 

But when I start the debugging session it gives me "Error connecting to the target".

The board schematic and the connection between the microcontroller and the 20-pin header as follows :-

and the microcontroller :-

  • Hi,

    Can you please compare & verify with the launchpad schematics once? You can find the same here:
    C:\ti\controlSUITE\development_kits\C2000_LaunchPad\LAUNCHXL-F28027\HwDevPkg

    Regards,
    Gautam
  • I am already taking the schematic from the launchpad !
  • Is your D1 glowing and did you check the voltage levels around the mcu?
  • I checked voltage levels, seems ok , i noticed before connecting the emulator pin 11 (TCK) idle state is 3.3v and when the emulator connected to becomes about 0.5v , and TDO idle voltage level is about 2.4V, is this normal ?
  • And what is the status of TRST value? Also, paste the results of Test Connection in Target Configuration.

  • TRST idle value is 0V, but i don't understand what you mean by "Test Connection in Target Configuration" ?
  • Amr Ayoub said:
    what you mean by "Test Connection in Target Configuration" ?

  • [Start: Texas Instruments XDS100v2 USB Emulator_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\ammr\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 'May 21 2014'.
    The library build time was '17:19:59'.
    The library package version is '5.1.507.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).

    -----[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.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length failed.
    The JTAG IR instruction scan-path is stuck-at-ones.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG IR Integrity scan-test has failed.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG DR Integrity scan-test has failed.

    [End: Texas Instruments XDS100v2 USB Emulator_0]
  • There's a new update about the situation : 

    Sometimes the debugger works after I make many restarts to the board (disconnect the power and reconnect with pushing the restart button many times ! ) and the test gives the following output ( note: sometimes I forced to replace the mcu as it always gives mcu locked error)

    [Start: Texas Instruments XDS100v2 USB Emulator_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\ammr\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 'May 21 2014'.
    The library build time was '17:19:59'.
    The library package version is '5.1.507.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).

    -----[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.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 38 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS100v2 USB Emulator_0]

  • So do you observe any loose connections?
  • Now I am using the Launchpad, it passes the scan-test on the JTAG

    but when I start the debugger it gives me this error:-

    C28xx: Flash Programmer: Warning: The configured device (TMS320F28027), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
    C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
    Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.

  • I hope you're target configuration is as follows: Connection - XDS100v2 & device : TMS320F28027
    Try loading a sample code to the launchpad and if, you still receive this error then either the device is locked or damaged!
  • I am confused and need to know the reason because i have this situation with this Launchpad many times before .

    Now I took the example proj_lap3a from motorware examples and I made the target configuration as generic C28xx device (the default target configuration for the example ) it passed the building but got same debugging error.

    Then I changed the target configuration as follows

    it gives me :

    Then I changed the linker command files and got:

    Also could you please help explaining what the reasons which make the microcontroller locked, as I don't think it's damaged because that happens to Launchpads before I just got them out from their box without connecting them to any hardware to cause any damage !

    one time the launchpad was working fine then I disconnected it from usb after programming and when I connect it again, i got that debugging error without changing anything or connection and I just changed the mcu in the launchpad then it's solved !

  • Amr Ayoub said:
    Also could you please help explaining what the reasons which make the microcontroller locked, as I don't think it's damaged because that happens to Launchpads before I just got them out from their box without connecting them to any hardware to cause any damage !

    Micro controller can get locked if you power cycle/reset or there's a power failure during erase process. Mcu enters into permanent lock mode in this case and is

    unrecoverable.  Also, are you able to build the project correctly without any errors?

    Amr Ayoub said:
    one time the launchpad was working fine then I disconnected it from usb after programming and when I connect it again, i got that debugging error without changing anything or connection and I just changed the mcu in the launchpad then it's solved !

    So replacing the controller solved the issue?

  • Replacing the mcu solved the problem, I programmed it two times and then the mcu locked again !

    for the project building as I attached the photos above, I took the example proj_lab from the motorware examples and I tried two target configurations (320F28027 and xds100v2) and it didn't build correctly (plz have a look on the photos have screenshots from CCS)

  • I changed the linker command file from (F28027.cmd) to (F28027F.cmd) and the build succeeded, now still the debugging problem.
  • Amr Ayoub said:
    Replacing the mcu solved the problem, I programmed it two times and then the mcu locked again !

    This sounds fishy... we need to find the root cause for this strange behavior. Did your programming session get stuck before getting locked? Also, please check your hardware thoroughly.

  • Gautam Iyer said:
    Did your programming session get stuck before getting locked?

    No from the start it gives the error with the code : (Error -1135 @ 0x0)

    Gautam Iyer said:
    please check your hardware thoroughly

    My hardware connection in the pcb as follows, also i assembled two of my pcbs and used two of  the Launchpad and experiencing same problem:

    my hardware connection as follows :

  • More than the JTAG there seems to be some other hardware issue.
  • Not only with my hardware, yesterday same problem happened with a launchpad I just got out from its box with a new USB cable and the demo example program with it (C2kLaunchPadDemo).

    I can't find reasonable explanation for what's happening and that mcu locking issue !

  • Mann... there's something really strange going on here! Any supply issues? Where do you derive your USB power from PC or laptop? Can you try this on another PC/laptop?