• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 839 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.

TMS320F280039C: LAUNCHXL-F280039C Error connecting to the target 2131

Ari Mendes
Intellectual 495 points

Part Number: TMS320F280039C
Other Parts Discussed in Thread: LAUNCHXL-F280039C, , C2000WARE

Hi, I have a project for the LAUNCHXL-F280039C that I was able to debug in the past. When I loaded the project again, compiled an tryed to load the code into the flash, a window show the error 2131, as figure below. I can debug others projects with the same board, and when I compare the configurations, I can't see any difference. What can it be?

I'm using the CCS version 11.2.0

Test Connection:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\ARI~1.SAN\AppData\Local\TEXASI~1\
CCS\ccs1120\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Mar 17 2022'.
The library build time was '15:43:48'.
The library package version is '9.7.0.00213'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
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 XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 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).

-----[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 XDS110 USB Debug Probe_0]

  • 0
    TI__Guru 50611 points

    Hi,

    In your project, please take a look target configuration, and make sure:

    • You are using CPU1_LAUNCHXL_RAM build configuration
    • TMS320F280039C_LaunchPad.ccxml is active.

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    Intellectual 495 points

    I'm using CPU1_LAUNCHXL_FLASH for both projects. The new one imported from F28003x examples the debugger works. TMS320F280039C_LaunchPad.ccxml is active in the same form both projects. Why on hell does one work and another does not?

  • 0 in reply to Ari Mendes
    TI__Guru 50611 points

    Ari,

    The non-working board was working before or it is first time you are trying?

    Can you check the boot-mode and make sure it is in 'Wait-Boot' mode and then try again?

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    Intellectual 495 points

    Hi, Santosh Jha.

    I'm using the same board for both projects. It's a Launchpad-F280039C. The non-working project alredy worked before, it started it from a drive library example, and followed the "F28003x Firmware Development Package" manual to add bitfield support. And I copied DCL,spll and others libraries to the project folder, I tried to do the project portable, outside from the directory "workspace_v11", but it still need that the C2000Ware_4_01_00_00 be installed to compile! 

    The difference from now to when it worked, is that I was compiling the project in another directory, I don't remember the name of the directory, because I copied the project from the network and placed it in any random local folder on the computer to compile for debugging. Maybe I missed the link with some file needed for debugging.

     I'm using the same CCS version, so it not a CCS version issue, when I test it in another computer and another Launchpad-F280039C, still the same debug problem. Is there a file or files relative to the debug that I can copy from the project that debug, to the project not debugging? Or some file path I need to pay attention to?

  • 0 in reply to Ari Mendes
    TI__Guru 50611 points

    Ari,

    Thanks for providing extra information. If it was working before, then probably it is booting from flash and there is some code in flash which is causing the issue. I will recommend to try the 'Wait Boot' mode. This way, it will not run any code from flash.

    Please refer to the User's Guide of the Launchpad for BootMode. Here is the link of the users guide.

    https://www.ti.com/lit/pdf/spruj31

    Thanks & Regards,

    Santosh