2024: As The Hardware World Turns

With 2024 now officially in the history books, it’s time to take our traditional look back and reflect on some of the top trends and stories from the past twelve months as viewed from the unique perspective Hackaday affords us. Thanks to the constant stream of tips and updates we receive from the community, we’ve got a better than average view of what’s on the mind of hardware hackers, engineers, and hobbyists.

This symbiotic relationship is something we take great pride in, which is why we also use this time of year to remind the readers just how much we appreciate them. We know it sounds line a line, but we really couldn’t do it without you. So whether you’ve just started reading in 2024 or been with us for years, everyone here at Hackaday thanks you for being part of something special. We’re keenly aware of how fortunate we are to still be running a successful blog in the era of YouTube and TikTok, and that’s all because people like you keep coming back. If you keep reading it, we’ll keep writing it.

So let’s take a trip down memory lane and go over just a handful of the stories that kept us talking in 2024. Did we miss your favorite? Feel free to share with the class in the comments.

Boeing’s Bungles

We’ll start off with what was undoubtedly one of the biggest stories in the tech and engineering world, although you’ll find little mention of it on the pages of Hackaday up until now. We’re talking, of course, of the dramatic and repeated failures of the once unassailable Boeing.

As a general rule, we don’t really like running negative stories. It’s just not the vibe we try and cultivate. Unless we can bring something new to the discussion, we’d rather leave other outlets peddle in doom and gloom. So that’s why, after considerable internal debate at HQ, we ultimately never wrote a story about the now infamous Alaska Airlines door plug incident at the beginning of the year.

Nor did we cover the repeated delays of Boeing’s Starliner capsule, a crewed spacecraft that the company was paid $4.2 billion to build under NASA’s Commercial Crew Program — nearly double the sum SpaceX received for the development of their Crew Dragon.

Things only got worse once the capsule finally left the launch pad in June. With human lives in the balance, it seemed in poor taste for us to cover Starliner’s disastrous first crewed flight to the International Space Station. The mission was so fraught with technical issues that NASA made the unprecedented decision to send the capsule back to Earth without its crew onboard. Those two astronauts, Barry E. Wilmore and Sunita Williams, still remain on the ISS; their planned eight-day jaunt to the Station has now been extended until March of 2025, at which point they’ll be riding home on SpaceX’s capsule.

We won’t speculate on what exactly is happening at Boeing, although we’ve heard some absolutely hair-raising stories from sources who wish to remain anonymous. Suffice to say, as disheartening as it might be for us on the outside to see such a storied company repeatedly fumble, it’s even worse for the those on the inside.

Desktop 3D Printing Reshuffling

While the tectonic shifts in the desktop 3D printer market didn’t start last year, 2024 really seemed to be the point where it boiled over. For years the market had been at a standstill, with consumers essentially having two paths forward depending on what they were willing to spend.

Had $200 or $300 to play with? You’d buy something like an Ender 3, a capable enough machine if you were willing to put in the time and effort. Or if you could stand to part with $800, you brought a Prusa i3, and didn’t worry about the little details like bed leveling or missed steps because it was automated enough to just work most of the time.

But then, Bambu Labs showed up. Founded by an ex-DJI engineer, the Chinese company introduced a line of printers that might as well have come from the future. Their speed, ease of use, and features were beyond even what Prusa was offering, and yet they cost nearly half as much. Seemingly overnight, the the market leaders at both ends of the spectrum were beat at their own game, and the paradigm shifted. The cheap printers now seemed archaic in comparison, and Prusa’s machines overpriced.

But while Bambu’s printers have dazzled consumers, they bring along some unfortunate baggage. Suddenly 3D printing involves cloud connectivity, proprietary components, and hardware that was designed for production rather than repairability. In short, desktop 3D printing seems on the verge of breaking into the legitimate mainstream, with all the downsides that comes with it these days.

It’s wasn’t all bad news though. When the community started experimenting with running alternate firmware on their hardware, Bambu’s response was better than we’d feared: users would be allowed to modify their firmware, but would have to waive their warranty. It’s not a perfect solution, but considering Prusa did more or less the same thing in 2019 when they released the Mini, the community had already shown they would accept the compromise.

