I’ve been away from writing for a bit for personal reasons and I’ve missed talking much about many events in the RISC-V world this year. Here’s a jumble of thoughts from October of 2021.
Low Points: BeagleV Starlight canceled, Nezha/D1 launch issues
I was lucky to have tinkered with the prerelease BeagleV board (codenamed Starlight) that featured the StarFive
JH-7100 SoC. It was well documented, had an amazing technical group of active participants from both corporate and hobbyist backgrounds, all working together on merit, and good tooling. Antmicro’s ‘Renode‘ emulator made developing on these parts a breeze.
Unfortunately for the business, BeagleV/Starlight and StarFive were unable to reach a production agreement and BeagleV Starlight project was cancelled. I did some software and hardware work that went into the proverbial chipper, but I managed to learn and refine some skills along the way. I remain hopeful that the low-volume (Two core) JH-7100 and later (Quad core, embedded GPU, PCIe) JH-7110 will be delivered at a similar price point by the likes of Antmicro or Radxa, which has already missed their ship date. It’s all resulted in some thrash, but it’s possible that all the players (Beagle, Antmicro, Radxa, Starfive) dust off and ship RISC-V boards.
I have possession of a Nezha developer board. This is the official development board made by Allwinner as a vehicle for their D1 chip. By contrast to StarFive, documentation on this device and board is poor. The maker of the chip and the board, Allwinner,
having a pretty poor record playing nicely with open source developers with license violations being common. When it was at a price point similar to BeagleV, it seemed an underdog as a single core device, but it did have the claim to fame of being the first shipping device of supporting the RISC-V Vector extension. I’ve been a member of a few different discord/slack/telegram groups for this device and they’ve all been dominated by people stuck at the starting line: just finding a maintained distro that doesn’t require a login in Chinese and a phone number in China is a common challenge.
Unfortunately for many developers, D1 supported only 0.7.1 of Vector, which has source and binary incompatibilities with the final 1.0 version of that extension which is currently (October 2021) in final stages of public review. This part also really requires Allwinner’s own use of GCC/Binutils to use these extensions well. Interestingly, the RISC-V part of this SoC comes from Alibaba’s XuanTie C906 line, which was itself recently open-sourced, though there have been serious issues trying to land Alibaba’s incompatible work in upstream projects like GCC and QEMU.
I’d love to be able to comment more on the actual development board, but can’t as it appears my board is apparently totally DOA. I hope to be able to write more about it soon.
This board gets the (somewhat deserved) criticism of being overpriced when compared to high-volume devices like Pi and the (awkward) criticism of having a single 1.0Ghz core and relying on an old version of the Vector specification. As the final version still doesn’t exist and fab times just plain take a while to get from Verilog to real silicon, we can be only so mad at the first chip to support even a pre-release V spec. We can be more upset that the chip requires violating the RISC-V specification on reserved bits in the paging machinery. All this does lead to an up-looking highlight to finish up this catch-up.
On the Horizon: Allwinner D1s/F133
This week, there’s been interest in a new revision of the D1. The Allwinner D1s (sometimes called the “F133” for reasons I haven’t yet grasped) is a cost-optimized version of the original D1. Where the D1 really seemed to ship only with their own development board, Nezha, the D1s seems to come out of the gate ready for the likes of SeedStudio and Mango Pi’s ~$10USD RISC-V board or in low quantity to put on your own open-source boards, like Xassette.
It’s a slightly confusing product, but some of that may just be translation/documentation issues. It’s cost-reduced, and that filters through to the boards we’ve seen so far. There’s 64MB of RAM on board, but it’s sold as “Linux ready”. The removal of HDMI signaling means no monitor and 64MB will require a very stripped down system. Cramming Linux into the 8MB on a K210 was (barely) possible, so this must be possible, even if cramped. Still, for a single-purpose or educational environment, that’s probably OK. The Allwinner F133 overview avoids any comparison to D1, refers to itself as “video decoding platform”, and even avoids use of the phrase “RISC-V” completely.
It’s interesting that one of the most controversial RISC-V chips of 2021 managed to ship a second revision this year while we have so many that have just seemingly collapsed under their own weight or never found their legs beyond original announcements. (Blink twice if you’re alive, PicoRio!)
As we approach the end of the year, we’ve had quite some changes in the RISC-V ecosystem. It’s likely that the product families that have most met or exceeded my expectations are the BL602/706 family and Espressif’s menagerie of ESP32-C3 and ESP32-C6.
What have been your biggest disappointments or surprises in RISC-Ville?
mark says:
I’d fanfared this year as “The Year Of The RISC-V Linux SBC”… I guess that shows my naivety, but also the level of my willing this technology to succeed.
I guess the biggest disappointment was the cancellation of the BeagleV. Didn’t we all want a capable, open source board? My hope, is that they’ll be back, and that the hiatus will have given them more time to consider what they’re doing.
A good friend of mine also bought a Nezha, and his was DOA too. I really hope that that can be rectified.
Nevertheless, there are joys too:
– The fact that RISC-V design has got to APU level is something, and not to be trivialized.
– That we’re at the point where we’re seeing SBC offerings – with undoubtedly more to come.
– The open sourcing of XianTie (and the announcement that they’ve already sold in excess of 2.5billion cores).
– Seeing the Alibaba T-head RVB-ICE Development Board being offered for sale – a board sufficient to drive ATMs, cash registers, digital signage etc…
– Also, it’s so refreshing to see the work being done in educational institutions in India, China, Switzerland, Finland… Perhaps the young will come up with different solutions! And
– the frankly magical ONiO.Zero microcontroller, which doesn’t need a power source – “Any sufficiently advanced technology…”
There’s a lot of interest in RISC-V. And a lot of companies – from Apple (can you believe that?!) all the way down, investigating what RISC-V can offer.
Robert Lipe says:
It’s been a mixed bag, for sure. Hopefully the committee ratifying a bucket full of extensions that have been simmering for a while will make it easier for the next generation of chips and the tool and library work around that.
I, too, am really bummed about BeagleV. It was an easy crowed to root for and participate in. Four cores and “desktoppy” at $129 ($149?) just seemed a sure ticket for success and still not really approached by anyone else. The project was really well run. Others claim to be working with JH-7100/7110, but I haven’t seen anything beyond press releases from them yet. The BeagleBoard foundation is still saying they’ll be back with a RISC-V solution and a data sheet that we’ve already seen. The only one I can think of in that space right now is D1/D1s and while it can hit nice price points, single core in 2021 makes it more of a big MCU than a general purpose MPU. There’s space in the market for something between the aging K210 and an Unleashed.
I have a lead on investigating the DOA D1, but even for those that have them powered up there’s a large amount of thrash around just getting them booted and an OS on them. Maybe once the kernel upstreaming issues are worked out (and they’re substantial) we’ll get a working distro that you can just dd to an SD card and run but it’s clear that we’re far from that right now on D1/Nezha.
Onio is certainly very interesting and one of the few places I’ve seen where RV32EMC makes sense, but have they actually shipped or even announced price yet? At a glance, I can’t find that they’ve actually shipped.
I’ve seen that 2.5B number, too, and think it’s complicated. That’s spread over their eleven designs and I suspect a lot of them are in very dense compute clusters inside Alibaba itself. (Which still counts…) It doesn’t really translate to hobbyist or even consumer-like products like a Raspberry Pi. We probably have similar numbers coming in now from Espressif with ESP32-C3 and maybe in quiet products using the designs by Bouffalo.) Hopefully we can soon tease apart the community/political issues of Allwinner and Xauntie and get lines drawn around those parts (maybe they’re “errata” vs. the RISC-V spec) and begin to see some strong hobbyist uptake. I’ll admit to still tinkering on my BeagleV and hoping it’ll work on Nezha if it ever powers up. :-/
I agree that RISC-V is getting a LOT of mindshare in interesting places and this should be an interesting rocket ride.
Thanx for writing!
mark says:
My friend with the Nezha emailed me this link today :
https://blog.3mdeb.com/2021/2021-11-19-nezha-riscv-sbc-first-impression/
And I wondered if it was of any use to you…
Robert Lipe says:
That seems a pretty reasonable intro to the board.
We’ve since concluded that my sample was missing many pieces and was broken enough to write it off as a DOA.
The first thing that cost me many hours is that they ignored the USB Power Delivery spec and misconfigured the resistors for a power target. If you have USB 3.0 power source and marked cables (e.g. Apple’s…) the device simply will not power on. This indicates they both dismissed the normative design rules for power and failed to actually test the product in the real world. USB Power expert railed on Raspberry Pi 4 (who later admitted the design mistake) pretty harshly at https://medium.com/@leung.benson/how-to-design-a-proper-usb-c-power-sink-hint-not-the-way-raspberry-pi-4-did-it-f470d7a5910
They also reused bits of the PTE that were already used by the spec, so they’re not conformant with the RV39 paging scheme, making upstreaming their kernel work problematic. See https://lwn.net/ml/linux-kernel/CAAhSdy2-y4xpM9PCrS0vgCN9ngFiBygeDOWcbgsX6Myb4XjDQg%40mail.gmail.com
mark says:
Hi
I’ve just heard from Christian Stewart that there’s a draft PR of SkiffOS for Nezha support here:
https://github.com/skiffos/SkiffOS/pull/189
I was wondering if you might like to test it…