Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of documentation topics needed for 65C816 support #156

Open
mooinglemur opened this issue Mar 3, 2024 · 2 comments
Open

List of documentation topics needed for 65C816 support #156

mooinglemur opened this issue Mar 3, 2024 · 2 comments
Labels
65C816 Issue specific to 65C816 support

Comments

@mooinglemur
Copy link
Contributor

mooinglemur commented Mar 3, 2024

  • new extapi16 call - must call in native mode, emx=0
  • new extapi call (not specific to 65C816 support but first implemented in the branch)
  • 65C816 opcode documentation
  • X16 platform-specific considerations
    • Intro - what parts of the 65C816 processor are used and which are not used
    • How to incorporate 65C816 code in your user programs
      • How to call the CBM API in such code
      • How to relocate the stack
    • How to write 65C816 native interrupt handlers
@mooinglemur mooinglemur added the 65C816 Issue specific to 65C816 support label Mar 3, 2024
@tomxp411
Copy link
Contributor

tomxp411 commented Mar 3, 2024

I can start by tackling the opcode list. I will do it the same way I did the 65C02 opcodes with the CSV generated list.

@tomxp411
Copy link
Contributor

tomxp411 commented Mar 6, 2024

I'm working on the 65C816 opcodes sheet now. I'd like to make this Appendix D and push down the "official expansion cards" appendix.

Where should we put the X16 platform-specific considerations stuff? In the same appendix, or should we maybe make that Appendix D and the opcode reference Appendix E?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
65C816 Issue specific to 65C816 support
Projects
None yet
Development

No branches or pull requests

2 participants