Now The V In RISC-V Stands For VRoom

Hundreds of variations of open-source CPUs written in an HDL seem to float around the internet these days (and that’s a great thing). Many are RISC-V, an open-source instruction set (ISA), and are small toy processors useful for learning and small tasks. However, if you’re [Paul Campbell], you go for a high-end super-scalar, out-of-order, speculative, 8 IPC monster of a RISC-V CPU known as VRoom!.

That might seem a bit like word soup to the uninitiated in the processor design world (which is admittedly relatively small) but what makes this different from VexRISC is the scale and complexity. Rather than executing one instruction at a time sequentially, it executes multiple instructions, completing them concurrently in whatever order it can handle. The VexRISC chip is a good 32-bit modular design that can run Linux. It pulls a solid 1.57 DMIPS/MHz with everything turned on. The VRoom already clocks in at mighty 6.5 DMIPS/MHz, with more performance gains. It peaks at 8 instructions every clock cycle with a dual register file and a clever committing system to keep up.

VRoom is written in System Verilog to leverage Verilator (a handy linting and simulation framework), and while there is some C that generates different files, we’d wager it is pretty run-of-the-mill compared to a TypeScript based project. VRoom currently boots Linux thanks to an AWS-FPGA instance (a Xilinx VU9P Ultrascale), though it has to be trimmed to fit. [Paul] has big plans working his way up to a server-class chip with lots of cores and a huge cache.

It’s all on GitHub under a GPLv3 license; go check it out! [Paul] also has a talk with lots of great details. If you’re interested in getting into RISC-V but a server-class isn’t your speed, we heard Espressif is starting to use RISC-V cores in their ever-popular ESP series.

Run Your Own Server For Fun (and Zero Profit)

It seems there’s a service for everything, but sometimes you simply learn more by doing it yourself. If you haven’t enjoyed the somewhat anachronistic pleasures of running your own server and hosting your own darn website, well, today you’re in luck!

Yes, we’re going to take an old computer of some sort and turn it into a web server for hosting all of your projects at home. You could just as easily use a Raspberry Pi –even a Zero W would work — or really anything that’ll run Linux, but be aware that not all computing platforms are created equally as we’ll discuss shortly.

Yes, we’re going to roll our own in this article series. There are a lot of moving parts, so we’re going to have to cover a lot of material. Don’t worry- it’s not incredibly complicated. And you don’t have to do things the way we say. There’s flexibility at every turn, and you’re encouraged to forge your own path. That’s part of the fun!

Note: For the sake of space we’re going to skip over some of the most basic details such as installing Linux and focus on those that have the greatest impact on the project. This article gives a high level overview of what it takes to host your project website at home. It intentionally glosses over the deeper details and makes some necessary assumptions.

Continue reading “Run Your Own Server For Fun (and Zero Profit)”

Haptic Smart Knob Does Several Jobs

A knob is a knob, a switch is a switch, and that’s that, right? And what about those knobs that have detents, set in stone at the time of manufacturing? Oh, and those knobs that let you jog left to right and then snap back to center — that can’t be modified…right? Well, you likely know where this is going, and in the video below the break, [scottbez1] shows off a new open source haptic input knob that can be all of these things with just some configuration changes!

The list of possibilities is long: virtual snap points, virtual spring loading, virtual detents, virtual end points. It’s a virtual smörgåsbord of configuration options that make this haptic smart knob a one stop shop for all of your knob needs. This is all possible because the knob contains a high resolution magnetic encoder chip that has a single degree resolution. The sensor is coupled, through software, to a brushless DC motor. The round LCD gives visual feedback as well.

As [Myself] on the Hackaday Discord channel noted, having configurable spacing and strength for detents, springs, and stops, is nothing short of incredible. Being able to reconfigure the knob at-will means that it can become context sensitive. It’s wonderfully unique and it’s open source, so you can make your own with the information available at GitHub.

And according to its creator, the only thing the Haptic Smart Knob can’t do is do your taxes or blend your margarita. Well, it’s open source, so perhaps some of our more enterprising readers can submit just the right pull request.

This isn’t Hackaday’s first Motorized Volume Knob feature, but it might be one of the neatest we have seen so far. Thanks to [mattvenn] on the Hackaday Discord server for the great tip!

Continue reading “Haptic Smart Knob Does Several Jobs”

RFM9x module held in an adapter board with flexipins

FlexyPins Might Help With Those Pesky Castellated Modules

[SolderParty] just announced FlexyPins (Twitter, alternative view) – bent springy clips that let you connect modules with castellated pins. With such clips, you can quickly connect and disconnect any castellated module, swapping them without soldering as you’re prototyping, testing things out, or pre-flashing modules before assembly. They’re reportedly gold-plated, and a pack of ~100 will set you back 6EUR, shipping not included.

