Nils M Holm
2023-10-28 16:43:26 UTC
I recently bought an SC114 SBC (RC2014), which is a great little
computer and fits my needs perfectly, mostly testing the T3X backend
for the Z80 a real CP/M system. Thanks to Derek, whom I have seen
posting here, for selling me a completely assembled kit.
There is one thing that gives me some headache, though. I cannot seem
to get serial communication, especially the on-board port, to work
properly.
My SC114 has a SC139 68B50 ACIA in addition to the on-board port
and a CF adapter from which it runs CP/M. The ACIA is connected via
the adapter that came with the computer and the on-board port is
hooked up with a three-wire connection. Both use FTDI adapters of
the kind that came with the SC114.
I can connect to the SCM console on the SC114 using either port,
both work fine. CP/M seems to want the ACIA as its console, which
is also OK. As soon as I try to do other things with the serial
ports, things get a bit weird, though. I am sure I am missing
something here, so maybe someone can help.
(1) I cannot get xmodem uploads to work with cu and lrzsz.
The machine I use for connecting to CP/M is a FreeBSD machine, so
I use "cu -l cuaU0 -115200" to connect. So far so good. When I start
an xmodem session using "~C sx -q file" and "xmodem file /r /x0 /q" on
CP/M, I get a NAK on every sector. I have set up the port for 8N1
and rts/cts. Now here are the weird things:
- The same sx command works for uploading files to my NC100, which
also needs hardware flow control.
- The same sx command works on the SC114 when using minicom instead
of cu.
However, I really prefer cu, because it is basically a command line
tool, so if anybody has an idea about what is going wrong, I would
be most grateful.
(2) The other thing: as far as I understand it, CP/M should provide
the on-board serial port as the TTY: device. STAT DEV: shows
CON: is CRT:
RDR: is TTY:
PUN: is TTY:
LST: is TTY:
Ok, so the first thing I tried is to connect another cu to the cuaU1,
which is connected to the on-board port (cu -l cuaU1 -9600), and run
PIP PUN:=CON:
which, if I remember correctly. should echo console input on the
serial port. I does echo input on the console, though, and nothing
appears on the other port.
Next thing I tried was STAT CON:=TTY:. Ok, now CON: is assigned to
TTY:, but the console is still connected to the same port. Looks like
CRT: and TTY: are really both the ACIA port. Can someone confirm? If
so, can this be changed?
Xmodem transfers on PUN: and RDR: simply time out, which would make
sense, because there is no connection to the on-board port.
This is how far I got. Any help would be much appreciated!
Nils
computer and fits my needs perfectly, mostly testing the T3X backend
for the Z80 a real CP/M system. Thanks to Derek, whom I have seen
posting here, for selling me a completely assembled kit.
There is one thing that gives me some headache, though. I cannot seem
to get serial communication, especially the on-board port, to work
properly.
My SC114 has a SC139 68B50 ACIA in addition to the on-board port
and a CF adapter from which it runs CP/M. The ACIA is connected via
the adapter that came with the computer and the on-board port is
hooked up with a three-wire connection. Both use FTDI adapters of
the kind that came with the SC114.
I can connect to the SCM console on the SC114 using either port,
both work fine. CP/M seems to want the ACIA as its console, which
is also OK. As soon as I try to do other things with the serial
ports, things get a bit weird, though. I am sure I am missing
something here, so maybe someone can help.
(1) I cannot get xmodem uploads to work with cu and lrzsz.
The machine I use for connecting to CP/M is a FreeBSD machine, so
I use "cu -l cuaU0 -115200" to connect. So far so good. When I start
an xmodem session using "~C sx -q file" and "xmodem file /r /x0 /q" on
CP/M, I get a NAK on every sector. I have set up the port for 8N1
and rts/cts. Now here are the weird things:
- The same sx command works for uploading files to my NC100, which
also needs hardware flow control.
- The same sx command works on the SC114 when using minicom instead
of cu.
However, I really prefer cu, because it is basically a command line
tool, so if anybody has an idea about what is going wrong, I would
be most grateful.
(2) The other thing: as far as I understand it, CP/M should provide
the on-board serial port as the TTY: device. STAT DEV: shows
CON: is CRT:
RDR: is TTY:
PUN: is TTY:
LST: is TTY:
Ok, so the first thing I tried is to connect another cu to the cuaU1,
which is connected to the on-board port (cu -l cuaU1 -9600), and run
PIP PUN:=CON:
which, if I remember correctly. should echo console input on the
serial port. I does echo input on the console, though, and nothing
appears on the other port.
Next thing I tried was STAT CON:=TTY:. Ok, now CON: is assigned to
TTY:, but the console is still connected to the same port. Looks like
CRT: and TTY: are really both the ACIA port. Can someone confirm? If
so, can this be changed?
Xmodem transfers on PUN: and RDR: simply time out, which would make
sense, because there is no connection to the on-board port.
This is how far I got. Any help would be much appreciated!
Nils
--
Nils M Holm < n m h @ t 3 x . o r g > http://t3x.org
Nils M Holm < n m h @ t 3 x . o r g > http://t3x.org