4 ms·
Your biggest limit, IMHO, is that the 6502 does memory access every cycle (some of the accesses are unused), so you need your memory (and perhipherals) to be ab
by toast0 4y ago
Your biggest limit, IMHO, is that the 6502 does memory access every cycle (some of the accesses are unused), so you need your memory (and perhipherals) to be able to respond fast enough, or you need to lengthen clock cycles when accessing slow perhipherals. I think ram access times tend to be in the 10s of nanosecond, so I'd guess you're going to have trouble scaling beyond 100Mhz without exotic ram or a different design. I don't know much about the internals to speculate if they could manage higher clock speeds, but I'd guess it would be fine?
- yjftsjthsd-h 4y agoCould you create a 6502 with cache and pipelining? My understanding is that those are both implementation details that shouldn't affect the "userspace ABI" that code running on the chip can see, other than making performance nonuniform (because it slows for every cache miss and branch misprediction). Obviously that only helps with true memory access; I don't think there's anything to be done for true I/O.
- vikingerik 4y agoI/O and memory access are the same thing for the 6502. All it can do is read or write from a bus with 16 address bits and 8 data bits. The environment/motherboard might have memory that responds to some combinations of those address bits, and it might have something like say an NES PPU that responds to other combinations, by handling those writes as tile or sprite data and generating a video output signal. You could hypothetically make a 6502 with a wider or dual bus, so that it could read or write more than one byte per cycle or both at the same time, if whatever else is on the bus on the other ends of the reads/writes is compatible with that. In that way you could speed up executing 6502 instructions by more than just increasing clock speed.
- ack_complete 4y ago6502s or 65C02s were used with cache in many Apple II accelerators. Apple licensed one of them for the Apple IIc.
- flohofwoe 4y agoPlugging such an "advanced 6502" into a traditional home computer design would break pretty much all games and scene demos, because those depend on "hard realtime" behaviour of the whole system down to single clock cycles (this is also why cycle-correct emulators are slower than emulators with less strict timing requirements - a cycle correct emulator can only take shortcuts for behaviour that doesn't "leak" into the rest of the system).
- vikingerik 4y agoThe 6502 can only address 2^16 bytes of memory, so you could just build that as a modern L1 cache. Heck, you might even be able to put 2^16 registers on the die these days. (You could say this falls under your "exotic ram" clause.) You could also do pipelining and parallel/out-of-order execution like modern processors, if you weren't worried about retaining cycle-for-cycle compatibility. You could even build it with a wider bus, so that you could read all of a 2/3/4 byte instruction in one cycle. Although at that point it's really semantics as whether you call it a 6502 or a new processor with binary compatibility.
- shadowofneptune 4y agoThe zero page is small enough to fit into a single vector register nowadays. Since the zero page is used like a register file, that alone could be a big advantage.
- toast0 4y ago> you could just build that as a modern L1 cache. I think this could work, although if that means the ram is on die, setting up the memory map is much more complex (although maybe you just have a chip select pin for the on-die ram, and have your address decoder circuitry select it when appropriate for your system) > You could also do pipelining and parallel/out-of-order execution like modern processors I don't think that fits the prompt of same fundamental design though.
- flohofwoe 4y ago> setting up the memory map is much more complex This is where the Z80 would come in handy with its separate 16-bit IO address space (accessed through special IO instructions and on the hardware level an IORQ output pin). The Z80 can also easily handle slow memory and IO devices through its WAIT input pin (but of course this just causes the CPU to slow down to the speed of the memory or IO device).