You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: