RTEMS | testsuites/libtests/fdt01: Use own device trees (!1537)

[Sebastian Huber (@sebhub)]

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

Project:Branches: sebhub/rtems:up/fdt01-own-dts to rtems/rtos/rtems:main
Author: Sebastian Huber

## Summary

The test `fdt01` compiled the device tree sources of the `xilinx-zynqmp`,
`mpfs` and `microblaze_fpga` BSPs. It compared the blobs with copies in its
own headers. Commit b3a3b372fa8 added a PCIe node to
`bsps/aarch64/xilinx-zynqmp/fdt/zynqmp.dts` and did not update
`zynqmp-test-dtb.h`. The blobs differ since then, and the test stops at
`init.c: 410 rc == 0` on every BSP.

The test now has its own copies of the three device tree sources. Each copy
compiles to the blob of its header, so a change of a BSP device tree no
longer reaches the test. The headers keep their blobs.

## Test

| Check | Result |
| --- | --- |
| `fdt01.exe` of `i386/pc586-sse` on Qemu, on `main` at 6acc6402b78 | fails at `init.c: 410` |
| `fdt01.exe` of `i386/pc586-sse` on Qemu, with this commit | passes |
| `fdt01.exe` of `sparc/gr712rc` SMP with the POSIX API on SIS with two processors, with this commit on a downstream tree | passes |
| Blob of each copied `.dts`, compiled with `dtc`, against the array of its header | identical |

## 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 find the cause of the `fdt01`
failure and to make the test independent of the BSP device trees.  Each
change was directed and reviewed.

### AI model used

Claude Opus 5.5 (claude-opus-5-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 change were produced in that session under my
direction, and the commit message was 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/1537
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-4j5e5lxcm830a0qo13kfwcfk4-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/20261012/55eacae6/attachment.htm>