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

Memory address typo in CHIP-8 Technical Reference #9

Open
tysonliddell opened this issue Mar 30, 2023 · 2 comments
Open

Memory address typo in CHIP-8 Technical Reference #9

tysonliddell opened this issue Mar 30, 2023 · 2 comments

Comments

@tysonliddell
Copy link

Hi @mattmikolay,

Thanks for the awesome CHIP-8 resources. I'm writing my first emulator now using your wiki and its links as a reference and I think I have come across a typo. On a system with 4096 bytes of memory, if the final 352 bytes are reserved (and the first 0x200), then addresses 0x200 to 0xE9F should be free for a CHIP-8 program. However the CHIP-8 Technical Reference says otherwise. This is the change that I think is needed:

- On VIPs with 4096 bytes of RAM (and modern implementations), this leaves addresses 0x200 to 0xE8F free. 
+ On VIPs with 4096 bytes of RAM (and modern implementations), this leaves addresses 0x200 to 0xE9F free. 
@tysonliddell
Copy link
Author

Interestingly, I found the following in the RCA COSMAC VIC CDP18S711 Instruction Manual:

After the above practice you are ready to design more sophisticated CHIP-8 programs. Always prepare a flowchart before actually writing a program. The last 352 bytes of on-card RAM are used for variables and display refresh. In a 2048-byte RAM system you can use locations 0200-069F for your programs. This area is enough for 592 CHIP-8 instructions (1184 bytes). In a 4096-byte RAM system you can use locations 0200-0E8F. This area is equal to 1608-CHIP-8 instructions (3216 bytes).

I wonder if this was the source of the typo, or if there's something else I'm not getting.

tobiasvl added a commit to chip-8/extensions that referenced this issue Feb 27, 2024
@pyrsmk
Copy link

pyrsmk commented Feb 27, 2024

I deleted my last comment because it was erroneous. Anyway, stumbled upon the same typo ;)

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

No branches or pull requests

2 participants