Made a new RAM brick based off the one from the system the computer came with, Can store 256 32bit numbers :3 (Original could too, this is just a different more compact form factor)

Compacted the ALU (Arithmetic Logic Unit, it does all the math), Registry (basically a small 8 slot RAM system used to store/transfer/interact with data), And the Program Counter, which was an absolute pain due to the amount of systems it is, The ROM however I could not really compact without having to manually enter the line of code each spot is, that's what 2/5th of it's area is for lol

Broke the system trying to add a feature, spent 90 minutes trying to figure out what I broke, took apart and octuple checked two of the most complex parts of the whole thing and only realized that the new feature I added had a testing signal left on

trying to figure out how to cram 10 3bit numbers into a 32 bit signal seems simple... then you realize you have brain damage and do not know how to tell the little math bricks how to do it for you
Insert cymbal banging monkey here

"no plan ever survives first contact" somehow fits into software and hardware development too

(Right side is a drawing screen, left is the actual screen that runs off saved data)

This image (as raw data with no header or other information) is only 80 Bytes lmao
🐾❤️

BEHOLD,
An 8gb hard drive!
I mean.... ahem...
An 8kb hard drive!!

I need to figure out how to store more than 1 signal value to an RSNOR latch.
if I could, I just UNLOCKED how much data I can store (at the cost of a lot of pain dealing with the new plethora of capacity)

Dids it :3

Figured out a system that will let me expand taller than 10 pixels by making the pixel controller a part of the pixel itself, Problem is it adds this unusual dithering texture to it
not sure I like it tbh, might try and play with the packed RGB stuff next attempt

Different pixel layouts :3
Posting more/experimental ones in comments

Just spent about 3 hours trying to add an equals to and less than flag to the ALU's current Negative and Zero flags
and realized that there's a reason it didn't have those two in the first place as I can just do A-B and if the Zero flag trips, then A and B are equals
If I do A-B and the Negative flag trips, then A is less than B
95% of the CPU designing process has been "use anything in more ways than one without interference with other functions"
I did just end up exactly where I started but now I know why this is setup like that :3

also have learned that "optimization" systems are literally just "is doing it this way more step efficient than the original design? if not, try again lol"

Was gonna buy vintage story to play with a friend but Netflix sniped the twenty bucks I got from a comm, anyone down for a quick commission of some sort??

Nvm, accidentally looking sad to the rescue

Played a bit of vintage story, got stoned to death by horrors beyond my imagination when I tried to grab my pottery from the pit kiln
10/10

takes apart the entire device, testing piece by piece in a known working system
FINDS NOTHING WRONG, CODE GOES THROUGH FLAWLESSLY

Takes apart the entire device, then sticks it back together
IT WORKS!?
Flips table

Like, I made a whole system to run both CPU setups side by side, comparing their steps, values, and order of operation as they run, and a halt at step system, just to basically fix it by turning it off and on again