4 years, 9 months ago.

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

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-M4 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.

/media/uploads/omm/hardfault.jpg

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

posted by Omid Manikhi 20 Feb 2015
Comment on this question

1 Answer

4 years, 9 months ago.

OK, I found the problem! The issue was that the code I was using called a disable_irq() right before those instructions which I reckon resulted in HardFault exception!


Assigned to Omid Manikhi 4 years, 9 months ago.

This means that the question has been accepted and is being worked on.

You need to log in to post a question