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.

C28xx: Error connecting to the target: (Error -1041 @ 0xFFFFFF4C)

Other Parts Discussed in Thread: TMS320F28027, CONTROLSUITE

I'm using Piccolo controlSTICK TMS320F28027 MCU. I'm new to CCS.
I was able to blink the LED using the example code provided but now with the same code and configuration I'm getting below error, please help me debug this error.

 

C28xx: Error connecting to the target: (Error -1041 @ 0xFFFFFF4C) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.73.0)

C28xx: Error connecting to the target: (Error -180 @ 0x0) The controller has detected a target power loss. The user must turn-on or connect the power supply for the target. (Emulation package 5.1.73.0)

-------------------ERROR LOG------------------------------------------------------------------------------------------------------------

[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\OMPRAK~1\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 'Apr  1 2013'.

The library build time was '23:55:08'.

The library package version is '5.1.73.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 '-180' (0xffffff4c).

The title is 'SC_ERR_CTL_NO_TRG_POWER'. 

The explanation is:

The controller has detected a target power loss.

The user must turn-on or connect the power supply for the target. 

[End]

-----------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------

---------------------------Test connection CCSv5 with Piccolo control stick is successful LOG:----------------------------

 

[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\OMPRAK~1\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 'Apr  1 2013'.

The library build time was '23:55:08'.

The library package version is '5.1.73.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.

--------------------------------------------------------------------------------------------

General Setup:

connection - XDS100v2 USB Emulator

Device Controlstick Piccolo F28027

created .ccxml  is linked to active project.

 

 

  • Hi!

    Compare your project proprities(configurations) for your working and no working cases. What's the differences?

    Regards,

    Igor 

  • Hi,

    No Changes in the configuration for working and not working cases.

    -----------------------------------

    Piccolo controlstick(USB) is connected to PC.But when I'm trying to "Find all connected XDS560V2 USB emulators" from "Sd560v2Config", i'm getting no emulators connected.

     

    Spectrum Digital Configuration Utility

    Supports:

    XDS560V2 USB

    @BEGIN-7

    MSG: NO EMULATORS CONNECTED

    @END-7

    ---------------------------------------------------------------

    server Application  :  C:\ti\ccsv5\ccs_base\commin\uscif

     

     

     

  • Hi!

    Did you try reloading for PC and for your target device?

    Regards,

    Igor

  • reloading for PC??

    I have tried restarting my PC, reinstalling the USB drivers of Piccolo control stick, changing the target configuration -->general setup.

    But how to debug, if there is issue with my target board??

    I'm confused like is this the issue related to target device or software.
    In this target device im not able to see LED(LD1) glowing when i'm connecting the target device to PC.
    Target device is getting detected but not able to connect emulator.
    with target device connected or Disconnected :: when I run "Test connection" i'm getting same log.

     

    C:\Users\~1\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]

    ---------------------------------

  • Hi!

    It seems there is some uncertainty. What USB emulator driver do you use : XDS100v2 or XDS560V2?

    Regards,

    Igor

  • sorry for late reply.

    The USB emulator driver is XDS100

    ------------------------------------

    From Utility:

    Spectrum Digital Configuration Utility

    Supports:

    XDS560V2 USB

    ------------------------------------------
    General setup:

    I'm using Texas Instruments XDS100v1 USB emulator.
    I'm just loading the examples I got from control suite, with these examples TMX320F28027.ccxml is also provided.
    I'm just linking this to the active project.

    Board or Device : Controlstick - PICCOLO F28027.

     

  • Ok! I see...

    1 When do you have error message "C28xx: Error connecting to the target" from CCS - when you try to run DEBUG of project?

    2 Did you try to look for your USB emulator connection at the System device manager of PC? It must be there when your target device is at power-on state.

    3 Try reinstall CCS and then XDS100v1USB driver and load some example project from controlSUITE again.

    Regards,

    Igor


  •  

    1ANS: After building the project when I try to Run->debug, I'm getting the above error.

    2.sorry, USB driver was XDS100v1USB only.

    3.Tried already, it is coming same error.

    Note: with the same setup I was able to Blink the LED. Now device is not getting detected.

    Qun: target board is getting heated. LED(LD1) not turning ON.How to check hardware is working properly or not?

  • Hi!

    I'm afraid that your device is damaged. But this is unlikely to it happen spontaneously. Do your device has only one LED. There are usually two LED : one indicates power-on and another indicates USB-connection. And what about power supply source? Could you mix up the polarity or the voltage?

    Regards,

    Igor

  • Hi Igor,

     

    There are 2 LED's one indicating power on and another is connected to GPIO34(Pin30,LED).I was blinking the same before the issue :(
    power supply is from PC USB port. From target board regulator I'm getting 1v output, Is it correct or regulator is gone?

    I know that it should not but,If I connect target board for more than 6hrs continuously, will it get damaged :) ??

    I was checking GPIO pin 34 ON/OFF by connecting CRO probe wire red to PIN34 and black(gnd) to PIN32.Leaving this I have not done any thing on target board.

    any suggestions on why board have gone bad?? 

     

  • Hi!

    Duration of connecting state device has not effect.

    Did I understand you right? Has your target device the power supply from USB dirctly? Point is that USB-bus provides +5VDC and moreover 1VDC insufficiently for power supply of MCU (it need ~3.3V). What voltage is on regulator input?

    Regards,

    Igor

  • yes .we both are on same page :).
     The regulator input is 5v (from USB port)but the output is 1v.
    But chances of regulator not working are very less right, as the supply given is 5v ?

    Note:output of regulator is going to LED(LD1) and supply to F28027 controller.

    If LED(LD1) is damaged after regulator, is there any chance like regulator o/p will show 1v?

     

  • Hi

    Could you locate an element that heats up (MCU, regulator or something else)?  I think if LD1 is damaged then it is not effect to output regulator voltage, because the chances are the LD1-chain contains limitative resistor and short circuit is not possible. On the other hand, if the heating and high drop voltage take place then it means that the current consumption increased, i.e. there is a short circuit somewhere, after all. And the LD1 is off because there is not enough voltage.

    Regards,

    Igor

  • Hi Igor,

    thanks for giving more clarity.

    Regulator is getting heated very fast in 10 to15 sec.

    F28335 controller, FTDI f2232D is getting slightly heated after 10 min.

    so what is causing short circuit?

  • Hi!

    Now of course the most right thing to test the regulator without load (MCU etc.). But perhaps all is soldered on the PCB. Or is there a possibility to separate regulator and the load yet?

    Regards,

    Igor

  • Hi Igor,

    yes its all soldered on PCB.

    there is chances like MCU might have been short and then MCU pulling current due to this regulator getting heated??

  • Hi!

    Maybe...Maybe...But what could cause a short circuit into the processor or on its pins? Did you connect anything to pins? It is very strange if the device was connected for 6 hours without some influence and then suddenly it breaks down spontaneously. Although sometimes it happens: http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/269504/942143.aspx#942143

    Regards,

    Igor