Watch Any Video On Your Game Boy, Via Link Cable

Game Boys have a link cable that lets two of them play together. You know, to battle with a friend’s Pokemon and stuff like that. But who says that it should be limited to transmitting only what Big N wants you to?

[Chromalock] wrote a custom GB program that takes in data over the link cable, and displays it on the screen as video, as fast as it can be sent. Add in a microcontroller, a level shifter, and software on the big computer side, and you can hook up your Game Boy Color as a normal video device and send it anything you want, from a webcam to any program that outputs video.

Well, almost. The biggest limitation is the data link cable, of course. On the older Game Boys, the link cable is apparently only good for 8 kHz, while the Color models can pull a not-quite-blistering 512 kHz. Still, that’s enough for 60 fps in a low-res black and white mode, or a slow, screen-tearing high-res color experience. You pick your poison.

There are gotchas that have to do with the way the GB displays palettes that get left as “to-do” on the software side. There is room for improvement in hardware too. (GB Link looks like SPI to us, and we’d bet you can push the speeds even higher with clever GB-side code.) In short, this is an awesome demo that just invites further hacking.

If you want to know more about the Game Boy to get started, and maybe even if you don’t, you absolutely must watch The Ultimate Game Boy Talk. Trust us on this one.

Continue reading “Watch Any Video On Your Game Boy, Via Link Cable”

Hacker Tools, Hacked Tools

We just love a good DIY tool project, and more so when it’s something that we can actually use cobbled together from stuff in our closet, or hacked out of cheap “toys”. This week we saw both a superb Pi Pico-based logic analyzer and yet another software frontend for the RTL-SDR dongle, and they both had us thinking of how good we have it.

If you don’t already have a logic analyzer, or if you have one of those super-cheap 8-channel jobbies, it might be worth your while to check out the Pico firmware simply because it gets you 24 channels, which is more than you’ll ever need™. At the low price of $4, maybe a little more if you need to add level shifters to the circuit to allow for 5 V inputs, you could do a lot worse for less than the price of a fancy sweet coffee beverage.

And the RTL dongle; don’t get us started on this marvel of radio hacking. If you vaguely have interest in RF, it’s the most amazing bargain, and ever-improving software just keeps adding functionality. The post above adds HTML5 support for the RTL-SDR, allowing you to drive it with code you host on a web page, which makes the entire experience not only cheap, but painless. Talk about a gateway drug! If you don’t have an RTL-SDR, just go out and buy one. Trust me.

What both of these hacker tools have in common, of course, is good support by a bunch of free and open software that makes them do what they do. This software enables a very simple piece of hardware to carry out what used to be high-end lab equipment functions, for almost nothing. This has an amazing democratizing effect, and paves the way for the next generation of projects and hackers. I can’t think of a better way to spend $20.

2025 Hackaday Europe CFP: We Want You!

Hackaday’s Supercon is still warm in our hearts, and the snow is just now starting to fall, but we’re already looking forward to Spring. Or at least to Hackaday Europe, which will be taking place March 15th and 16th in Berlin, Germany.

Tickets aren’t on sale yet, but we know a way that you can get in for free.

Call for Participation

What makes Hackaday Europe special? Well, it’s you! We’re excited to announce that we’re opening up our call for talks right now, and we can’t wait to hear what you have to say. Speakers of course get in free, but the real reason that you want to present is whom you’re presenting to.

The Hackaday audience is interested, inquisitive, and friendly. If you have a tale of hardware, firmware, or software derring-do that would only really go over with a Hackaday crowd, this is your chance. We have slots open for shorter 20-minute talks as well as longer 40-minute ones, so whether you’ve got a quick hack or you want to take a deep dive, we’ve got you covered. We especially love to hear from new voices, so if you’ve never given a talk about your projects before, we’d really encourage you to apply!

Here is last year’s lineup, if you’re wondering what goes on, and if your talk would fit in.

Continue reading “2025 Hackaday Europe CFP: We Want You!”

Tis The Season

’Tis the season for soldering! At least at my house. My son and I made some fairly LED-laden gifts for the immediate relatives last year, and he’s got the blinky bug. We were brainstorming what we could make this year, and his response was “I don’t care, but it needs to have lots of LEDs”.

It’s also the season for reverse engineering, apparently, because we’re using a string of WS2812-alike “fairy lights”. These are actually really neat, they look good and are relatively cheap. It’s a string of RGB LEDs with drivers, each dipped in epoxy, and run on a common three-enameled-wire bus. Unlike WS2812s, which pass the data on to the next unit in the line and then display them with a latching pulse at the end of a sequence, these LED drivers seem to count how many RGB packets have been sent down the wire, and only respond to their own number.

