TechyMagThings

Among the many forgotten might-have-beens of the games console world, the Atari Jaguar occupies a special place. It was the final gasp of Atari Corporation, the Jack Tramiel-era incarnation of the famous pioneering game console brand that brought us the ST line of computers, and like Marlon Brando’s Terry Malloy character from On the Waterfront, it coulda been a contender. But the early ’90s games business wasn’t kind to the console from Sunnyvale, and it was squeezed from behind by the SNES and Genesis/MegaDrive, and in front from the PlayStation. Thirty years later then, can it run Linux? [Cakehonolulu] is here to show us how.

With only 2 megabytes of RAM and space for 8 megabytes of ROM, this is hardly a powerhouse. But its 16-bit 68000 processor is a supported Linux architecture, albeit with the -nommu flag on compilation. The “Jerry” DSP chip has the required serial port and timer to boot a first Linux kernel, and after a bit of hackery to make it jump to the ROM location, something boots. There’s no init process until the flat executable file for a -nommu kernel is navigated, but with that past a BusyBox userspace and a graphics driver for the “Tom” graphics chip gives it a chunky on-screen console. The code can be found in a GitHub repository, for the curious.

It seems to be the moment for 68k consoles to receive the Linux treatment, as it’s only a few weeks since we saw it on a MegaDrive. Other ’90s consoles aren’t far behind though, with the Nintendo 64 falling to the penguin a few years ago. Meanwhile, the Dreamcast had Linux running decades ago.

Jaguar image: Evan-Amos, Public domain.

In the early 1990s, Don’t Copy That Floppy was an anti-piracy campaign that attempted to connect with computer-savvy youth through the power of hip-hop. While somewhat difficult to imagine given our current draconian Digital Rights Management (DRM) hellscape, warning kids about the potential legal ramifications of duplicating floppy disks containing copyrighted software was seen as necessary since at the time there was usually nothing preventing users from simply copying the contents of one disk to another.

Unfortunately 30+ years down the road, we’re now finding that somebody really should have been backing up some of those disks. Which is why the University of Cambridge of launched the Future Nostalgia project and produced Copy That Floppy! — a phenomenal guide on preserving the contents of floppy disks while we still can.

There’s no telling how much data could potentially be lost to time because its stuck on such an antiquated and fragile storage media, and the situation only gets worse with the passage of time. The problem isn’t just that modern computers don’t have floppy drives. The disks themselves degrade with age, a process which is accelerated if they aren’t stored properly.

As such, Copy That Floppy! only briefly touches on the most ideal situation — that is, buying a USB floppy drive and making copies of the bog standard 3.5 inch disks you might come across. It then moves right on into more advanced topics, such as interfacing with less common drive types, how to safely clean floppies, and the use of advanced tools such as Greaseweazle to analyze captured disk images.

We’ve seen demonstrations of some of these techniques before, and a few years back Adafruit got interested in floppy preservation with modern hardware. But in-depth guides like these that pull all that information together into one place are valuable resources.

In some parts of Canada, you’ll rarely hear someone use the phrase “whatever paddles your canoe” instead of the more usual “whatever floats your boat”– and apparently, at least for one Swede, that’s steam power. The video, linked and embedded below, is a detailed tour of a canoe equipped with a small boiler and an outboard motor that has been converted to run using steam pressure by [Kenneth Karlsson].

The canoe itself appears to be a Grumman of the “prospector” type, wide in body to hold all the gear you’d need for extended wilderness trips– or, in this case, a small boiler. Amidships is the ideal place, as it won’t affect the balance of the boat. Amidships is an odd place to put an outboard– in the North American homeland of the canoe, if you aren’t moving under your own power, it is more common to cut off the curved stern of the canoe and mount the outboard to the newly-made transom. [Karlsson]’s choice to put the outboard off one side will be less maneuverable than a stern mount, but saves the need to modify the canoe and makes for much shorter steam lines. Shorter steam lines means less hose to potentially leak and scald the occupants, as well as fewer losses, so we can’t really argue with the tradeoffs.

The engine is an old two-stroke outboard that has a single steam cylinder retrofitted to it, along with a heat exchanger to warm up lake water with exhaust steam before it heads the boiler. The water is filtered first, of course, but we do hope the new owner– who posts on YouTube with channel “Steam Canoe” is diligent about cleaning the boiler. It doesn’t look like super high pressure steam, but the vapour phase of water is always something to be respected.

If the potential of scalding steam leaks and boiler explosions put you off, but you still won’t pick up a paddle, canoes can be rigged with sails— or you can just hand the paddle to a robot arm. Though given this is Hackaday, maybe you’d rather skip the canoe and climb aboard the good ship Benchy instead.

Sold by German DIY store OBI, the OBI Energy Tracker is a €15 set of two devices, one of which you essentially stick on top of your existing electricity meter. This then allows for electricity usage to be measured and tracked, with the data sent to the second, gateway device. This latter cloud-bound device is linked to an OBI account via the heyOBI app. This correspondingly called for the gateway device to be reverse-engineered and freed from its cloud-based shackles, a task that [Aaron Christophel] happily took upon himself.

