RTEMS | bsps/microblaze: Fix the test interrupt and add the CPU counter (!1451)

[Sebastian Huber (@sebhub)]

Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1451

Project:Branches: sebhub/rtems:up/microblaze-tm27 to rtems/rtos/rtems:main
Author:   Sebastian Huber



## Summary

Issue #5726: The BSP cannot raise a test interrupt and has no CPU counter

Three commits. The first probes the interrupt controller and raises the
interrupt through it where the probe succeeds. The second adds
`TM27_INTERRUPT_VECTOR_ALTERNATIVE` on the AXI UART Lite. The third runs the
second counter of the AXI timer as the CPU counter.

`spcpucounter01` turns red on Qemu with the third commit, for the reason the
issue gives. The test passed before only because the counter was a fiction.

The alternative vector is verified on Qemu only. Qemu raises the interrupt of
the device from the interrupt enable alone, while a real device raises it on a
transition of its FIFO. The family also covers real boards such as `kcu105`, so
that path needs a test on hardware.

**BSP** `microblaze/petalogix_s3adsp1800` · **Simulator** Qemu

## AI Details
<!-- Make sure you have read our statement at https://www.rtems.org/generative-ai/ -->

### Prompt used

None as a single prompt.  The work was done in an interactive Claude Code
session on the RTEMS tree.  The task was to run the test suites of the
simulator BSPs, diagnose every failure and fix the cause.  Each change was
directed and reviewed.

### AI model used

Claude Opus 5 (claude-opus-5), through Claude Code.

### How AI was used for the contribution

- [ ] Formatting
- [ ] Test creation.
- [x] Code comments.
- [ ] The entire contribution was generated using AI
- [ ] AI code completion such as Copilot in VSCode.

The diagnosis and the implementation were produced in that session under my
direction, and the commit messages were drafted there.

### Access

I have not used a product which claims copyright in its output, and I have
legitimate access to the one I used.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1451
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-77n8xkj9nwplxtrpkptz0bsxz-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


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