TechyMagThings

We aren’t sure what [Lazy_Duck] is doing with video games, but it must require a lot of controllers. Dismayed at the cost and complexity of commercial gamepads, they started soldering and 3D printing to get a cheaper basic controller.

The emphasis is on throwing things together, so there’s no dedicated PCB. Just a protoboard with an RP2040-Zero, a joystick, a few buttons, and a microswitch. A 3D-printed case rounds out the project.

On the printing side, the device uses heat-set threaded inserts, which should make for a very sturdy build. For software, the GP2040-CE firmware handles everything, acting like a controller and managing configuration via a web page.

Even if you don’t want a cheap gamepad, you could apply the principles and software used here to create any kind of gamepad you want. The firmware makes good use of the dual-core RP2040. It also offers a lot you could add to your version of the cheap controller, like OLED displays, RGB LEDs, and more.

Of course, you could also get fancy with the 3D printing side, too. For example, a resin printer makes nice button caps.

In a world where wireless earbuds are increasingly seen as devices that you toss into the e-waste bin as soon as they stop working, it’s heartening to see companies take the opposite approach with their designs. In a recent teardown of the new Fairbuds 2 by [iFixit] we get a blow-by-blow report of disassembling one of these devices, getting to its rechargeable LIR1054 coin cell, as well as the very accessible PCB should you have to replace a shorted capacitor or similar issue.

Much like with the first version, the 3.6 V lithium-ion coin cell can be extracted simply by pulling on the battery door, which leverages it out of the enclosure. Despite this easy access method and no glue these earbuds are still IP54 rated, so they’re safe to wear when you’re dashing for shelter in a sudden downpour.

To get further into the device, you have to overcome the plastic clips that hold the enclosure together, along with what appears to be a few dabs of glue. Inside it you find the PCB containing the guts, including the Airoha AB1577S, Cortex-M4F-based IC that provides the Bluetooth Low Energy capabilities as well as enabling the touch control and other features.

Below the PCB is the coin cell holder, followed by the only part that saw real glue usage, namely the driver section. Presumably this is the compromise to keep things like sweat out of the device. Even so, after disassembly [iFixit] managed to reassemble the device and the earbud remained in working condition.

The case for the earbuds is even easier to disassemble, using just some bolts to unfasten. The USB-C port is soldered to the PCB which [iFixit] dinged them on, but still gave it a 10/10 on their repairability score.

Compared to Apple’s AirPods this is obviously a whole different world, although recently [iFixit] was somewhat pleased with the most recent AirPods generation being slightly more repairable, with non-destructive entry for a battery swap at least somewhat feasible.

Determining the shape of an object which can change dynamically is a bit of a challenge, one that especially vexes those who are really into Virtual Reality. Sensing the orientation of various limbs and appendages usually requires external sensors like cameras, or limit the focus to specific details like just the hands and fingers of the player. A more comprehensive and potentially flexible approach might be possible using optical waveguides, as demonstrated by [Qifan Yu] et al. in a recent article in Advanced Intelligent Systems.

Waveguides are structures that guide electromagnetic waves, with optical waveguides such as used here targeting EM radiation in the optical band. This can even allow for the use of cheap and plentiful optical fiber, though here custom elastomeric waveguides are manufactured. These are laid out onto the sheet in a double-sided, overlapping zig-zag pattern, which allows for easy reconstruction of the shape of said sheet based on how the wave propagation through the waveguide changes.

By characterizing the behavior of the signals through the waveguide, its shape and thus that of the sheet can be reconstructed. This was then demonstrated to be accurate by wrapping the sheet around a volunteer’s arm, elow and hand, detecting the flexing and movement of individual joints.

Although fairly bulky in the demonstrated configuration and with an unoptimized algorithm, it’s conceivably something that can be miniaturized to the point where it can be woven into regular fabric. This could make for sensor sheets that could track the configuration of everything from robots to human bodies for something like VR purposes.

In the 8-bit home computer boom of the early 1980s, Sir Clive Sinclair’s machines were always among the cheapest on the market, often packing a surprising level of sophistication in their limited hardware. If there was one component that was key to their success it was the Ferranti ULA, or Uncommitted Logic Array, a clever way to make an ASIC from a chip containing a library of logic parts ready made. The Sinclair ULAs have been reverse engineered, but their full details have remained a mystery. Until now it seems, because here’s [Happy Little Diodes] with a treasure trove of original Ferranti design documents covering all the Sinclair parts.

