Cortex‐A55 in aarch32 - MarekBykowski/readme GitHub Wiki

Development for Cortex-A55 in aarch32

FVP_Base_RevC-2xAEMvA
...
--parameter bp.secureflashloader.fname=bl1-fvp.bin
--parameter bp.flashloader0.fname=fip-fvp.bin
--parameter bp.virtioblockdevice.image_path=core-image-minimal-fvp-base-arm32-20250630100348.rootfs.wic
--parameter cluster0.has_arm_v8-4=1
  • If fvp-base in aarch32 is in request then we build for armv7a and run it on the fvp-base with CPUs coming out of reset in aarch32. See parameter cluster0.cpu2.CONFIG64=0 passed to the model. You can also note from here an execution state is configured perCPU.
FVP_Base_RevC-2xAEMvA
...
--parameter bp.secureflashloader.fname=bl1-fvp.bin
--parameter bp.flashloader0.fname=fip-fvp.bin
--parameter bp.virtioblockdevice.image_path=core-image-minimal-fvp-base-arm32-20250630100348.rootfs.wic
--parameter cluster0.has_arm_v8-4=1
--parameter cluster0.cpu2.CONFIG64=0
  • Cortex-A55 is armv8.2-a. We have a variant, managing on the git branches, in which Yocto supports for armv8.2-a

The take-away from here is we have a model ready-for-use that supports development for Cortex-A55 in aarch32.

Stating that any proof-of-concept/request-for-change to the system behavior, eg. exception vectors, mmu, etc. can be implemented and test-run on the model.

You are just a few commands away from having the fvp-base up and running

Clone meta-arm and poky

cd <your_path>
git clone -b arm-aem-scarthgap https://github.com/MarekBykowski/meta-arm.git
git clone -b arm-aem-scarthgap https://github.com/MarekBykowski/poky.git

Build

cd <your_path>/poky
source oe-init-build-env arm-aem-build
bitbake core-image-minimal

Run

cd <your_path>/poky
source oe-init-build-env arm-aem-build
./run.sh

image

Connect to the model with armds

(armds is not free and requests licensing)

To enable the fully fledged development for armv8a in either aarch64 or aarch32 we can connect the armds to to the fvp-model model. See an excerpt from it below

image
⚠️ **GitHub.com Fallback** ⚠️