TechyMagThings

If you’ve used MicroPython much, you know that debugging usually amounts to printing a few things out, trying your code out, and then repeating. But [ghi-electronics] wants you to have full on-chip source-code debugging in Visual Studio. You don’t need anything special to use it — just a supported MicroPython host and the same USB cable you program with now.

The downside is that you either have to build a custom MicroPython image and flash it or use one that they include. They support several Raspberry Pi Pico versions and ESP32 chips, as well. However, at least one “odd” Pico we had lying around wouldn’t take the firmware. A stock one did, and it worked as you would expect. A little more investigation showed the odd Pico (an RP2040 GEEK) probably did take the firmware; it just produced an error during setup. There is a known problem with Linux and the ESP32-S3 having similar behavior.

Of course, you can build your own image, but now you are talking a bit more work to get a toolchain and all the dependencies together. For simple programs, you might not need a full-blown debugger. But it is nice to be able to peek at variables and see the control flow visually.

There are a few limitations documented on GitHub. For example, you can’t catch exceptions that the code already catches, although, presumably, you could set a breakpoint in the exception handler. Breakpoints halt all threads. There are a few other limits, but nothing we’d consider a showstopper.

Full Python has some debugging assistance built into it. MicroPython has some of the same things, but it isn’t trivial to build a debugger.

In 1982, desktop computers were coming into their own, and no clear leaders had emerged. But everyone knew they wanted a piece of the action. This led to, among other things, Sony’s SMC-70, which, frankly, for 1982, was a good-looking, if not oddball, machine. [Tech Tangents] shows the machine off in a recent video.

From the front, the computer looks more-or-less like everything else. But as you move backward, you can see this computer wasn’t another typical entry into the market. One of the things that was the hallmark of successful business computers of the day was expandability. The earlier Altair had the later-titled S100 bus. The IBM PC had the ISA bus. But in both cases, you had to open the box to plug and unplug cards.

The SMC-70, though, had a very unique system. Instead of boards, users would line up modules and stab them with what amounted to skewers to mechanically secure the stack of modules. You could stack some modules vertically or horizontally using ribbon cables or external cables. This particular box needed some power supply work, and a 3D printer lets it look essentially stock.

Computing-wise, the SMC-70 was pretty typical. A CP/M machine with a 4 MHz Z-80 wasn’t novel then, although few CP/M systems had 3.5-inch floppies. What set the Sony apart was its 16-color graphics system, which was well ahead of its time. It even had some sound capability.

It also had a module that offered quite a bit of video output capability, which shouldn’t be surprising given Sony’s other product lines. There was, apparently, an 8086 module that eventually became available, but it was late and didn’t run MS-DOS (but could run CP/M-86).

A few nice features didn’t catch on. A dedicated red help button on the keyboard was a nice idea, for example. There was even a RAM disk mode, which was great if you didn’t suffer power outages.

Of course, Sony made many more computers. If you want to play with a CP/M machine, you probably could get a virtual one up in a few minutes.

In the cross-over between the era of tapes into that of MP3s, you’d see quite a few of those special cassette tapes that were actually digital music players inside. Some simply provided a 3.5 mm input, while others were complete MP3 players or Bluetooth receivers that just happened to also output to the magnetic read head of a cassette player. Recently [Jonathan Rowny] decided to make his own version of the latter.

Although getting the actual audio signal into the read head is easy enough – requiring little more than its equivalent being used as a write head on the cassette side – actually interfacing with the player’s mechanisms like auto-stop, reverse and so on requires the use of some gearing that detect motion on what would be the tape spools, as well as transfer the motion from the take-up spool to the other spool so that features like the auto-stop mechanism don’t get triggered.

A lot of inspiration here can be found in e.g. the videos made by [Clint] of [Lazy Game Reviews] who looked at a number of examples – including their internals – over the years, with various levels of functionality. For this particular implementation an ESP32-S3 module is used for the brains, along with a microSD card reader for music and a PCM5102 I2S audio codec to create the analog audio signal.

The gears were printed using an SLA printer and seem to work all right. Unfortunately he didn’t realize the importance of the capstan as the mechanism that actually transports the tape, so its motion was not measured as is done in the better cassette adapters. This will likely be corrected in a future iteration, however.