Of course, this is basically “fancy pieces of wire”, purpose-shaped, gold-plated and, hopefully, made out of material that is springy enough and doesn’t snap easily after bending a few times. We’ve seen this concept used for prototyping before, with random pieces of wire doing a pretty good job of maintaining connectivity, but these clips bring it that much closer to production-grade. It also makes us wonder – just how hard it is to solder 30-40 of them into a circuit? Do they self-align enough with the footprints given, or do you have to hold them with tweezers at a peculiar angle as you solder them? Time will tell, of course.

Continue reading “FlexyPins Might Help With Those Pesky Castellated Modules”

Hands probing inside a case with tools

Hardware Hacking 101 Needs Matching Toolkit

One doesn’t always have the luxury of sipping tea comfortably while hacking a piece of hardware at a fully-equipped workbench, where every tool is within reach. To address this, [Zokol] shares an early look at a hardware hacking toolkit-in-progress, whose purpose is to make hacking sessions as productive as possible while keeping size and weight within reasonable limits. There isn’t a part list yet, but there are some good tips on creating your own.

A view of a wide variety of toolsTo put together an effective hardware hacking toolkit, one must carefully consider what kinds of tasks need to be performed, and in what order. Once a basic workflow is identified, one can put together a set of complementary hardware tools and resources to meet the expected needs. The goal is to have the tools to go as far as one can in a single session, and identify any specialized equipment that will be needed later. That way, follow-up sessions can be as effective as possible.

Since hardware hacking is all about inspecting (and possibly modifying the behavior of) electronic devices, [Zokol] observes that step one is always to begin with external interfaces. That means common cables and adapters should all be part of a hardware hacking toolkit, otherwise the session might end awfully early. The next step is to open the device, so common tools and ways to deal with things like adhesives are needed. After that, diagnostic tools like multimeters come into play, with tools becoming more specialized as investigation proceeds. It’s a very sensible way to approach the problem of what to bring (and not bring) in a hardware hacking toolkit, and we can’t wait to see what the final version looks like.

Hardware hacking sometimes involves hardware that can’t be opened without damaging it. The Google Stadia controller is one such piece of hardware, and [Zokol] addressed the problem of how to permanently disable the microphone by figuring out exactly where to drill a hole.

the Caps Wiki logo, showing a few bulging capacitors, with "Caps Wiki" text under it

Caps Wiki: Place For You To Share Your Repair Notes

A right-to-repair battle is being waged in courts. The results of it, we might not see for a decade. The Caps Wiki is a project tackling our repairability problem from the opposite end – making it easy to share information with anyone who wants to repair something. Started by [Shelby], it’s heavily inspired by his vintage tech repairs experience that he’s been sharing for years on the [Tech Tangents] YouTube channel.

When repairing a device, there are many unknowns. How to disassemble it? What are the safety precautions? Which replacement parts should you get? A sporadic assortment of YouTube videos, iFixit pages and forum posts might help you here, but you have to dig them up and, often, meticulously look for the specific information that you’re missing.

The Caps Wiki talks a lot about capacitor replacement repairs – but not just that. Any device, even modern ones, deserves a place on the Caps Wiki, only named like this because capacitor repairs are such a staple of vintage device repair. You could make a few notes about something you’re fixing, and have them serve as help and guideline for newcomers. With time, this won’t just become a valuable resource for quick repairs and old tech revival, but also a treasure trove of datapoints, letting us do research like “which capacitors brands or models tend to pass away prematurely”. Plus, it also talks about topics like mains-powered device repair safety or capacitor nuances!

Continue reading “Caps Wiki: Place For You To Share Your Repair Notes”

Pre-exploded PSU close-up: shown is inductor with the heatsink it shorted against.

The Little Replacement PSU That Could: Kill A Microsoft Surface And Monitor

Recently [Big Clive], everyone’s favorite purveyor of anything electronic that’s dodgy, cheap, cheerful, decidedly crispy or any combination thereof, got sent a very dead external power supply unit. Being clearly a third-party PSU with poorly written and many (likely not truthful) safety approval markings on its label, this PSU had the dubious honor of having destroyed a Microsoft Surface computer as well as the monitor that was connected at the time.

In [Clive]’s video (also embedded after the break) the black and very crispy board is examined, showing a wealth of vaporized traces and plenty of soot. What’s however most fascinating is the failure mode: instead of something obvious like e.g. the main transformer between the primary and secondary side failing, here it would seem that an inductor (see heading image) on the secondary side had its insulation rubbed off and shorted on a nearby heatsink. A heatsink that just happened to be also electrically connected on the primary (mains-level) side.

Judging by the former owner’s report and aftermath, this led to a very sudden and violent demise of the PSU, with mains power very likely making its way into the unsuspecting Surface system and connected monitor. The number of ‘very nope’ design decisions made in this PSU are astounding, and a lesson for both aspiring EEs and anyone considering getting a ‘cheap’ third-party replacement PSU.

(Thanks to [Helge] for the tip)

Continue reading “The Little Replacement PSU That Could: Kill A Microsoft Surface And Monitor”