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

Other Parts Discussed in Thread: TMS320F2812

Hi, 

     Am using TMS320F2812 custom kit with XDS100 USB V1 emulator , while running am getting following error

How should avoid these error and for what reason this kind of error will arise ???

C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located. (Emulation package 5.1.232.0)

Note: am using Code Composer Studio Version: 5.5.0.00077

Many Thanks, 

Thiyagarajan.S

  • Hi,

    while running am getting following error

    How should avoid these error and for what reason this kind of error will arise ???

    You get while entering the debug mode or while debugging?

    Regards,

    Gautam

  • Gautam, 

          while entering the debug mode...

  • Gautam , 

           I done Test Connection at Target configuration file, the following are test results........., i dont know what is report telling,. could you please explain....

    [Start]

    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\user\AppData\Local\.TI\693494126\
    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 'Aug 20 2013'.
    The library build time was '22:56:19'.
    The library package version is '5.1.232.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]

  • Did you check the voltage levels on your custom board? Are they fine or do they've any deviations? Also, check the component's health for eg. are any of them getting over-heated?

    Regards,

    Gautam

  • Hello,

    Is there any isolation chip in your custom kit?

    First of all, please make sure that your chip and your external XDS emulator get power properly.

    Best regards,

    Maria

  • Gautham & Maria, 

         I checked the Core voltage and IO voltage are correct. but my controller getting little heat.

    i dont know y so ????

  •      I checked the Core voltage and IO voltage are correct. but my controller getting little heat.

    i dont know y so ????

    Little heat should be fine but it should not be Burning heat!

  • Gautham & maria, 

                    what about my problem, how to solve it., yet am facing the same problem . please tell about Test connection report , which i posted in my previous post.

    Many Thanks,

    Thiyagarajan.S

  • Did you check your XDS100 emulator with any other kit? or do you've only one kit?

  • Gautham, 

                I Have only one kit, that too XDS100 USB v1 emulator in on board. 

  • I Have only one kit, that too XDS100 USB v1 emulator in on board.

    If I'm not wrong you had this issue previously and then you got it solved right? Again you're facing this issue?

  • Gautam, 

            From the test connection result. the following might be problem 

    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]------------------------

     

    please tell solution to sort out my problem...

    Many Thanks, 

    Thiyagarajan.S

  • Gautam, 

        This is new issues , i not yet faced this before....

  • I did check you're Test Connection results but I want to know more about the history of this board.

  •     This is new issues , i not yet faced this before....

    Ok, so this is the first time connection issue for a new custom board. So, first of all I would like you to go through this link:

    http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting_FAQ

    Regards,

    Gautam

  • Hello,

    Because this is custom board, it has many reasons why the Test Connection failed.

    I also made custom board (but with external XDS100v2 Emulator) and I faced problem that solved in this thread:

    http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/321906/1120577.aspx#1120577

    I used F28069 Control Card as the reference to make the connection between my board and External Emulator.

    Based on what you said, seems that you make your own XDS100v1 that is on board (not external like mine) into your custom board, is it correct or not?

    What was your reference when you made your board?

    Best regards,

    Maria

  • Also please confirm that your XDS100v1 is recognized by your PC.

    Best regards,

    Maria

  • Maria, 

         I checked in my PC Device Manager, At some times it recognize and sometimes its not.

    now again i checked the test Connection following are results;

    [Start]

    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\user\AppData\Local\.TI\693494126\
    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'.

    An error occurred while soft 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 '-151' (0xffffff69).
    The title is 'SC_ERR_FTDI_OPEN'.

    The explanation is:
    One of the FTDI driver functions used during
    the connect returned bad status or an error.
    The cause may one or more of: invalid emulator serial number,
    blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the emulator can be located.

    [End]

    Many thanks,

    Thiyagarajan.S

  • There seems to be some kind of loose connection on FTDI and USB part of the kit. Also I hope you've programmed the EEPROM of FTDI; if not:

    Q: Ok, I built an XDS100, but how do I program the EEPROM for manufacturing?

    • A: FTDI has a utility for this called MProg. See here.
    • A: For 28x development cards, you may want to see this [| post]

    Regards,

    Gautam

  • Gautam, 

           I cleared the XDS100 USB v1 Emulator problem , now it enable all the time at Device manager i checked, but yet am not able to debug, it prompt some error 

    C28xx: Trouble Reading Register PC: (Error -2130 @ 0x800) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)
    C28xx: Trouble Reading Register ST1: (Error -1041 @ 0xFFFFFF66) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.232.0)
    C28xx: GEL: Error while executing OnTargetConnect(): Target failed to read register ST1 at (ST1&~(0x0100)) [f2812.gel:286] at C28x_Mode() [f2812.gel:77] at OnTargetConnect() .
    C28xx: Error: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 5.1.232.0)
    C28xx: Unable to determine target status after 20 attempts
    C28xx: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
    C28xx: GEL: Target must be connected before calling the function

     

    I Dont Know what to do ?????, Kindy solve my issues please .., 

  • First of all I would like you to try with a simple sample code. Let me know if you still receive these errors.

  • Gautam, 

                   i even run the maths coding, without using any peripheral, again am getting the error , little heat in processor.

    Error : 

    C28xx: 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.232.0)
    C28xx: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)

    and i also done the test connection , i  pasted here results please where it fails., 

    [Start]

    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\user\AppData\Local\.TI\693494126\
    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 'Aug 20 2013'.
    The library build time was '22:56:19'.
    The library package version is '5.1.232.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 many-ones then many-zeros tested length was -16384 bits.
    The many-zeros then many-ones tested length was -16193 bits.

    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.
    Test 1 Word 362: scanned out 0xFFFFFFFF and scanned in 0xFDFFFFFF.
    Test 1 Word 363: scanned out 0xFFFFFFFF and scanned in 0x00070000.
    Test 1 Word 364: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 365: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 366: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 367: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 368: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 369: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 1, skipped: 0, failed: 1
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 2
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 3
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 4
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 5
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 6
    Some of the values were corrupted - 72.1 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.
    Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 1, skipped: 0, failed: 1
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 2
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 3
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 4
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 5
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 6
    Some of the values were corrupted - 85.4 percent.

    The JTAG DR Integrity scan-test has failed.

    [End]

    Please gautham, solve this issues as soon

  • again some error :

    C28xx: 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.232.0)

  • Ohh! Your JTAG integrity test itself is failing. There's a complete possibility that:

    1. MCU might've got damaged.

    2. Device is in a permanent lock stage.

    Overheating of mcu definitely points out towards the first possibility.

    Regards,

    Gautam

  • Gautam, 

                 I changed the processor and i powered and checked its not heated immediately,., then i started debug .,it entered debug successfully and i clicked the Run Button, suddenly i got the following error and device started getting heated ., for what possibility these kind of think will happen ??????????????????

    Error:

    C28xx: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)

     

  • Yes, indeed the MCU was damaged! Before placing a new one, you should've atleast checked the voltage levels on the board. I guess, even this mcu might've got damaged. Now before removing the mcu please check the voltage levels on the board esp. towards LDO. There's a possibility that LDO might have got damaged. Let me know what you observe.

    Regards,

    Gautam

  • Gautam, 

         This below  statement didnt understand , i dont know what is LDO., could you elaborate what i should do ???

    Now before removing the mcu please check the voltage levels on the board esp. towards LDO. There's a possibility that LDO might have got damaged. Let me know what you observe.

     

  • In short, check voltages in and around voltage regulator in power supply section.

  • Gautam, 

                 I not found any short in board , but when i start debug the project , processor getting heat and the processor damaged , i.e., processor VCC and GND short now, . again i removed the processor and attempting to solder new Processor., any checking points their to test, ? y this happening .,?

  • Don't solder the mcu until you find out the issue!

    processor VCC and GND short now

    Did you resolve this issue?

  • Gautam, 

              Once i removed the processor, the vcc and ground is not short.  so only  i attempt to solder the new processor. after soldered a new processor again i started debug the kit and again its started heat ...... 

  • Thiyagu, I would suggest you to get your board checked thoroughly by an expert. Don't solder the mcu until your board is cleared. There seems to be other shorts on the board if not between Power and GND.

    Regards,

    Gautam