Roger ? I don¹t think so. I¹m using 3-wire as well with RTS/CTS jumpered per the build instructions. I have attached three files for the loopback program I¹m using (hopefully they get posted). It¹s a bit of a hack-job, clipping pieces of code from different places plus what¹s on S100-Computers. I¹m actually surprised it worked the first time. The SCC is running at 19200 baud and my console at 9600. The setup is the S100 Z80 board, a CompuPro 64k board (with certain memory ranges disabled), a Solid State Music IO4 (UAR/T based console board I use for everything) and the S100-SCC. The board passes the loopback so I know it¹s not the board ? it has to be a configuration setting in the ROM preventing input from being processed by the code. Rich -- Rich Cini Collector of Classic Computers Build Master and lead engineer, Altair32 Emulator http://www.classiccmp.org/cini http://www.classiccmp.org/altair32 On 11/8/14, 12:36 AM, "norwestrzh via N8VEM-S100" <n8vem...@googlegroups.com> wrote: >Hi Rich -- > >>> .... configuration also exhibits ³input anomalies². In this case, I >see only output ? no input. I can definitely ³see² characters coming >>> through the interface (using my protocol analyzer), but nothing on >the screen. > >I'm having the same problem. I can spew output from the serial card to >an RS232 device, but cannot get any input back from the RS232 device. >My board also "passes" the loopback test. I was assuming that there is >something about the RS232 "control" signals on the interface that I'm >not doing correctly, but so far I've not found out what that is. I'm >just trying to use a "simple" 3-wire connection (that works for so many >other UARTS -- Z80 DART, Z80 SIO, 8251, etc. etc.). Is there something >strange about the SCC? > >Roger > > >-- >You received this message because you are subscribed to the Google Groups >"N8VEM-S100" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to n8vem-s100+...@googlegroups.com. >For more options, visit https://groups.google.com/d/optout.
Attachment:
sccloop.ASM
Description: Binary data
Attachment:
sccloop.hex
Description: Binary data
Attachment:
sccloop.lst
Description: Binary data