As part of further testing of my simulator on STM32, I compiled from the source code SuperMon 816. The program starts and does not suspend, unfortunately some functions, e.g. A or M, do not work correctly.
So I decided to start the Supermon under the control of the Kowalski simulator and it turns out that the same deserves exactly the same bad results. What can the reason be?
The changes I made are added at the end of the source file, in addition I exchanged WAI orders to NOP, and set the vectors.
As part of further testing of my simulator on STM32, I compiled from the source code SuperMon 816. The program starts and does not suspend, unfortunately some functions, e.g. A or M, do not work correctly.
So I decided to start the Supermon under the control of the Kowalski simulator and it turns out that the same deserves exactly the same bad results. What can the reason be?
The changes I made are added at the end of the source file, in addition I exchanged WAI orders to NOP, and set the vectors.
I’d expect with the stack pointer (SP) set to $FFFF you would experience problems ($FFFF is the default in the source code—you evidently didn’t edit that). Try lowering SP to somewhere outside of the 65C816 hardware vector space and see what happens—setting SP to $CFFF is a good start. Note that the software is designed to run on actual 65C816-powered hardware. Supermon 816 has not been tested in a simulated environment.
The version of Supermon816 you are using assumes that your console understands a subset of the VT100/ANSI/ECM48 display control sequences. If you read through the source code (which you “assembled,” not “compiled”—those words mean two different things), you will see where the VT100-style control sequences are defined. They will produce bizarre effects on your display if it doesn’t implement a VT100-style console.
Included with the Supermon 816 source code posted at my website is a PDF that goes into some detail on adapting the software to different systems, as well as describing the software’s usage. If you haven’t read that PDF, you should.
Thank you for the link to the page. In the meantime, I found a solution to the malfunction. I downloaded the source file from some github specifically for Kowalski Simulator and found an error in proc. getbyte. I see that the error is already corrected in the source file on your page ( 2023/08/14 A) Corrected an inadvertent coding error in the GETBYTE sub-
; routine )
I am attaching the file that works for Kowalski Simulator
I am attaching the file that works for Kowalski Simulator
You should be able to assemble the latest version (V1.1.3) to run in the simulator. It has some minor edits that improve performance in a few areas. I didn’t document the edits, since they don’t affect function.
