Adding A Gentle Touch To Prosthetic Limbs With Somatosensory Stimulation

When Nathan Copeland suffered a car accident in 2004, damage to his spinal cord at the C5/C6 level resulted in tetraplegic paralysis. This left him initially at the age of 18 years old to consider a life without the use of his arms or legs, until he got selected in 2014 for a study at the University of Pittsburgh involving the controlling of a robotic limb using nothing but one’s mind and a BCI.

While this approach, as replicated in various other studies, works well enough for simple tasks, it comes with the major caveat that while it’s possible to control this robotic limb, there is no feedback from it. Normally when we try to for example grab an object with our hand, we are aware of the motion of our arm and hand, until the moment when our fingers touch the object which we’re reaching for.

In the case of these robotic limbs, the only form of feedback was of the visual type, where the user had to look at the arm and correct its action based on the observation of its position. Obviously this is far from ideal, which is why Nathan hadn’t just been implanted with Utah arrays that read out his motor cortex, but also arrays which connected to his somatosensory cortex.

As covered in a paper by Flesher et al. in Nature, by stimulating the somatosensory cortex, Nathan has over the past few years regained a large part of the sensation in his arm and hand back, even if they’re now a robotic limb. This raises the question of how complicated this approach is, and whether we can expect it to become a common feature of prosthetic limbs before long. Continue reading “Adding A Gentle Touch To Prosthetic Limbs With Somatosensory Stimulation”

Graphene lattice

How Graphene May Enable The Next Generations Of High-Density Hard Drives

After decades of improvements to hard disk drive (HDD) technology, manufacturers are now close to taking the next big leap that will boost storage density to new levels. Using laser-assisted writes, manufacturers like Seagate are projecting 50+ TB HDDs by 2026 and 120+ TB HDDs after 2030. One part of the secret recipe is heat-assisted magnetic recording (HAMR).

One of the hurdles with implementing HAMR is finding a protective coating for the magnetic media that can handle this frequent heating while also being thinner than current coatings, so that the head can move even closer to the surface. According to a recent paper by N. Dwivedi et al. published in Nature Communications, this new protective coating may have been found in the form of sheets of graphene.

Continue reading “How Graphene May Enable The Next Generations Of High-Density Hard Drives”

Test Your ‘Blue Pill’ Board For A Genuine STM32F103C8 MCU

With the market for STM32F103C8-based ‘Blue Pill’ boards slowly being overrun with boards that contain either a cloned, fake or outright broken chip, [Terry Porter] really wanted to have an easy, automated way to quickly detect whether a new board contains genuine STM32 silicon, or some fake that tries to look the part. After more than a year of work, the Blue Pill Diagnostics project is now ready for prime time.

We have covered those clone MCUs previously. It’s clear that some of those ‘Blue Pill’ boards obviously do not have a genuine STM32 MCU on them, as they do not have the STM32 markings on them, while others fake those markings on the package and identifying can be hard to impossible. Often only testing the MCU’s actual functionality can give clarity on whether it’s a real STM32 MCU.

These diagnostics allow one to test not only the 64 kB of Flash, but also the 64 kB of ‘hidden’ Flash that’s often found on these MCUs (rebadged 128 kB STM32F103 cores). It further checks the manufacturer JDEC code and uses a silicon bug in genuine STM32F1xx MCUs where the BGMCU_IDCODE cannot be read without either SWD or JTAG connected.

Another interesting feature of Blue Pill Diagnostics is using Mecrisp-Stellaris Forth as its foundation, which allows for easy access to a Forth shell via this firmware as well, not unlike MicroPython and Lua, only in a fraction of the Flash required by those. We have previously written about using Mecrisp-Stellaris in your projects.

The Compromises Of Raspberry Pi Hardware Documentation

[Rowan Patterson] informed us about a recent ticket he opened over at the Raspberry Pi Documentation GitHub repository. He asked about the the lack of updates to the Raspberry Pi 4’s USB-C power schematics for this board. You may recall that the USB-C power issue was covered by us back in July of 2019, yet the current official  Raspberry Pi 4 schematics still show the flawed implementation, with the shorted CC pins, nearly two years later.

