triggering MEXT irq. is hanging freeRTOS demo #130
Replies: 1 comment 3 replies
-
The problem with FreeRTOS and external interrupts is that there is basically no unified interface for this. Many RISC-V cores have a core-local or platform-local interrupt controller connected to the "RISC-V external machine interrupt". These controller provide a more sophisticated interface for acknowledging interrupts. Furthermore, there is no "default" option in FreeRTOS that could be used to support NEORV32-specific interrupts like the FIRQs. I am working on a "plug-in" for the kernel, but somehow that got shelved... 🙈 Anyway, the NEORV32 I have tested the "blinky" RTOS demo with the external interrupt. In my test scenario In theory, even a permanent external interrupt should not crash the system - it should only stall it. However, it looks like a permanent external interrupt is causing a stack or heap overflow that finally crashes the kernel (tested with |
Beta Was this translation helpful? Give feedback.
-
I need help again please. I can't figure out why, but triggering MEXT irq. causes freeRTOS demo to hang after a while. I've changed only the uart baud to 115200 (but I admit that running it on 19200 makes it crash a little bit later), otherwise it is in original state, but I've tried to change stack size (to more) and it did not changed anything. My VHDL top looks like this:
I've tried to comment out everything in SystemIrqHandler too but it will crash eventually too. What can be the cause of this? Is it lacking context save/restore or something?
I'm sorry for flooding discussions section, but again I really have no clue what went wrong this time too.
Beta Was this translation helpful? Give feedback.
All reactions