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: ccs901 -> No register is present in the debug view, no .sysmem section in the cmd files and breakpoint hasn't been working.

Other Parts Discussed in Thread: TMS570LS3135, TMS570LS3137

Tool/software: Code Composer Studio

Hello there,

 

-> For the screenshots please see the case CS0037980:

warning #10247-D: creating output section ".sysmem" without a SECTIONS specification

 then:

For the HDK development kit TMS570LS31x ICE Board, with USB xds100v2 jtag I have chosen: TMS570LS3135 (not sure).

1. Does this match with the development kit?

When verifying the connection:

[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\fa\AppData\Local\TEXASI~1\CCS\ccs901\

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 25 2019'.

The library build time was '17:36:26'.

The library package version is '8.1.0.00007'.

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]

then when I would debug:

2. As I am not able to step through (see below), please let me know what I should to have the debug running on HDK board?

2nd round:

The only place where I’ve got linker files:

Current project configuration switched to TMS570LS3137, added the linker command file from above:

Now the linker file content is:

I have searched through the cmd files, no .sysmem section in any of the linker files.

Now when I am debugging:

The program doesn’t stop at the breakpoint.

  • Hello,

    All your screenshots did not get posted correctly. Can you try to repost them?

    Thanks

    ki

  • Hi Ki,

    Let''s see now.

    --

    Kind regards,

    Alexanderti.warning.sysmem.odf.pdf

  • Hi Ki,

    h_stm_v1.zip

    and the project as well.

    --

    KInd regards,

    Alexander

  • Thanks for the document with the screenshots.

    Your JTAG connectivity test passed, which is a good sign. You have good low-level communication with your board from CCS. Your target configuration (ccxml) file is likely fine also.

    The reason why you are unable to read the registers in the Registers view is because the target is running. If you halt the target, you will be able to see the Register contents.

    I loaded the example program you attached. The issue is that when the program is run (after load), it appears to hit some exception. When I disable "auto-run to main" and reload the program, the program is loaded correctly and the program counter is correctly set at the correct entry point (_c__int00 on line 190 of boot_non_cortex_m.asm). If you single step from this point, you will see that the issue occurs when trying to execute line 206 to clear the modes.

    I don't know why this is happening. But the root cause is likely due to either some issue with the application, or some target configuration issue. It is likely not a tools issue. I would suggest starting a new thread in the Hercules forum. The experts there can help debug this best.

    Thanks

    ki

  • Your follow up post was split off and moved to a new thread in the Hercules forum:

    https://e2e.ti.com/support/microcontrollers/hercules/f/312/t/813461

    the reason is because:

    Ki said:
    I don't know why this is happening. But the root cause is likely due to either some issue with the application, or some target configuration issue. It is likely not a tools issue. I would suggest starting a new thread in the Hercules forum. The experts there can help debug this best.

    I will close this thread since the original tools specific questions have been answered.

    Thanks

    ki

  • Hi Ki,

    Thank you for your support, for opening and referencing the new thread in this post.

    --
    Kind regards,
    Alexander