[PATCH] test: do not write to 0x0 except on sandbox

[Tom Rini]

On Wed, Nov 05, 2025 at 07:07:47PM +0100, Heinrich Schuchardt wrote:
> ARM and RISC-V do not have memory at 0x0.
> On X86 interrupt vectors are stored at 0x0.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt at canonical.com>
> ---
>  test/cmd/fdt.c      | 4 ++++
>  test/common/print.c | 8 ++++++--
>  2 files changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/test/cmd/fdt.c b/test/cmd/fdt.c
> index 96a8488e172..6b07999c88f 100644
> --- a/test/cmd/fdt.c
> +++ b/test/cmd/fdt.c
> @@ -269,6 +269,10 @@ static int fdt_test_move(struct unit_test_state *uts)
>  	uint32_t ts;
>  	void *buf;
>  
> +	/* This test requires low writable memory */
> +	if (!IS_ENABLED(CONFIG_SANDBOX))
> +		return -EAGAIN;
> +
>  	/* Original source DT */
>  	ut_assertok(make_test_fdt(uts, fdt, size, &addr));
>  	ts = fdt_totalsize(fdt);

In one of those "what is even going on?" moments, just out of context we
set newaddr to 0x10000 and then "fdt move addr newaddr ts". Loooking at
my logs for am62x_beagleplay_a53 where memory is not at 0x0, this test
is currently running and passing. I'm going to fire the platform up and
poke now.

> diff --git a/test/common/print.c b/test/common/print.c
> index 76ee851fe6a..389d6bf4069 100644
> --- a/test/common/print.c
> +++ b/test/common/print.c

These tests are also running and passing on am62x_beagleplay_a53 I see
in that same log.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20251105/aa6f5c8f/attachment.sig>