Naked IRQ #121

pca006132 · 2021-01-18T16:48:21+08:00

pca006132 commented

2021-01-18 16:48:21 +08:00

This fixes the compiler warnings by using only asm in the naked IRQ handler, and jump to our actual handler for IRQs.

It seems that the error introduced previously is due to EHABI expecting our non-naked handler to have a caller, and tries to unwind the stack, which causes interesting interrupts. (probably, I did not really dig into which line in the libunwind causes the problem, as I still don't know how to attach to a running core1 with openocd)

Addressing https://git.m-labs.hk/M-Labs/zynq-rs/issues/73. This fixes the compiler warnings by using only asm in the naked IRQ handler, and jump to our actual handler for IRQs. It seems that the error introduced previously is due to EHABI expecting our non-naked handler to have a caller, and tries to unwind the stack, which causes interesting interrupts. (probably, I did not really dig into which line in the libunwind causes the problem, as I still don't know how to attach to a running core1 with openocd)

pca006132 added 1 commit 2021-01-18 16:48:22 +08:00

9e8b554c6d runtime/kernel/core1: use correct ABI

sb10q reviewed 2021-01-18 17:00:58 +08:00

src/runtime/src/irq.rs Outdated

													
				@ -27,0 +43,4 @@

				            // save the SP and set it back after exiting IRQ

				            // exception unwinding expect to unwind from this function, as this is not the entrance

				            // function, maybe to IRQ which cannot further unwind...

				            // if we set the SP to __stack1_start, interesting interrupts would be triggered when