opcodes can now be loaded into memory!
returning the content at that PC
created the CPU block
created the CPU block
added the CPU block
created the pcb block and ready  queue
testing if it reads the opcode
proper naming convention
for testing purposes
for testing purposes
got rid of a few parameters
for testing purposes
stupid mistake!
so confused on the difference between memory and memory manager
just debugging
cannot use the memory array in memory manager
had to add more parameters
OH! supposed to read the memory array here
PCB block was messed up due to javascript not syncing
giving a proper naming convention