I know of someone who has run this BSP on hardware and I'm not aware of
any usage with xen (though it could very well be the case). It really
needs more documentation which is something I guess I should sit down
and do at some point. The ILP32 AArch64 BSP isn't a direct replacement
for this BSP since ILP32 is still AArch64 but using the ARMv7 data model
instead of the full 64-bit data model that AArch64 typically uses.
The secret to using this BSP is to know that JTAG boot mode/application
loader pokes some bits that the FSBL does not poke by default, so if
you're going to configure it to boot from media in BOOT.bin instead of
JTAG then you also need to bundle in the ARM Trusted Firmware (ATF) bl31
binary.
This bit of information also applies to the aarch64/xilinx-zynqmp BSP,
but starting recommendation for that is to use the prebuilt u-boot
BOOT.bin which includes the ATF bl31 binary and so it isn't critical
knowledge for getting started.
Kinsey
On 9/7/2021 13:19, Gedare Bloom wrote:
Hi Chris,
What I understand about the arm/xilinx-zynqmp BSP is that it was made
to run RTEMS paravirtualized under Xen. It drops into aarch32 mode. It
probably can be replaced by the aarch64 version using the ilp32 once
that is stable, and someone can confirm the PV use case works.
Gedare
On Fri, Sep 3, 2021 at 9:51 PM Chris Johns <chr...@rtems.org> wrote:
Hi,
I am testing the console driver with the aarch64/xilinx_zynqmp_lp64_zu3eg BSP
when I saw the BSP.
Is this BSP still valid?
Does this BSP work on real hardware?
Who is looking after this BSP?
Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
