CCS/TM4C129ENCPDT: debug session not starting with fresh install of ccs 8.1 on macos mojave

Aaron Solochek

Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL, SEGGER, UNIFLASH

Tool/software: Code Composer Studio

I had been successfully using CCS8.1 on macos mojave for a couple of weeks and then let it update itself to 8.2. That broke the c++ indexing (I posted about that in a different thread) so I did a fresh install of 8.1.

When I attempt to start a debug session, using either my jlink, or my XDS100v2, the gui switches to the debug view, and whichever JTAG target I had selected shows up in the Debug window, but it does not connect to the device, nor load the code image onto the device. As I mentioned, I had previously been using 8.1 and it worked, but that install was originally 8.0 and was upgraded. When using the XDS100 emulator, I can "verify the connection" and that succeeds, but the debug session still won't connect and load the program.

Since everything was working a few weeks ago on 8.1, this feels like it's a configuration problem. I've looked through the preferences and don't see anything different from the settings on my working CCS installs.

Any help would be greatly appreciated.

over 5 years ago

0 desouza over 5 years ago

TI__Guru**** 168367 points

Hi,

Does the error message match one of the errors reported in the reference below?
software-dl.ti.com/.../ccs_debugging_jtag_connectivity_issues.html

Given that CCSv8.1.0 stock was re-installed and the "Test Connection" button works, I am suspicious that something may be going on with the common point of failure: the device or board.

I have Mojave installed in a host here and was able to talk to my EK-TM4C1294XL board with either Debug Probe: a XDS100v2 from Blackhawk and a Jlink v8.0. My CCSv8.1.0 is using the stock versions of the relevant components (TI Emulators 8.0.27.9 and SEGGER J-Link 6.32.0.0) and I also have CCSv8.2.0 installed in a different directory in the same host, thus I don't think it is a problem that was introduced to the OS by the newer release (a udev rule or other system-wide setting).

As a last idea, Mojave may have introduced a change that is affecting the ability to communicate only on some hosts - unfortunately, the fact that CCSv8.x releases were never tested on this OS reduces our ability to perform further validation at this time (CCSv8.3.0 will be fully tested on this OS).

Hope this helps,
Rafael

0 Aaron Solochek over 5 years ago in reply to desouza

Intellectual 280 points

I don't think it is a hardware problem because CCS 8.2 works, and uniflash works.

I don't get any error message, but that link looks helpful. I'm going to try manually launching the debug session and see what I discover.

Thank you.

0 Aaron Solochek over 5 years ago in reply to Aaron Solochek

Intellectual 280 points

I tested this, and I found the option for making the debugger automatically connect to the target when the debug session is launched, but when I go to run->load->load program the dialog isn't pre-filled in with the .out file for this project (in v8.1, it is in v8.2). Then when I click ok, I get a beachball for a couple seconds (that's normal when I'm using the jlink) and then CCS crashes. I've tried this twice with the same result. So I don't know what's going on, but hopefully it won't matter soon because v8.3 will be out and that will fix the c++ indexing, which is the only reason I'm trying to use 8.1 anyway.