Friday, February 23rd 2018, 7:47am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Jan 14th 2018

Posts: 3


Sunday, February 11th 2018, 7:44am

Having Hard Fault in Tiva Launchpad FreeRTOS with J-Link but works fine in ICDI

I'm doing a relatively intermediate FreeRTOS learning exercise with Tiva TM4C123GXL Launchpad from this site especially that Task_SPI_Transfer project.…he-tm4c/?page=2

The problem is that whenever I'm using SEGGER J-Link EDU, I always end up with an undebuggable hard fault once I run it. I followed the setup and wiring for the launchpad to J-link from this website below

except for the 3.3V and GND which were pointed wrongly in the picture.

I have tried three test scenarios for that:

IDE - Eclipse Oxygen with GNU ARM Eclipse plugins; Debugger - J-Link
Result: Hard fault. The CFSR register points me to bus fault, precise error, but the instruction address is 0x40000 which contains absolutely no code. Other things that I've noticed is that a certain thread disappeared (thread #5) and this message appeared. I am attaching that picture.

IDE - TI CCS v6.2; Debugger - J-Link
Result: Hard fault. The CFSR register points me to imprecise error. Tried to reduce clock from 80MHz to 40MHz then to 20MHz. Nothing changed it's still imprecise hard fault.

IDE - TI CCS v6.2; Debugger - the default ICDI
Result: It WORKS! It should be since many people said it does (based on the forum). Strange....

What's wrong with J-Link here? I also want to note that in the first exercise in the webpage, about a LED blinking task, I was able to run it in all THREE CASES above with no problems. But once I insert a semaphore, like xSemaphoreTake() just like in the project I'm having trouble with, that's when the hard faults start to appear.

I can't settle with just TI ICDI; the reason I bought J-Link is because it's more universal, it has thread-awareness, and I can do a FreeRTOS tracing via SystemView. I can't do those things with ICDI. That's why I need help to fix this.

EDIT: Oops seems like I placed this in the wrong thread. Please transfer to J-Link forums if needed.
ubermensch has attached the following images:
  • hard_fault.png
  • before.png
  • after.png

This post has been edited 1 times, last edit by "ubermensch" (Feb 11th 2018, 7:50am)


Super Moderator

Date of registration: Jan 2nd 2017

Posts: 716


Thursday, February 15th 2018, 9:29am


*Thread has been moved to J-Link/Flasher related*

Thank you for your inquiry.
Such an issue is not known to us.
Generally J-Link will only execute tasks that the IDE tells him to do. So whatever the IDEs tell J-Link to do when you insert the semaphore will cause the hard fault.
Could you provide a J-Link log file of the session when the error appears?
Please understand that we can only give advice for SEGGER products. Eclipse, FreeRTOS and CCS are all not SEGGER products, so please get in touch with the proper support channels as this is most likely no J-Link issue.

Best regards,



Date of registration: Jan 14th 2018

Posts: 3


Friday, February 16th 2018, 2:33pm

Hi Nino,

Here are the logs as you requested. Hope that this helps. I hope that my suspicion about J-Link is wrong, since in my 3-case experiment the bug appears whenever J-link is present and being used.
ubermensch has attached the following image:
  • stack.png
ubermensch has attached the following files:
  • log1.txt (221.4 kB - 10 times downloaded - Last download: Yesterday, 9:03pm)
  • log2.txt (245.97 kB - 9 times downloaded - Last download: Yesterday, 9:04pm)
  • log3.txt (227.9 kB - 11 times downloaded - Last download: Yesterday, 10:55pm)


Super Moderator

Date of registration: Jan 2nd 2017

Posts: 716


Wednesday, February 21st 2018, 4:58pm


this issue has not to do with the J-Link itself but how IDEs are using J-Link.
Attached is an example project for the eval board created with Embedded Studio using the CPU support package manager:…gy/cpu-support/

You can also open the Ozone debugger project included in the folder:…-link-debugger/

Is the example project working on your hardware?

Does the issue happen only with FreeRTOS enabled?
Do generic projects work with the IDEs you try to use?

Should you still encounter hard faults take a look at our application note regarding hard faults to find out where they are exactly coming from:

Please understand that we can't put more time into this case as generally everything is working from a J-Link perspective.
Should the issues be realted to FreeRTOS contact the FreeRTOS support forum.

Best regards,
SEGGER - Nino has attached the following file: