RTEMS | bsps/arm/realview-pbx-a9: Fix Data Abort when accessing PL111 registers (#5523)

[Cibi P (@cibi_p)]

Cibi P created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5523



## Summary

While testing the framebuffer on the `realview_pbx_a9_qemu` BSP: A fatal source exception occurs during PL111 controller initialization. Find the log below.

[fatal_error.log](/uploads/328a7ca1445d61b035b75340834d8dfc/fatal_error.log)

## Steps to reproduce

1. Enable the Framebuffer driver in an application `#define CONFIGURE_APPLICATION_NEEDS_FRAME_BUFFER_DRIVE R` .  and open the /dev/fb0 in the application as `int fd = open("/dev/fb0", O_RDWR);` .
2. Run the application in QEMU using the `realview-pbx-a9` machine.
3. The system crashes at `pl111_fb_initialize()` When attempting to write to the `timing0` register.

**Root Cause:** In `bsps/arm/realview-pbx-a9/start/bspstarthooks.c`, the MMU configuration table defines the peripheral boundary at `0x10020000U`. Since the `.end` address in the ARM MMU setup is exclusive, the PL111 registers starting at `0x10020000U` are left unmapped, leading to a Data Abort.

**Proposed Solution:** Expand the MMU section to include the PL111 memory region.

## Expected behaviour

1. The ser should be able to open the /dev/fb0 file without any crashing.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5523
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/20260316/1e0f58c7/attachment-0001.htm>