Oddball LCDs Reverse Engineered Thanks To Good Detective Work

Is there anything more discouraging to the reverse engineer than to see a black blob of epoxy applied directly to a PCB? We think not, because that formless shape provides no clue as to what chip lies beneath, and that means a lot of detective work if you’re going to figure out how to use this thing.

[Sudhir Chandra]’s detective story starts with a bunch of oddball LCDs, slim 1×32 character units rather than the more familiar 2×16 displays. Each bore the dreaded black COB blob on the back, as well as a handful of SMD components and not much else. Googling revealed no useful documentation, and the manufacturer wasn’t interested in fielding calls from a hobbyist. Reasoning that most manufacturers wouldn’t spin up a custom chip for every display, [Sudhir] assumed there was an ST7066, a common LCD driver chip, underneath the blob, especially given the arrangement of external components. But a jumper set was bodged together under this assumption didn’t get the display going.

Next up were more destructive methods, to decap the COB and see what kind of numbers might be on the chip. Sandpaper worked at first, but [Sudhir] eventually turned to the “Chips a la [Antoine]” method of decapping, which uses heat and brute force to get at the goods. This got down to the chip, but [Sudhir]’s microscope wasn’t up to the task of reading the die markings.

What eventually cracked the case was tracing out the voltages across the various external resistors and matching them up to other chips in the same family as the ST7066, plus the realization that the long, narrow epoxy blob probably covered a similarly shaped chip, which led to the culprit: an ST7070. This allowed [Sudhir] to build an adapter PCB for the displays, with plans for a custom Arduino library to talk to the displays.

This was a great piece of reverse engineering and a good detective story to boot. Hats off to [Sudhir] for sticking with it.

Can Google’s New AI Read Your Datasheets For You?

We’ve seen a lot of AI tools lately, and, of course, we know they aren’t really smart, but they sure fool people into thinking they are actually intelligent. Of course, these programs can only pick through their training, and a lot depends on what they are trained on. When you use something like ChatGPT, for example, you assume they trained it on reasonable data. Sure, it might get things wrong anyway, but there’s also the danger that it simply doesn’t know what you are talking about. It would be like calling your company’s help desk and asking where you left your socks — they simply don’t know.

We’ve seen attempts to have AI “read” web pages or documents of your choice and then be able to answer questions about them. The latest is from Google with NotebookLM. It integrates a workspace where you can make notes, ask questions, and provide sources. The sources can be text snippets, documents from Google Drive, or PDF files you upload.

You can’t ask questions until you upload something, and we presume the AI restricts its answers to what’s in the documents you provide. It still won’t be perfect, but at least it won’t just give you bad information from an unknown source. Continue reading “Can Google’s New AI Read Your Datasheets For You?”

Hilarious Security Flaw In Counter Strike 2 Is Now Patched

Normally, when we talk about video games having bugs, it’s some kind of item duplication glitch or a hilarious failure in the jacket equip code of some tedious first-person-shooter online wardrobe simulator. Counter-Strike 2 has had a more embarrassing faux-pas, however, with a security hole allowing bad actors to theoretically capture the IPs of their fellow players in a server. You won’t believe how this came to happen.

The exploit has already been making its way around the forums, with one [Crouch9706] raising the alarm. It’s all down to the way Counter-Strike 2 renders the names that players have entered in their Steam gaming profiles. In certain menus and other parts of the UI, the game will actually parse HTML in a player’s name. Typically, the way to trigger it is to join a game and vote to kick yourself. This brings up a dialog for other players that shows them your player name and parses the HTML. The only limitation is you only get 32 characters for your HTML.

There’s a nifty little extra trick to this, though, in that you can use this technique to snag another player’s IP. By putting in HTML that links to your own server, you can log any player IPs that connect to the server seeking an image, for example.

Of course, it’s not the biggest risk, with many players being behind ISPs that use CGNAT, making the harvested IPs rather useless. However, this sort of unexpected code injection is really not acceptable from a security standpoint. At the very least, it has the potential to expose players to nasty imagery.

Word on the street (Nitter) is that the exploit has now been patched. Meanwhile, if you’re working on a game that for some mad reason, executes code based on player names or any other such data, consider patching your work ASAP. If you find similar exploits in the wild, don’t hesitate to hit up our tipsline—and notify the developers, too!

Homemade Raman Laser Is Shaken, Not Stirred

You wouldn’t think that shaking something in just the right way would be the recipe for creating laser light, but as [Les Wright] explains in his new video, that’s pretty much how his DIY Raman laser works.

Of course, “shaking” is probably a gross oversimplification of Raman scattering, which lies at the heart of this laser. [Les] spends the first half of the video explaining Raman scattering and stimulated Raman scattering. It’s an excellent treatment of the subject matter, but at the end of the day, when certain crystals and liquids are pumped with a high-intensity laser they’ll emit coherent, monochromatic light at a lower frequency than the pumping laser. By carefully selecting the gain medium and the pumping laser wavelength, Raman lasers can emit almost any wavelength.

