richard_damon wrote on Thursday, December 01, 2016:
The Heap Functions for FreeRTOS are not ISR safe, because they do not turn off the interupts for the full period they need to protect the heap (as that is likely much too long for many applications).
Allocating heap memory in an ISR is generally a bad idea, as the timing characteristics for a general heap are not good for an ISR (somewhat slow and unpredictable). Generally, it is best to pre-allocate the memory the ISR might need, and have it use that.
If you really need to use the heap in the ISR, then you will need to make your own version of the malloc wrapper which guards itself with a critical section (disable interrupts), and a second wrapper, as a xxxFromISR which has any needed ISR wraping (depends if the Microblaze port supports interrupt nesting). Note, this will cause a significant increase in worse case interrupt latency, which may be hard to detect, as it will be intermittent.