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

ET-3400 Memory Map boundaries aren't provided #13

Open
ricknun opened this issue Jun 12, 2019 · 0 comments
Open

ET-3400 Memory Map boundaries aren't provided #13

ricknun opened this issue Jun 12, 2019 · 0 comments

Comments

@ricknun
Copy link

ricknun commented Jun 12, 2019

The Memory and Disassembly panels show ROM and RAM (hardware boundaries) but not all boundaries given on page 87 of the ET-3400 manual: Monitor ROM, Not Usable, Displays, Not Usable, Keyboard, Not Useable, Optional 256 bytes User RAM, 59 bytes monitor RAM, 197 bytes user RAM. A thought: Make the Memory and Disassembly fields address only (remove ROM, RAM and the entire choice selection) and instead load a default Memory Map file that includes all the ET-3400 boundaries mentioned. (I would order them from low numbered address to high, instead of as shown on page 87.) The Disassembly panel then clearly shows how close user program/data is getting to important device boundaries. Consider adding another tab, resulting in Breakpoints, Device Map, and User Map. The Device Map would be the ET-3400 (or ETA-3400?) boundaries. The User Map would be the auto-loaded same-name map functionality done already.

Added after submission: Warnings or red highlighting could be given if user program/data ever appeared in the wrong place, like the Not Usable or ROM areas.

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

1 participant