Preventing A Garage Door Opener From Rebooting When Offline

It’s always great when a smart garage door opener allows for easy local integration into a smart home network, but it’s not so nice when said device still insists on connecting to certain remote servers, and even reboots constantly due to time-outs. This was the problem that [Kusha] was facing with a LiftMaster MyQ Home Bridge garage door control. The solution ended up being to dump the key for the encrypted MQTT communication and setting up a dummy server.

The encryption key is stored on the Cortex-M4 MCU, with fortunately the debug interface with the SWD pins and everything else left in plain view on the PCB. From there it only takes a bit of creative wiring and a bit of Arduino code to read out the needed data.

After this you still need to set up an MQTT broker with this key installed and capable of serving pings to the device after it connects. For this part [Kusha] provides a Docker configuration to streamline this process if you are into containers. Setting up an existing Mosquito or similar MQTT broker for secure MQTT access isn’t overly complicated otherwise.

Of course the device will still try to connect to the mqdevice.com domains where the manufacturer’s MQTT brokers are running, but with a local DNS server you can gently coax these to be redirected to your own MQTT broker instead. After this the device will be convinced that it’s now Cloud-Enabled and stop trying to reboot all the time to fix the egregious problem of not having internet access after being put on an IoT VLAN or similar.

Custom Firmware For Fortinet FortiGate 60 Firewall/Router

When [Matt Williams] found an old enterprise firewall in the trash, he knew he had to do something with it. After cracking it open, he found that this 2000s-era Fortinet FortiGate 60 hardware firewall has some very hackable hardware in the form of a VIA C3 mainboard. This is an x86-compatible CPU that was very popular in small form-factor and industrial solutions around 2000s, meaning that it should be able to run just about anything that’s happy to run on its 400 MHz single core.

Unfortunately it wasn’t a standard Mini-ITX C3 board like the one that [Matt] also has kicking around, as that one features standard DIMMs for the memory modules. For this firewall the 128 MB of SDRAM was soldered to the board, with the only clue as to how to initialize it in the original firmware. Ergo this firmware had to be reverse-engineered to figure out just how this was supposed to happen.

With that done, Linux 2.4 was happy enough to boot on it with a bit more tweaking. Using the framebuffer driver applications like DOOM happily ran, as the above graphic shows. That it’s very much green is due to only the green pin on the VGA connector being probed. Since it’s a firewall Fortinet only added a physical DE-9 port in addition to the internal IDE interface and CF card slot.

If one were to wire up these pads on the mainboard to physical connectors, it would actually make for a pretty decent little system for what the kids call retro gaming these days.

Reverse Engineer That USB Device In Style

Proprietary device drivers, dedicated applications, and their ilk are the bane of the open-source hacker. If only we could snoop on every device out there, recording the “secret” USB transactions as they go over the wire, we’d have a chance.

[Emir Mrkaljević]’s tool, usb-rea, aims to make this process a whole lot less painful. The workflow is like this: you start capturing on USB, make an annotation about what action you’re taking, press the button a few times, and then move on to the next action.

sudo modprobe usbmon
usb-rea capture start -o lamp.pcapng
usb-rea mark -m lamp.pcapng.actions.json "brightness 0%"    # then click it in the vendor app
usb-rea mark -m lamp.pcapng.actions.json "brightness 50%"   # ...repeat for 3+ values per setting
usb-rea capture stop
usb-rea report lamp.pcapng -o report.md
usb-rea scaffold lamp.pcapng -o lamp_driver.py
usb-rea dissector lamp.pcapng -o lamp.lua      # Wireshark dissector for the same protocol

Usb-rea records all the USB traffic, timestamps it relative to your actions, and gives you a report, a driver, and a Wireshark protocol dissector out the back side. There is even an MCP file so that you can hand off the grunt work to the bots, possibly enabling this to work closed-loop?

Of course, you don’t want to reinvent the wheel, so it’s fun to see that there’s also a usb-rea lookup command to see if your VID:PID is already in the dataset. Most of the devices are CPU coolers, RGB controllers, and other blinged-out computer peripherals, but we imagine that it’s a lot more broadly applicable. We looked for our mouse on the list, but it’s sadly not there.

Usb-rea is not a silver bullet to bring back abandoned peripherals from the grave, because you still need to run the proprietary driver during the recording. But if you get ahead of the game and document the protocols before the manufacturers abandon them, you stand a chance. Get recording!

