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.
Part Number: TMDXLCDK138
Tool/software: Code Composer Studio
May be "Tools" forum is a more appropriate place to post a question but I can't reach it :)
Is it possible to connect an XDS110 debug emulator of Launchxl-CC1350-4 to a LCDKOMAPL138?
I've made wire connections between these two boards but I'm still receiving an error -233 while "Testing connection" and error -2131 when trying to start a debug session. EMU0/1 & RTCK are left unconnected. I also tried to alter a TCK rate from 100kHz to 2.5MHz.
Thanks in advance
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to desouza:
It's weird to hear this especially from you. About 2 years ago you posted a video on how to do it:
Moreover, I saw somewhere on this forum that XDS110 & XDS110v3 could connect to the omap and XDS110v2 couldn't.
In reply to Dmitry Kinyov59:
Finally, I've managed to connect the Launcpad's XDS110 debug probe to the omap's JTAG. The problem was connected to the RESET output signal which was in Hi-Z state when deasserted. But on the LCDKOMAPL138 board the respective RESET input tied to GND through 4.7kOhm resistor.
Probably, the special adapter has a pull-up resistor to 3.3V for this pin. But I did't have such an adaptor and connected these two boards with simple wires. That's why I have to add a pull-up circuit to the RESET pin.
I hope, this info can be usefull to others who want to use a Launchpad's XDS110 debug functionality.
I didn't face the problem connecting to the DSP core. Probably, the evolution of debug probes' firmware for the last 2 years played the role (I'm using CCSv9.0.1 & XDS110 fw ver. 126.96.36.199). There was an issue with the ARM core connection though. But I've managed to overcome it. I can connect to these two cores with a single button press ("F11" - start a debug session).
But what really makes me pain is the debug pace on the ARM core. Unlike the debug of the DSP core (each step executes almost instantly), stepping over (F6 key) a program on the ARM core is taking few seconds per each step.
I've compared it to the XDS100v2. The debug pace of the ARM core with this debug probe is much faster than with the XDS110 probe. Not as fast as the DSP core though but decent. I don't notice the difference in debug speed when changing the TCK clock limit.
For now we're considering purchasing an XDS100v3 debug probe. We expect to get a performance not worse than with the XDS100v2.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.