The Sinclair QL Forum

After much wall head butting to try to get git to create a repository on my NAS box due to new, higher security (paranoia) updates I've finally got the code and PCBs onto Github here:

https://github.com/stephen-usher/Pico-Scanned-Keyboard-Matrix-Emulator

I'll add a binary for the QL firmware ...

Oh, so this could eventually be used for something like an Amiga then too? A handy item would be something of a pass-through connector that lets you hook up both original and the USB keyboard so you could run a connector outside the case and use both the original or hook the USB to it.

Funny ...

And all fixed!

https://youtu.be/eKsEGuwRFOQ?si=gRmY12IxoGUb2Pni

Once I've cleaned up the code I can post all of this on Github.

Adding replacement software for different machines shouldn't be too difficult using the QL code as a basis. It'll be mostly the translation code which would need to be ...

Using some example USB keyboard code I found on Github I've managed to get a USB keyboard mostly working.


IMG_4536.jpeg


Autorepeat isn't working and there is some key bounce, which could be being caused by the same thing.

More worryingly, however, with the keyboard plugged into the Pico I'm ...

I like it. Congrats for successful development

For what the serial port?
Would not save resources (in this case) to use the Arduino Nano? for power and signal level compatibility.


The serial port is there mainly so that I can debug the USB HID (keyboard and maybe joystick) support via the ...

And the RS232 works... though when the board is powered by the PicoATX power supply the 74LS244 didn't get power as it seems that the Pico doesn't power the VBUS line if powered by VSYS, so a bodge wire was necessary.

The boards arrived just after lunch, so I quickly built one up. Just a minor issue with the DB9 sockets I bought overlapping one of the header positions, but nothing a pair of wire cutters couldn't fix.

The good news is that it works at least as well as the breadboard version so far. I've not ...

The OPD is not running QDOS and the OS treats the RAM as a set of 4K fixed size data pages in a database which it controls.

The machine is acting more like an early 1970s minicomputer than a micro.

My diagnostic ROM can do this, at least for memory up to 768K. I don't know what the memory map above that looks like and whether there's a risk that the memory test code might hit I/O ports etc. and give false reports of bad RAM.

What ever happened to this project?

The Telestore was also another target but I don't think anyone managed to read the EPROMs as they are soldered to the board?


It's on Github for everyone to enjoy. :-)

https://github.com/stephen-usher/OPD-Computer-One-Disk-Interface

The Telestore with the ...