Re: [meta-arm] fvp-base doesn't support armv8.2

Jon Mason <[email protected]>
Newsgroups org.yoctoproject.lists.meta-arm
Message-ID <CAPoiz9wk6fWsbOJkoiG1mMO6t39Zo8Dsv3JBQMxm=AZXh4m6RQ@mail.gmail.com>
On Sun, Jun 8, 2025 at 4:14 PM Marek Bykowski via
lists.yoctoproject.org
<[email protected]> wrote:
>
> When I simply change to "require conf/machine/include/arm/arch-armv8-2a.inc" and "FVP_CONFIG[cluster0.has_arm_v8-2] = "1"" and "FVP_CONFIG[cluster1.has_arm_v8-2] = "1" " the FVP_Base_RevC-2xAEMvA doesn't boot at all. I do not see even a single line of log even from bl1. Would that mean the SW stack/Yocto doesn't support armv8.2 for fvp-base model platform?


No, this doesn't necessarily indicate a lack of support in the
software stack — rather, it means you're using an untested
configuration. So far, we've only validated support for ARMv8.0, v8.4,
and more recently v8.5 on the FVP Base platform.

I'm not sure which release or branch you're working from, so I’ll
assume you're on master. If that's the case, you may need to disable
the ARMv8.5 configuration in meta-arm-bsp/conf/machine/fvp-base.conf.

Additionally, I recommend enabling debug in TF-A to help with early
boot visibility. You can do this by setting TFA_DEBUG = "1" in
meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-fvp-base.inc.

A good starting point would be to use the ARMv8.0 configuration and
confirm that it boots correctly — which it did in previous releases —
before attempting to move up to v8.2.

Let me know how it goes or if you need help with any of these changes.

Thanks,
Jon

> Thanks,
> Marek
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#6533): https://lists.yoctoproject.org/g/meta-arm/message/6533
> Mute This Topic: https://lists.yoctoproject.org/mt/113539838/3616920
> Group Owner: [email protected]
> Unsubscribe: https://lists.yoctoproject.org/g/meta-arm/unsub [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.