RTEMS | bsps/mips/malta: Fix the reset and quieten the PCI probe (!1455)

[Sebastian Huber (@sebhub)]

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

Project:Branches: sebhub/rtems:up/malta-reset to rtems/rtos/rtems:main
Author:   Sebastian Huber



## Summary

Issue #5730: The board never resets and the PCI probe prints at every boot

Two commits. The first writes `0x42` through a `volatile` pointer to the
uncached alias of the software reset register. The second puts `print_bars()`
and its calls under `DEBUG_PCI`.

With both, a test on Qemu prints its own output and nothing else, reaches the
end of test line and exits with status zero. `bsp_reset()` compiles to the
three instructions which the store needs:

    lui v0,0xbf00
    li  v1,66
    sw  v1,1280(v0)

Qemu exits on the reset because the runner passes `-no-reboot`. A board which
reboots instead needs no change here, because `0x42` is what the register
takes either way.

**BSP** `mips/malta` · **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/1455
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-d9ptavsr0wxl9911gtufvr9wz-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/73850ff1/attachment.htm>