The whole process is also covered in two videos, with the first providing all the essentials on reprovisioning the original firmware for a local MQTT server in English, while the second, German-language video focuses on custom firmware for the ESP32-C3 inside of the gateway device.

Inside the reader device is a Cortex-M0+-based BAT32G135 MCU that communicates with the meter via its IR protocol. This is then communicated via 868 MHz LoRa to the gateway device that will be placed somewhere within Wi-Fi reach by the user. Inside this latter device is as mentioned the ESP32-C3, which by default runs firmware that communicates via secure MQTT with an AWS cloud instance for the typical cloud-based shenanigans.

The aforementioned reprovisioning option doesn’t require firmware flashing, just a handful of steps to follow. This involves fetching the 32-bit TEA key, generating your own PKI, running your own MQTTS-capable broker and having the provided Python script handle the rest from there.

Flashing custom firmware is the other option, with straightforward UART/JTAG reflashing sadly disabled by the manufacturer. With the effort required here you could perhaps argue that simply connecting the reader device to a custom gateway device might be a lot easier, especially if you already have a LoRa transceiver and associated hardware.

The Intel 80386 is a rather fascinating slice of computer history. It marked the first 32 bit X86 processor, and was a staple of early desktop computing. Like all chips, it has a number of quirks, one of which being the fact that all commands are executed in microcode. By this nature, it was a rather excellent prospect to be re-implemented in an FPGA core called the z386. However, it was lacking a feature native to the original 386, early start memory access. If you haven’t been c, [nand2mario] went forth to fully implement this feature for FPGA 80386s.  

Instead of taking a cycle to find and allocate the memory required for executing the next instruction, the 386 would start this in the previous cycle. This is achieved in hardware by nature of having a separate memory management unit. In the FPGA, the key difficulty proved to be in getting the computation fast enough to execute within a single cycle. This change netted an approximate 9% performance benefit. However, for [nand2mario] this was too small a performance uplift. 

Some rewrites of the store cue allowed for cutting a cycle out of the process further improving the performance. However, more performance required slight deviations from the design of the original 386. Because code-branches are performance critical, the z386 project now computes the branch memory jump several cycles earlier than the 386, reducing the cycle time for the jumps from 9.25 to a mere 6. Some final changes to the microcode decode frontend rounded out the optimizations covered in this latest blog post.

The net result is an approximate 39% increase in performance in the all important DOOM benchmark. The z386 still not a complete project, the performance is still lacking compared to the 386, and it remains unable to boot Windows. X86 is complicated, which will take time, so make sure to stay tuned for more coverage! While you wait, make sure to check out our original writeup of the z386 project. 

Pauli Rautakorpi, CC BY 3.0.

Flight sims are wonderful to play around with to get immersed in the position of a pilot. Racing sims can give you a thrill that can only be beaten by the real thing. However, most of this tech is on the more expensive side, so it would be great if you could use some of the hardware already found in your house. Many Sony headphones already have rotation and movement data built in for spatial audio, so why not start there?

[Nicholas Slattery] had this very idea and has produced an open-source application to connect your headphones straight to your sim. There’s a surprising amount of support built into many headsets that use a known protocol called the Android Head Tracker HID protocol. This allowed [Nicholas] to connect a family of Sony headphones straight into OpenTrack, which is often used with flight sims. The best part is you can still use the headphones as normal with a Bluetooth connection.

If you want to give this a try with your own rig, check out [Nicholas]’s GitHub here. While flight and driving sims might be expensive to put together, it’s never too hard to hack together something to lower that barrier! Whether it’s a flight sim force-feedback joystick or driving sim hand-breaks we got you!

The 19th century was an absolutely electrifying era, including in a literal sense. Although the phenomenon of electricity had been known by that time for centuries, actually making it do useful work was a much taller order. Aside from big, coal-powered generators, there also was a need for a more compact electrochemical solution, such as in the form of a wet or dry cell. One of the first major commercial successes here came in the form of the Leclanché cell, such as the genuine version that [Big Clive] found in an old UK building’s attic and has now revived.

Invented in 1866 by French scientist Georges Leclanché, the Leclanché cell features an ammonium chloride electrolyte solution, carbon cathode and zinc anode. There’s also a manganese dioxide depolarizer for preventing hydrogen build-up. Here water is the solvent for the ammonium chloride (also known as sal ammoniac).

The version that [Clive] got his grubby mitts on features a glass container, an already partially consumed zinc electrode and a slightly cracked porous ceramic tub that contains the carbon electrode and the manganese dioxide. After placing the components inside the specially shaped glass jar and filling it with an electrolyte mixture of one part ammonium chloride and four parts water by weight, the cell starts generating its approximate 1.4 VDC.

This type of wet cell was very popular, being essentially ‘rechargeable’ by topping up the water and replacing the zinc electrode consumable. They did suffer from a voltage drop-off during use due to increasing internal resistance, something that got improved upon with the zinc-carbon dry cell. Itself effectively an evolution of the Leclanché wet cell.

From there zinc-carbon dry cells got replaced with alkalines, which itself got mostly replaced by NiMH and Li-ion cells. Despite more than a hundred years between the electrochemical cell that [Clive] featured in his video and today’s batteries, it’s clear that this wet cell was quite literally just the Victorian-era equivalent of an alkaline AA cell.