XDS110ISO-EVM: XDS110 Debugger: No source available

Hello, here is some additional info from the 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\GERHAR~1.WOE\AppData\Local\TEXASI~1\
CCS\ccs1271\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 'Apr 19 2024'.
The library build time was '14:04:01'.
The library package version is '12.7.0.00130'.
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]

Gerhard

Hello,

It looks like the device is currently in an ITRAP ISR:

Source: TRM

Are you able to connect to the device successfully, view the memory contents (in the memory browser), and check if the program was successfully programmed? 

Best,

Matt

Hello Matt, thanks for the quick reply. I can not view the memory content. The memory browser does not show anything.

That is what I see when I try to start the program:

Hello,

Please type in the address in the memory browser, with the "Data" option configured in the drop down.

Gerhard Woelfl said:

That is what I see when I try to start the program:

Can you debug/step through the application and see what triggers the ITRAP? 

Best,

Matt

Hello Matt, that is what I see at 0x80000

Hello,

It looks like the codestart for the application was programmed correctly.

 Can you try stepping through your code (make sure not to step into the function calls) and see what line causes the error?

Best,

Matt

Hello Matt, I think we are close to the problem: On my hardware I used an external 50MHz clock oscillator pin 69 / X1 instead an quartz oscillator: Since I got the clock from another hardware part I didn't check it. Below you see at which function call I get into trouble. Is it possible to configure the µC to either an external 50MHz oscillator or just on the internal oscillator. I didn't find this in the system configuration.

Hello,

I think the 50MHz clock on X1 is the problem. As per the datasheet, X1 can only accept 2-20MHz from an external oscillator.

Best,

Matt

Hello Matt, thank you very much for the support and quick responses. It was very helpful  !!

Regards

Gerhard