A while ago I tried to get the RPi4 into the seL4 CI due to how fragile the platform is. After some fixes/work I thought it was ready to go but then it got blocked on not working in release mode (https://github.com/seL4/ci-actions/pull/278).
seL4test would just hang in release mode. What seems to be causing this is the BCM serial driver as applying this patch fixes everything:
I don't know anything about GPIO and don't really have the chance to understand it right now so I don't know why this works. In fact, I don't even remember why I tried commenting out this.
Debug mode of sel4test does not make use of the actual serial driver (which seems weird in my opinion now that I think about it) which is why this issue only came up in release mode.
If someone more familiar with GPIO could take a look at this that would be great.
A while ago I tried to get the RPi4 into the seL4 CI due to how fragile the platform is. After some fixes/work I thought it was ready to go but then it got blocked on not working in release mode (https://github.com/seL4/ci-actions/pull/278).
seL4test would just hang in release mode. What seems to be causing this is the BCM serial driver as applying this patch fixes everything:
I don't know anything about GPIO and don't really have the chance to understand it right now so I don't know why this works. In fact, I don't even remember why I tried commenting out this.
Debug mode of sel4test does not make use of the actual serial driver (which seems weird in my opinion now that I think about it) which is why this issue only came up in release mode.
If someone more familiar with GPIO could take a look at this that would be great.