MSP430FR2675: Is use of `assert` safe inside interrupt service routines?

Hello,

Let me check on this.

Hi pcpro178,

I haven't been able to track down anyone that can provide a for sure answer.  Give me another day to track down someone who has some experience with this and can comment.

Hi pcpro178,

No luck finding an answer to your question.  Let me keep looking.

Thanks.

Based on the suggested post, it sounds like the only drawback to using the factory-supplied `assert()` inside of an ISR is that it will consume a lot of memory.

The assert function in the MSP430 run time library for the TI compiler ends up calling fprintf to output an error string containing the file name and line number where the assertion failed. That would be OK for a PC program, but will require an excessive amount of code / data memory in a MSP430 device.

My understanding is that functions like fprintf, depending on implementation, may dynamically allocate memory by calling `malloc()` and that malloc is not necessarily thread safe.   I see that the CCS tools implementation of assert uses fputs.  Can you speak to the usage of TI's implementation of fputs and malloc inside of an ISR?

Last I looked, the printf "core" (__TI_printfi()) didn't use malloc. I don't know about the I/O functions.