Most gain media for Raman lasers are somewhat exotic, but luckily some easily available materials will work just fine too. [Les] chose the common solvent dimethylsulfoxide (DMSO) for his laser, which was made from a length of aluminum hex stock. Bored out, capped with quartz windows, and fitted with a port to fill it with DMSO, the laser — or more correctly, a resonator — is placed in the path of [Les]’ high-power tattoo removal laser. Laser light at 532 nm from the pumping laser passes through a focusing lens into the DMSO where the stimulated Raman scattering takes place, and 628 nm light comes out. [Les] measured the wavelengths with his Raspberry Pi spectrometer, and found that the emitted wavelength was exactly as predicted by the Raman spectrum of DMSO.

It’s always a treat to see one of [Les]’ videos pop up in our feed; he’s got the coolest toys, and he not only knows what to do with them, but how to explain what’s going on with the physics. It’s a rare treat to watch a video and come away feeling smarter than when you started.

Continue reading “Homemade Raman Laser Is Shaken, Not Stirred”

Raspberry Pi Changes HATs

Following on the heels of their Raspberry Pi 5 launch and some specifications for their RP1 all-in-one peripheral chip, the Raspberry Pi folks have now released an update to the HAT peripheral hardware specification reflecting the new model. Called the HAT+, it represents a major step forward with some significant changes.

Most visible will be changes to the mechanical specification, for while the original HAT specification was very rigid this new version is much looser. A HAT+ must only mate with the 40-pin connector, including the ID pins, and line up with only a single mounting hole compared to the four on the original. Electrically, a HAT+ must recognise the standby power state in which the 3.3-volt line is powered down while the 5-volt line remains active, while software-wise, there are changes to the content of the ID EEPROM including the ability to inform about stackable smaller HATs.

Continue reading “Raspberry Pi Changes HATs”

Terminal-Based Image Viewer, and Multi-OS Binary, and Under 100kb

[Justine Tunney]’s printimage.com is a program capable of splatting full-color images to text mode terminal sessions, but that’s not even its neatest trick. It’s also a small binary executable capable of running on six different operating systems: Linux, Windows, MacOS, FreeBSD, OpenBSD, and NetBSD. All without having to be installed or otherwise compiled first. On top of it all, it’s less than 100 kb.

How is this possible? It’s thanks to [Justine]’s αcτµαlly pδrταblε εxεcµταblε format, implemented by a project called Cosmopolitan which aims to turn C into a build-once-run-anywhere language. The printimage.com source code is included within the Cosmopolitan project.

If the name sounds a bit familiar, it’s probably because the Cosmopolitan project is a key piece of a tool we recently covered: llamafile, which allows people to package up an LLM (large language model) as a single-file, multi-OS executable.

As printimage.com shows, terminal windows are capable of more than just text. Still, plain ASCII has its appeal. Check out the ASCII art STL file viewer which might just make your next sick ASCII art banner a bit easier to generate.

Two pieces of paper on a table with a pair of pliers, a screwdriver, and a cup of what is probably coffee or tea. The sheets show a diagram of a bicycle handlebar on one side with a labeled "controller box, controller lever, mount, and battery." The other sheet shows a side view of a 150kg servo mounted on a plate that runs over to a brake caliper with a battery, receiver, and power stabilizer. These parts are also labeled in red text.

Wireless Bike Brakes

Bicycles are the most efficient machines for moving a person around, and wireless drivetrains have been heralded as a way to make shifting more consistent and require less maintenance. [Blake Samson] wondered if the same could be true of wireless brakes.

A closeup of a bike front fork with a large 150kg servo mounted to a plate that puts it above the disc brake caliper. To the side of the caliper, wires are visible going between the servo, control box, and battery.Inspired by the controller for an RC car, [Blake] picked a 150 kg servo attached to a cable-actuated hydraulic disc caliper to apply the braking force. The servo, receiver, power stabilizer, and batteries were all mounted on a custom steel plate fabricated to mount under the caliper. [Blake] cut up an old set of mountain bike brake levers to reuse the handlebar mounts and then put the batteries, controller, and finger triggers on them.

Confident in his hacking skills, [Blake] then took the bike out on some trails to test the brakes. As a prototype, there were a few surprises along the way, like one of the triggers staying locked in the braking position, but they performed admirably enough that he’s mulling over a Mk. 2.

Bikes are one of our favorite hacking platforms. Be sure to checkout this dreamy cargo bike build, an awesome bike camper, or what can happen if your bike is dependent on the cloud to work.

Continue reading “Wireless Bike Brakes”