By the way Willard, where did you find the info for SNDCOM and SD232C? Can you point me to romfuncs-600.pdf and m100_unpublished.asm? Sounds like they would be good items to have in my archives. I'd love to match things up with what I have for the NEC machines.
In looking at my own documented disassemblies and matching up my NEC memory mapped locations against what I'm seeing in my disassembly for the M100, I'd be guessing that 6E32 is the start of SD232C on a Model 100 but I'd like to see the "official unofficial" docs that you have. On Sun, Aug 13, 2017 at 7:40 PM, John R. Hogerhuis <[email protected]> wrote: > Hmm. Maybe it does, I'd have to look. But I've also written code that just > uses the out instruction. > > But pushing a dummy value on the stack is weird. If I used that I wouldn't > be surprised if there's a bug in Hterm because that doesn't sound > familiar. > > Anyway I just mentioned it because that push b seems like a sharp edge to > file down. > > Plus it raised the question in my mind of why the undocumented entry point > sd232c. Someone wanted it for something. But if it goes around flow control > I can't imagine what it is for. > > -- John. > > > > On Sun, Aug 13, 2017 at 4:04 PM Willard Goosey <[email protected]> wrote: > >> On Sun, 13 Aug 2017 22:41:19 +0000 >> "John R. Hogerhuis" <[email protected]> wrote: >> >> > Why not just do an OUT instruction. I don't remember it taking any >> > more than that (once the port is opened). >> > >> That's not what my projects (m100.def and m100smallclib) are really >> about. They're about documenting/using the ROM interface. If people >> want to party on the bare metal they can. >> >> Me? I'm enough of a CS guy to be willing to abstract away crusty old >> support chips. ;-) >> >> Also last time I looked hterm uses SD232C so why you giving me >> grief? ;-) >> >> Willard >> > -- Gary Weber [email protected]
