I'm doing a relatively intermediate FreeRTOS learning exercise with Tiva TM4C123GXL Launchpad from this site especially that Task_SPI_Transfer project.
forum.43oh.com/topic/9487-my-t…ertos-on-the-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
wiki.segger.com/TM4C123G_LaunchPad
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.
forum.43oh.com/topic/9487-my-t…ertos-on-the-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
wiki.segger.com/TM4C123G_LaunchPad
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.
The post was edited 1 time, last by ubermensch ().