I recently got my hands on a Milk-V Jupiter 2, one of the first generally available RVA23-compliant RISC-V boards with H-extension support. Naturally, the first thing I wanted to try was virtualization with KVM and libvirt.

As a RISC-V enthusiast who works with Kubernetes professionally, I wanted to explore the current state of Kubernetes support for the RISC-V architecture. Previously, I experimented with a fork of k3s built for RISC-V. The experience was successful—I managed to run pods for applications with RISC-V-compatible versions. However, since the build wasn’t officially maintained, I held off on deploying it in my homelab. A few days ago, I noticed that the Kubesolo project now offers binaries for RISC-V. Excited, I decided to test it on my Milk-V Mars CM Lite, which currently runs Arch Linux RISC-V.

…

Since the first time I learned about the existence of RISC-V, I have been fascinated by it. I wanted to run operating systems on it, and try out software on the ISA.

In this guide I will be explaining how I flash an ESP8266 chip using a Raspberry Pi. More specifically; a Raspberry Pi 2. But any model with GPIO pins will do. In this guide I will be flashing MicroPython on the chip.

One of the last aspects I wanted to explore and get working on my MangoPi MQ-Pro, is GPIO. For this experiment, like my previous endeavor trying out Bluetooth on my MangoPi MQ-Pro, I used the Ubuntu 22.10 RISC-V image for the SiPeed LicheeRV Dock image.

I received my MangoPi MQ-Pro a few months ago, and was very eager to test out all the hardware which I use the most on SBC's. Bluetooth is not one of the features I use a lot on SBC's. But after having tested out a lot of operating systems and hardware features of the board, I decided to also try and see what the status of Bluetooth on the board was.

As of writing this article, there are a few choices of operating systems to choose from for the Allwinner D1. In the future, more choices will probably become available. In this article we will take a closer look into FreeBSD and xv6 for the Allwinner D1. I will use a MangoPi MQ-Pro to test these operating systems.

In this post I will give an overview on how a ran some software compiled for x86_64 on my RISC-V SBC, a MangoPi MQ-Pro. We will be using an awesome piece of software called Box64.

As the title says, this article will be about using a Raspberry Pi SBC (whatever model), instead of a USB Console Cable to debug another SBC, router, microcontroller... The need for this came when I received my MangoPi MQ-Pro, I wanted to try different operating systems for this SBC, but I didn't have access to a USB Console Cable, at least not one that was 3.3V tolerant. I wanted to have access to the serial console because a lot of OS images for the MangoPi, at the time of writing this article, didn't have HDMI drivers. I have already used a Raspberry Pi to flash and interact with micropython on an ESP8266, so I thought, why not use the same method to interact with my new MangoPi.

The first question you might ask yourself when reading the title of this article is; why would you want to this. My answer to that question is, why wouldn't you?