Turning A Junk Laptop Screen Into A Portable Monitor

Sure, you can buy a portable monitor off your favorite e-tailer, but with perfectly fine displays in devices like laptops being tossed out every single day, why not repurpose those instead? That’s what [ScuffedBits] recently did with the panels  pulled from some old laptops.

A good question with any such salvaged panel is just how practical it is to still use them, with disqualifying features being things like passive-matrix TFTs as well as the use of CCFL backlighting as with one of the three panels demonstrated in the video.

Looking up the model number of a panel on a site like panelook.com will tell you the display technology, resolution and other important details before you decide to commit to using it. If it’s using a LED backlight and at least Low-Voltage Differential Signaling (LVDS) but ideally eDP you can likely find a cheap driver board for it that has all the requisite inputs like HDMI and power.

The hardest part is probably the case for the panel, as they’re rather thin and fragile. Here [ScuffedBits] opted to 3D print two different types of cases, with the second variant probably being the best version as it protects most of the panel. Installing these is quite easy: slide the panel into the first half, then add the second half of the case to close it up. Permanently keeping the case in place was left as an exercise to a future [ScuffedBits], while demonstrating why it’s definitely the hardest part of repurposing an old laptop display.

Continue reading “Turning A Junk Laptop Screen Into A Portable Monitor”

Qualcomm’s New QCC74x Appears To Target The ESP32 MCUs

These days wireless microcontrollers featuring built-in WiFi and Bluetooth are all the rage, with Espressif’s range of ESP32 MCUs being the default option for commercial and hobbyist projects alike. This makes Qualcomm’s recently released QCC74x MCU rather interesting, as specification-wise it would seem to be placed firmly in ESP32 territory.

On the radio side you get 1×1 WiFi 6, Bluetooth 5.4, and IEEE 802.15.4 (e.g. Thread and Zigbee), coupled with a single-core 352 MHz RISC-V CPU with FPU and DSP features and 484 kB of SRAM. The SDK for this MCU is hosted on Codelinaro, featuring the typical FreeRTOS-based stack, though confusingly Bluetooth and Zigbee support are currently marked as ‘not supported’. This might still be in progress.

Where the competition with Espressif feels clear is in the pricing, with the highest-performance evaluation board (QCC748M EVK, pictured above) listed for $13 (before taxes/tariffs). This gets you 8 MB of PSRAM built-in with unspecified link speed, but likely the same QSPI as used for the NOR Flash. USB support is available on this higher-end tier, while absent on the QCC743. Development documentation is also available, and looks fairly complete based on first glance.

Overall the QCC74x looks to be an upgrade to the older and significantly less powerful QCC730 MCU. Depending on software support and final pricing it could make for an interesting competitor to some of Espressif’s modules like its ESP32-C series or ESP32-S2, though the upcoming ESP32-S31 would seem to have it matched or beat on all metrics.

Running Windows CE On The Nintendo 64

Although Windows CE doesn’t use the NT kernel, it’s similarly designed to run on a wide variety of system architectures. Since the Nintendo 64 uses a MIPS CPU it should basically just run either kernel. You might assume that the N64’s rather limited specs are a bit of a problem, but fortunately Windows CE is designed to run on a digital potato, and requires only a MB of RAM. Since that just so happens to be what the N64 has under the hood, [Throaty Mumbo] was optimistic about getting Windows CE running on the 1990s game console.

The idea for this project came when [Throaty] was tinkering with an IBM Workpad Z50 laptop that uses almost the same CPU as the N64 and also runs Windows CE. Although said laptop is probably a lot more practical of a platform to run Windows on, this didn’t mean that it wouldn’t be a fun challenge.

Since CE was intended to be customized by companies for their own embedded hardware this means that you can use an official SDK, such as Microsoft Windows CE 2.11 Platform Builder. Making Windows CE 2.11 run on an N64 thus involves creating a board-specific configuration and compile that against said SDK.

If you want to give it a shot yourself, the entire project is available on GitHub which is where you find most of the technical details as well. When using a flash cart such as the EverDrive, you can also put applications on the SD card and run them from within the Windows GUI. You’ll still be limited by the N64 hardware, but otherwise the experience is very smooth as the video below demonstrates.

Continue reading “Running Windows CE On The Nintendo 64”

After Stumbling From CVE To CVE Will Linux Get A Kill Switch?

For the few people who have spent the past weeks living under a security rock, the Linux kernel has found itself the subject of multiple severe bugs in the form of Copy Fail and Dirty Frag, both of which allow for privilege escalation. They’ve made many people very upset, and also potentially put many thousands of systems at risk of exploitation. Worse is that system managers are generally left to twiddle their thumbs while waiting for patches to be rolled out. This is where NVIDIA engineer [Sasha Levin] has proposed a ‘kill switch’ for affected kernel functions.

The basic concept seems rather simple, with this feature merely intercepting a call to the affected function and instead returning a predefined return value. This makes it less extreme than hitting a general SCRAM button on the entire kernel, and could theoretically allow the affected systems to keep running until the patched kernel becomes available.

A disadvantage of this is that it obviously modifies the kernel, patching it in-memory so that you need to reboot the system to clear it. Another potential disadvantage is that it opens a potentially massive attack vector, with people in the Cybersecurity sub-Reddit roundly rejecting the idea. Amidst all the other anxious conversions there is also the concern that this particular patch was at least partially generated by an LLM (Claude Opus 4.7) , so one may hope that if it does gets merged into mainline it’ll at least be properly vetted by multiple pairs of well-caffeinated human eyes.

