Everything You Wanted To Know About Padauk MCUs And More

At this point you’d need to have lived underneath a rock somewhere on the dark side of the Moon to not have heard about these amazing, 3-cent microcontrollers. A number of places have pitched in on them, but comprehensive reviews, let alone a full-blown review of the entire ecosystem surrounding these Padauk MCUs have been scarce. Fortunately, [Jay Carlson] has put in a lot of effort to collect everything you could possibly want to know about anything Padauk.

The most important take-away is that these MCUs do not have any kind of communication peripherals. UARTs, I2C, and SPI all have to be done in software. They’re not very great at low-power or battery-powered applications due to high power usage. Essentially you’ll be using GPIO pins a lot. On the other hand, its multi-CPU context, FPPA feature is rather interesting, with the article covering it in detail.

As for the development tools, [Jay] came away very impressed with the In-Circuit Emulation (ICE) instead of running code on an MCU, as this can reduce development times significantly. This makes even the OTP (one-time programmable) property of most Padauk MCUs less significant than one might at first assume.

Then there’s the actual programming of the MCUs. The Micro C compiler Padauk provides essentially implements a sub-set of the C language, with some macros to replace things like for loops. Initially this may seem like a weird limitation, until you realize that these MCUs have 64 to 256 bytes of SRAM. That’s bytes, without any prefixes.

Finally, [Jay] shows off a couple of test projects, including a NeoPixel SPI adapter and bike light, which are all available on Github. The WS2812b project is something we have seen before, for example this project from [Anders Nielsen] (featured in the article image), which provides another take on this range of MCUs.

Did reading [Jay]’s article change your mind on these Padauk parts? Have you used these MCUs and ICE parts before? Feel free to leave your thoughts in the comments.

Ask Hackaday: At What Point Is Hand Pick And Place Too Much Work?

Just a section from a render of the board in question. It's a daunting task for anyone facing it with a set of tweezers or a vacuum pencil.
Just a section from a render of the board in question. It’s a daunting task for anyone facing it with a set of tweezers or a vacuum pencil.

A friend of ours here at Hackaday has an audacious design in the works that we hope will one day become a prototype that we can feature here. That day may be a little while coming though, because it has somewhere close to a thousand of the smaller SMD components in multiple repeated blocks on a modestly sized board, and his quote from a Chinese board house for assembly is eye-watering. He lacks a pick-and-place machine of his own, and unsurprisingly the idea of doing the job by hand is a little daunting.

We can certainly feel his pain, for in the past we’ve been there. The job described in the linked article had a similar number of components with much more variety and on a much larger board, but still took two experienced engineers all day and into the night to populate. The solder paste had started to spread by the end, morphing from clearly defined blocks to an indistinct mush often covering more than one pad. Our eyes meanwhile were somewhat fatigued by the experience, and it’s not something any sane person would wish to repeat.

Mulling over our friend’s board and comparing it with the experience related above, are we on the edge of what is possible with hand pick-and-place, or should we be working at the next level? Board assembly is a finely judged matter of economics at a commercial level, but when at a one-off personal construction level the option of paying for assembly just isn’t there, is there a practical limit to the scale of the task? Where do you, our readers, draw the line? We’d love to hear your views.

Meanwhile our friend’s audacious project is still shrouded in a bit of secrecy, but we’ll continue to encourage him to show it to the world. It’s not often that you look at a circuit diagram and think “I wish I’d thought of that!”, but from what we’ve seen this fits the category. If he pulls it off then we’ll bring you the result.

PCB image, Andrew Magill (CC BY 2.0).

Tiny LED Cube Packs Six Meters Of Madness

When [Freddie] was faced with the challenge of building a sendoff gift for an an LED-loving coworker he hatched a plan. Instead of making a display from existing video wall LED panels he would make a cube. But not just any cube, a miniature desk sized one that wasn’t short of features or performance. We’d be over the moon if someone gifted us with this itty-bitty Qi coil-powered masterpiece of an RGB cube.

