# Getting Hardfault when trigerring interrupt in a task

**URL:** <https://forums.freertos.org/t/getting-hardfault-when-trigerring-interrupt-in-a-task/18704>\
**Category:** Kernel\
**Tags:** debug\
**Created:** [December 11, 2023, 7:57am UTC](https://forums.freertos.org/t/getting-hardfault-when-trigerring-interrupt-in-a-task/18704 "2023-12-11T07:57:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hs2](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@hs2](https://forums.freertos.org/u/hs2)\
**Post date:** [December 11, 2023, 8:20am UTC](https://forums.freertos.org/t/getting-hardfault-when-trigerring-interrupt-in-a-task/18704/2 "2023-12-11T08:20:57Z")

</div>

I guess your are using FreeRTOS API calls in your ISR(s), right ? Could you show the code ?  
Did you verify that the priority and FreeRTOS are configured correctly ?  
Did you enable configASSERT for development ? There are also assert checks in FreeRTOS catching wrong interrupt prios.  
See the FreeRTOS docs (in case you’re using a Cortex-M MCU as I suppose) [RTOS for ARM Cortex-M](https://www.freertos.org/RTOS-Cortex-M3-M4.html) and mabe also this post [Understanding priority levels of ISR and FreeRTOS APIs - #16 by aggarg](https://forums.freertos.org/t/understanding-priority-levels-of-isr-and-freertos-apis/10453/16) containing a good and easy to understand explanation using interrupts/ISRs with FreeRTOS.

---

_[View the full topic](https://forums.freertos.org/t/getting-hardfault-when-trigerring-interrupt-in-a-task/18704)._
