Recently, I've started wondering how I could use my newfound knowledge of assembly language. After doing some thinking and a little bit of research, I decided that I had a few different options available to me. The first option was writing my own intermediate-level programming language, and the second was an assembly-based operating system written from the ground up with perhaps the integration of my own programming language as an interface for developing applications for the operating system. The third and final idea I came up with was using a lower-bit assembly language with an EEPROM programmer and some older style processors such as ones from both the 8 and 16-bit eras.
So, what did I pick? Well, I actually have chosen to do all of these things; I've already started working on my own operating system in assembly (different to Renovate OS that I'm developing in C for my company) which you can view the source code for on GitHub here: https://github.com/alexanderwalford-official/Open-OS-Assembly Currently, as of writing this blog post there's not much to the operating system as all it does is print some text using a template assembly file I found on the tutorial I was following to understand how to compile assembly into an operating system. I plan on changing the entire contents of the kernel file shortly, followed by including more assembly files.
As for the option of programming chips from the 8 and 16-bit era, I'll be holding off for now until I've gained more experience in writing in lower-bit assembly language. The main difficulty with lower-bit assembly language is that you typically have many fewer registers and the code you write has to be much more optimised. As I have already worked with the Raspberry PI 4B platform, I may look at the Arduino Uno R3 in C++ before moving on to programming EEPROM chips in assembly.
So, what did I pick? Well, I actually have chosen to do all of these things; I've already started working on my own operating system in assembly (different to Renovate OS that I'm developing in C for my company) which you can view the source code for on GitHub here: https://github.com/alexanderwalford-official/Open-OS-Assembly Currently, as of writing this blog post there's not much to the operating system as all it does is print some text using a template assembly file I found on the tutorial I was following to understand how to compile assembly into an operating system. I plan on changing the entire contents of the kernel file shortly, followed by including more assembly files.
As for the option of programming chips from the 8 and 16-bit era, I'll be holding off for now until I've gained more experience in writing in lower-bit assembly language. The main difficulty with lower-bit assembly language is that you typically have many fewer registers and the code you write has to be much more optimised. As I have already worked with the Raspberry PI 4B platform, I may look at the Arduino Uno R3 in C++ before moving on to programming EEPROM chips in assembly.
Comments
Post a Comment