AnsweredAssumed Answered

osMutexDelete / osSemaphoreDelete result in a HardFault at "SVC 0".

Question asked by Omid Manikhi on Feb 19, 2015
Latest reply on Feb 20, 2015 by Omid Manikhi

Greetings!

I'm running the Texas Instruments SimpleLink driver ( for CC3100 ) which I have ported to the mbed platform on a FRDM-K64F board with a MK64FN1M0VLL12 ARM Cortex-M4F processor. Now at some point the driver which I'm running from my main() function tries to delete the Semaphores and Mutexes which it previously allocated. the problem is that this simple operation results in a HardFault. Now I am certain that these Mutexes and Sepmaphores are actually allocated.

I have stepped through the instructions and I can see that "svc 0" is where the HardFault is triggered.

xhardfault.jpg.pagespeed.ic.b_nxVSTMmZ.webp

Does anyone have any clues as to why this might be happening?? I would appreciate any help.

Outcomes