Hi Pawel,
Quick heads up. I am getting build errors on the linux-morello kernel now.
Commit 87d06928f90fe910311210a0149d03f3420f593c can't be found in
morello/master any more. It seem to be in tag morello-last-5.18
Cheers,
Alex
This series of patches will stop the FVP from opening terminal windows
and add detailed instructions on how to run the model to the README.md
Pawel Zalewski (2):
README.md: update
fvp: do not try to start the terminal
README.md | 54 ++++++++++++++++++++++++-----------
conf/machine/morello-fvp.conf | 12 +++++++-
2 files changed, 49 insertions(+), 17 deletions(-)
--
2.34.1
Hi Pawel,
I had email from Andrew Murray the other day on the impressive work
you're doing at The Good Penguin to connect your embedded board farm to
GitHub workflows.
I mentioned we've done a little here at Dynamic Devices on CI for the
Yocto layers we maintain (ref: https://www.youtube.com/watch?v=TsAcxd_acJI)
We were down at the Digital Catapult yesterday talking about the new
meta-morello layer and it was extremely well received.
This got me thinking and I seem to remember you mentioned you were
putting your Morello board on the Internet? Did you do this?
Maybe you've already looked at this but I was pondering whether we could
connect a GitHub workflow to a build system artifact folder which we
could then expose as a USB gadget device.
This could then be made to look to the Morello Hardware like a connected
USB drive, I think.
And thus we could enable people to remotely build and test and
experiment with real CHERI enabled hardware?
In particular one of the really interesting ideas mentioned to me
yesterday was that even businesses without access to production CHERI
silicon could run and test their products on a CHERI enabled development
board, thus ensuring a level of enhanced security on their non-CHERI
production hardware. A sort of "Tested with CHERI" stamp.
Let me know if any of this is of interest!
Cheers,
Alex
Also playing catchup trying to get some CHERI BSD examples built up as
> recipes. Might ping you on the basics here if poss. and try to write up.
>
Having more purecap libraries would be great, thank you.
One really basic question is when you build the your demo app how is it
> build for PureCap/compatibility API? I can's see this using llvm-objdump
>
You can tell that the app is "purcap" by reading the elf header.
Entry point address LSB set to 1 will load the app in C64 mode, the flags
field will also be set to 0x1000.
Pawel