The photo above is a plugboard that contains a Raspberry Pi Pico 2 connected to an OLED display, an 8×16 LED Matrix Feather, and a four line by twenty column LCD backlit character display. The OLED display and the 8×16 LED Matrix Feather were purchased from Adafruit (links below), while the LCD character display came from a collection of parts given to me when their owner passed away back in 2023. Barely visible is a single white LED in the upper left corner. It has a long orange wire connecting it to pin 29 (GPIO22) on the Pico 2.
The highly simplified schematic only shows direct connections. Those direct connections are the LCD display and the single LED. There’s a STEMMA QT connector off to the very left which is used, with proper cabling, to electrically connect the OLED and 8×16 LED matrix feather to the Pico 2. I chose to go this route because it keeps the schematic simple and easy to put into a blog post.
Right now I have the RISC-V version of MicroPython 1.24.1 flashed onto the Pico 2. My code behaves exactly on the RISC-V cores as it does on the ARM Cortex M33 cores, which I find amazing. I’m working with the RISC-V cores because I don’t have a use case for using the M33 cores, especially their security features. I’m not quite the fan of ARM I used to be. If there’s any opportunity where I can use and support RISC-V-based devices then I will, and this is one of those opportunities.
I have been working with Arm (or ARM) processors for decades, going back to the 1990s. Arm used to be an acronym for Acorn RISC Machines because it was the BBC Acorn Computers that developed the initial instruction set architecture (ISA) for a processor that would be better than what was available at the time, which was Intel’s 16-bit 80286. Two engineers on staff designed the first ARM processor. Just two. Their first silicon release was ARM1 in 1985. The ARM processors themselves would go into many computers of the late 1980s to 1990s, not the least of which was the Apple Newton. The ARM portion of Acorn Computers would eventually be spun off in 1999 as Advanced RISC Machines. Thus would begin the long uphill marketplace climb to mobile marketplace dominance today.
So here we are with Arm getting ready for its initial public offering as a publicly traded company. And Arm has amassed an army of lawyers to go out and do what only lawyers can do, which is to stomp anything that smells like it might be a threat to Arm’s hegemony in this space, or possibly using their “mark.” And thus we come to Maria Markstedter and what used to be her web site, arm-assembly[dot], but which has been renamed due to said Arm lawyers to https://leg-assembly.com/ . That site has been available for years, with the full knowledge of earlier Arm. Ms. Markstedter has been one of many supporting resources for Arm, providing a needed teaching resource, especially when it comes to deep security issues which reverse engineering (especially of malware) can provide.
I have my own copy of the book Arm Assembly, and I’m glad I serendipitously purchased mine when I did, because the lawyers are threatening to have the book reprinted if they find anything they don’t like it in. If you want the first copy of that book I suggest you grab a copy before they’re all gone. I got mine at Amazon.
So what can we do against Arm? The same thing we did against Intel back in the late 1990s and early 2000s. Promote an alternative. In this case it should be RISC-V (pronounced RISC FIVE). RISC-V is a ten-year-old ISA that was developed at Berkeley, the same university complex that gave us the first RISC chips that led directly to MIPS, SPARC, and yes, even the first ARM chips. Except this time RISC-V is an open ISA, meaning anyone can create silicon using it and not have to pay for the privilege. And more importantly not get bullied and threatened by any controlling organization or business, which is what Arm has evolved into.
So here I am again doing my small part to advance a new way of computing. I am but one of very many. From what I can tell the use of RISC-V processors are rising, starting with the low end in embedded projects — just like it did with Arm. If I can spec a RISC-V processor in a design, I will. If I can’t, I won’t. But over time RISC-V processors will only get better, and those design wins that go to another processor today will go to RISC-V tomorrow — just like it did with Arm. Frankly, as with Intel, Arm has only itself to blame.
Radarwitch
You must be logged in to post a comment.