Replies: 1 comment
-
I'm slowly copying/pasting some of the glitchworks monitor.asm code into my code. My first experiment will be to copy the code needed to display memory to the terminal. This will also require all the supporting code to get a command from the terminal parse it, etc, etc, etc. I've noticed that their code doesn't use interrupts from the 8251 to fetch entered keystrokes, but just sits there in a tight loop. I chose not to do that because I kind of want to make mine work like a mulit-tasking process. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
``; Download a record in INTEL hex format
DLINT: CALL GETBYT ; Get length
ANA A ; End of file?
JZ DLEOF ; Yes, handle it
MOV C,A ; Begin Checksum
MOV B,A ; Record length
CALL GETBYT ; Get HIGH address
MOV H,A ; Set HIGH address
ADD C ; Include in checksum
MOV C,A ; Re-save
CALL GETBYT ; Get LOW address
MOV L,A ; Set LOW address
ADD C ; Include in checksum
MOV C,A ; Re-save
CALL SETOFF ; Handle record offsets
CALL GETBYT ; Get type byte
ADD C ; Include in checksum
MOV C,A ; Re-save
DLINT1: CALL GETBYT ; Get data byte
MOV M,A ; Save in memory
INX H ; Advance to next
ADD C ; Include in checksum
MOV C,A ; Resave checksum
DCR B ; Reduce count
JNZ DLINT1 ; Do entire record
CALL GETBYT ; Get record checksum
ADD C ; Add to computed checksum
ANA A ; Clear carry, set Z
RET
Beta Was this translation helpful? Give feedback.
All reactions