FreeRTOS on Microblaze - fast_interrupt vs interrupt_handler

npatel wrote on Tuesday, January 03, 2017:

I am working with microblaze and I can see the port is using the address 0x10 and one function to handle interrupts. This allows proper saving on stack etc. for the operating system.

If I wanted to use the fast_interrupt attribute, which simply jumps to the interrupt fuction instead of having to jump to 0x10 address, what do I have to do in the interrupt routine to allow for proper FreeRTOS compatibility. Would fast_interrupt method even be supported to run FreeRTOS?

The reason I am asking, is I can see in portasm.S the function “_interrupt_handler” is doing special saving and loading of stack, etc. Would I need to do this to support fast_interrupts?

Thanks in advance for all the help!

rtel wrote on Wednesday, January 04, 2017:

I have never done this so I’m not really sure, but I suspect if your
fast interrupt is not using the FreeRTOS API, or at least not attempting
to perform a context switch, then you probably don’t have to do anything
(other than ensure whatever resources are needed by the fast interrupt
are provided).