IAR constantly crashing with TM4C1294XL launchpad

Yes, that would be great, thank you!
For using a J-Link, could you also provide me with some guidance on how to actually connect it to the Launchpad? Are there any additional jumper configurations as well?

You, Sir are most welcome.

Perhaps best that I start w/the set-up for your board's "ICDI." Firm/I have never used this vendor's 4C129 yet the set-up under IAR should be very similar. I'm just leaving client now - will be few hours before I can respond - and I will...

Hello Robert,

I have used IAR with ICDI without any issues. I am not promoting ICDI over J-link but ensuring that we do not overlook something in the code.

Is the application code using JTAG pins for GPIO or using the SysCtlClockSet function? Is the ICDI configured with the correct JTAG TCK frequency?

Regards
Amit

Is the application code using JTAG pins for GPIO or using the SysCtlClockSet function? Is the ICDI configured with the correct JTAG TCK frequency?

I would consider an issue with the debug pod driver as well (i.e. the Win7/Win10/MacOS/Linux driver for the USB device). Perhaps there went something wrong during installation.

At my PC here, a J-Link and a ICDI (Launchpad onboard) work both flawlessly - under IAR WB 7.30.

Hello f.m.

I can double confirm that with both J-Link and ICDI being used for a two board communication debug

Regards
Amit

Thanks everyone for your input.

I can confirm that I am not using any JTAG port pins in my build and my system clock is maxed at 120MHz, so I don't think those are the problems.

To further verify that, I have tried loading and running the "blinky" example from TivaWare to see if the debugger has the same issue. I had the same exact problem. The program would compile just fine and when I clicked download and debug it would download successfully as well. The problem occurs when after downloading I click run or singe-step in the debugger and IAR freezes/crashes. If I then reset the target device, the program starts running correctly; I can see the LED blinking.

So, it really seems like something is wrong with the debugger or the drivers for it. I tried downloading the latest "Stellaris"  drivers and loading them via Window's device manager, but that has not yielded any better results.

I have J-Link laying around somewhere that I would like to try. I'm just not sure how to hook it up to the Launchpad. Do you have any guidance on how I could try that? I see on the Launchpad some empty via labeled as X1. I'm wondering if I need to solder into those.

Amit,

You also asked "Is the ICDI configured with the correct JTAG TCK frequency?" I don't actually know what the correct JTAG TCK frequency is. When I look at the TI Stellaris options in IAR I see that the JTAG/SWD speed is set to 500kHz. Is that correct?

Hello Robert

Yes, 500KHz is fine. Also does the driver come up correctly on your PC? Did you try another PC?

Regards
Amit

Robert Lane said:

I have J-Link laying around somewhere that I would like to try. I'm just not sure how to hook it up to the Launchpad. Do you have any guidance on how I could try that?

U6 on the EK-TM4C1294XL is a connector which can be used for an external debugger. U6 is a 10-pin .05 inch pitch connector and you need an adapter such as ARM-JTAG-20-10 to connect the EK-TM4C1294XL to a J-Link.

See also Orientation of U6 External debug connector on EK-TM4C1294XL is not clear

Amit, as far as I can tell the driver comes up correctly in that device manager says that it is running properly. I have not tried a different PC with this Launchpad. As soon as I can track one down I'll let you know.

Chester, thank you for your response. I'm not sure if I have an adapter like that anywhere, but I will try to find one.

Ok, an update. So I tried the same Launchpad on a different PC and loaded the same blinky program from TivaWare 2.1.2.111 and it ran completely fine and IAR had no problems with the debugger.

Also, I got a new Launchpad and fresh from the box I connected it to my PC and tried to load the blinky program. It compiled and built just fine, but as soon I clikced "download and debug" I got a warning about loading the debug file. After that IAR froze and was not responsive. It never completed or even started the download.

It's really starting to look like something is wrong with my PC. At this point I can't tell if it is IAR itself, the drivers or even Windows.
Any more input or suggestions would greatly be appreciated. Thanks.

One more update. I have a J-Link with a 20-10 pin adapter and tried using it with IAR and the Launchpad. Everything works! I was able to download the blinky program and step through it just fine with the debugger.

This really makes me think that there is something wrong with the ICDI driver.

It's really starting to look like something is wrong with my PC. At this point I can't tell if it is IAR itself, the drivers or even Windows.
Any more input or suggestions would greatly be appreciated. Thanks.

Not that I'm a real expert in the PC area - but USB always involves an internal USB hub, with a driver supplied by Microsoft, the motherboard vendor or whoever. If this driver is unstable, or contains bugs, all dependent drivers (like the J-Link or ICDI driver) will have issues.

You can try to update this motherboard drivers, or try to connect your debug pod to a different USB port. Most PCs/motherboards contain several those USB hubs, or at least two, often different one's. If you are lucky, the other driver is more stable.

In my last company, I had a (Win7) PC that ran into Bluescreens, a few seconds after a simpe USB-to-serial adapter was utilized...

f. m. said:

Not that I'm a real expert in the PC area - but USB always involves an internal USB hub, with a driver supplied by Microsoft, the motherboard vendor or whoever. If this driver is unstable, or contains bugs, all dependent drivers (like the J-Link or ICDI driver) will have issues.

You can try to update this motherboard drivers, or try to connect your debug pod to a different USB port. Most PCs/motherboards contain several those USB hubs, or at least two, often different one's. If you are lucky, the other driver is more stable.

In my last company, I had a (Win7) PC that ran into Bluescreens, a few seconds after a simpe USB-to-serial adapter was utilized...

Since the J-Link appears to work just fine and I have tried different USB ports, including a separate powered USB hub, I would doubt its the Windows drivers. But then again, it is Windows so you never know. 

Since the J-Link solution has got me back on track, I will continue with it. If I come across any thing that allows me to use the ICDI again, I'll try to pass it along.

cb1- said:

There are (very) low cost, "Segger, J-Links" which perform extremely well w/IAR & such boards.  

Appears this (very) early response correctly diagnosed your issue!

Vendor's low cost ICDI (attempts) cannot compare w/REAL JTAG/SWD pods - designed by those w/LONG Focused expertise.