Indeed that is strange. I don't see anything you are missing. Normally:
should be enough to enable the interrupts, but it looks like you are doing that.
The devil is often in the detail, and the problem may lie somewhere in the source code, the config.txt, be an issue with firmware revision, etc, so it is hard to diagnose the problem without full access to source code...
So I've provided a bare bones (complete) implementation, to show it working. If you can run that and it works, then you have a starting point that works, and an endpoint that is broken (your current code) and you should be able to gradually mutate one into the other, until you find out which change causes things to break.
Since it is 362 lines of code, I've created a gist on github for it, rather than copy/paste the whole thing here.
I've tested on a real Raspberry pi 3B, and under Qemu, and both work. Good luck!
Code:
msr daifclr, #2The devil is often in the detail, and the problem may lie somewhere in the source code, the config.txt, be an issue with firmware revision, etc, so it is hard to diagnose the problem without full access to source code...
So I've provided a bare bones (complete) implementation, to show it working. If you can run that and it works, then you have a starting point that works, and an endpoint that is broken (your current code) and you should be able to gradually mutate one into the other, until you find out which change causes things to break.
Since it is 362 lines of code, I've created a gist on github for it, rather than copy/paste the whole thing here.
I've tested on a real Raspberry pi 3B, and under Qemu, and both work. Good luck!
Statistics: Posted by pmoore — Tue Feb 20, 2024 2:18 pm