• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 82 subscribers
  • Views 5138 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/TMS320F280049: C28xx_CPU1: Error connecting to the target: (Error -1135 @ 0x0) / Problem to access the µC

Gero Heuer
Prodigy 130 points
Part Number: TMS320F280049


Tool/software: Code Composer Studio

Hello,

i want to set up the new f280049- microcontroller-system but i have problems. I use CCS 8.1  with the XDS100v2 from SpectrumDigital. I created a simple "hello world"-program by using the c2000- resources "empty_bitfield_project".

I had some troubles with the powersupply of my PCB, so i am not sure if the f280049 isnt damaged(?). Until now i havent any access to the microcontroller. Additionally my pcb-layout from the JTAG-chain isnt updatet on the new stand:

 

I dont have the pullups on TMS,TDI and TDO because in our older f28069-project they wasnt needed. 

Now I am confused because the CCS target-connection test works fine,  but i cant flash the program to target:

[Start: Texas Instruments XDS100v2 USB Debug Probe]

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\GEHE~2.MTM\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 'May 30 2018'.
The library build time was '23:03:35'.
The library package version is '8.0.27.9'.
The library component version is '35.35.0.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 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 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 64 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 64 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 Debug Probe]

This works!

But everytime i try to debug (get access on µC) i get the following error-message:

C28xx_CPU1: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9) 

I have checked the correct project-settings:

And i have checked the correct GEL-file in the target configuration. My XDS100v2 also works fine with the f280049M-ControlCard. 

Did anybode know the Errorcode "Error -1135 @ 0x0" ?  And why do the target-connectiontest works without any fault?

best regards

gero

  • 0
    TI__Guru* 80600 points
    Gero,
    I'd like for you to try to launch the debug session manually vs using the "debug" button

    1)From the Target Configurations Window, right click on the ccxml you have created for this target and select "Launch Selected Configuration"
    -If this fails let me know the error code
    2)Assuming above worked, now right click on the C28x processor and click "Connect"
    -Note what happens here.

    Basically I want to remove all of the other things that the "debug" button does, like load the project, go to main, etc.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Prodigy 130 points

    Hi Matthew,

    first i tried the "Launch Selected Configuration":

    That works. 

    >>>> 2)Assuming above worked, now right click on the C28x processor and click "Connect"

    Here I dont find a possibilty to choose "connect" at right click. If i right click on the "C28xx_CPU1" or the "TMS320F280049", i only can choose "test connection". When i start the "test connection" the JTAG-targettest starts and finished successfully:

  • 0 in reply to Gero Heuer
    Prodigy 130 points

    I tried out the following (right click on XDS100v2 USB Debug.......C28xx........):

    and got this:

  • 0 in reply to Gero Heuer
    TI__Guru* 80600 points
    Gero,
    Thanks for doing this, it helps eliminate some issues.

    Next, I'd like to make sure that the device is in a state in which we know we can grab control reliably. So, let's configure the device in Wait Boot mode, GPIO24 tied low and GPIO32 tied high.

    On power up the device will go into Wait Boot, which goes into a known code loop from un-secure memory.

    If the device is not in wait boot, we could be executing from a secure region of memory, and if the emulator attempts to gain control while code is executing from these regions the connection will be terminated by the device.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Prodigy 130 points

    Hi Matthew,

    for this point I need some time, because the both boot-pins are not connected with any  PCB-wires. Our hardware-guys are very busy at moment, so I will reply again when the boot-pins are configured.

    Here is a part of my µC-schematic. I think the f280049 is connected correctly:

    Thank you very much for your help.

     

  • 0 in reply to MatthewPate
    Prodigy 130 points
    Hi Matthew,

    I am ready to check the next steps:

    >>Next, I'd like to make sure that the device is in a state in which we know we can grab control reliably. So, let's configure the device in Wait Boot mode, GPIO24 tied low and GPIO32 tied high.

    Thats done


    >>On power up the device will go into Wait Boot, which goes into a known code loop from un-secure memory.

    How can I see this?

    >>If the device is not in wait boot, we could be executing from a secure region of memory, and if the emulator attempts to gain control while code is executing from these regions the connection will be terminated by the device.

    How could I do this?

    The Boot-pins are configured and when I try to connect to the target there comes another error-code now:

    Error connecting to the target:
    (Error -1015 @ 0x0)
    Device is not responding to the request. Device may be locked, or the debug probe 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 8.0.27.9)

    Best regards

    Gero
  • 0 in reply to Gero Heuer
    TI__Guru* 80600 points
    Gero,
    Unfortunately there is no way to see that we are in Wait Boot mode, unless we are able to connect to the device. Doing this should have solved any potential problem with the CSM module or code issues.

    Is it possible for you to put a scope probe on XRSn and make sure that it is steady high(3.3V)? If we see a toggle/pattern that would be an indication that the WatchDog is timing out, and would drive a different debug.

    At the same time it would be good to check the levels on VDDIO/VDD/VDDA, etc just to make sure we don't have anything out of the ordinary.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Prodigy 130 points

    Matthew,

    we had checked the VDDIO/VDD/VDDA Levels und I scoped the XRSn Pin. The Voltage-Levels are ok. Here is a scope-pic from the controllerstart:

    (channel 1yellow=XRSn / channel 2  green= V_Supply)

    14ms after the Controllerstart the XRSn-Pin goes low. After that its stable at high. The Duration auf the XRSn-pulse is 56µs:

    But the Error when try to start connect the device is still:

    C28xx_CPU1: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9) 

    Maybe the µC is damaged (?)

  • 0 in reply to Gero Heuer
    TI__Guru* 80600 points
    Gero,
    Thanks for the plots, while we do see XRSn toggle, it shouldn't prevent us from connecting to the device through the JTAG interface. Do you have another F280049 device that you could replace the existing device on your board to see if indeed that there is damage to the MCU?

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Prodigy 130 points

    Matthew,

    ok, I will replace the f280049-Controller on my PCB. This will take some time. When I am finished i reply again.

    Tanks a lot for your help.

    Best regards

    Gero

  • 0 in reply to Gero Heuer
    TI__Guru* 80600 points
    Gero,
    Wanted to see if you had the opportinuity to replace the C2000 MCU and note any improvements?

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Prodigy 130 points

    Hello Matthew,

    unfortunately we had no time and capacities for the replacement of the µC. So I have to wait.

    I will post, when I have news

    Thanks

    Gero

  • 0 in reply to Gero Heuer
    TI__Guru* 80600 points

    Gero,

    I'm going to close the thread for now, please let us know what you find with regard to replacing the device.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Prodigy 130 points
    Hello Matthew,
    ok. I am still waiting for the new PCB. So, i will give you information later.
    Thank you
    Best
    Gero