Vanity Project: System Emulator

Having played with pico-8 (which I love!), I was wondering about creating an emulated computer system from scratch.  I couldn't really figure out what the point would be. 

A demonstration system for secondary students? - probably too complicated. 

A competitor to pico-8? - just why? pico-8 is awesome.

A replacement for LMC? - probably too complicated.

A nostalgia trip about tinkering with the Commodore 64 back in the day? - maybe.

Just for fun? - ...

Well I eventually accepted the idea that I am actually crazy enough to enjoy putting together a virtual system for no other reason that it might be interesting to try.  With that in mind, I chose to do it in C# because I hadn't used MonoDevelop in ages.  (Writing a VM which runs inside the .NET VM does feel a little VM-ception though).

I decided to start from a 6502-style instruction set, with Load Immediate and such (although I'll probably pass on the more complicated addressing modes), but I thought I'd make the fundamental unit 32-bit instead of 8.  This would make working with floats feasible, as well as increasing the memory-size cap way beyond anything I'd actually need.

The bytecode CPU is simple enough: an array of register values and a giant switch() statement does perfectly fine.  Likewise with the memory controller: read that location into this register, etc.  I/O devices and the boot sequence though?  When it's me making up my own rules, what counts as cheating?

In the interests of future flexibility, I decided to use an interface somewhat similar to the I2C bus in embedded systems.  The CPU will have a pair of instructions which can set/get a numbered register on a numbered device.

I then settled on a target of making the simplest possible interface that would allow the machine to be programmed via its own interface.  That would need a basic OS with keyboard input, text output and commands to set/display memory values and copy to/from persistent storage.

For some reason, I decided I wanted the system to load a BIOS program first, which would search for some kind of boot sector on a storage device, load code from that sector into memory, then run it.  I allowed the BIOS to parse hex from a text file rather than resorting to a hex editor (I'm still not sure how I feel about cutting that corner ;)).

And today's progress means I now have a BIOS program which outputs the word 'blah' to the console via CPU instructions to set registers on a 'ConsoleOutputDevice'.

...

Well, somehow I still feel proud of this. :)


I think the future rules of my facile little game will include: hardware can be implemented in C# but any and all software, interrupt routines, drivers, etc. should be implemented through the system's own interface.

So yeah, that's...a thing.

I definitely feel like I've plumbed new depths of weird...





Comments

Post a Comment

Popular posts from this blog

Micro:Bit and SPI display

I want to explore the full potential of the BBC Micro:bits my school has. Making rock-paper-scissors games and the like is all well and good, and the students love it (for the most part), but it always feels a little bit gimmicky.  But when students really get engaged and suggest ideas for them (e.g. games, compass display), it all gets a little bit cramped and feels like it could  kinda  work, but not really . Then I found out that all the tiny strips on the edge are actually GPIO pins, not just the fat 0, 1 and 2 ones.  Since then, I've wanted to explore what I can do with it. Hence, over the last few days I have been trying to get the microbit to control a TFT display. I first went for this 2.4" display with a touchscreen.  The SPI interface is just for the microSD, not for the screen but I didn't think that would be a problem because the micro:bit has so many pins.  After much frustration, I discovered that there are many of the pins you can't reliably use extern
Read more

DCS World with TrackIR under Ubuntu

This is a record of my experience of setting this up.  It's meant more as a record for my future self than a tutorial, but maybe somebody will find it useful. 1 - Install DCS First step, install DCS World via the Steam client as normal.  2 - Install LinuxTrack Linuxtrack Download here: https://github.com/uglyDwarf/linuxtrack/wiki/Downloads   Instructions here: https://github.com/uglyDwarf/linuxtrack/wiki/universal-Linuxtrack-package   Using the gui (ltr_gui) requires qt4 libraries, which I could not find in my standard Ubuntu repositories, so I had to use the ppa instructions here: https://ubuntuhandbook.org/index.php/2020/07/install-qt4-ubuntu-20-04 Run ltr_gui from linuxtrack's bin directory to check everything works so far before moving on to get it running under Proton.  3 - Install LinuxTrack into the DCS World prefix NOTE: Attempting to install for Wine games WON'T WORK e.g. here https://github-wiki-see.page/m/uglyDwarf/linuxtrack/wiki/Wine-Games   This is because Ste
Read more

Cardboard Mock-up of USB Joystick

Image
For years now (literally years ), I have been playing around with the idea of making a USB joystick.  You may have seen my previous experiment in building a throttle control . I wanted to use a similar idea to the throttle, taking the angular motion of the handle and magnify it when applying it to the potentiometer.  e.g. move the handle through 45 degrees and the potentiometer gets moved through 90 degrees. I also wanted it anchored at the rear, so I can build a mount to attach it to my computer chair. In the video you can see a cardboard mock-up I made today.  I'm amazed it worked at all, but it even provides a solid foundation for designing the proper plywood one. The process of making a cardboard mock-up was really useful.  There were three fatal flaws in my sketch design which I would not have found out until I tried to make it: Pushing the joystick left/right when it was already pulled full back makes it catch on the rear support. The internal supports in the
Read more