[Alasdair Allan], responsible for the Raspberry Pi  documentation, mentioned that they’re in the process of moving their documentation from Markdown to AsciiDoc, and said that they wouldn’t have time for new changes until that was done. But then [James Hughes], Principal Software Engineer at Raspberry Pi,  mentioned that the schematics may not be updated even after this change due to a of lack of manpower.

As [James] emphasized, their hardware will probably never be open, due to NDAs signed with Broadcom. The compromise solution has always been to publish limited peripheral schematics. Yet now even those limited schematics may not keep up with board revisions.

An easy fix for the Raspberry Pi 4’s schematics would be for someone in the community to reverse-engineer the exact changes made to the Raspberry Pi 4 board layout and mark these up in a revised schematic. This should be little more than the addition of a second 5.1 kΩ resistor, so that CC1 and CC2 each are connected to ground via their own resistor, instead of being shorted together.

Still, you might wish that Raspberry Pi would update the schematics for you, especially since they have updated versions internally. But the NDAs force them to duplicate their efforts, and at least right now that means that their public schematics do not reflect the reality of their hardware.

Rhisotope: Addressing Poaching By Making Rhinoceros Horns Radioactive

There is no question that poaching has become an existential threat to the five species of rhinoceros alive today. Even the wildlife reserves where most rhinos live struggle to provide protection from the wanton and cruel poaching of the world’s last remaining rhinos.

Poachers are generally looking to sell the horns which consist of pure keratin, the same material that makes up our fingernails and hair. Rhino horns have seen a big rise in demand the past decades, with a black market in Vietnam representing the biggest buyers, primarily for use in fever and other medicines, as well as for processing into carved trinkets. This has contributed to a further rhino population collapse. Statistics from 2017 show about 18,000 white rhinos and fewer than 5,500 black rhinos remaining. Recently, the northern white rhino population in Africa went effectively extinct with the death of the last known male individual.

Clearly, if we wish to prevent extinction, we need to deal with poaching. The latest suggestion here is part of the Rhisotope project. This would make rhino horns radioactive, but how exactly would doing so prevent poaching? Let’s take a look.

Continue reading “Rhisotope: Addressing Poaching By Making Rhinoceros Horns Radioactive”

Intel’s ATX12VO Standard: A Study In Increasing Computer Power Supply Efficiency

The venerable ATX standard was developed in 1995 by Intel, as an attempt to standardize what had until then been a PC ecosystem formed around the IBM AT PC’s legacy. The preceding AT form factor was not so much a standard as it was the copying of the IBM AT’s approximate mainboard and with it all of its flaws.

With the ATX standard also came the ATX power supply (PSU), the standard for which defines the standard voltage rails and the function of each additional feature, such as soft power on (PS_ON).  As with all electrical appliances and gadgets during the 1990s and beyond, the ATX PSUs became the subject of power efficiency regulations, which would also lead to the 80+ certification program in 2004.

Starting in 2019, Intel has been promoting the ATX12VO (12 V only) standard for new systems, but what is this new standard about, and will switching everything to 12 V really be worth any power savings? Continue reading “Intel’s ATX12VO Standard: A Study In Increasing Computer Power Supply Efficiency”

Gdbdiff: Diff-ing A Real RP2040 MCU Against An Emulated MCU

What to do when developing an RP2040 emulator but validating the emulator instruction by instruction is a slow and tedious process? Why, automatically compare it against the real hardware if you’re [Uri Shaked], of course. This is the purpose of gdbdiff. This project uses the GDB remote serial protocol via OpenOCD to run test firmware step by step.

During a livestream (video linked via the above link), this allowed [Uri] to find a number of instruction bugs in the emulator this way. These issues involved issues such as incorrect flags in the APSR register and an edge case in the LSRS register. This gdbdiff livestream is part of an entire series of live-coding sessions during which [Uri] writes an RP2040 emulator from scratch.

We applaud [Uri] for creative thinking here, and assume that this way the livestream was probably more entertaining to watch than when doing instruction-level debugging purely by hand :)