CCS/TMS320C6416: CCSv8.0 / CCSv3.3 / CCSv6.1

Hello,
This is usually a low level HW issue where the debugger is unable to read the device ID of the device on the target. See the below link for more details and suggestions:
software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

Hope this helps
ki

Hey Ki-Soo Lee..
tried sampling the communication between the debugger and the DSP to make sure the signals there pass with no significant interference and i gotta say.. they look pretty clean on my oscilloscope.. and with the correct I/O voltages required for operation with the TMS320C6416T ..
It seems like the integrity check is working flawlessly as well, not a single error indicated by the debugger "Test connection" with all the random signals being sent down the JTAG chain, they all go through the Jtag's DATA REGISTER and the Jtag's INSTRUCTION REGISTER correctly.
I even tried using another 3rd party product, It was a USB Blaster that i could get into very low levels of the JTAG chain with and see if it's responding as i expected.. when i fill the IR with 38 (Length of IR) '1's I do seem to have a Bypass DR (1bit Register). and I do manage to control the Tap machine using TMS and I can shift data in and out both the DR and the IR. so what could possibly be preventing me from managing to connect to my DSP .. 

PS: 

I have control over the EMU0 and EMU1 pins through code composer, and right now they are both set to HIGH-Z on my Debbuger.. could it be that i need to force a certain logic level on the DSP EMU pins to enter debug mode ?

Give that the low level JTAG connectivity tests pass ("Test Connection"), your connections are like ok.

Other past causes for the error you observe is invalid target configuration and also invalid GEL files - especially for custom targets. Is your C6416T board a custom board? Are you using a startup GEL file?

I tried using CCSv8 with a Blackhawk USB560v2 System Trace Emulator and was able to connect to my C6416T DSK without issue. I used the standard dsp641x.gel file and also tried without a gel file.

Thanks
ki

Hello Ki-Soo-Lee,

My tries have been only with a ccxml target configuration file without including a gel file since i have no project to load, i was first gonna try to connect to the DSP by launching the target configuration file and then "Connect to target" to have access to the memory space on the DSP.
I'm using a custom board, on startup of the board I have another processor upload the DSP's code into the DSP through the HPI. and after the device has started and everything is done i know my DSP is running code, and all i want to do is be able to see the L2 memory and Registers in assembly mode without having the load a project. my target configuration is 100% correct, it's a single component JTAG chain with only the TMS320C6416T in it and I have the right settings set for the debugger. Do i need to learn how to configure a Gel file to be able to Connect to the DSP? doesn't the Gel file run only AFTER you manage to "Connect to target" ? what else can i try to do to make this work? Can you give a brief explanation and possibly link me to an advanced guide of how the Gel file system works and how can I adjust it to my DSP and board to make it work correctly when trying to debug?

Thank you in advance, your reply is appreciated.

Akibdo Lamersi said:

I'm using a custom board, on startup of the board I have another processor upload the DSP's code into the DSP through the HPI.

Akibdo Lamersi said:

my target configuration is 100% correct, it's a single component JTAG chain with only the TMS320C6416T in it

So if I understand correctly, there is another processor, in addition to the C6416, and it is NOT on the same JTAG scan chain as the C6416? The C6416 is the only device/processor on the JTAG scan chain? What is the IR/DR length of your Test Connection results?

Akibdo Lamersi said:

doesn't the Gel file run only AFTER you manage to "Connect to target" ?

There is a call back function called StartUp(). Any actions in there get executed when the debugger is launched and before the target is connected. The actions in there do not (and should not) access the target. The most common use case for StartUp() is setting up the debugger memory map.

Akibdo Lamersi said:

Can you give a brief explanation and possibly link me to an advanced guide of how the Gel file system works and how can I adjust it to my DSP and board to make it work correctly when trying to debug?

See the below document:

http://www.ti.com/lit/an/spraa74a/spraa74a.pdf

Note that I don't think the GEL file is the root cause of your issue. As mentioned before, I can connect to a C6416T DSK without one. However, custom boards can be quite complex and require additional setup that a DSK would not. 

Have you ever been able to connect to you custom board in the past with any CCS version?

Thanks

ki

Hey again Ki-Soo Lee,

First, as an answer to your question - the ONLY device in the JTAG chain I've been trying to connect to is indeed the TMS320C6416T.

If i boot the DSP in Emulation mode by leaving the debugger's EMU0=EMU1=HIGHZ, Test connection gives : IR Length 38bit, DR Length is 1bit.

If I boot the DSP in Boundary-Scan-Mode by forcing the EMU0=EMU1='0', Test connection gives : IR Length = 8bit, DR Length 1bit. 

Second, what makes you think that it is not the missing GEL file that's causing this problem, you said those GEL configurations are important especially on custom boards so doesn't that contradict it?

Third, Yes I was able to Connect to a DSP on another custom board, although it was the TMS320C6414T (Same silicon revision as my TMS320C6416T) and that was not the same custom board at all but an entirely different product. with using only a CCXML Target Configuration file and simply selecting the "TMS320C6414" from the component list and selecting the Blackhawk XDS560v2 System trace emulator as my debugger i was able to do so.

And Last but not least, you said you were able to a C6416T DSK without a gel file. that is understandable, although I do want to ask just to make sure.. when choosing a processor from the list of processors that Code composer offers, you chose the C6416 as there is NO C6416T found in that list. or am I mistaken?

I have several custom boards which have the C6416T mounted on them and all of them give off the same type of error when trying to connect.

FYI : I'm using Blackhawk XDS560v2 System trace emulator although i have the BH-560-LAN and the Spectrum Digital XDS510 USB available to me as well.

I'm also using Code Composer 8.0 although i have CCSv6.1 and CCSv5.2 available to me as well.

I am able to connect to the custom board with the C6414T with all the Code composer versions i listed above but unfortunately none work on the C6416T.

Thanks a lot for your help it is very much appreciated, I hope we can find a proper solution.

Akibdo Lamersi said:

the ONLY device in the JTAG chain I've been trying to connect to is indeed the TMS320C6416T.

but are there other devices physically on the scan chain? Please provide the full output of the "Test Connection" results

Akibdo Lamersi said:

Second, what makes you think that it is not the missing GEL file that's causing this problem, you said those GEL configurations are important especially on custom boards so doesn't that contradict it?

The device ID error is a pretty low level one, likely not related to an initialization issue. That kind of error occurs pretty early in the connect stage, before any initialization is likely run.

Akibdo Lamersi said:

And Last but not least, you said you were able to a C6416T DSK without a gel file. that is understandable, although I do want to ask just to make sure.. when choosing a processor from the list of processors that Code composer offers, you chose the C6416 as there is NO C6416T found in that list. or am I mistaken?

Yes, there no specific option for the 6416T so I chose the standard 6416. That worked fine for me.

Also please attach the ccxml file you are using.

Thanks

ki