We're currently working on a 6 month project with the Digital Catapult
in the UK to add Yocto support to the Morello board.
You can see the project plan here:
I'd be pleased to talk to you about any potential for collaboration.
We've been working on building and booting the 1.1 Morello release on
the Morello hardware we have here
We've got the vanilla Poky build booting on the board and now want to
prove out that the CHERI support is trapping memory write overflows.
We followed Deepak's advice to build the examples from morello-aarch64,
which seem to be configured to build statically.
Copying these across to the root filesystem and running results in a
"Bus Error" though.
Does anybody have any thoughts on what we might be missing here?
We have been tasked with creating a Linux Yocto distribution for the
Morello server and we were given a green light to upstream the
patches. We do have the hardware that we can test it on, in fact we
have already had Morello Linux running in its current state on the
board with some simple user space apps in purecap mode. The scope of
this work would include the toolchain, bsp, kernel and musl-libc in
the user space.
I am aware that there is an existing meta-arm layer that we could use
as a starting point. The question is how and should we commit our
patches to the project ?