When something as exciting as a completely open CPU architecture comes along, it's hard to stop Codethink's engineers from getting involved. We've set up an internal research project with the goal of learning about RISC-V, and we have some interesting results already.
Why is Codethink interested in RISC-V?
The worldwide interest in RISC-V is not because it is a great new chip technology, the interest is because it is a common free and open standard to which software can be ported, and which allows anyone to freely develop their own hardware to run the software. -- History -- RISC-V International
The RISC-V architecture has a clean, modular design based on well-established CPU design principles. With the core specifications stable since 2019, we can now see software and hardware development starting to flourish. RISC-V is developed entirely in the open. (Here's the Github repo, if you don't believe me).
Engineers love open tech because it lets us work effectively, and it's not just about easier troubleshooting. An unprecedented level of customisation will be possible when designing RISC-V products, enabling more efficient manufacturing and operation. This has benefits right across the tech sector, and we're excited to start working with customers on the next generation of digital devices.
As of early 2021, most of the available RISC-V devices are microcontrollers. We want to run a graphical desktop or IVI environment, and so we need some hardware that's a bit more powerful. Our first research goal was to evaluate the available system-on-a-chip offerings and test and improve the software and hardware.
You probably know that we are opinionated about build tools. The lightweight, reproducible bootstrap process we contributed to the Freedesktop SDK should allow us to bring up a desktop-class Linux environment on a RISC-V board in a few short weeks. But did it? Read on for details of how we got on.
Freedesktop SDK on an Icicle
We identified the Icicle developer board, based around Microchip's Polarfire system-on-a-chip as a good starting point for application-class RISC-V hardware.
We're working from home as much as possible, so we've set up each board with a Raspberry Pi as a "remote control" which allows us to reboot and reflash the boards via the network. We also set up each board with a GPU to enable hardware-accelerated graphics.
As this is a developer board we didn't expect to just "plug and play". Our starting point was Microchip's board support package, which is developed on Github. Ben Dooks, who we recently interviewed, has worked with them to report and resolve several issues we found.
In parallel, we began an independent, reproducible OS bootstrap for the RISC-V architecture.
The Freedesktop SDK bootstrap process quickly resulted in a working
riscv toolchain that could produce binaries for the target, and the next stage was a more complete rootfs. Although BuildStream supports cross-compilation, we prefer to native compile when possible because, once you move beyond common embedded Linux components, upstream support for cross-compilation can be unreliable.
One benefit of RISC-V's clean design is that emulating the CPU on a developer laptop is already practical -- in fact, you can even emulate it in your browser. QEMU already has RISC-V support, so we set BuildStream up with
qemu-user and started building.
The result? Lots of work on the Freedesktop SDK to add support for the new architecture, to the point that we can build and boot a console-only rootfs for the board containing all the usual userland tools. You can try it out right now - see the instructions on the Freedesktop SDK wiki.
Our next goal is to show GNOME's developer preview OS running on a real RISC-V board. As part of that, we'll continue working on the Freedesktop SDK which underpins GNOME OS. The target is to have RISC-V accepted as a supported architecture of the Freedesktop SDK, which will enable the Flatpak ecosystem of Linux apps to support RISC-V officially.
As well as the Icicle board, we've pre-ordered some Hifive Unmatched boards too, and we're hoping the desktop form factor will get us closer to our goal.
Want to get involved? You can try our work in progress build in QEMU, join in with Freedesktop SDK issue 1165, or simply subscribe to our RISC-V newsletter for updates.
Keep up with our RISC-V news
Fill out the form to receive our latest updates on the open CPU architecture in your inbox.
Related blog posts:
- Linux Kernel and RISC-V: Meet the Codethings: Ben Dooks talks about Linux kernel and RISC-V >>
- Programming Language: Improving RISC-V Linux support in Rust >>
- Using Git LFS and fast-import together
- Testing in a Box: Streamlining Embedded Systems Testing
- SDV Europe: What Codethink has planned
- How do Hardware Security Modules impact the automotive sector? The final blog in a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part two of a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part one of a three part discussion
- Automated Kernel Testing on RISC-V Hardware
- Automated end-to-end testing for Android Automotive on Hardware
- GUADEC 2023
- Embedded Open Source Summit 2023
- RISC-V: exploring a bug in stack unwinding
- Adding RISC-V Vector Cryptography Extension support to QEMU
- Introducing Our New Open-Source Tool: Quality Assurance Daemon
- Long Term Maintainability
- FOSDEM 2023
- Think before you Pip
- BuildStream 2.0 is here, just in time for the holidays!
- A Valuable & Comprehensive Firmware Code Review by Codethink
- GNOME OS & Atomic Upgrades on the PinePhone
- Flathub-Codethink Collaboration
- Codethink proudly sponsors GUADEC 2022
- Tracking Down an Obscure Reproducibility Bug in glibc
- Web app test automation with `cdt`
- FOSDEM Testing and Automation talk
- Protecting your project from dependency access problems
- Porting GNOME OS to Microchip's PolarFire Icicle Kit
- YAML Schemas: Validating Data without Writing Code
- Deterministic Construction Service
- Codethink becomes a Microchip Design Partner
- Hamsa: Using an NVIDIA Jetson Development Kit to create a fully open-source Robot Nano Hand
- Using STPA with software-intensive systems
- Codethink achieves ISO 26262 ASIL D Tool Certification
- RISC-V: running GNOME OS on SiFive hardware for the first time
- Automated Linux kernel testing
- Native compilation on Arm servers is so much faster now
- Higher quality of FOSS: How we are helping GNOME to improve their test pipeline
- RISC-V: A Small Hardware Project
- Why aligning with open source mainline is the way to go
- Build Meetup 2021: The BuildTeam Community Event
- A new approach to software safety
- Does the "Hypocrite Commits" incident prove that Linux is unsafe?
- ABI Stability in freedesktop-sdk
- Why your organisation needs to embrace working in the open-source ecosystem
- RISC-V User space access Oops
- Tracking Players at the Edge: An Overview
- What is Remote Asset API?
- Running a devroom at FOSDEM: Safety and Open Source
- Meet the codethings: Understanding BuildGrid and BuildBox with Beth White
- Streamlining Terraform configuration with Jsonnet
- Bloodlight: Designing a Heart Rate Sensor with STM32, LEDs and Photodiode
- Making the tech industry more inclusive for women
- Bloodlight Case Design: Lessons Learned
- Safety is a system property, not a software property
- Meet the Codethings: Safety-critical systems and the benefits of STPA with Shaun Mooney
- Why Project Managers are essential in an effective software consultancy
- FOSDEM 2021: Devroom for Safety and Open Source
- Meet the Codethings: Ben Dooks talks about Linux kernel and RISC-V
- Here we go 2021: 4 open source events for software engineers and project leaders
- Xmas Greetings from Codethink
- Call for Papers: FOSDEM 2021 Dev Room Safety and Open Source Software
- Building the abseil-hello Bazel project for a different architecture using a dynamically generated toolchain
- Advent of Code: programming puzzle challenges
- Full archive