Speaking of Prusa, feelings on how they’ve decided to respond to this newfound competition have been mixed, to put it mildly. In developing their new Core ONE printer it looks like they’ve engineered a worthy opponent for Bambu’s X1, but unfortunately, it appears the company has all but abandoned their open source hardware roots in the process.

RP2350 Has a Rocky Start

The release of the Pi Pico development board made our list of highlights for 2021, and in the intervening years, the RP2040 microcontroller at its heart has become a favorite of makers and hackers. We’ve even used it for the last two Supercon badges at this point. So the fact that its successor made this year’s list should come as no surprise.

But while the release of the Pi Pico 2 over the summer was noteworthy in its own way, it wasn’t really the big story. It’s what happened after that triggered debate in the community. You see, the RP2350 microcontroller that powered the Pico 2 launched with a known bug affecting the internal pull-down resistors. A bug that Hackaday alumn Ian Lesnet started documenting while incorporating the chip into a new version of the Bus Pirate. It turned out the scope of said bug was actually a lot worse than the documentation indicated, a fact that the folks at Raspberry Pi didn’t seem keen to acknowledge at first.

Ultimately, the erratum for the RP2350 was amended to better describe the nature of the issue. But as for an actual hardware fix, well that’s a different story. The WiFi-enabled version of the Pico 2 was released just last month, and it’s still susceptible to the same bug. Given that the hardware workaround for the issue — adding external pull-downs — isn’t expensive or complicated to implement, and that most users probably wouldn’t run into the problem in the first place, it seems like there’s no rush to produce a new version of the silicon.

Voyager 1 Shows its Age

Admittedly, any piece of hardware that’s been flying through deep space for nearly 50 years is bound to run into some problems, especially one that was built with 1970s era technology. But even still, 2024 was a rough year for humanity’s most distant explorer, Voyager 1.

The far-flung probe was already in trouble when the year started, as it was still transmitting gibberish due to being hit with a flipped-bit error in December of 2023. Things looked pretty grim for awhile, but by mid-March engineers had started making progress on the issue, and normal communication was restored before the end of April.

In celebration Dan Maloney took a deep-dive into the computers of Voyager, a task made surprisingly difficult by the fact that some of the key documentation he was after apparently never got never digitized. Things were still going well by June, and in September ground controllers were able to pull off a tricky reconfiguration of the spacecraft’s thrusters.

But just a month later, Voyager suffered another major glitch. After receiving a command to turn on one of its heaters, Voyager went into a fault protection mode that hadn’t been triggered since 1981. In this mode only the spacecraft’s low power S-band radio was operational, and there was initially concern that NASA wouldn’t be able to detect the signal. Luckily they were able to pick out Voyager’s faint cries for help, and on November 26th, the space agency announced they had established communications with the probe and returned it to normal operations.

While Voyager 1 ended 2024 on a high note, there’s no beating the clock. Even if nothing else goes wrong with the aging hardware, the spacecraft’s plutonium power source is producing less and less energy each year. Various systems can be switched off to save power, something NASA elected to do with Voyager 2 back in October, but eventually even that won’t be enough and the storied spacecraft will go silent for good.

CH32 Gains Momentum

We first got word of the CH32 family of low-cost RISC-V microcontrollers back in early 2023, but they were hard to come by and the available documentation and software toolchains left something to be desired. A 10¢ MCU sounds great, but what good is it if you can’t buy the thing or program it?

The situation was very different in 2024. We ran nearly three times the number of posts featuring some variant of the CH32 in 2024 than we did in the previous year, and something tells us the numbers for 2025 will be through the roof. The fact that the chips got official support in the Arduino IDE back in January certainly helped increase its popularity with hobbyists, and by March you could boot Linux on the thing, assuming you had time to spare.

In May bitluni had clustered 256 of them together, another hacker had gotten speech recognition running on it, and there was even a project that aimed to turn the SOIC-8 variant of the chip into the world’s cheapest RISC-V computer.

