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.

XDS100V2 problem in loading the program into flash of TMS320F28027

Other Parts Discussed in Thread: TMS320F28027, ISO7220C, C2000-GANG

I have tested the program with TMS320F28027 launchpad.

It has successfully loaded and was tested successfully.

However, when I had tried to load same program into TMS320F28027 with XDS100V2.

It is showing loading error.

I have made same connection between MCU and XDS100V2 shown in datasheet of TMS320F28027 page No 86 ( Emulator connection without signal buffering for the MCU).

Please guide

  • Hi Ashutosh,

    What error do you receive?

    Regards,
    Gautam
  • Previously it was shownin pop up window incicating " Load error"

    Now it is showing different message in the popup window.

    "
    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.450.0)"

    Please help
  • Try a "Test Connection" on Target Configuration window and share the results.
  • Means exactly what should be done

  • following is the result when "Test Connection" on Target Configuration window is done
    -----[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]
  • XDS100v2 seems to be malfunctioning. Also, check the connection without connecting to the target; do you get the same result?
  • Also one point I like to bring to your notice is that emulator is brand new recently purchàsed.

    When I removed the MCU connection with XDS100V2 and

    following is the result when "Test Connection" on Target Configuration window is done

    [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\Owner\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 'Mar  9 2014'.

    The library build time was '22:27:48'.

    The library package version is '5.1.450.0'.

    The library component version is '35.34.40.0'.

    The controller does not use a programmable FPGA.

    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 '-183' (0xffffff49).

    The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

    The explanation is:

    The controller has detected a cable break far-from itself.

    The user must connect the cable/pod to the target.

    [End: Texas Instruments XDS100v2 USB Emulator_0]

  • Hi Ashutosh,

    If this is a custom board that you have made, have you confirmed some other key (non-JTAG) portions of the board?

    For example:
    1) Is the device being powered correctly - is 3.3V and 1.8V being measured on both rails.
    2) Is XRSn being pulled high by a resistor?  Once the chip is powered, how does XRSn behave?  If things work correctly, it should pull XRSn low until it gets powered appropriately then go high.  (if the boot mode is set to flash and there is no code in flash, then additionally XRSn will occasionally toggle due to a watchdog reset)


    Thank you,
    Brett

  • This is odd! If its a brand new one then this test should pass without MCU connection. Can you try replacing the USB cable?
  • 1. At pin no 3 i.e XRS I am getting 3.3 Volt with continuous toggle pulse (i.e voltage is made zero)of duration 64usec . The time period between two pulses is 12.8 msec.

    2. Across crystall I am not getting pulses of 10Mhz. I am getting hih frequency distorted noise.

    3. Pin 32(VDD) and 43 (VDD) are connected to ground through 2.2 uF capacitor as internal regulator is enabled. However, at pin 32 and 43 I am getting 1.92 volt supply.

    4. Pin 34 VREGENZ is connected to ground to enable internal regulator.

    5. At pin 11 (VDDA) and pin 35 (VDDIO) i am getting stable supply of 3.28 Volt.  

    6. Pin No 10 (Vrefhi) and 12 (Vrefli) are grounded.

    Enclosed is the Connection Diagram of TMS320F28027 along with XDS100V2 Header pin. and scrren shot of the settings

    So Please advise If I am Wrong as i am getting error whileuploading prgram in flash of TMS320F28027 by using XDS100V2

    Error-1135 @0x0)

    The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. ( Emulation package 5.1.450.0

    My XDS100V2 is newly purchased

    Moreover, is it required to use ISO7220C between XDS100V2 and TMS320F28027 ???

    The XDS100v2 is written Spectrum Digital.
    It is recognized by Device Manager as TI XDS100 Channel A and TI XDS100 Channel B.
    USB\VID_0403&PID_A6D0&REV_0700&MI_00
    USB\VID_0403&PID_A6D0&MI_00

    TDI, TMS, TDO, TCK, and TRSTn are directly connected to F28027 pins without using isolator IC i.e ISO7220C.
    TRSTn is pulled down with 2k2 resistor.
    Boot switch is also implemented i.e In case XDS100V2 is not connected to Board through header, The GPIO 34 and 37 are pulled up to 3.3 volt using 2.2 kohm for Boot Mode

    As indicated in http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide  is it required to connect 22ohms series resister in TCK,RTCK and TDO near emulator header. If so how it is now possible to connect.

    Moreover when I connected GPIO34 to ground using 2.2k ohms resistor 

    The JTAG DR Integrity scan-test has suceeded.

    However, another error occured

    Case1 : I had tried to load the program in flash following error was displayed 

    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.

    C28xx: GEL: File: C:\ti\example3\GPIO\Debug\GPIO.out: Load failed.

    Case 2:: I had tried to load the program in Ram following error was dispalyed

    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: File Loader: Data verification failed at address 0x00008000 Please verify target memory and memory map.

    C28xx: GEL: File: C:\ti\example3\GPIO\Debug\GPIO.out: a data verification error occurred, file load failed.

    Input : supply rail at 3.3 Volt stable

    However, at XRS i am still getting toogle of 13 msec. This thing I am not able to elminate.

    THS XDS100v2 is new one.

    Please guide I am not able to solve since last two weeks.

  • Please find the enclosed connection diagram of TMS320F28027 and XDS100V2 14pin header pin

    I have changed the USB cable then also it is showing cable break error as it was earlier when when have disconnected 14pin header pin fromMCU. I think it is correct as we have disconnected the header pin from MCU

    Also my Target settings in CCS are follows

    Connection Type : Texas Instruments XDS100V2  USB Emulator 

    Board on Device : Exprimenter kit Piccolo TMS320F28027 or TMS320F28027 ( for both I had tried)

    3107.Connection Diagram of TMS320F28027.xls

  • Same thing is happening no change in error Please see the enclosed connection diagram and comment on it if it is correct or not The enclosed diagram is in breet lees reply
  • Connection diagram seems fine. My worry is XDS100v2 should pass without any connection to the target device. Can you check and verify the behaviour on another PC?

  • I don't have provision for another PC to test.

    Moreover, Please check connection diagram, are they correct.

    I am getting 3.1 Volt at the input instead of 3.3 volt,will it matter.

    GPIO 34 and 37 are not pulled up externally during emulator mode.

    Please check the enclosed diagram.

    Do I need Isolator between XDS100v2 and MCU 

    I am now helpless0045.Connection Diagram of TMS320F28027.xls

  • 1. XRX is toggling with constant frequency with time period 13 msec. This is I thnk watchdog reset. I think dose it creats problem while loading the program in flash using XDS100v2
    2.XDS100v2 has pass the test connection in target configuration with target connected.
    However, it is showing it is showing load fail 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.
    C28xx: GEL: File: C:\ti\example3\GPIO\Debug\GPIO.out: Load failed.
  • Replied to your other thread.

    Regards,
    Gautam
  • I find it depressing to read so many threads like this on the TI support forum that stop without any useful resolution from TI.

    I am now facing an issue that appears to closely match the one described in this thread, but I guess nobody out there cares.

  • Hi James,

    In some cases, the customer will jump their questions to another thread and get resolved in those parallel thread.  Also, in many cases we require a back-and-forth that does not always occur.  Finally, especially with custom boards we require the customer to manage a fair amount of the debug process.

    We also, despite our best efforts, fail occasionally.

    ===

    Regardless, please create a new post for the issue you are currently facing.  Link other threads in if you see a similarity.  Posting a new thread will ensure that you get responded to.

    Good luck in your project.


    Thank you,
    Brett


  • Please ground. Gpio34. Through 2.2kohms resistors and then remove it and connect to 3.3volt as suggestef

  • Hello Ashutosh Pailwan1,

    I'm facing a similar issue to flash the TMS320F28027. I've got (Error -1155 @ 0x0) Device may be operating in low-power mode. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).

    I've tried to lower TCLK and I still get the error. I followed the measurements that you described and all seems to be the same, one exception on XRS that does not toggle, just is pulled up in 3V3. The odd thing is that the XDS100V2 JTAG DR Integrity scan-test has suceeded.

    I used as well a C2000-Gang programmer and still can't flash the uc. The cable for JTAG is a Tag-Connect Cable with less than 3 inchs.

    Any advise on this kind of error?

    See bellow my schematic. I did based on TMS320F28027 Launchpad.

    Thank you!