If you’re new to programming the 6502 microprocessor—or revisiting it from the world of modern computing—one of the first terms you’ll encounter is the opcode. This blog post lays the foundation for the rest of the series by explaining what opcodes are, how they relate to the 6502’s architecture, and why understanding them is key.
Read MoreWhen diving into programming for the Commodore 64, one of the most crucial aspects to grasp is how memory is organized and accessed by the 6502-based CPU. Unlike modern systems with gigabytes of RAM and virtual memory management, the C64 operates within a tight 64KB address space, and every byte counts. The 6502’s 16-bit Address.
Read MoreSo there we are. My blog about my project, the 6502 simulator. And surely you’re wondering why? Why another 6502 simulator?
Read MoreIf you want to see what opcodes are implemented yet, milestones etc. …
Read MoreWhen building a 6502 emulator, one of the most fundamental architectural decisions you’ll face is how to organize memory access. It’s tempting to embed the memory array directly into the CPU class – especially for early prototypes – but as your emulator grows, this tight coupling becomes a liability. A better approach is to implement.
Read MoreRegarding observing the cycles, I changed my mind. At first, I didn’t attach any importance to it. After some more reading and getting a better understanding of the importance the cycles have, even in a simulation, I will will do some changes to the code.To do this in a way that keeps the code flexible.
Read More