Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to boot Zephyr on FVP_BaseR_AEMv8R #44886

Closed
cfriedt opened this issue Apr 15, 2022 · 0 comments
Closed

Unable to boot Zephyr on FVP_BaseR_AEMv8R #44886

cfriedt opened this issue Apr 15, 2022 · 0 comments
Assignees
Labels
area: ARM64 ARM (64-bit) Architecture bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Comments

@cfriedt
Copy link
Member

cfriedt commented Apr 15, 2022

Describe the bug

In the Armv8R AArch64 profile, the Armv8R AArch64 is always in secure mode. But the FVP_BaseR_AEMv8R before version 11.16.16 doesn't strictly follow this rule. It still has some non-secure registers(e.g. CNTHP_CTL_EL2).

The issue is:
Since version 11.16.16, the FVP_BaseR_AEMv8R has fixed this issue. The CNTHP_XXX_EL2 registers have been changed to CNTHPS_XXX_EL2. So the FVP_BaseR_AEMv8R (version >= 11.16.16) cannot boot Zephyr.

This PR will fix it:
Also means, after the fix, the minimum required version of FVP will be 11.16.16. Since there is almost no one uses the version less than 11.16.16 and also no way to download the older versions, I think I will not spend time doing the logic of the fvp version checking. It's enough to add an announcement of the minimum required FVP version in the board doc

@cfriedt cfriedt added bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug area: ARM64 ARM (64-bit) Architecture labels Apr 15, 2022
@cfriedt cfriedt self-assigned this Apr 15, 2022
@cfriedt cfriedt closed this as completed Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ARM64 ARM (64-bit) Architecture bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

No branches or pull requests

1 participant