the call to 5030 includes a full stack push and then the RST 7 hook, then on to 503C.
So, either works. Depends if you want to bypass the RST 7 hook. If there was some display modifying thing, like DVI, in use then you'd need the RST 7 hook included. If the use case is pure T200, with the LCD only, then.. 503C is sufficient. the below snip is from my XLS disassembly, but this is also viewable using VirtualT and the disassembler function. Steve 5030H (E5H) PUSH H 5031H (D5H) PUSH D 5032H (C5H) PUSH B 5033H (F5H) PUSH PSW 5034H (FFH) RST 7 ; Jump to RST 38H Vector entry of following byte 5035H DB 08H 5036H (CDH) CALL 503CH 5039H (C3H) JMP 1604H ; Pop AF, BC, DE, HL from stack On Sat, Feb 12, 2022 at 2:26 PM Willard Goosey <[email protected]> wrote: > sorry its been a rough week will look at this tomorrow... > > thank you for this > willard > > > > Sent from my Galaxy Tab® A > > -------- Original message -------- > From: B 9 <[email protected]> > Date: 2/8/22 4:31 PM (GMT-07:00) > To: [email protected] > Subject: Re: [M100] t200 addresses? from hterm.git > > On Sun, Jan 23, 2022 at 4:47 PM Stephen Adolph <[email protected]> > wrote: > > >> Also, sometimes both entries can be valid. Depends on the use case. >> > > That may be right. Both call 20540, asc("@") and 20528 print "@" to the > screen, so I could see the reasoning for calling both 503CH and 5030H as > LCDPUT. However, the techref only lists 503CH and there's the question of > what do those extra 12 bytes of instructions do? I PEEKed and they're not > NOPs. So, what is the use case for calling 5030H instead? > > —b9 > > P.S. For anyone who can understand 8085 machine code, the extra bytes are: > 229, 213, 197, 245, 255, 8, 205, 60, 80, 195, 4, 22. >
