Re: Modern, but fully compatible 6502?

From: Jim Brain <brain_at_jbrain.com>
Date: Tue, 6 Sep 2022 09:22:28 -0500
Message-ID: <f290cb4f-3c55-7fd3-0d09-2fb31c977d53_at_jbrain.com>
On 9/6/2022 7:00 AM, silverdr_at_srebrnysen.com wrote:
>
>>> Were they? I always considered them to be a side-effect of the internal decoder matrix which did not specifically "NOP" the unused opcodes (which IIRC was done with the CMOS versions), but just bluntly decoded the individual parts of the opcode, generating corresponding enable signals.
>>>
>>> So stuff happened like e.g. loading the accumulator, but also throwing the X register onto the internal data bus.
>> As I recall, a few incomplete decodes enabled two things to bump data onto a bus, which would then boil down to NMOS behavior with 2 outputs pushing electrons to the input.
> Still, you don't always have to go bottom-up and reimplement NMOS physics to get the desired behaviour. Top-down approach is OK sometimes too. You know.. if it looks like a duck, walks like a duck and quacks like a duck.. ;-)

I was just responding to the comment about the undocumented opcodes 
being simply actions performed by incomplete decoding and not anything 
related to NMOS process idiosyncrasies. I agree one does not need to 
re-implement NMOS physics to achieve compliance, as groepaz notes.

Jim

-- 
Jim Brain
brain_at_jbrain.com
www.jbrain.com
Received on 2022-09-06 17:00:04

Archive generated by hypermail 2.3.0.