Recently we’ve been blessed with a bevy of beautiful, animated RGB cubes but none hit quite this intersection of size and function. The key ingredient here is tiny but affordable RGB LEDs which measure 1 mm on a side. But LEDs this small are dwarfed by the otherwise minuscule “2020” package WS2812’s and APA102s of the world. Pushing his layout capabilities to the max [Freddie] squeezed each package together into a grid with elements separated by less than 1 mm, resulting in a 64 LED panel that is only 16 mm x 16 mm panel (with test points and controller mounted to the back). Each of these four-layer PCBs that makes up the completed cube contains an astonishing 950 mm of tracking, meaning the entire cube has nearly six meters of traces!

How do you power such a small device with no obvious places to locate a connector? By running magnet wire through a corner and down to a Qi coil of course. Not to let the cube itself outshine the power supply [Freddie] managed to deadbug a suitably impressive supply on the back of the coil itself. Notice the grain of rice in the photo to the left! The only downside here is that the processor – which hangs diagonally in the cube on a tiny motherboard – cannot be reprogrammed. Hopefully future versions will run programming lines out as well.

Check out the video of the cube in action after the break, and the linked photo album for much higher resolution macro photos of the build. While you’re there take a moment to admire the layout sample from one of the panels! If this sets the tone, we’re hoping to see more of [Freddie]’s going-away hacks in the future!

Continue reading “Tiny LED Cube Packs Six Meters Of Madness”

PCIe Multiplier Expands Raspberry Pi 4 Possibilities

It probably goes without saying that hardware hackers were excited when the Raspberry Pi 4 was announced, but it wasn’t just because there was a new entry into everyone’s favorite line of Linux SBCs. The new Pi offered a number of compelling hardware upgrades, including an onboard PCI-Express interface. The only problem was that the PCIe interface was dedicated to the USB 3.0 controller; but that’s nothing a hot-air rework station couldn’t fix.

We’ve previously seen steady-handed hackers remove the USB 3.0 controller on the Pi 4 to connect various PCIe devices with somewhat mixed results, but [Colin Riley] has raised the bar by successfully getting a PCIe multiplier board working with the diminutive Linux computer. While there are still some software kinks to work out, the results are very promising and he already has  a few devices working.

Getting that first PCIe port added to the Pi 4 is already fairly well understood, so [Colin] just had to follow the example set by hackers such as [Tomasz Mloduchowski]. Sure enough, when he plugged the port multiplier board in (after a bit of what he refers to as “professional wiggling”), the appropriate entry showed up in lspci.

But there was a problem. While the port multiplier board was recognized by the kernel, nothing he plugged into it showed up. Checking the kernel logs, he found messages relating to bus conflicts, and one that seemed especially important: “devices behind bridge are unusable because [bus 02] cannot be assigned for them“. To make a long story short, it turns out that the Raspbian kernel is specifically configured to only allow a single PCI bus.

Fortunately, it’s an easy fix once you know what the problem is. Using the “Device Tree Compiler” tool, [Colin] was able to edit the Raspbian Device Tree file and change the PCI “bus-range” variable from <0x0 0x1> to <0x0 0xff>. From there, it was just a matter of plugging in different devices and seeing what works. Simple things such as USB controllers were no problem, but getting ARM Linux support for the NVIDIA GTX 1060 he tried will have to be a topic for another day.

[Thanks to Paulie for the tip.]

Process Characterization On The Cheap With A Custom Test Rig

Testing is a key part of any product development cycle. Done right, it turns up unknown bugs and problems, and allows for them to be fixed prior to shipment. However, it can be a costly and time-consuming process. The [Bay Libre] team needed to do some work on power management, but the hardware required was just a little on the expensive side. What else does a hacker do, but build their own?

Enter the Thermo-Regulated Power Measurement Platform. It’s a device designed to control the die temperature of a chip during process characterization. This is where a chip, in this case the iMX8MQ, is run at a variety of temperatures, voltages, and frequencies to determine its performance under various conditions. This data guides the parameters used to run the chip in actual use, to best manage its power consumption and thermal performance.

