Okay, so thanks everyone, so welcome to our talk, can't focus any conductor, hold my
beer, we didn't bring beer because we drank it, we're really sorry, it's kind of what
we do at Open Hardware, but just for some instructions, I'm Charlie Man, so I lead communications
and dissemination for the European Tristan Project, which is all about getting risk
5 out of the lab and into industry, and I also get to lead technical content at the Open Hardware
Foundation.
So, yes, my name is Cairo Kaplan, I am a verification engineer at Open Hardware Foundation
and I also work on managing European projects under the Planet Foundation framework.
Thank you, and just a quick overview of what we'll take
you through today on today's testing menu, why we need a revolution in European silicon,
which we really do.
The Master recipe, a little bit about our Tristan Project, and also about the unified risk
5 IP access platform, which will henceforth be referred to as the UAP because it's
mouthful, and a little bit about how we built it, what it's for, the quality control that's
behind it, and also the tasting room, so you get to see a couple of the cool risk 5 projects
that have already been donated.
Just a few disclaimers, everything we're going to show you is licensed under the Open
Source Eclipse License.
It is a work in progress, so please don't expect this to be perfect, but we hope by the
end you'll be interested enough that you'd also like to contribute, maybe donate some
of the risk 5 IP you're working on, and a lot of what we are doing this for is supporting
European technical sovereignty, underneath the ship's act.
You've probably heard so much about this in recent months, so we need more European sovereignty.
This is our way of contributing towards that, making risk 5 a reality in Europe.
Just a little bit of context too, don't worry, we'll get to the fun stuff soon, all
the work that we're talking about today was developed and funded under the ChipsJU Project
Tristan, our sister or wife project, depending on how you look at it, is older, so they
do the software side of things.
They've also joined, which is fantastic, scale for edge, Rebecca and Rigoletto, also projects
researching risk 5 applications in Europe, but we were so great, they joined too, which
is fantastic, so you can now find IP from every single one of these projects in the
UAP.
On to the fun stuff.
I apologize for my chat GPT graphics, I'm not a designer.
But we're here to talk about today is, well, an issue that's very close to my heart is,
why is it so damn hard for us hard, where folks to find any verified risk 5 components,
that are fully open sourced.
On the side, we've got our software counterparts and they just get to tap up the free
bar whenever they want to, because they can just fork their project straight from get hub.
And it's great, they're contributing back, it's a nice cycle, but it's not fair.
We get stuck in a long queue for expensive beer.
We don't know how it's been brewed.
We don't know what's in it.
We don't know if it's going to go with the other beer that we've already got.
Quite frankly, why should we have to queue for expensive beer?
Now, I'm sure we're talking to the choir here.
It is very possible to find your recipes for free open sourced beer online.
It is going to be difficult, though, because quite frankly, we have a silo problem in Europe
when it comes to risk 5 IP.
We've got world-class projects, absolutely top of the range, the freaking hard to find, though,
the repositories are isolated, the servers are really, really specific.
We've got non-standardised metadata, we've got no long-term maintenance, and this is a real
issue with European Research Projects.
We produce outstanding IP, and then we just walk away and leave it, and nothing happens,
and we really want to change that.
And of course, maybe you do find the ingredients, the IP that you need.
It's going to be really fricking expensive, though, and a lot of them are covered by
NDAs.
So, let's just say that we have a very motivated benefactor.
They've dropped us a couple of million, you know, to burrow up our beer silicon.
You've got a test-each into the German ingredient and make sure it works together.
Like, not all of that is going to be done for you.
And after all of this hard work, what if it doesn't work in the end?
What if you end up with nothing?
And that's a genuine issue in hardware.
And quite frankly, we're thirsty, and we don't believe that engineers should have to
wait for beer.
And us waiting for beer is a massive flipping problem for Europe.
Like, there is a 700 billion global semiconductor market.
We've captured 10% of that, that's nothing.
We have some of the best IP in the world, we can do more.
The chips-chair U project is trying to get us up to 20% by 2030.
We're making great strides, but it's going to take us all contributing to make sure
that we reach the goal that we want to reach.
And this is one of the reasons we exist.
The open hardware foundation, we are the champions of beer brewing.
We are an industry partnership with the eclipse foundation.
We basically, well, we like to think, we are the leader in industrial grade risk five
cores.
Everything that we produce is open source.
It's permissively licensed at its production ready.
And we are already used in projects across Europe for some very large names, including
Talis, and a bunch of others, which I can't tell you about, but I'm working on it.
I won't stop too long on the cores that we have.
We produce the core five family.
Everything that we have is either rated at TRL 4 or TRL 5, ready for adoption.
If you want to talk to us or get your hands on any of this IP, come and see us afterwards
or talk to us at the Eclipse booth.
And again, we've mentioned the Tristan project.
We've come to the Tristan project through Eclipse, because Eclipse is based here in Brussels.
The Tristan project is a $50 million project to mature and industrialize European risk five.
46 partners, including Talis who I've mentioned, ETH Zurich, and XP, some massive
names in research and development of risk five components.
We like to think that we provide the brewery equipment, so you can make your own risk five.
Oh, and actually just on a side note, if anyone is interested, this project is wrapping up
in six months in the summer.
We're going to be at the risk five summer in Italy, and we are bringing all of our
demonstrated models.
So if you want to get a closer look at what we've produced, come talk to us.
And with that, I'm going to hand over to my colleague Cairo to actually take you through the
UAP.
Thank you for the introduction, Charlie.
So yeah, I'll try to keep up with it if you're a presentation.
So yeah, the master's type.
So we are open hardware trying to build the infrastructure of European risk five collaboration.
So this is why Tristan and the OpenRF Foundation, we have launched the
Unified risk five access platform for now on quality UAP,
which is one of the outcomes from the three years of work of the Tristan project.
So the UAP, in fact, is a first of its kind and in this sense that we are trying to provide a
single collection of verified industry-ready risk five IPs or not only cores, but also the
peripherals and low levels of trends and the society projects.
And I'll develop here in Europe.
So yeah, it's a consolidation of a hardware, software components with a very clear view of each item's
maturity level, visibility, licensing, which is also very important and also the integration workflow.
So much of what's developed on the Tristan and what's available on the UAP is open source,
but it's not restricted to that.
So yeah, critically, it's interested that IP from multiple EU research project is captured
and maintained in a way that an organization can benefit from it, not only the organization,
but also students and engineers, we're trying to driving a sustainable long-term collaboration.
So yeah, in fact, right now, as Charlie said, we have IP from Tristan and Israel,
which were the first two projects that were involved on this, but also recently also from Rebekah,
SK for Edge, and yeah, and more to come. So yeah, let's see what features the UAP has.
So let's say the core of the UAP is what we call the vitriopository, which was the initial name
of the UAP as some of the concept characteristics, I can say that it's centralized,
the sense that the IPs that we show with catalogue, they remain on the partner servers,
that means it can be on GitHub, on Project SkitLab, or even on other companies.
So the index, the metadata we don't host is actually IP itself. Of course, for open-holder IPs,
it's GitHub on the organization. The UAP is also a tool for discovery. Actually, it's more
oriented towards people, humans, we have other projects that's more integrated with software tools,
let's talk about later. So it really tries to be and propose to be a single port of what you can
find the risk-5 IPs and slurators and so on, and you got this sovereignty. We follow the
fair data principles, which means a findable, accessible, interoperable, and reusable information.
And we back up this infrastructure and European servers.
And now about the IP card, which is, that's it's a more
machine level or software-integrated part, it's run by the IP container task group,
with this initiative. We are still on the conception part on the prototype. So we build a
JSON file that has the metadata about an IP regarding terrestrial license, I say, the profile
and core configuration, so that let's say once you run your data tool or setup, you can get
information automatically, you don't need to access an upside for that. And yeah, it's a working
progress. We plan to generate this information automatically. So we can get dependency
IP, which they'll choose like a bender or fused as you see. So yeah, on this, we are really
building this up, so if you have a contribution on that, you're welcome.
And yeah, the testing IP compatibility matrix, we are trying to, we are also building
data base where you can each, we can have information about each IP, regarding their compatibility
of other IPs, to get interface and profile. So now the testing room will explain the
current type list for a reputable IP. So this is how the UAP looks currently. It's a variable
both at the open-harder group GitHub, it's server design GitHub page, actually. And it can be
embeddable easily on other projects website, including Tristan. It's composed now, currently,
of four pages, the welcome page, that's what you see on the right, where you can see the
list of the basic information and list of projects that listed the platform page that I show
in the next slides, which the what you really want to see when you access this, it's the dynamic
table with the permission of IPs available, enter page. For now, we have been a really
project centric in the sense that this was a tool initially used more to, so that you
research project can add their own IPs and know the status of development across time, but
trying to make it more open so that I need to be associated with a project. So this is the
purpose where you can add information about it and the help page that has the information
how you can help or contribute. So this is the platform page that says it's the main page that you
will see when you want the first column is the name of an IP or the name of a contribution
from an existing IP. You can see that valid figures the openholder CVC, since CVA true,
then a category here I filter for course because I think that's more in terms of many of you,
but we can also add, we also have peripherals, real-time OS, and other regulators and so on.
This list of categories still being viewed, being viewed. The license, this is very important,
so I'll talk about how we prefer to use the soldepal license for hardware IP, so it's a business
friendly. This status, this is something more interesting for user projects, but for you guys outside
maybe interested in that, basically the description, and the associated project,
if we're using the future, as I said, when we transfer it from the project to IP centric,
of course it can also be seen on a mobile phone or small screens.
Yeah, this is the architecture of that, so it's basically a post of two layers.
So the first part, let's say it's the UAP websites, it has a list of several views.
You can see that as an engineer, project manager, or project reviewer, this shows, for instance,
if you are a project manager, the information about IPs and which work item it has related
in a project reviewer, if they want to see during the window of time, where the project has been reviewed,
they create status of a single project, and for the public, we are not interested in
project, we're interested in IPs and their status. So yeah, this is completely a frontend code,
so you can host it not only on GitHub page, you can mirror it and back up everywhere,
this makes it very easy to be transferred. The database path let's say it's the
future repository, it's where we store, currently, the information about the each IP in the future
this will be obtained automatically through the IP cards, and yeah, there is a, since it's
hosting GitHub, we have some say validation scripts for when we have new contributions,
of course, we are to open how the as part of the system will review it, it's the governance
of that, we will make changes in the future, since when it's an answer, but this is how it's
done now, and then at the very right is where actually the IP sits on, it's where also you
the JSON IP cards will be stored, so it can either be open source IP from open how to
it's on GitHub or it can be hosted on a partner repository, be on GitHub or if it's a proprietary
project, you can provide assets or information on such an IP. So now I show some of the IPs that
are included on such a list, as for example, the first one that's, let's say it's the most popular
penader IPs, the CVA6, so yeah, it's a, it's a industrial grade application class family
of course, it's a, it's a, it's quite a family because CVA6 is highly configurable, so
under the framework of a Tristan project, one of the configurations, the CVA2,
E6, X, has reached a chart of five, the level of verification, thanks to the effort that
by Tales, but also for contribution by us, open hardware and CNA, as I said, it's highly
configurable, you can not leave them so that, and you are not, if you use the CVA6
CNA to brush, you use it as it is, you can modify it, many, some companies they, they customize it
and let's say they patch it when they use on their own, you know, projects, but yeah, that's all I can say for that.
The CVA2A4TP, the SessionA2, it's an embedded class CPU, we use it on the, on the
counter, you need projects, it's also has many configurations, it's, it's built through,
we use the on efficient power efficient, but also on this build operations, I guess that's the
CVA2, E40P is one of the configurations that we choose, TLF5 on previous years,
you have the CVA2, E40P, VQ, that's for noise TLF4, also the PX, the F40X, which has the
accession interface, that's a co-processor interface, so yeah, and then the, let's say there's
malice score that has been working on this project, it's on the CVA2, it's a two-stage pipeline
core, initially it was, it was developed at the zero risk, donated to low risk, as a lab
X project, we took some configuration of that to make it right to be in this upgrade, it's still
TLF4, TLF3, by now, but we are making it working to make it TLF5, so yeah, these are the
examples of cores that you can find on this platform, what you can also find now talking about
verification security, continuously subject, you can also find the open-hunter core V, very
if, which is our function verification framework using a UVM for the core 5 family, and for the
CVP, it's not the case right now, but we have a roadmap that we add metrics on regarding
users, also from its insights about each other's IP and status badges, for other IPs we show,
as I said, the current TLF level, which is very important if you want to use it on a prototype
and finally, some interesting characteristics of the UAP are ready, most of it's already implemented
right now is that the UAP as an other open-hunter IPs, they are hosted on GitHub, but they are
backed up on a crypto foundation on GitHub instance, it's doing weekly, we are working to make
it possible to us to mirror in case GitHub goes down, let's say, and also supporting
supporting a user warranty, we hosted on vaccination EU servers in France, and yeah, that's it
yeah, before finishing it, it's just a benefit, sustainability, as I said, it actually
requires low maintenance because it's basically for now it's only front-end code,
the governance from it, it's this initiative is led by OpenHunter and an XP, there is a
three-stern on the virtual repository task group, this may change the future, but the
virtual repository task group was continuous, and so yeah, and we are ready to onboard new projects
and trying to make it more friendly for general IPs, of course, trying to be always
in fact as an open source of contributions to be added on this platform, that's how a final message
we tend to build sustainable, sovereign European ecosystem for the third carries results
for contributing to the blue, and yeah, the where you can have information about that until
access the actual platform, that's it, thank you