Borland C++ 2.0 Compiler Source Reconstructed

As the successor to Turbo C++, Borland C++ was a staple of professional IDEs for C and C++ development, starting with the initial 2.0 release in 1991. Being a commercial project the original source code for the toolchains were naturally not made available by Borland, but thanks to the efforts of [Abedegno] we have now got what is claimed to be a byte-perfect recreation, in the sense that the binaries compiled using the toolchain are identical to the original toolchain.

The process of creating the source from the original toolchain binaries is detailed in a separate document, including the use of [Abedgno]’s Claude Code-based Exhume tool to assist in the effort.

Having the source code for BC++ 2.0 available is probably most useful for projects that deal with DOS-based software from the same era, as well as for purely historic interest reason. When BC++ 2.0 was released, the C programming language had only just seen itself standardized in the form of C89, and C++’s initial standard in 1998 was still years away.

Thanks to [Stephen Walters] for the tip.

Using A Toothbrush’s NFC Chip To Unlock A Computer

Depending on which type of electric toothbrush you are using, the replaceable brushes may contain an NFC chip that the handle and possibly base station uses to track various details, such as time spent brushing and when to replace the brush. The Philips Sonicare of [Circuit Helper] is one such unit, with its NFC chip tracking aspects like runtime and pressure.

Unsurprisingly it’s easy enough to read and write this same NFC chip with a PN532 NFC reader and ESP32-S3 MCU. This reveals data fields for everything from brush type, to total runtime and expected lifetime, inviting a bit of experimentation on how certain usage patterns affects these data fields.

This much is perhaps not too shocking, but the fun part is what you can do with the chip after you have figured out how to write to its memory. How to unlock these units and their NXP NTAG213 IC has been figured out a few years ago already, so the hardest part was to figure out what to do with this information.

The demonstrated use case in the video is to unlock an Apple Macbook, which is maybe a bit too niche. Also demonstrated is taking the chip and its antenna out of the brush, which turns out to be quite easy. Perhaps salvaging just this one part of the brush is the more practical and hygienic option, as who doesn’t like building up a strategic supply of ‘free’ NFC chips?

Continue reading “Using A Toothbrush’s NFC Chip To Unlock A Computer” →

USB-C Hub Or Nintendo Switch 2 Dock? Relax, It’s Both!

[Nozomi] travels with a Nintendo Switch 2, but the official dock is bulky and doesn’t seem to be made for travel. USB-C hubs with displays are common, but they won’t work with the Switch. Not without a little hacking, anyway.

It was obvious that the hub wasn’t too far off. It will charge the Switch, so Power Delivery was working. A sniffer showed that even the DisplayPort initialization happened. A little flashing on the hub allowed it to complete the proprietary protocol, and that made TV mode work, but HDR was washed out. [Nozomi] theorized it was a mismatched color space, so that required a patch for a different chip. Another flash forces the right color tag for HDR TV, but there would have to be another patch for HDR DP.

That patch doesn’t exist. Variable refresh rate also does not work. We didn’t find the actual code for the patches, but we still thought the detective work was worth the read. Some people don’t want a more portable dock, but a less portable one.

Reverse Engineering A 1960s Diode-Transistor Logic IC

Before transistor-transistor logic (TTL) took over, diode-transistor logic (DTL) was a common sight especially in pre-IC circuits where it was a major improvement over resistor-transistor logic (RTL). That said, it’s rare to see DTL used in ICs considering how e.g. TI’s 5400 and 7400 series set the trend in the 1960s. This makes the Signetics ST680a quad-NAND gate DTL DIP IC that [Ken Shirriff] ogled recently a bit of a treat.

This was also one of the earliest ICs to use the then brand new plastic dual in-line package (PDIP) for modular convenience, even if [Ken] was none too happy about as unlike ceramic DIP, PDIP requires more extreme methods to decap to access the die for reverse-engineering.

Overall, TTL is faster and less power-hungry than DTL, but it took a while to work out its issues, including noise immunity and fan-in/out issues. Until then alternatives like DTL still made sense as a well-understood and mature technology. In the article an example is provided of how a DTL NAND gate as used in this IC works, which is really quite simple in how it uses multiple diodes to sum the inputs, which subsequently drives the transistors.

We’d like to thank [CuriousMarc] for finding this IC in his strategic reserve of unknown ICs and for doing the initial decapping using hot air, as well as [Ken] for doing the analysis and documenting of this fascinating glimpse into early semiconductor logic history.