Skip to main content

USB keyboard interface for Minstrel 4th - Prototype to PCB

T

oday we transfomed this magnificent mess of wires....

Into this beautiful little module
It plugs into the Minstrel 4th's RC2014 port, either directly, or as here, using an RC2014 backplane. It accepts a USB keyboard* via an OTG adaptor (USB A to micro).

Like its inspiration, the Jupiter Ace, you wouldn't want to spend serious typing time on the Minstrel's tactile keyboard. It's nice to have a familiar layout of full-size keys, and the interface's firmware buffers your input, meaning that you can type as fast as you like. 

It took a lot of development time to get to a working breadboard prototype. It's pretty fragile and so it feels very good to have received the first PCBs today. 

There was a minor hitch, which has to do with my limited understanding of the Pico's confusing VBUS/VSYS power supply circuit. In the end it was easily solved with a solder bridge and here it is working:
Since ordering these version 1 boards, I decided to add the ability to connect to the interface using a Terminal on a modern computer, meaning that you can type via the terminal app and have a 'paper tape' record of your work, either by copying and pasting from the terminal or using a capture file. You can then re-paste word definitions or longer listings into the terminal. I think I'll find this more convenient than saving and loading**. Here's a quick demo:

With the minor correction made, and FTDI header added to the PCB design, version 1.1 is ordered, along with components to make the first batch.


I'm now selling this item: the listing's url changes over time as I make and sell batches, so please contact me at:  shirley at newstuffforoldstuff dot com  for details




* not all keyboards are supported. I still haven't found out what factor determines whether a keyboard works with the TinyUSB Pico library, all I can say is that some do, some don't. 
 
** this has the added benefit that you can compile and paste a 'clean' listing of your tested word definitions. I've found EDIT, REDEFINE and FORGET problematic with Ace Forth.  




Comments

Popular posts from this blog

ZX81 reversible internal 16k upgrade

T his post is an upvote for Tynemouth Software's  ZX81 reversible Internal 16K RAM upgrade . Their instructions are easy enough for even me to follow and don't involve cutting tracks. This is the ZX81 I've had out on display and used whenever I wanted to. It's an issue 1 and was probably a kit judging by some very untidy assembly. It has a ZX8-CCB  composite video mod and an external keyboard fitted. On board it has two 1k x 4-bit chips.  The ZX81 originally came with 1k on board. Thanks to a trick with compressing the display in ram, that was enough to type and run a small program but you soon felt the limitations. Back in the early 80s, the solution was a 16k ram pack which plugged into the back[1] and this is the way I've been using this particular machine. These ram packs are notorious for 'ram pack wobble'. Even if fastened into place, you can still randomly find your work disappearing. This is a very reliable solution using a more modern 32k chip (half

Driving NeoPixels with Z80

I 've long been thinking about a version two   RC2014 LED matrix module . I've had a matrix with a MAX 7219 on a module. It's a nice enhancement. But there's only so much you can do with a single-colour LED array right? Wouldn't it be cool to have RGB LEDs?  At Liverpool MakeFest I saw a wall-sized ping-pong ball NeoPixel display and picked up some NeoPixels with the intention of making one. Possibly driven by my RC2014.  I enjoy learning about protocols and have had some SPI devices working with the RC2014 - bit-banging SPI works really well because it doesn't care about timing. NeoPixels really do care about timing though. From Adafruit's web page about their 8x8  NeoPixel matrix: If there's one thing I want to get across in this blog post, it's don't just accept what you're told . Question everything. Learn about what's going on and find out why you're being told something isn't possible. Get creative with workarounds. I'

Making new ROMs for the Vic20 / Vicky Twenty

M y Vicky Twenty is very nearly complete.  As things stand, the board and every single component is new*. The processor and VIAs are newly-manufactured (W65C02 and W65C22).  Obviously the Vic1 chip isn't manufactured today, but there is 'new old' stock about. I have been able to buy a Vic 1, date code 1987 (which seems very late). It obviously hasn't been in a computer before, passes the acetone test and works. The same goes for two of the ROMs - character and BASIC. But I haven't been able to buy a new-old Kernal ROM (901486-07). I am able to borrow one - all of the boards I have, have this particular ROM socketed. I don't know whether all of this indicates that the Kernal has proved less reliable than the other two. I recently bought a TL866 for another project. Of all the retro-computing hardware things I've had to learn to do, making ROMs has been one of the simplest. So far, everything has been very easy and worked first time.  I'm not sure that it&