Assert on locking mutex in ISRhttps://devzone.nordicsemi.com/f/nordic-q-a/108679/assert-on-locking-mutex-in-isrHello, I&#39;m facing the assertion error because some part of the code tries to lock the mutex from the ISR context. I would like to hunt this ISR down, the xpsr from the assertion log is 0x41000025 but I&#39;m not able to map this 0x25 to the ISR. Where canen-USTelligent Community 13Tue, 27 Feb 2024 09:44:48 GMTRE: Assert on locking mutex in ISRhttps://devzone.nordicsemi.com/thread/470965?ContentTypeID=1Tue, 27 Feb 2024 09:44:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8424c6d5-37f4-4c72-b882-9dc1b12af74fSusheel Nuguru<p>Enable these in your prj.conf to get more details on the assert.</p> <p><pre class="ui-code" data-mode="text"># Debugging configuration CONFIG_THREAD_NAME=y CONFIG_THREAD_ANALYZER=y CONFIG_THREAD_ANALYZER_AUTO=y CONFIG_THREAD_ANALYZER_RUN_UNLOCKED=y CONFIG_THREAD_ANALYZER_USE_PRINTK=y # Add asserts CONFIG_ASSERT=y CONFIG_ASSERT_VERBOSE=y CONFIG_ASSERT_NO_COND_INFO=n CONFIG_ASSERT_NO_MSG_INFO=n CONFIG_RESET_ON_FATAL_ERROR=n CONFIG_THREAD_NAME=y</pre></p> <p>I think might have just implemented some callback function that is being called in the isr context from the driver. You are the best to know which callback function you just implemented/enhanced before getting this error.&nbsp;</p><div style="clear:both;"></div>