We even put our own official stamp of approval on the CH32 by giving each and every attendee of Supercon 2024 one to experiment with. Not only did attendees get a Simple-Add On (SAO) protoboard with an onboard CH32, but the badge itself doubled as a programmer for the chip, thanks in no small part to help from [CNLohr].

Evolution of the SAO

But the CH32 isn’t the only thing that got a boost during Supercon 2024. After years of seeing SAOs that were little more than a handful of (admittedly artistically arranged) LEDs, we challenged hackers to come up with functional badge add-ons using the six-pin interface and show them off in Pasadena by way of an event badge that served as a power and communications hub for them.

The response was phenomenal. Compared to the more complex interfaces used in previous Supercon badges, focusing on the SAO standard greatly reduced the barrier of entry for those who wanted to produce their own modular add-ons in time for the November event. Instead of only a handful of ambitious attendees having the time and experience necessary to produce a modular PCB compatible with the badge, a good chunk of the ticket holders were able bring along SAOs to show off and trade, adding a whole new dimension to the event.

While it’s unlikely we’ll ever make another Supercon badge that’s quite as SAO-centric as we did in 2024, we hope that the experience of designing, building, and sharing these small add-ons will inspire them to keep the momentum going in 2025 and beyond.

Share Your 2024 Memories

Even if this post was four times as long, there’s no way we’d be able to hit on everyone’s favorite story or event from 2024. What would you have included? Let us know in the comments, and don’t be afraid to speculate wildly about what might be in store for the hacking and making world in 2025.