The documents were picked up on eBay, and contain folders with printouts, engineering drawings, and hand written design notes. They cover the full range of Sinclair products of the era, including the ZX81 and Spectrum, the ZX printer, the Microdrive, the Spectrum Interface 1, and even the curious little flat screen TV. Oddly the IP is now held by the satellite broadcaster Sky as the holder of Amstrad’s portfolio, but fortunately Sky have recognised their historical importance and allowed their sharing with minimal changes. They’re all catalogued with download links in a Google spreadsheet, so dig in and see what you can find. Of particular interest are the ULAs that haven’t been reverse engineered yet, and the subtle differences between different versions of the same ULA as the engineers tried to fix bugs. The video is below the break.

If you’re curious about the ULA and Ferranti, we linked to a period film about it.

Since we last covered the way that the Linux Kernel project has been dealing with the influx of code created using LLM-based coding assistants, all the way back in April, things have changed a lot, with most recently the Linux maintainers deciding to fully drop the requirement to mark LLM-assisted commits with the Assisted-by tag.

While not a fully uncontroversial decision – as also reported by Phoronix – with key maintainers already having made this decision it seems certain to proceed. This is not the only change made fairly recently, with a ‘Sashiko’ bot introduced that is supposed to handle code reviews.

In a July LKML post [Linus Torvalds] defends this decision, with a follow-up post in August by [Jakub Kicinski] it being stated that budget has been secured for using Meta’s LLMs, using said LLM-based resources for reviewing patches, as well as creating and editing commit messages. As noted by [Jakub] they’re running multiple frontier models on each patch to try and weed out confabulations.

Whether this will prove to be the right decision remains to be seen. Whereas most open source projects have firmly banished or heavily curtailed LLM-based contributions on slop, copyright as well as licensing grounds, the Linux Kernel project may be an interesting experiment in what the outcome of the exact opposite approach will be.

If you want to play old Commodore games, there are C-64 emulators available for just about any platform– but most of them are so high level, they’re really meant for just that: playing games. [antirez] has a different goal with his c64-hw-sim project— it’s a lower-level emulation that simulates every chip and every connection on an ASSY 250407 motherboard, and all the chips on it, too. Ever wondered what happens when a specific chip is missing, or a random pin is shorted to ground or forced high? You can do all that in software, with no risk of harming antique hardware.

While that might be a fun bit of faffing about for a certain sort electronics sadist, the real utility is to learn about the hardware, both in the abstract and to help you troubleshoot a board you might have. It’s likely that many given failure modes reproduce the same effects– lots of things can knock out the display output, for example–but at least if you’ve reproduced a flaw in software you can try testing the hardware to see if that’s the cause of your problem. Assuming the simulation covers your hardware issue, anyway.

There’s cycle-accurate chip emulation for the processor, CIAs, SID and VIC-II via code by [Andre Weissflog], a.k.a. [flooh]. Meanwhile analog circuitry in the video, audio and power sections are not simulated so not everything fault will be replicable here. Still, it might be a neat tool– just don’t try and run any games on it, because even on high-end modern hardware it only runs at about one-third speed. That’s fast enough for diagnostics, but not so much for Maniac Mansion, never mind Elite. 

Speaking of Elite, did you know the source– both of the port and the original– is available with comments? If you want an emulator you can play, you can get it on everything from microcontrollers like Teensy to your personal computer.

Thanks to [Salvatore] for the tip!

Do you want to get an AI agent to do something to an iPhone? You could try and jailbreak the device and do some heavy software hacking, or… you could grab a microcontroller off the shelf and have it do the hard work. [Henry Yuan] explains how to achieve this with an ESP32.

The first step is getting an AI agent access to the current state of the phone screen—which [Henry] achieves with AirPlay screen mirroring and UxPlay. A Gstreamer pipeline is then used to feed the screen as a JPEG stream to the AI agent of your choice. Then comes control, which is achieved by an ESP32-S3 acting as a USB-HID device, emulating both USB mouse and keyboard. With iOS AssistiveTouch enabled, this gives the agent control over inputs to the device. From there, it’s up to the AI agent to figure out the actions to make to achieve the desired behavior, which is obviously very use-case specific.

It might sound a little convoluted, but this approach has benefits. There’s no requirement to have an Apple Developer Account, or XCode, or a Macintosh at all. You can just get your agent tinkering away on the phone without any of that fussy overhead. We’ve featured some other great iPhone hacks of late, as well. Video after the break.