CCSv6 crashes when starting to debug with J-Link

Hi Pauli,

Is this because of there is not yet support for J-Link in latest CCS?

This seems to be the only valid reason. I would request you to go with CCS v5.5 which is readily available for download.

Regards,
Gautam

Hi Pauli - While we currently do not support J-Link with CCSv6, it is something that we are looking to officially support in future releases (don't have a concrete schedule yet). J-Link with CCSv6 is currently one of those "use at your own risk" type deals. Some have gotten it to works fairly reliability while others had no luck at all.

Can you provide a Crash Dump File and attach it to this thread? It can shed some light on the root cause of the crash and perhaps we can provide a workaround (if one exists).
processors.wiki.ti.com/.../Troubleshooting_CCSv6

Thanks
ki

Pauli Korhonen said:

The problem with this setup is that whenever I start debug session, the CCS crashes to desktop without any message. The code is first compiled successfully and the chip is erased but when CCS tries to download the firmware it crashes.

I have had similar crashes with J-Link under CCS 6.1 for Linux (https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/406782)

With J-Link under Linux one I found that instead of trying to start a debug session in CCS, was to use the following sequence:

a) In the "Projects" folder of the Target Configurations view locate the .ccxml file for the project.

b) In the Target Configurations view right-clock on the .ccxml file and select "Launch Selected Configuration".

c) In the Debug view right click on the "Segger J-Link Emulator_0/<CPU name> and select "Connect Target"

d) Use the Run -> Load -> Load Program menu and select the .out file for the project as the program file. This loads the program into flash and runs to main.

e) I was then able to successfully debug the program.

Maybe this work-around will also prevent your crash?

Chester Gillon said:

I have had similar crashes with J-Link under CCS 6.1 for Linux (https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/406782)

With J-Link under Linux one I found that instead of trying to start a debug session in CCS, was to use the following sequence:

a) In the "Projects" folder of the Target Configurations view locate the .ccxml file for the project.

b) In the Target Configurations view right-clock on the .ccxml file and select "Launch Selected Configuration".

c) In the Debug view right click on the "Segger J-Link Emulator_0/<CPU name> and select "Connect Target"

d) Use the Run -> Load -> Load Program menu and select the .out file for the project as the program file. This loads the program into flash and runs to main.

e) I was then able to successfully debug the program.

Maybe this work-around will also prevent your crash?

Thank you for your suggestion. I have followed it successfully to point d). Unfortunately CCS crashes immediately when I click OK on dialog for load program into flash.

Actually this is the same point where CCS crashes if I simply click "debug" and follow closely what is happening in any particular time. There is a dialog showing "Erasing flash" (or something like that) and then "Loading program into memory" (can't really read what it says as it crashes at the same time) and then CCS just disappears, no Windows nor CCS crash dialog.

There is, however, a crash dump created which I attached to this post. The first one, starting with c1a..., is a dump created by following Chester Gillon's suggestion. Second dump, starting with e34..., is dump created by simply clicking "debug". I believe thought that the reason for crash is in both cases the same. At least it is happening at the same point i.e. loading program into flash.
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/81/dmp.7z

same here with:

CCS 6.1.1 - Target RM48HDK
Win7 64Bit
JLink_V502f driver
CCS integration of jlink with www.segger.com/ti-code-composer-studio.html (Plugin)

CCS crashes when starting debug session (tested with simple blinky project)

Anny suggestions?

Thanks
Andreas

Hi,
exactly same problem
JLink_V510d
TM4C1230
CCS V6.1
still there is no solution?

Siyavash Asadi said:

still there is no solution?

According to the TI Code Composer Studio supported IDEs section of the Segger website, full support for J-Link is planned for CCS 6.2 March 2016.