Fixing A Cotton Candy Vending Machine

Cotton candy is probably the best way to eat pure sugar, which makes having your very own cotton candy vending machine to automate making it a bit of a dream. The machine that [Block’s Retro Repairs] got should therefore make him very happy, but unfortunately it was bought as defective. After digging into the machine in an earlier video, this time around there’s some actual success and proper cotton candy to enjoy.

The PCB with the rather frayed temperature sensor. (Credit: Block's Retro Repairs, YouTube)
The PCB with the rather frayed temperature sensor. (Credit: Block’s Retro Repairs, YouTube)

The way that cotton candy is made involves spinning thin threads of sugar, which are created by the heating and rapid crystallization of the sweet stuff. Unfortunately this machine wasn’t even really extruding sugar any more, so it had to get a deep clean to remove probably years of crusty buildup. After this things still weren’t working right, although cranking up the temperature on the induction heated head improved the results somewhat.

To really fix the machine, this head with its clearly dodgy thermocouple had to be disassembled. This revealed that said sensor was looking rather frayed, potentially shorting out against the aluminium head and likely not in the entirely right position any more. After adding some insulation back and making sure that the thermocouple was located closer to the top of the head, it was time for more testing.

Repairing the thermocouple seems to have fixed most ills, with still some calibration of the temperature required, but finally resulting in fancy shaped cotton candy in its myriad of colors. Along with the looming hazard of potentially acquiring Type II diabetes from all the testing, there was still a problem involving the remote management feature of this Red Rabbit machine.

These $6,000 vending machines do feature an Android 7-based software with a Rockchip SoC and access to a lot of settings via its large touch screen, but features such as setting prices for the products are locked away via a remote account. The machine was sadly still linked to someone else’s account, and so far Red Rabbit support had not responded to any documentation, repair help or account unlinking requests. This has left the machine in somewhat of a pickle.

It was possible to dump the software of the machine, which can be fetched from Archive.org, so if anyone would like to pitch in and break this remote lock, that would be very welcome. It’s also considered to replace the cash reader with a simple button or so, but where’s the fun in that?

Continue reading “Fixing A Cotton Candy Vending Machine”

Automating Window Shades With Home Assistant

Most people love window shades, but many dislike the tedium of having to open and close them over the course of each day. While there are automation options here, if you’re in a rental place like [Rooster Robotics], then you’d prefer something less intrusive, as well as less cloud-bound. This is basically why he opted to build his own solution from scratch to open and close roller shades via Home Assistant.

The comments to the video helpfully point out that technically his point about there not being commercial options with a forced remote account ‘feature’ is false, as the Aqara Roller Shade Driver E1 for example is just a regular Zigbee device which can be used with a wide range of home automation ecosystems. That said, it’s always nice to have your own device that you fully control.

Of course, these devices are deceptively simple, as you still have to somehow know how far open the curtain is, which is also useful if you just want to open the curtain a certain amount. The other issue is the need to have the motor parallel with the wall unless you enjoy having a big wart sticking out from the wall.

Solving the first issue was attempted with a Hall effect sensor, and the second with angled gearing. With some refinements this led to a functioning design, allowing the development of a custom PCB with an ESP32-S3 module for WiFi control. In the final design the Hall effect sensor and magnets were replaced with an AS5600 magnetic rotatory position sensor that requires just one magnet and offers a much higher resolution.

Currently the design files are not available, but [Rooster Robotics] has indicated that they are looking at open sourcing the files in the future.

Continue reading “Automating Window Shades With Home Assistant”

Testing Giant Fire Darts From The Mary Rose

Fire arrow versus the recreated fire dart. (Credit: Tod's Workshop, YouTube)
Fire arrow versus the recreated fire dart. (Credit: Tod’s Workshop, YouTube)

The Mary Rose was a carrack in the English Tudor Navy of King Henry VIII  that fought in multiple battles during the 16th century before it was sunk in 1545. After its wreck was located in 1971 and raised in 1982 the ship and all the items contained within the partially preserved hull became the focus of intense study. Among these items are the weaponry found, including the cannons, but also massive darts that seemed to have been designed for an incendiary payload. Recently [Tod’s Workshop] collaborated with others to test these presumed incendiary darts.

Although fire arrows have been around for a while, seeing what appears to be super-sized versions of these is somewhat unusual, but could make sense in taking out enemy ships of the time. The main questions are how you would even fire them, and how effective they would be. Were the darts thrown by hand from e.g. the crow’s nest, or fired from a cannon?

The reproduction darts used are based on the recovered remnants of the original darts, with an incendiary mixture inside a pitch-covered cloth covering. This mixture would be ignited by wooden fuses after a set amount of time, at which point the resulting fire would be basically impossible to put out. Obviously, this also means that if you were to throw one of these darts, it can absolutely not fall onto your own ship.

First tested was throwing the dart by hand, which seems like it would clear the ship. Of course, the three recovered darts were found near a rather special cannon that appeared to be both a miscast and angled upwards. Whether that cannon was used for launching apparently somewhat experimental darts is hard to say, but it can be tested. Sadly, lacking a full-sized black powder cannon a scale model dart was fired using compressed air.

From that scale test it’s clear that at full charge the dart would disintegrate due to the rapid acceleration, but a ‘soft’, or reduced, charge could work against nearby targets. Once the dart lodges itself into the enemy ship’s structure, it would definitely cause severe damage as further tests in the video demonstrate. Having a salvo of these fire darts fired at you from a nearby ship would definitely make for a pretty bad day.

Continue reading “Testing Giant Fire Darts From The Mary Rose