 open source chip design. Who here in the audience uses Linux? Please, a short sign of hands. Feels like almost 100%, I would say. Okay, 100% of people use Linux. So who of you uses it on open hardware? Please, another show of hands. Yeah, that's not too many. Who of you would like to use it on open hardware? And I guess that's why you're here. So I'm glad that we have Drew Fustini here, our new speaker. He's an open source hardware designer and embedded Linux developer and also the vice president of the open source hardware association. And who better to tell you how to run your Linux on open source hardware? Please welcome Drew with a big warm round of applause and have fun with this talk. Thank you very much. Thank you. Thank you. I'll skip past my introduction. I'm going to skip over the introduction. It's Congress, so most of you are probably familiar with open source graphics. And I just wanted to tell you a little bit about what open source hardware is. So open source, in general, there's Linux, for example, a good example. There's Android, there's also Linux in it, LibreOffice, with which I, for example, made this presentation. Firefox is an open source browser. So you know the term open source software, I think quite well. So, yeah, it's about the fact that you can modify the software and share it because the whole design, the design, basically the software is publicly available. When we talk about open source, yeah, so in the context of open source, people use different terms, they use free Libre open source software. They all have different backgrounds and in this presentation, I'm going to put them together a little bit and just say open source hardware. Other people should use the term free hardware or Libre hardware. So, yeah, open source hardware is a hardware that is publicly available in the public, so that everyone can look at it, modify it, distribute it, create the hardware, or even sell it. And yeah, that's what we've been thinking about for about 10 years on the open source hardware. We just wanted to have a definition. So, open source hardware is not just about electronics, it's also about the mechanical design, basically every physical object that you can free design data. In the context of electronics, what we're looking at here is, for example, the schematic on the left side or the layout of the plate on the right side. Or, for example, if we take a look at the outputs, then we usually talk about the data that is used from the Dicat software that you can still work with. So, for example, the data with which you save key-cut or EGLE project data. And what is also important is that you make sure that people, that they can actually build it, that the materials, the individual building blocks are available. And that is then summarized in the Beloff material. So, how many of you have already heard of Arduino? Okay, already a lot. So, Arduino was a microcontroller board that was developed in Italy by a small university in Italy, more than ten years ago. And that was good enough to make a whole series of interactive electronic projects. And they just made the hardware design and the code available on the Internet. And that has greatly increased. Many people have used different projects. And if you look at, for example, the preview pages, then I have also linked everything. So, one thing that is interesting is that when Arduino started, they explained what their motivation was. So, I can only recommend that. One of the most popular Arduino boards is the Arduino Uno. And where do we know that it is open source hardware? When we look at the website, then you can download the design data. In that case, it is the Eagle Design Software. And we can download the schematic, the layout of the board. We need to think about licenses, of course. And there are many different options. There are, for example, the Creative Commons licenses. What is very widespread is the CC by SA. By is for attribution and share like SA. There is also a blog post. So, there is also a blog post that explains why you shouldn't add the non-commercial clause if you want. That is still followed by the philosophy of open source licenses. There are also other licenses, for example, the permissive licenses, the Apache, the BSD, the MIT, or the copy left licenses. Then there are specific licenses for open source hardware that we want to take a closer look at. The CERN is a big physics lab in Europe that developed the open hardware repository. And they are basically building electronics for their physics experiments. And they want to share that with other labs all over the world. And because of that, the open hardware license was invented. One of the people who is working on it in this team is Ravius Serrano. And there is a good video here that explains what the motivation behind it was. There are not only licenses, there are also copyright and patents. Adi Douglas gave an interesting talk a few years ago that is linked here. He talks about what is good for your project, depending on what kind of goals you want to achieve. He talks about what kind of options you have. What is the whole point here? What is the reason why we talk about it? The reason why you want to make an open source hardware project is because you want to contribute to other people. You want to work with other people in design. And that is the main reason why I would say that people should publish it. If you are not interested in other people having a part, then that probably won't be the right thing. It would be important to think about it, whether you want to do it or not. At the beginning I mentioned the Open Source Hardware Association. It is a non-profit. There are board members from all over the world. One of the things we do is that we publish everything that you need to publish open source hardware projects. But the main thing we do is open hardware summit and that we will take place in New York in March. I hope that a few of you will be able to do that. It will be our tenth time that we will do that. This year we decided to do something a little bit different. We have the Open Hardware October. It is about the people from all over the world organizing meetups, talks and workshops. We start with an event in Vienna. We already had 40 events in 14 different countries and we will do that again in 2020. I hope that a few of you will also have part. If you are wondering what will happen, you can watch the talks. They are linked to the slides. There are different projects that people do. I do a lot of electronics, but there are other projects like science, art or design. Another thing we do with the Open Source Hardware Association is a certification program. It is about software identification. You go to this website, fill out the information, give us the links to design files and documentation and then you get this logo. The value of this, if you do a project, you can put this logo on your packaging and people can identify it as an Open Hardware project. You go to the website and enter the ID number and then there are the documents connected. If you want a certain device and you see this logo, you can go online and see it in the database. If you are interested and want to know more about Open Source Hardware Association, you can go to this website, you can become a member. We have mailing lists, we have photos. If you want to follow us on Twitter, then the handle is Ahohasummit and we have another handle for the event in March. Alicia Gibb is one of the people who started it. She wrote a book called Building Open Source Hardware. I recommend you to watch it. The main theme of this talk is Linux on Open Source Hardware. These are my two favorite things. One of my favorite projects was developed by Bunny. He gave a talk on the first day of the conference. And Sean Cross. He gave me a talk about the latest open source laptop. It was 4 or 5 years ago. I have it for many years. It is a laptop that you can use every day. It has a few extra features like an FPGA and a software defined radio. If you go to the CDC area in Congress, you can see the Form Laptop. It is a complete open source hardware laptop. I recommend you to watch it. In the CDC area. Another project I am involved in is the Beagleboard. It is an organization that helps open source hardware computers. We work with different manufacturers. We work with the community. The Beagleboard project started in 2008. It was an ARM computer. Many people wanted it back then. The board was pretty popular for that. This is the Beagleboard. It fits in a small box. If you have already used the Beagleboard, the Beagleboard Black is the most popular one. Because it is open source hardware, the Beagleboard from different manufacturers. From different price points. Different manufacturers do different things. They decide to add HDMI ports. Another one is a bit more expensive. It has industrial grade components. The important thing with open source hardware is to use the open source hardware. It is a very simple solution. It is a very simple board layout. It is a four layer PCB. It has Eagle files and KeyCat files. If you are familiar with it, you can order the board. You can order the parts yourself. It has a logic analysis tool. It has built the Beagleboard. It needs the things it needs. For example, the Gigabit network port. It has the pocket Beagleboard. Here is an example of a logo. It is one of the newest boards. We registered it in the summer. It has the US country code and the 169. It is easy to recognize for people that it is an open source hardware. You can go to the data bank and find the data. What I wanted to mention is Olimax. It is a company from Bulgaria. It is one of the best companies I know. They have an open source product line. They also have a great block behind the open source hardware. A few years ago they built the ARM 64 bit system. It was completely open source. It is a free software. In 4STEM it was introduced how the process was introduced and how the proprietary process was converted. If you have not heard of KiCat or PiCat, it is not about how it speaks. It is a software to develop chips. It runs on Windows, Mac or Linux. There are developers working on the ARM. There are people who work on it. It is nice to see that there are people who develop this tool as a full time job. If you want to try it out, there is a tutorial on YouTube, getting to Blinky. Olimax has taken the board they developed and built a laptop which is called TerraZone. The design files are also on GitHub. The idea is to build a modular laptop with different boards. Another interesting project was the chip. The idea was to build a $9 computer. There was a great Kickstarter. Unfortunately, the company went to the first plate. But it was all open source. The PCB layout was all open source. The chip was developed. Unfortunately, the company went to the first plate. Christopher developed his own chip. What is on the chip, if you click on the left, you see what is going on. Then there was the other board. It is a bigger factor for microcontrollers. It is a complete system. It is fully open source. There is a crowdfunding campaign. One of the things I wanted to talk about is the idea of Open Source and FPGAs. I will tell you about how that plays into Linux. What happened over the last few years, there were probably a lot of people here who participated in the congress, like Christopher Wolff, who built open software tools so that you don't have to use the proprietary programs. There was an overview in the Hexbox magazine where you can download the PDF if you want to take a look at it. There was a few years ago by Christopher Wolff about the congress where he was talking about the latest ICI. He wrote different software programs to program the FPGAs. The project is called ISTOM. David Shaw developed open source software and developed the ECP-5. In the last few years there was the X-Ray and Simbiflow project that developed open source software tools to program Xilinx FPGAs. Why is this important for Linux? If you have an FPGAs that is powerful enough, you can actually do a software on it. And then you can do a Linux design on it. Greg, who is also here in the congress, developed this cool board here, Orange Crab, and he actually managed to get Linux running on it yesterday. You can download it, and then let Linux run on a software on the Simbiflow FPGAs. Another board, this one came from a hackerspace in Croatia. It also uses the ECP-5 FPGA to run Linux on it. And for that there is a crowdfunding campaign that you can take a look at. There is also a developer that developed this trellis board that you can see here. It is relatively attractive for the user because you can run Linux on it. It actually has RAM. You can also, it's completely open source, you can download it and run Linux on it. And then there is a Game Boy, but they actually also have an ECP-5 FPGA on it, so you can run Linux on it. So that is a trend that you can see a bit in the last time. Then there is the Open FPGA assembly on the congress, and here you can see a bit how a software actually looks when gates of this software are placed on the FPGA. One way we do this is we come on a software. How do you synthesize your software? What is really important is a software called the Lightaxx. It is possible to build a system on chip within the FPGA. There is a Python-like language, which is called MyGen, and then there is a blog post by Bunny that explains the advantages of this language. What can you build with it? You get a RAM controller, PCI controller, and so on, and basically you can build what a Lightaxx is also possible to run a RISC-5 software. And that is what the OrangeCrab software uses, which was installed in the Hackadab project. So Linux and Lightaxx is what a lot of people use there. So I started talking about RISC-5 and I already mentioned RISC-5 a few times. For those of you who don't know it, you might already know it from the X86 or Instruction Set. So these are the instructions that the processor does when you write a code and compile it. RISC-5 is an Instruction Set that was developed at the Berkeley University in California, and it's open source. That means that everyone can implement it in a chip or an FB card. One example of this is from the University of Columbia that developed their own microcontroller based on RISC-5. That's the OpenV microcontroller. And it can perform the RISC-5 Instruction Set. But it's not capable enough to run Linux but it's more for microcontroller use. The other design is called LowRisk and they had the idea that they developed a chip based on RISC-5 to build smartphones out of it. One of the people who started LowRisk is Alex Brebery. He had a very interesting talk a few months ago about the link to this talk that you see here. He talks about the tool chains and so on and so forth. Similar to that, there's another organization called FOSSI, the Free Open Source Silicon Foundation. They have a conference here in Europe to organize. There's also a conference called LedgeUp. They also host a website called LibreCourse. There are chip designs, IP blocks for different purpose applications like IP boards. You can share these designs with other people. There was also an event earlier this year called Week of Open Source Hardware. You can see that online. One of the other companies that use the RISC-5, they are connected to this company and they build one of these microcontrollers. One of the co-founders and the CTO has a very interesting talk about the RISC-5 ecosystem that is linked here. They decided to take all the course to RISC-5. This is another microcontroller board but unfortunately that can't lead to Linux because it's too weak. One of the surprises of the FOSSI conference was the Porma of CY-5. It's a 64-bit board. It has a disadvantage. It's an evaluation board and it's pretty expensive. It doesn't have a lot of numbers. There are high-end boards like this that are very expensive because it has a lot of quantities. There are billy microcontrollers that are basically a microcontroller with a lot of memory. It's possible to lead to Linux. On the Linux Plumbers conference this year, there was an interesting talk on this topic. There's a talk and slides from the conference. They added support to the Linux kernel for the RISC-5 processor. The support is there but it's not particularly great. We can work with it, but it's not the best support. If you're more interested in where Linux is running, you can watch this talk. It's a few months old and it's about how the Linux kernel runs on RISC-5. The other cool thing is that Red Hat and Fedora have released a definition for Fedora Linux. If you don't have it, you can test it on your computer. One of the things that's exciting that was presented on RISC-5 two weeks ago, was that NXP said that it's going to give a Linux chip next year. That's going to be great. It would allow us to develop a board that's not too expensive and has a lot of performance. One thing that I'm going to hopefully have is a board that's going to cost under $100. One way to use FPGAs, is to use the chip that's going to come out. I'm wondering if it's possible to develop it until the next CTC contest. If you're interested, please contact me. I don't know if we have any time left. I don't know if we have any time left. But now I'm ready for a few questions. Thank you very much. That was the translation of C36 C3. We're going to start right after the question. Please leave us feedback with the hashtag C3T or feedback at c3lingo.org. We're going to continue with the questions. Sure, take your time. Just start talking into the microphone. Yeah, why is the microphone of the signal angel not working? We'll just start with a question from microphone number two then, while the signal angel is working out his microphone. There you go. Does it work? It works. Thank you very much for the interview. I had a lot of fun with the Beagleboard and the Bell System. I actually brought it to the stage and one of the things that really inspired me in the project was the Xenomai Echzeitoper Betriebssystem. It's a wonderful bridge between the difference between the processors and the octopus that connects to everything. There's a simple introduction and do you have more examples? Yeah, so let's take a quick look at the people who are not very familiar with the concept. The Xenomai is a kind of co-cunnel that runs next to Linux and allows real-time use. For example, audio with less latency for instruments or motor control or something like that. In the Linux kernel there's a lot of work to be able to use the Linux kernel better for real-time tasks. But this Xenomai kernel is the moment that a lot of people use. There's also something called the machine kit. It's a system for hard real-time use. For example, running a motor controller. For real-time use it's always the question if there are deadlines. Here they use Xenomai because they can tell you a minimal latency. But there's a lot of work to be done on real-time support. And if you're interested in Bell, I think there's something that's much better. Okay, let's try it again. Do you have to get the open hardware and software design to get this certification? If we use the open source hardware definition, then you can use any data you want. This is also the case with mechanical design. It's actually proprietary software. Kikad is really good in the last 5 years. But 10 years ago, most people used proprietary software for mechanical design and electronic design. For collaboration, free software is much better because you have the maximum number of people to participate in it. But it's not a requirement at the moment, it's just a best practice. How far is the performance on a risk-five for daily things? You can go on the downside to the problem with the software on the FPGAs. At least with this ECP-5, which I mentioned, it only runs at 50 or 100 MHz. That's the reason why I mentioned the Simpliflow and Project X-ray. It's possible to use the bigger Silings FPGAs that promise higher performance. At the moment, it's not comparable with ARM or Intel. But the cool thing about the FPGAs is that you can see that the periphery device is very flexible. You can add accelerators even though the attack frequency isn't that high. That's why I'm hoping people will use the FPGAs directly. That's the problem at the moment in the ecosystem. We need chips from the internet to create a package manager. Do you think it's possible to build a package manager for open hardware? That's a very good question. Open hardware is almost 20 years of open software. It's difficult to upgrade the tools. A lot of people use it to make the designs. Collaboration is a lot more difficult. It's not the same as the source code. If I look at the GIFs in GIT, they're not very important. We need tools to create better tools that allow us to change and try to do something that can be done with a meaningful tool. I think that's a very important thing. I did talk to someone who talked to someone who has open source hardware observatory. In terms of being able to build a package manager, I think that would be the visibility of the project. You can look at LibreCourse. There are many IP parts like Ethernet, built-in or storage controller that you can use. Chipped design is a little better, because if you look at the hardware design code, it's like a normal source code. In your presentation, you said that there are different projects for commercial FPGAs. There are projects that often want to develop FPGAs. We talked about open source tools. We talked about open source tools that are designed for FPGAs, but then it's about open source chip design. I haven't heard from projects that want to build an open source FPGA. But if you heard something about it, tell me. In the hardware hacking area, Tim and somebody else talked about what happened there. In the first talk of Bunny, on the first day of the congress, it was about this topic. What about performance per watt? What about performance per watt? What about performance per watt? I don't think there are any best choices compared to ASIC or something like that. I don't know how to say the numbers around that. I haven't seen so many numbers, but a lot of it is still in the early days of ESC-5. Especially with the soft cores, they won't be good. There's another project from the ETH Zurich, which is the OLP pulp. It's for Parallel Ultra Low Power. That's a family of low power risk 5 cores. Good question though. Microphone number one. Thank you for the great lecture. As you said, there are a few NDRs and OHA reports. Do you have the risk 5 core? My question is, do we have all the components together to develop an open source processor? I think there's still a lot of work to be done there. I think there's still a lot of work to be done there. I think there's still a lot of work to be done there. I think there's still a lot of work to be done there. If we look at Sci-Fi, there's the core open source, but not all IP blocks are open source. We hope that when future people do chip and system under chip design, they will use open source. With Sci-Fi chips, for example, there's the problem in USB. There's, for example, an beta-V synopsis from which you can buy something like that. But we still have the problem that there are no high quality open source IP cores for some things. And that's it for today. Thank you again to all of you. Thank you again to Drew. Thank you very much for the awesome talk. Another big warm round of applause please. Thank you.