The rig consists of a Peltier element with controller, a heatsink, and a fan. This is lashed up to a series of Python scripts that both control the chip temperature and run through the various testing regimes. Thanks to this automation, what would normally be a day’s work for an engineer can now be completed in just two hours.

Through a few smart component choices, the team accomplished the job at around one-tenth of the cost of commercial grade hardware. Granted, the average hacker probably won’t find themselves doing process characterization for cutting-edge silicon on a regular basis. Still, this project shows the value in building custom hardware to ease the testing process.

Testing is key to success in production. Custom jigs can make for light work when large orders come in, and we’ve run a primer on various testing techniques, too.

The Gorgeous Hardware We Can’t Take Our Eyes Away From

High resolution digital cameras are built into half of the devices we own (whether we want them or not), so why is it still so hard to find good pictures of all the incredible projects our readers are working on? In the recently concluded Beautiful Hardware Contest, we challenged you to take your project photography to the next level. Rather than being an afterthought, this time the pictures would take center stage. Ranging from creative images of personal projects to new ways of looking at existing pieces of hardware, the 100+ entries we received for this contest proved that there’s more beauty in a hacker’s parts bin than most of them probably realize.

As always, it was a struggle to narrow down all the fantastic entries to just a handful of winners. But without further adieu, let’s take a look at the photos that we think truly blurred the line between workbench and work of art:

Continue reading “The Gorgeous Hardware We Can’t Take Our Eyes Away From”

The Amazon Dash Button: A Retrospective

The Internet of Things will revolutionize everything! Manufacturing? Dog walking? Coffee bean refilling? Car driving? Food eating? Put a sensor in it! The marketing makes it pretty clear that there’s no part of our lives which isn’t enhanced with The Internet of Things. Why? Because with a simple sensor and a symphony of corporate hand waving about machine learning an iPhone-style revolution is just around the corner! Enter: Amazon Dash, circa 2014.

The first product in the Dash family was actually a barcode scanning wand which was freely given to Amazon Fresh customers and designed to hang in the kitchen or magnet to the fridge. When the Fresh customer ran out of milk they could scan the carton as it was being thrown away to add it to their cart for reorder. I suspect these devices were fairly expensive, and somewhat too complex to be as frequently used as Amazon wanted (thus the extremely limited launch). Amazon’s goal here was to allow potential customers to order with an absolute minimum of friction so they can buy as much as possible. Remember the “Buy now with 1-Click” button?

That original Dash Wand was eventually upgraded to include a push button activated Alexa (barcode scanner and fridge magnet intact) and is generally available. But Amazon had pinned its hopes on a new beau. Mid 2015 Amazon introduced the Dash Replenishment Service along with a product to be it’s exemplar – the Dash Button. The Dash Button was to be the 1-Click button of the physical world. The barcode-scanning Wands require the user to remember the Wand was nearby, find a barcode, scan it, then remember to go to their cart and order the product. Too many steps, too many places to get off Mr. Bezos’ Wild Ride of Commerce. The Dash Buttons were simple! Press the button, get the labeled product shipped to a preconfigured address. Each button was purchased (for $5, with a $5 coupon) with a particular brand affinity, then configured online to purchase a specific product when pressed. In the marketing materials, happy families put them on washing machines to buy Tide, or in a kitchen cabinet to buy paper towels. Pretty clever, it really is a Buy now with 1-Click button for the physical world.

There were two versions of the Dash button. Both have the same user interface and work in fundamentally the same way. They have a single button (the software can recognize a few click patterns), a single RGB LED (‘natch), and a microphone (no, it didn’t listen to you, but we’ll come back to this). They also had a WiFi radio. Version two (silently released in 2016) added Bluetooth and completely changed the electrical innards, though to no user facing effect.

In February 2019, Amazon stopped selling the Dash Buttons. Continue reading “The Amazon Dash Button: A Retrospective”