15 thoughts on “2024: As The Hardware World Turns

  1. I’m glad you didn’t list controversial Hackaday articles about non‐software/ hardware that seemed to be written to generate lots of comments.

  2. i continue to be astonished by raspberry’s gloss of their erratum and honestly i’m not impressed by hackaday’s gloss here either.

    it’s a “microcontroller” without high-impedance inputs. full stop. it lacks high-impedance inputs, which i have taken for granted on every microcontroller since the 8051. there are work-arounds but if you need a high-impedance input then adding resistors to decrease the impedance is going in the wrong direction. for digital signals, you will need at least a transistor if you actually need high impedance.

    it’s just the sort of thing that is not a big deal for a lot of tasks but for a ‘general purpose’ chip it’s a fatal flaw. i would never buy a microcontroller without a high-impedance input. so far as i’m concerned, decently capable I/O is the killer feature that separates a microcontroller from an SBC like the regular pi. it requires a more careful disclosure than i’ve seen yet from raspberry. and a more consistent disclosure than i’ve seen on this site.

    1. 💯 I also don’t understand why people describe this issue as some minor thing that can be worked around easily. It just breaks a fundamental assumption of a GPIO port.
      This is one of the things that will bite you when you least expect it.

    2. The errata actually has a full leakage current diagram vs voltage, so I’m not sure how it could get more careful.

      I do agree I’m surprised they haven’t come out and said it’ll be fixed, though. It’s sneakily annoying enough I’m not planning on using an RP2350 at all. Just not worth it.

    3. I’m (not) surprised that people insist on burning Raspberry Pi specifically over a single erratum (that wasn’t even their fault) that really can’t be solved in the short term when every other major microcontroller vendor has errata lists as long as your arm that they haven’t even bothered to address after a decade or more.

      “I would never buy a chip that can’t do X” without any reference to whether your application actually needs X or not? It’s your choice to make but it’s clearly not an impartial one.

      Also, insisting that they provide immediate and fully accurate timelines for their future decisions around their product line? Yeah, that’s a realistic demand, and no company has ever been punished in the market for revealing more than the bare minimum (this is sarcasm, if you couldn’t tell.) Anything other than the impossible “we’ve gone back in time and fixed the issue and you already have the fixed chips and a $1000 refund” only results in more abuse. The absolute smartest choice any manufacturer can make is to shut up and not announce anything before it’s completely ready.

      1. i’ve used a handful of different microcontrollers and indeed they have all had errata but i have barely run into them. in fact, i think literally the only time i ran into one, the work-around was both software and complete. i definitely use high-impedance inputs and rely on them! i’m sorry i forgot to tell you that in this comment!

        many of them go unaddressed because they simply don’t matter. they’re rightfully a footnote. many others are unaddressed because the chip has fallen out of widespread usage (or isn’t used for new projects).

        the complete absence of high impedance inputs on a popular new general purpose microcontroller is not just a footnote and cannot be worked around in just software and no workaround is complete if you genuinely needed high-impedance inputs. your work around will always have a trade off in extra components and power draw. like i said, it simply doesn’t matter for a lot of use cases, but in my life i know it would matter. i bought a handful of rp2040s specifically intending to use them for mopping up I/O functions, and i will never buy the rp2350 because it isn’t as suitable for that purpose.

        but your last paragraph gets to the heart of the matter. i want disclosure in the forefront. it shouldn’t be buried. the flaw isn’t the severity of a footnote and the disclosure should be more visible than a footnote. when the flaw was first discovered, their impulse was to try to hide it so that they could have time to discover a better workaround. that was a mistake and ran contrary to the interests of their community, but an understandable mistake! now we know there is no complete workaround and that a core function is completely missing. they should disclose this in the sales material, not just in an appendix to the manual.

        i do not want $1000. i do not want a retroactive fix. i do not want a timeline for the future or a disclosure of backstock quantities. i do not want anything unreasonable or impossible or unaffordable. i want an honest transparent vendor. that’s all.

        and this is the reason people pick on raspberry foundation in particular — the raspberry pi has this exact same situation. it’s a very good board for a lot of uses but it is one of the most closed options out there. they make money off of a fraudulent reputation for openness.

  3. There should be a companion article 2024: As the software world turns. Microsoft’s Windows 10/11 transition and updates mess would be at the top. The e-waste blindness to dump working hardware still pervades MS. Their low level bullying (mild threats of no updates if you Rufus, noncompatibility watermarks and pop-ups) is getting ridiculous. (My software has no or any decent replacements in the other universes. Please don’t suggest switching). If HaD did such an article, the torrential flood might fill several pages.

    1. I’m not particularly pleased with getting ads when I open my laptop now also. I mean come on, do they really need the revenue on top of what they make already? It’s an insult to their customers and actually the first time I’ve seriously considered swapping to another OS.

        1. Linux is waiting… but your actions tell me that you prefer the abuse.

          I hear what you’re saying; but even speaking as someone who has used Linux almost exclusively for about 15 years I’d say you’re being a little harsh. Heck, even I use Windows occasionally, (Win2K in a VM, but still…).

          For some folks, there is Windows software for which there simply isn’t a good-enough Linux equivalent. Loss of functionality, a steep learning curve, the impossibility of sharing files to collaborate with ‘mainstream’ colleagues – all of these are non-trivial considerations

          That said, if it took this much abuse to trigger even mild contemplation of using a different OS, you may be right. The commenter whose handle is ‘merser’ may be suffering from Stockholm syndrome.

  4. SATA ssd memories appearing on Amazon with low prices and read speeds of ~400 -550 MB/s.

    m.2 similar hardware memories appear on Amazon. Some with very high read speeds … but more expensive.

    which is best option? For what apps, of course.

    1. i might be missing your point but it reminds me of how insanely great prices for huge capacity (for example) microsd flash went from a clickbait scam to something you can just buy on temu et al and reasonably likely to actually get what you ordered. that’s a pretty underappreciated development imo and something that really came true for me in 2024. the too-good-to-be-true deals all seem to be true lately

    2. From what I’ve read m.2 is 6 or 7 times faster than SATA. I have one as the drive in an all-in-one I-3, it starts up Ubuntu Studio in 9 seconds. That’s fast. It has to be part of the motherboard.

  5. As a general rule, we don’t really like running negative stories. It’s just not the vibe we try and cultivate. Unless we can bring something new to the discussion, we’d rather leave other outlets peddle in doom and gloom.

    I just want to say that I appreciate this. I can get bad news or ragebait anywhere. HaD is where I read creative and interesting texts, like the regular hacks or one of the longer stories (hello Mining and Refining). When there is bad news, like the Arecibo collapse, we get a proper link to the full report on the root cause.

    Thanks!

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.