You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 3How do we know the ‘green’ NOPs are by design? Is there a design document confirming them as such?user3840170– user38401702022-09-28 19:17:36 +00:00Commented Sep 28, 2022 at 19:17
- @user3840170 Well, is there one that tells otherwise? Beside, looking at the decode ROM does show that there are default entries that let them terminate that way - as usual, code is documentation :))=Raffzahn– Raffzahn2022-09-28 19:23:03 +00:00Commented Sep 28, 2022 at 19:23
- 1Opcodes of the form xxx0 mm01, including 1000 1001, all behave identically prior to the cleanup cycle, save for the fact that 1000 mm01 turns the last post-decode read, if any are done into a write with the accumulator on the bus. Instructions of the form xxx0 1001, including 1000 1001, all advance the program counter during the operand fetch, and then proceed to the cleanup/start next operation state without doing any post-decode reads, leaving the value that was fetched during the cycle after the opcode fetch in the temporary register.supercat– supercat2022-09-28 20:41:31 +00:00Commented Sep 28, 2022 at 20:41
- 1@Raffzahn, it might improve your answer to include a relevant snippet from the microcode, showing STA immediate being "dummied out".wizzwizz4– wizzwizz4 ♦2022-09-29 11:40:38 +00:00Commented Sep 29, 2022 at 11:40
- I suspect the change in how the 65C02 handles undefined opcodes was motivated by the fact that it's CMOS. In NMOS, if something will pull down a signal in all cases where it needs to be low, and nothing will pull it down in cases where it needs to be high, one can ignore cases where the value doesn't matter. In CMOS, one must identify all cases where nothing will pull down a signal and ensure that it gets pulled up in those cases, even it would have been acceptable for the signal to be pulled down instead.supercat– supercat2023-11-05 18:04:11 +00:00Commented Nov 5, 2023 at 18:04
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ms-dos), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you