Before moving to land grid array (LGA) packaging whereby each pin on the substrate is just a copper pad, processors commonly used pin grid array (PGA) packaging, including the still highly relevant AMD AM4 socket. With PGA you get a pin soldered onto the copper pad which inserts into the ZIF socket, rather than a fragile pin on the mainboard side. Repairing a damaged PGA pin can be easy if just the pin broke off at the solder joint, or rough if the pad was destroyed, as in the case of this Pentium III CPU that [Bits und Bolts] recently tried to fix.

In the case of something like a ground pin or similarly unimportant pin you can ignore the damage, but in this case it concerned an important pin for this 1.2 GHz Tualatin PIII core, with the damage consisting of a well and truly destroyed pad. The first step to repair the damage is thus to try and rebuild the pad, which was done using solder mask and solder.

Although a PIII-era Celeron CPU is definitely not a high-value CPU, since they have so few and such large pins they do make for useful test subjects when it comes to PGA repair practicing. In this case the affected data pad and pin appears to have been repaired successfully, with it running overclocked to 1.6 GHz and crushing similarly or higher clocked Pentium 4 and AMD Athlon CPUs of the era.

Surveillance cameras from Flock Safety have become a controversial privacy battleground, as the communities in which they are installed wake up to their sinister potential, and stories roll in of law enforcement professionals abusing their access. One has had its disk contents dumped, and we’ve been treated to some insights courtesy of [Micah Lee]. In short: their approach to security is deeply flawed.

It’s interesting to find that instead of a custom hardened OS, these devices run Android. Not just Android, but Android 8.1, a long out of support version originally released in 2017. This is is the year Flock Safety was founded, which may or may not be coincidental. Like any old version of a widely used operating system it has a host of known vulnerabilities, none of which are patched on this version.

The Android version is small beer compared to the revelation that they contain a hard-coded and very open-access API key that can be used by any mildly curious miscreant to reveal information from any Flock camera using its MAC address. One would hope that a product marketed for use by law enforcement might have paid attention to such a basic lapse, but it seems not. Whether or not this can be corrected by a software upgrade and the leaked key deactivated without turning off the network depends on whether thy can do upgrades tailored to specific devices, but either way we wouldn’t like to be the team tasked with fixing that one.

In a way it’s reassuring that the surveillance apparatus when it came was so incompetently managed, and we hope that these vulnerabilities will have moderated its effect. We’re sure more tasty discoveries will emerge as investigations proceed, and we’ve got the popcorn ready.

Image: Tony Webster, CC BY 2.0.

The Cheap Yellow Display is an all-in-one ESP32 board with a touchscreen, that’s as the name suggests, cheap. It’s appeared in a great many projects since it emerged from the depths of AliExpress, and today thanks to [Nickm324] it takes the turn of becoming a mini TV.

The tiny TV project world is one of successive developers building on previous works to deliver their own refinements on the idea, so this one borrows heavily from an earlier ESP32 project. Its twist on the idea is a single button interface using the CYD’s BOOT button. It supports a range of “channels” of which each one is a different piece of media played from the SD card. As far as we can see it’s only able to play synchronised .mjpeg and audio files, probably a shortcoming of the older ESP32 found on the CYD. The photo features a rather cutesy retro 3D printed TV case which annoyingly isn’t linked from the repository at the time of writing.

It’s a nice idea, and the CYD makes it as easy as possible with minimal wiring. Yes it’s a novelty, but we’re guessing there could be many non-novelty applications for it too. It’s certainly not the first such project we’ve seen, here’s an earlier one.

With an El Niño event in full swing those of us in the northern hemisphere have just had a roasting hot summer, and those in the southern are about to have one. We know what that means, even with the best laid plans the slightest bit of exercise is going to raise a lot of sweat. And if you’re carrying a backpack that means a soaking down your back. Never fear though, because for that one, [Crafterboi] is here with a fan-assisted back protector.

The idea is simple enough, an open framework that sits between you and the backpack, allowing air to flow. If that weren’t enough, there are a couple of 5 volt fans at the top to blow air through the space. It’s printed using PETG, because as he explains, on a really hot day some surfaces can exceed the temperature at which PLA starts to soften.

We like the idea of this project, but what we especially like is that his prototype was made of a pizza box. ten out of ten for resourcefulness! Meanwhile this isn’t the first time we’ve seen a cooling backpack as others have had Peltier systems and evaporative coolers. We would link you to them, but sadly those are both from Hackaday’s early years and link rot has taken their websites.