For many people, a retrocomputer is a classic machine from the past lovingly brought back to working order. But for some, the idea of a retrocomputer is wider than that, encompassing modern hardware that delivers to feel like a device from the past.
The Monotron from [Jonathan Pallant] is one such computer. It’s definitely a retrocomputer such as you might have found in the 1980s, but it’s running on a much more modern Tiva-C TI Launchpad dev board sporting an ARM Cortex M4.
The platform has been created entirely in Rust, and emulates what would have been a rather desirable machine in the early 1980s. With an 800×600 pixel 8-colour VGA display interface, 32k of RAM, and mono 8-bit audio, it already has a few simple demos and games running upon it. [Jonathan Pallant] has given more than one talk on its design and capabilities, we’ve placed one of them as a video below the break. There is even a PCB available which adds all the ports as well as a micro SD card slot for program storage.
We like the Monotron, and we look forward to seeing it develop. It’s an exciting time for retrocomputig with projects such as the RC2014 Z80 machine and the Gigatron TTL RISC processor, but is there space for an emulated one such as this? We hope so.
At the end of August I made the trip to Hebden Bridge to give a talk at OSHCamp 2019, a weekend of interesting stuff in the Yorkshire Dales. Instead of a badge, this event gives each attendee an electronic kit provided by a sponsor, and this year’s one was particularly interesting. The RC2014 Micro is the latest iteration of the RC2014 Z80-based retrocomputer, and it’s a single-board computer that strips the RC2014 down to a bare minimum. Time to spend an evening in the hackerspace assembling it, to take a look!
It’s An SBC, But Not As You Know It!
The kit contents
The kit arrives in a very compact heat-sealed anti-static packet, and upon opening was revealed to contain the PCB, a piece of foam carrying the integrated circuits, a few passives, and a very simple getting started and assembly guide. The simplicity of the design becomes obvious from the chip count, there’s the Z80 itself, a 6850 UART, 27C512 ROM, 62256 RAM, 74HCT04 for clock generation, and a 74HCT32 for address decoding. The quick-start is adequate, but there is also a set of more comprehensive online instructions (PDF) available.
I added chip sockets and jumpers to my kit.
Assembly of a through-hole kit is hardly challenging, though this one is about as densely-packed as it’s possible to make a through-hole kit with DIP integrated circuits. As with most through-hole projects, the order you pick is everything: resistors first, then capacitors, reset button and crystal, followed by integrated circuits.
I’m always a bit shy about soldering ICs directly to a circuit board so I supplemented my kit with sockets and jumpers. The jumpers are used to select an FTDI power source and ROM addresses for Grant Searle’s ROM BASIC distribution or Steve Cousins’ SCM 1.0 machine code monitor, and the kit instructions recommended hard-wiring them with cut-off resistor wires. There was no row of pins for the expansion bus because this kit was supplied without the backplane that’s a feature of the larger RC2014 kits, but it did have a set of right-angle pins for an FTDI serial cable.
Your Arduino Doesn’t Have A Development Environment On Board!
Having assembled my RC2014 Mini and given it a visual inspection it was time to power it up and see whether it worked. Installing the jumper for FTDI power, I attached my serial cable and plugged it into a USB port.
A really nice touch is that the Micro has the colours for the serial cable wires on the reverse side of the PCB, taking away the worry of getting it the wrong way round. A quick screen /dev/ttyUSB0 115200 to get a serial terminal from a bash prompt, hit the reset button, and I was rewarded with a BASIC interpreter. My RC2014 Micro worked first time, and I could straight away give it BASIC commands such as PRINT "Hello World!" and be rewarded with the expected output.
The SCM ROM monitor.
So I’ve built a little Z80 single board computer, and with considerably less work than that required for the fully modular version of the RC2014. Its creator Spencer tells me that the Micro was originally designed as a bargain-basement RC2014 as a multibuy for workshops and similar activities, being very similar to his RC2014 mini board but without provision for a Pi Zero terminal and a few other components. It lacks the extra hardware required for a more comprehensive operating system such as CP/M, so I’m left with about as minimal an 8-bit computer as it’s possible to build using parts available in 2019. My question then is this: What can I do with it?
So. What Can I Do With An 8-bit SBC?
My first computer was a Sinclair ZX81, how could it possibly compare this small kit that was a giveaway at a conference? Although the Sinclair included a black-and-white TV display interface, tape backup interface, and keyboard, the core computing power was not too far different in its abilities from this RC2014 Micro — after all, it’s the same processor chip. It was the platform that introduced a much younger me to computing, and straight away I devoured Sinclair BASIC and then went on to write machine code on it. It became a general-purpose calculation and computing scratchpad for repetitive homework due to the ease of BASIC programming, and with my Maplin 8255 I/O port card I was able to use it in the way a modern tech-aware kid might use an Arduino.
The RC2014 Micro is well placed to fill all of those functions as a BASIC and machine code learning platform on which to get down to the hardware in a way you simply can’t on most modern computers, and though the Arduino represents a far more sensible choice for hardware interfacing there is also an RC2014 backplane and I/O board available for the Micro’s expansion bus should you wish to have a go. Will I use it for these things? It’s certainly much more convenient than its full-sized sibling, so it’s quite likely I’ll be getting my hands dirty with a little bit of Z80 code. It’s astounding how much you can forget in 35 years!
The RC2014 Micro can be bought from Spencer’s Tindie store, with substantial bulk discounts for those workshop customers. If you want the full retrocomputer experience it’s a good choice as it provides about as simple a way into Z80 hardware and software as possible. The cost of simplicity comes in having no non-volatile storage and in lacking the hardware to run CP/M, but it has to be borne in mind that it’s the bottom of the RC2014 range. For comparison you can read our review of the original RC2014, over which we’d say the chief advantage of the Micro is its relative ease of construction.
A smartphone in 2019 is an essential piece of everyday equipment. Many of you are probably reading this page on one, and it will pack a very significant quantity of computing power into your hand. Pocket computing has a long history stretching back decades before the mass adoption of smartphones though, and Paleotronic has an interesting retrospective of that earlier history.
The piece starts with the Radio Shack PC-1, a rebadged Sharp with a calculator-style keyboard and a one-line alphanumeric LCD display, then continues through the legendary TRS-80 Model 100 to the era of the palmtop. It’s a difficult subject to cover in its entirety as there are so many milestones on the pocket computing path, but it’s an interesting read nevertheless as it successfully evokes the era when a 300 Baud connection via an acoustic coupler was a big deal. We might for example have mentioned the Atari Portfolio if only for its use by a young John Connor to scam an ATM in Terminator 2, and as any grizzled old sysadmin will tell you, there was a time when owning a Nokia Communicator might just save your bacon.
Of the classic pocket computing devices mentioned, only one has received significant coverage here. The TRS-80 model 100 still has a huge following, and among quite a few hacks featuring it we’ve seen one brought into the smartphone age by getting the ability to make a cellular connection.
TRS-80 Model 100 image: Jeff Keyzer from Austin, TX, USA [CC BY-SA 2.0]
There are many ways to attach a project to the Internet, and a plethora of Internet-based services that can handle talking to hardware. But probably the most ubiquitous of Internet protocols for the average Joe or Jane is the web browser, and one of the most accessible of programming environments lies within it. If only somebody with a bit of HTML and Javascript could reach a GPIO pin on their Raspberry Pi!
If that’s your wish, then help could be at hand in the form of [Victor Ribeiro]’s RPiAPI. As its name suggests, it’s an API for your Raspberry Pi, and in particular it provides a simple web-accessible endpoint wrapper for the Pi’s GPIO library from which its expansion port pins can be accessed. By crafting a simple path on the address of the Pi’s web server each pin can be read or written to, which while it’s neither the fastest or most accomplished hardware interface for the platform, could make it one of the easiest to access.
Security comes courtesy of Apache password protected directories via .htaccess files, so users would be well-advised to consider the implications of connecting this to a public IP address very carefully. But for non experts in security it still has the potential to make a very useful tool in the armoury of ways to control hardware from the little single board computer. It’s not the first try at this idea as we’ve seen a PHP example early in the Pi’s lifetime as well as one relying upon MySQL, but it does seem to be a simpler option than the others.
We no longer use floppy disks on the vast majority of computers, but a recent Old New Thing blog post from Microsoft sheds light on one of their possible unexpected legacies. It seems Windows disk cache items expire after two seconds, and as the post explains this has its origin in the development of MS-DOS 2.0.
Disks, especially floppy disks, are slow compared to computer memory. A disk cache is a piece of memory into which the operating system puts frequently loaded items to speed up access and avoid its having to repeatedly access the disk. They have an expiry time to ensure that the cache doesn’t become clogged with data that hasn’t been needed for a while.
IBM PC floppy drives didn’t implement any form of notification for a disk eject, so it became quite possible for a disk to be ejected while the operating system still believed cached data from it to be valid. Thus a pair of Microsoft engineers tried their hardest to swap floppy discs as fast as they could, and it was discovered to be an impossible task in under two seconds. This became the cache expiry time for a Microsoft OS, and thus we’re told the floppy’s legacy lives on as more than just the ‘save’ icon.
As this is being written the Internet is abuzz with a viral Tweet about railroad gauges having an origin in the width of a Roman horse, that rail historians are debunking with a reference to the coal tramways of [George Stephenson’s] Northern England. It’s thus sometimes dangerous to take simple soundbite origin stories at face value, but since in this case our source is Microsoft themselves we think we can take it as being close to the horse’s mouth. Even if it isn’t a Roman horse.
IBM floppy drive image: Michael Holley [Public domain].
It’s fair to say that 2019 has not been a good year for the aircraft manufacturer Boeing, as its new 737 MAX aircraft has been revealed to contain a software fault that could cause the aircraft to enter a dive and crash. Now stories are circulating of another issue with the 737, some of the so-called “Pickle forks” in the earlier 737NG aircraft have been found to develop cracks.
It’s a concerning story and there are myriad theories surrounding its origin but it should also have a reassuring angle: the painstaking system of maintenance checks that underpins the aviation industry has worked as intended. This problem has been identified before any catastrophic failures have occurred. It’s not the story Boeing needs at the moment, but they and the regulators will no doubt be working hard to produce a new design and ensure that it is fitted to aircraft.
The Role of the Pickle Fork
For those of us who do not work in aviation though it presents a question: what on earth is a pickle fork? The coverage of the story tells us it’s something to do with attaching the wing to the fuselage, but without a handy 737 to open up and take a look at we’re none the wiser.
Fortunately there’s a comprehensive description of one along with a review of wing attachment technologies from Boeing themselves, and it can be found in one of their patents. US9399508B2 is concerned with an active suspension system for wing-fuselage mounts and is a fascinating read in itself, but the part we are concerned with is a description of existing wing fixtures on page 12 of the patent PDF.
A cross-section of the aircraft wing fixing, in which we’ve highlighted the role of the pickle forks. (Boeing)
The pickle fork is an assembly so named because of its resemblance to the kitchen utensil, which attaches firmly to each side of the fuselage and has two prongs that extend below it where they are attached to the wing spar.
For the curious engineer with no aviation experience the question is further answered by the patent’s figure 2, which provides a handy cross-section. The other wing attachment they discuss involves the use of pins, leading to the point of the patented invention. Conventional wing fixings transmit the forces from the wing to the fuselage as a rigid unit, requiring the fuselage to be substantial enough to handle those forces and presenting a problem for designers of larger aircraft. The active suspension system is designed to mitigate this, and we’d be fascinated to hear from any readers in the comments who might be able to tell us more.
We think it’s empowering that a science-minded general public can look more deeply at a component singled out in a news report by digging into the explanation in the Boeing patent. We don’t envy the Boeing engineers in their task as they work to produce a replacement, and we hope to hear of their solution as it appears.
If you owned a classic Commodore home computer you might not have known it at the time, but it would have contained a versatile integrated circuit called the MOS6526. This so-called CIA chip, for Complex Interface Adaptor, contained parallel and serial ports, timers, and a time-of-day counter. Like so many similar pieces of classic silicon it’s long out of production, so [Daniel Molina] decided to replicate a modern version of it on a PCB using 74HGT CMOS logic.
The result will be a stack of boards board that appear to be about the size of a 3.5″ floppy disk covered in surface-mount 74 chips, and connected to the CIA socket of the Commodore by a ribbon cable. The base board is the only one completed so far and contains the data direction registers and parallel ports, but the succeding boards will each carry one of the chip’s other functions.
It seems rather odd to use so much silicon to recreate a single chip, but the point is not of course to provide a practical CIA replacement. Instead it’s instructive, it shows us how these interfaces work as well as just how much circuitry is crammed into the chip. It’s no surprise that it’s inspired by the C74 Project, a TTL 6502 processor that we featured last year.
If that’s your wish, then help could be at hand 
