Debugger connection problem TMS320F28377D.

Hi Mubin,

Any changes you made on the controlCard or docking station? Also, did you restarting CCS/PC?

Regards,
Gautam

Hi Gautam,
I did not any change in controlCard. I have check by restarting CCS/PC. Getting same problem.

Regards,
Mubin Qadri.

Check the voltage levels on the card and docking station. Compare them with schematics... Check for any deviation.

Regards,
Gautam

I have already check voltage levels.
Regards,
Mubin Qadri

Hi Gautam,
Any suggestion? i am new on this platform and now i am stuck on it.
Thanks and regards,
Mubin.

Mubin - Have you looked at the wiki article I posted? Your issue is more of a memory access issue than a connectivity issue.

ki

Hi Ki,
I have seen the article but i didn't understand how to solve this memory problem. I am first time using CCS and new on this platform.
Thanks & Regards,
Mubin Q.

The article is basically saying that the issue lies somewhere between an invalid linker command file, invalid debugger memory map, or target initialization file. I can't say what the particular issue in your case is because I don't have any details other than a screenshot of your error message. Can you show be a full screenshot of CCS when the error occurs?

Hi Ki,

PFA

regards

Mubin.

Hi Ki,
Any solution?
Regards,
Mubin

Can you zip and attach your outfile? I would like to see if I can load it on my F28377D target.

Thanks
ki

Hi Ki,

PFA zip folder of out file.

usb_dev_serial_cpu01.rar

regards,

Mubin.

Hi Ki,

PFA of zip folder of outfile.

usb_dev_serial_cpu01.zip

regards,

Mubin.

hi ki,
have you try my out file? any progress?
Thanks & Regards,
Mubin.

Yes, it loads fine for me.

Can you try this ccxml file?

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/81/F2837xD.ccxml

Thanks

ki

hi ki,
I have tried your target configuration file and i am getting same error.
thanks and regards,
Mubin.

is my controller memory damaged? or else?

thanks
mubin.

So far this is what we confirmed:
-Your program is fine
-Your target config file is fine

It looks like your hardware environment has some issue.

Can you run the "Test Connection" button and post the results?
processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

Thanks
ki

hi ki,
Below is screenshot of test run

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

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\mubin.q\AppData\Local\TEXASI~1\
CCS\ti\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 'Dec 11 2014'.
The library build time was '17:05:59'.
The library package version is '5.1.636.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 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 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.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]



Thanks,
Mubin.

Hi ki,
Any progress?

Thanks,
Mubin.

hi ki,
Any solution for my problem?

Thanks and Regards,
Mubin.

Hi Mubin,

Sorry for the delay in response. I don't know what the cause of the issue is. Your program is fine since I can load it with no trouble. You used my ccxml file which works for me but it did not work for you. Your basic JTAG connection is fine.  Since this used to work, something may have happened to your board. Can you try using a different project from controlSUITE. Perhaps the blinky project in the first lab of the 28377D workshop here. See if you can get that project to load. That is supposed to work out of the box.

ki