Over the decades there have been many programming languages, some of which have flowered briefly, and others that have stuck around despite newer, better, and faster competition. Few languages embody this last group more than FORTH, over five decades old and still cropping up wherever a simple, elegant, fast, and compact stack-based programming language fits the bill. [Alexander Williams] has now taken it somewhere new, with a FORTH in RISC-V assembly which runs on the GD32 series of microcontrollers that are RISC-V lookalikes of the popular STM32 ARM parts.

We have to admit to last having used FORTH on an 8-bit home computer in the 1980s, aside from a moment’s idle play on discovering that the Open Firmware on Apple computers is a FORTH interpreter. Thus we’re intrigued by this implementation, but not from a position of FORTH expertise. We’d expect such an efficient language to be extremely quick though, so it’s definitely something to keep an eye on for when a suitable dev board comes our way. If it interests you, take a look at the GitHub repository.

If you missed the Chumby, we’re sorry.  They were relatively inexpensive Linux appliances that acted as a clock, Internet radio, and feed reader. The company went belly up, although there was some functionality remaining thanks to one of the founders and now, for a subscription fee, you can still keep your Chumby operating. However, [Doug Brown] bought one with the goal of using it for his own applications. But the 2.6.28 kernel is showing its age. So he decided to push a new kernel on the device.

If you are a Chumby enthusiast, don’t get too excited. The goal isn’t to provide the existing Chumby apps with a new kernel, [Doug] says that’s probably impossible. Instead, he wants a modern booting infrastructure and kernel on the device for his own software.

The post is only part one, but it covers how he got U-Boot to load from an SD card. Given the success of that, we don’t think it will be long before the new kernel is running, too.

Understanding the boot process is a bit of arcane knowledge and [Doug] found back in 2013 that he didn’t quite understand it well enough to get the 3.13 kernel on the box, but now he’s ready to take the challenge and based on his work so far, we agree.

We were sad when Chumby stopped selling hardware. Chumby had white labeled the device to other companies, too, and we saw at least one of those driving a robot.

The HP-16C Computer Scientist is much beloved as the only dedicated programmer’s calculator that Hewlett-Packard ever made. Most surviving examples in the world are well-used, and you haven’t been able to order one from HP since 1989. Thus, [K Johansen] set about building a tribute to the HP-16C using modern hardware.

The build relies on a Raspberry Pi Pico as the brains of the operation. As with so many classic HP calculators, it operates in Reverse Polish Notation, and includes the customary stack operations. To serve a programmer well, it’s set up to accept entry in hexadecimal, octal, decimal, and binary formats, and can readily convert between them. Beyond that, it’s equipped with the usual arithmetic operators, as well as bitwise operations like NOT, AND, and so on.

Perhaps what we love most, though, is the keypad. It was all put together with a combination of cheap AliExpress keypads, a label maker, and a laser printer. It’s a wholly DIY job, and a little rough around the edges, but it makes the calculator far easier to use.

It’s not an exact replica of the HP-16C, but the differences in operation are minor.Those wishing to build their own can grab the required files from the project’s Github page. We’ve seen replicas of other classic HP calculators before, too. If you’ve got your own mathematical projects brewing up in the lab, don’t hesitate to send them in to the tipsline!

The original Ghostbusters movie is a classic that’s still delivering nearly 40 years after its release — just let that sink in for a minute. Almost every aspect of the film, from hand props to quotes, is instantly recognizable, even to people who haven’t based their lives on the teachings of [Venkman], [Stantz], and [Spengler]. To wit, we present this PKE meter-style WiFi scanner.

Of course, [Kevin McAleer]’s project is strictly in the “Just for Fun” category. But that doesn’t mean it’s not at least somewhat useful. The design is pretty close to the original PKE meter, with a little bit of creative license taken to make it easier to build. Guts include a Raspberry Pi Pico W and a generous 320×240 LCD display. The body of the meter is entirely 3D printed; design files are of course available. The meter’s arms are geared together to move with a single hobby servo.

On the software side, [Kevin]’s GUI lets users see a list of WiFi hotspots in the area and select one from the list. From there, the position of the arms is determined by the RSSI for the hotspot, similar to how the prop was supposed to indicate the proximity to a spook, specter, or ghost. There’s perhaps a bit of a missed opportunity by not adding LEDs to the arms, but we’ll let that slide.

The video below has full design and build details, but fair warning that it’s a bit on the long side. That’s probably just a reflection of how much work [Kevin] put into this, though. Of course, you may rather build a PKE meter that “actually” detects ghosts, in which case we’ve got you covered.

Often with more “modern” complex protocols involving handshaking, token exchanges, and all the other hoops and whistles accompanying them, we forget how useful and powerful serial can be. In what might be a wonderful tribute to that, [Davide Gironi] created a simple AVR-powered 16-digit serial display.

It can display two numbers, and that’s it. A MAX7219 drives the display, and the brains are an ATmega8. It’s straightforward to send new values: a start byte, a CRC, the data to display, and an end byte. A CP2102 provides a UART to USB interface to connect to a host. An EEPROM helps it remember the last numbers shown. It supports positive, negative, and floating-point numbers.

This is a beautiful example of doing one thing and doing it well. The design is simple and allows it to be used for anything. You can show the current stock market price, the time for the next two trains for your commute, or whatever else you can think of. [Davide] included a schematic, code, and a 3d printed enclosure.

Perhaps the idea could be combined with a clever design for a single-motor seven-segment display.

Over the last few years we have brought you many stories about John Deere tractors, and how their repair has been locked down such that only manufacturer-authorised technicians can work on them. They’ve become a poster child in the battle for the right to repair, a symbol of the worst practices. Finally now we can bring you some good news of sorts, as the agricultural giant has signed a memorandum of understanding with the American Farm Bureau Federation to ensure that their products will henceforth be repairable by people without Deere approval.

We can’t imagine that Deere will have taken this step willingly, and while we’d like to imagine that consumer protests in favour of right-to-repair have hit their mark, we’re guessing that it’s more of an economic pressure at work alongside the threat of legislation outside their native America. If farmers getting caught out waiting for a Deere van to arrive while their crop withers in the field wasn’t enough, when the price of a second-hand tractor without the DRM outstrips that of a newer one with it, eventually the sales of new tractors will also suffer.

So this is good news, and we’re guessing that other agricultural manufacturers doing the same DMCA practices will now follow suit. But it’s not a complete victory. The problem starts not with the DMCA restriction itself, but with the extension of the machine’s computer system into every part, including those many parts which simply don’t need it. It’s not a complete victory if anyone can now use the software to register a new hydraulic valve with the system; instead that hydraulic valve should not have to be authorised in the first place. It’s this creeping unnecessary complexity which is the true enemy of right-to-repair, and we shouldn’t forget that.

Header image: Dwight Sipler, CC BY 2.0.