Why flashing A_cpu-bootloader results updates in both versions of UEFI DTB

[user16748]

I’m running custom PCB with AGX Orin L4t 35.4.1
I’m seeing very similar error as ASSERT TerminalConIn.c(2078): ((BOOLEAN)(0==1)) and it turned out using a separate DTB for UEFI and disabling extra THS can eliminate the problem.
However one thing I don’t understand is why is that I only flashed with
-k A_cpu-bootloader and it fixed both A and B in UEFI?
Basically I confirmed I see problems in UEFI menu in both A and B before flashing. Then I flashed A, reboot, confirmed problem fixed in A, but also fixed in B if I switch to B.

What’s even weird is that even I reflash the “old bad” UEFI dtb after the test, which is the same as kernel DTB, which does not disable the extra THS, the problem does not re-occur.

Why is that?

[KevinFFF]

Hi user16748,

@user16748

-k A_cpu-bootloader and it fixed both A and B in UEFI?

It would only flash the bootloader partition in slot A.
Please also run the command again to flash it in slot B with -k B_cpu-bootloader.

Why flashing A_cpu-bootloader results updates in both versions of UEFI DTB

It is the expected result since the DTB is stored in UEFI binary.
You can find the following line in p3701.conf.common

UEFIBL="uefi_jetson_with_dtb.bin";