RTEMS | Implement MicroBlaze TM27 via AXI timer (!980)

Sam Price (@TheSamPrice) gitlab at rtems.org
Mon Feb 2 06:05:23 UTC 2026




Sam Price commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/980#note_140647


@joel 
I think this is causing issues with some tests and might not be a good option.

I am trying to run the CPU tests for the cpu usage api.
Part of the CPU use api is currently run under a test that needs the tm27 working properly for interrupts.

Feel like i am fixing 1 issue but causing others.

I could go in and patch qemu to allow for software driven interrupts and follow the spec outlined via xilinx.

```
*** BEGIN OF TEST RHILATENCY ***
*** TEST VERSION: 7.0.0.9deb5b8323b71d80ff221105da4ad675e24ceb98-modified
*** TEST STATE: EXPECTED_PASS
*** TEST BUILD: RTEMS_POSIX_API
*** TEST TOOLS: 12.4.1 20240905 (RTEMS 7, RSB no-repo, Newlib 038afec1)
Rhealstone: Interrupt Latency - -6

*** END OF TEST RHILATENCY ***


[ RTEMS shutdown ]
RTEMS version: 7.0.0.9deb5b8323b71d80ff221105da4ad675e24ceb98-modified
RTEMS tools: 12.4.1 20240905 (RTEMS 7, RSB no-repo, Newlib 038afec1)
executing thread ID: 0x0a010002
executing thread name: TA1
qemu-system-microblazeel: terminating on signal 15 from pid 2600736 (python3)
```

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/980#note_140647
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260202/caa06004/attachment-0001.htm>


More information about the bugs mailing list