This means that if you cut up a string of 200 LEDs, it behaves like a string of 200 WS2812s. But if you cut say 10 LEDs off the string, where you cut them matters. If you cut it off the front of the string, you only have to send 10 color packets. If you cut them off the other end, you need to send 290 dummy packets before they even start listening. Bizarre, but ’tis the season for bizarre hacks.

And finally, ’tis the season for first steps into “software architecture”. Which is to say that my son is appreciating functions for the first time in his life. Controlling one LED is easy, but making a light show is about two more abstraction layers on top of that. We’ve been having fun making them dim, twinkle, and chase so far. We only have two more weekends, though, and we don’t have a final light show figured out yet, but after all, ’tis the season for last minute present hacking.

Did You Know YoSys Knows VHDL Too?

We’ve been fans of the Yosys / Nextpnr open-source FPGA toolchain for a long while now, and like [Michael] we had no idea that their oss-cad-suite installer sets up everything so that you can write in Verilog or VHDL, your choice. Very cool!

Verilog and VHDL are kind of like the C and ADA of the FPGA world. Verilog will seem familiar to you if you’re used to writing code for computers. For instance, it will turn integer variables into wires that carry the binary values for you. VHDL code looks odd from a software programmer’s perspective because it’s closer to the hardware and strongly typed: an 8-bit integer isn’t the same as eight wires in VHDL. VHDL is a bigger jump if you have software in your brain, but it’s also a lot closer to describing how the hardware actually works.

We learned Verilog, because it’s what Yosys supported. But thanks to GHDL, a VHDL analyzer and synthesizer, and the yosys-ghdl-plugin, you can write your logic in VHDL too. Does this put an end to the FPGA-language holy wars? Thanks, Yosys.

[Michael] points out that this isn’t really news, because the oss-cad-suite install has been doing this for a while now, but like him, it was news to us, and we thought we’d share it with you all.

Want to get started with FPGAs and the open-source toolchain? Our own [Al Williams] wrote up a nice FPGA Boot Camp series that’ll take you from bits to blinking in no time.

Thanks For Hacking

It’s that time of year again, when the turkey roasts and we think of the important things that we’re thankful for. Here at Hackaday, we’re simply thankful for all of you out there. The readers who make Hackaday worth writing for, and the hackers out there who give us something to write about.

It’s no exaggeration to say that we have one of the most bizarrely creative communities out there, and we’re thankful to still be chronicling all of the inventive madness, all of the engineering feats, and all of the projects that succeed and those that fail. It’s truly a pleasure, day in and day out, to read and to write about.

So thank you all for being Hackaday, for sticking with us through our 20th year now, and for continuing to share your hacks and sending in the tips when you see one that you’d like us to share. Keep on hacking, and we can’t wait to see what you’re up to in 2025.

Art of 3D printer in the middle of printing a Hackaday Jolly Wrencher logo

Open Source, Forced Innovation, And Making Good Products

The open-source hardware business landscape is no doubt a tough one, but is it actually tougher than for closed-source hardware? That question has been on our minds since the announcement that the latest 3D printer design from former open-source hardware stalwarts Prusa Research seems like it’s not going to come with design files.

Ironically, the new Core One is exactly the printer that enthusiasts have been begging Prusa to make for the last five years or more. Since seeing hacker printers like the Voron and even crazy machines like The 100 whip out prints at incredible speed, the decade-old fundamental design of Prusa’s i3 series looks like a slow and dated, if reliable, workhorse. “Bed slinger” has become a bit of a pejorative for this printer architecture in some parts of the 3DP community. So it’s sweet to see Prusa come out with the printer that everyone wants them to make, only it comes with the bitter pill of their first truly closed-source design.

Is the act of not sharing the design files going to save them? Is it even going to matter? We would argue that it’s entirely irrelevant. We don’t have a Core One in our hands, but we can’t imagine that there is anything super secret going on inside that couldn’t be reverse engineered by any other 3DP company within a week or so. If anything, they’re playing catch up with other similar designs. So why not play to one of their greatest strengths – the engaged crowd of hackers who would most benefit from having the design files?

Of course, Prusa’s decision to not release the design files doesn’t mean that they’re turning their backs on the community. They are also going to offer an upgrade package to turn your current i3 MK4 printer into the new Core One, which is about as hacker-friendly a move as is possible. They still offer kit versions of the printers at a discount, and they continue to support their open-source slicer software.

But this one aspect, the move away from radical openness, still strikes us as bittersweet. We don’t have access to their books, of course, but we can’t imagine that not providing the design files gains them much, and it will certainly damage them a little in the eyes of their most devoted fans. We hope the Core One does well, but we also hope that people don’t draw the wrong lesson from this – that it does well because it went closed source. If we could run the experiment both ways, we’d put our money on it doing even better if they released the design files.