To better understand your use case, could you please share the build command used for TF-A along with the boot log?

The build command: make PLAT=zynqmp DEBUG=1 bl31

The boot log you can find in the boot-log attachment file.

[destination_cpu = a53-0, exception_level= el-3, trustzone] bl31.elf

The error is different. You can find the log in the boot-log-bl31-elf attachment file.

[destination_cpu = a53-0, exception_level= el-3, trustzone, load = <load address of bl31>] bl31.bin

The error is different. It looks like the FSBL is not even able to start bl31. You can find the log in the boot-log-load attachment file.

Best regards, Michał Kruszewski

Sent with [Proton Mail](https://proton.me/mail/home) secure email.

On Tuesday, July 8th, 2025 at 1:35 PM, Belsare, Akshay akshay.belsare@amd.com wrote:

[AMD Official Use Only - AMD Internal Distribution Only]

Thank you [@Michał Kruszewski](mailto:mkru@protonmail.com) for reaching out.

To better understand your use case, could you please share the build command used for TF-A along with the boot log?

Also, could you please try once with the following update to bootgen.bif file

[destination_cpu = a53-0, exception_level= el-3, trustzone] bl31.elf

OR

[destination_cpu = a53-0, exception_level= el-3, trustzone, load = <load address of bl31>] bl31.bin

Regards,

Akshay Belsare

From: Michał Kruszewski via TF-A tf-a@lists.trustedfirmware.org Sent: Tuesday, July 8, 2025 3:29 PM To: tf-a@lists.trustedfirmware.org Subject: [TF-A] Context uninitialized assertion failure in xlat_tables_core for ZynqMP

Hello,

I want to boot Linux on ZynqMP (XCZU15EG).

I follow the standard procedure.

I have generated FSBL using Vitis.

I have compiled bl31 (tag: xilinx-v2025.1).

I have a standard boot.bif configuration looking as follows:

the_ROM_image:

{

[bootloader] fsbl.elf

[pmufw_image] pmufw.elf

[destination_cpu = a53-0, exception_level= el-3, trustzone] bl31.bin

[destination_cpu = a53-0, exception_level= el-2, load = 0x10000000] images/u-boot.bin

}

However, the bl31 reports the following error during the handoff to u-boot:

ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:788

BACKTRACE: START: assert

0: F_FUNCTION: 0x2880

1: F_FUNCTION: 0x4cac

2: F_FUNCTION: 0x2628

3: F_FUNCTION: 0x36e0

4: F_FUNCTION: 0x108

5: F_FUNCTION: 0xfffcd8e8

BACKTRACE: END: assert

This is an assertion for context being uninitialized in the mmap_add_region_ctx function.

/* Static regions must be added before initializing the xlat tables. */

assert(!ctx->initialized);

Does anyone have any idea what might be wrong?

Best regards,

Michał Kruszewski

Sent with [Proton Mail](https://proton.me/mail/home) secure email.