Terminal over Serial - Revision history

Barberd: /* RSDOS */

2022-12-07T15:21:28Z

RSDOS

← Older revision		Revision as of 11:21, 7 December 2022
Line 5:		Line 5:
	One will need to use terminal software. There are a variety:		One will need to use terminal software. There are a variety:

	== RSDOS ==		== DECB / RSDOS ==
	* [https://www.6809.org.uk/twilight/sock/twi-term.html Twilight Terminal] *		* [https://www.6809.org.uk/twilight/sock/twi-term.html Twilight Terminal] *
	* Netmate *		* Netmate *

Barberd: /* OS9 */

2022-12-07T15:19:02Z

OS9

← Older revision		Revision as of 11:19, 7 December 2022
Line 21:		Line 21:

	== OS9 ==		== OS9 ==
			* KBCom
	* SuperComm		* SuperComm
	* xcom9		* xcom9

Barberd: /* RSDOS */

2022-12-07T15:18:22Z

RSDOS

← Older revision		Revision as of 11:18, 7 December 2022
Line 14:		Line 14:
	* Autoterm *		* Autoterm *
	* Ultimaterm *		* Ultimaterm *
			* V-Term *
	* Others (search the [https://colorcomputerarchive.com/ Archive] for 'comm' and 'term')		* Others (search the [https://colorcomputerarchive.com/ Archive] for 'comm' and 'term')

Barberd: /* Connecting to a Linux shell over null modem */

2022-12-07T14:37:53Z

Connecting to a Linux shell over null modem

← Older revision		Revision as of 10:37, 7 December 2022
Line 36:		Line 36:
	systemctl start serial-getty@ttyUSB0.service		systemctl start serial-getty@ttyUSB0.service

	~~Look in~~ Modify ttyUSB0 to the appropriate device for the system, such as ttyS0 or ttyUSB1.		Modify ttyUSB0 in the above examples to the appropriate device for the system, such as ttyS0 or ttyUSB1.

	If using a USB connection one may instead get creative with a /etc/udev/rule.d to spawn a prompt only when connected.		If using a USB connection one may instead get creative with a /etc/udev/rule.d to spawn a prompt only when connected.

Barberd: /* TERM setting in Linux */

2022-12-07T02:43:34Z

TERM setting in Linux

← Older revision		Revision as of 22:43, 6 December 2022
Line 42:		Line 42:
	=== TERM setting in Linux ===		=== TERM setting in Linux ===

	Linux will generally default to a vt100 or similar terminal. Depending upon the terminal software used, this should be modified to something more appropriate:		The TERM setting instructs programs within Linux on how to have the terminal reposition the cursor or clear the screen. The settings are controlled through the termcap and terminfo databases. Very often, applications use the terminfo or ncurses library to abstract away the hard work of parsing the databases and performing the screen manipulation.

			Linux will generally default to a vt100 or similar terminal type for a serial connection. Depending upon the terminal software used, this should be modified to something more appropriate:

	* dumb will work with most coco terminal software, but will not allow any manipulation of cursor positioning or screen clearing, meaning software that uses the ncurses library will not work, like vi, nano, top, etc. Technically, dumb expects an 80 column display, so even this mode may give some trouble for some terminal software.		* dumb will work with most coco terminal software, but will not allow any manipulation of cursor positioning or screen clearing, meaning software that uses the ncurses library will not work, like vi, nano, top, etc. Technically, dumb expects an 80 column display, so even this mode may give some trouble for some terminal software.
Line 73:		Line 75:
	export TERM=videotex		export TERM=videotex

	The [[Deluxe RS232 Pak]] ROM doesn't ~~seem to~~ handle vt52-style control codes (locking up if it receives one!), so the following terminfo works ok. Make a new file named deluxers232.ti:		The [[Deluxe RS232 Pak]] ROM doesn't handle vt52-style control codes (locking up if it receives one!), so the following terminfo works ok. Make a new file named deluxers232.ti:
	deluxers232\|TRS-80 Color Computer Deluxe RS232 Pak,		deluxers232\|TRS-80 Color Computer Deluxe RS232 Pak,
	am,		am,

Barberd: /* Connecting to a Linux shell over null modem */

2022-12-07T02:22:51Z

Connecting to a Linux shell over null modem

← Older revision		Revision as of 22:22, 6 December 2022
Line 29:		Line 29:
	Once one has their terminal software on the CoCo working, one will need to configure agetty to listen on the Linux machine to provide a login prompt and start a shell. One can test this with:		Once one has their terminal software on the CoCo working, one will need to configure agetty to listen on the Linux machine to provide a login prompt and start a shell. One can test this with:

	sudo getty ttyUSB0		sudo setsid getty ttyUSB0

	This will provide a single session ~~and doesn't allow direct~~ ioctl() calls ~~(so some things like ctrl-C and ssh password prompts don~~'t work~~) but is good for testing~~. Once ~~its~~ working, configure it to run getty ~~directly by~~ initd or the system daemon. This will vary by distribution but most modern distributions will normally support something like:		This will provide only a single session but is good for testing. Make sure to included setsid otherwise certain ioctl() calls won't work. Once working, configure your system to run getty through initd or the system daemon. This will vary by distribution but most modern distributions will normally support something like:
	systemctl enable serial-getty@ttyUSB0.service		systemctl enable serial-getty@ttyUSB0.service
	followed by		followed by
	systemctl start serial-getty@ttyUSB0.service		systemctl start serial-getty@ttyUSB0.service

	Modify ttyUSB0 to the appropriate device for the system, such as ttyS0 or ttyUSB1.		Look in Modify ttyUSB0 to the appropriate device for the system, such as ttyS0 or ttyUSB1.

			If using a USB connection one may instead get creative with a /etc/udev/rule.d to spawn a prompt only when connected.

	=== TERM setting in Linux ===		=== TERM setting in Linux ===

Barberd: /* Connecting to a Linux shell over null modem */

2022-12-07T02:03:24Z

Connecting to a Linux shell over null modem

← Older revision		Revision as of 22:03, 6 December 2022
Line 31:		Line 31:
	sudo getty ttyUSB0		sudo getty ttyUSB0

	This will provide a single session and doesn't ~~pass~~ some ~~control codes~~ but is good for testing. Once its working, configure it to run getty directly by initd or the system daemon. This will vary by distribution but most modern distributions will normally support something like:		This will provide a single session and doesn't allow direct ioctl() calls (so some things like ctrl-C and ssh password prompts don't work) but is good for testing. Once its working, configure it to run getty directly by initd or the system daemon. This will vary by distribution but most modern distributions will normally support something like:
	systemctl enable serial-getty@ttyUSB0.service		systemctl enable serial-getty@ttyUSB0.service
	followed by		followed by

Barberd: /* Advanced termcap/terminfo */

2022-12-06T20:59:51Z

Advanced termcap/terminfo

← Older revision		Revision as of 16:59, 6 December 2022
Line 55:		Line 55:

	Many early terminal software packages implement a subset of the vt52 terminal:		Many early terminal software packages implement a subset of the vt52 terminal:
	* Videotex had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual]. The [[Direct Connect Modem Pak]] ROM seems to be compatible with these codes as well~~. The [[Deluxe RS232 Pak]] ROM is NOT compatible; it locks up with any escape signal~~.		* Videotex had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual]. The [[Direct Connect Modem Pak]] ROM seems to be compatible with these codes as well.
	* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]		* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]

Line 71:		Line 71:
	export TERM=videotex		export TERM=videotex

	The [[Deluxe RS232 Pak]] ROM doesn't seem to handle vt52-style control codes, so the following terminfo works ok. Make a new file named deluxers232.ti:		The [[Deluxe RS232 Pak]] ROM doesn't seem to handle vt52-style control codes (locking up if it receives one!), so the following terminfo works ok. Make a new file named deluxers232.ti:
	deluxers232\|TRS-80 Color Computer Deluxe RS232 Pak,		deluxers232\|TRS-80 Color Computer Deluxe RS232 Pak,
	am,		am,

Barberd: /* Advanced termcap/terminfo */

2022-12-06T20:59:15Z

Advanced termcap/terminfo

← Older revision		Revision as of 16:59, 6 December 2022
Line 55:		Line 55:

	Many early terminal software packages implement a subset of the vt52 terminal:		Many early terminal software packages implement a subset of the vt52 terminal:
	* Videotex had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual]. The [[Direct Connect Modem Pak]] seems to be compatible with these codes as well. The [[Deluxe RS232 Pak]] is ~~mostly~~ compatible~~, but seems to lock~~ up ~~upon getting the Esc-Y~~ signal.		* Videotex had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual]. The [[Direct Connect Modem Pak]] ROM seems to be compatible with these codes as well. The [[Deluxe RS232 Pak]] ROM is NOT compatible; it locks up with any escape signal.
	* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]		* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]

Line 70:		Line 70:
	This will create a new file in ~/.terminfo/v/videotext. To use this entry, use		This will create a new file in ~/.terminfo/v/videotext. To use this entry, use
	export TERM=videotex		export TERM=videotex

			The [[Deluxe RS232 Pak]] ROM doesn't seem to handle vt52-style control codes, so the following terminfo works ok. Make a new file named deluxers232.ti:
			deluxers232\|TRS-80 Color Computer Deluxe RS232 Pak,
			am,
			cols#32, lines#16,
			bel=^G, cr=\r, cud1=\n, ind=\n,
			kbs=^H, clear=^L, kcuu1=\032, cub1=^H,
			Then run
			tic deluxers232.ti
			to create ~/.terminfo/d/deluxers232 and use it by entering
			export TERM=deluxers232
			This won't allow for any ncurses-based applications, but will at least have some idea of the screen size and allow for backspace.

	=== File transfers in Linux ===		=== File transfers in Linux ===

Barberd: /* Advanced termcap/terminfo */

2022-12-06T17:48:06Z

Advanced termcap/terminfo

← Older revision		Revision as of 13:48, 6 December 2022
Line 54:		Line 54:
	If one of the default termcap entries aren't working for one's chosen terminal software, one will need to find the control codes for their terminal software of choice and build an appropriate entry. This may require looking through the terminal software's documentation or contacting the creator. Use 'infocmp' to dump an existing termcap file and 'tic' to compile a new one. 'man terminfo' to get a list of the fields and their syntax.		If one of the default termcap entries aren't working for one's chosen terminal software, one will need to find the control codes for their terminal software of choice and build an appropriate entry. This may require looking through the terminal software's documentation or contacting the creator. Use 'infocmp' to dump an existing termcap file and 'tic' to compile a new one. 'man terminfo' to get a list of the fields and their syntax.

	~~Both of these seem to~~ implement a subset of vt52~~; that could be a good starting point~~:		Many early terminal software packages implement a subset of the vt52 terminal:
	* Videotex ~~and its descendants (Deluxe RS232 Pak and Direct Connect Modem Pak)~~ had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual].		* Videotex had many control codes available; see page 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/Videotex%20%28Tandy%29.pdf Videotex manual]. The [[Direct Connect Modem Pak]] seems to be compatible with these codes as well. The [[Deluxe RS232 Pak]] is mostly compatible, but seems to lock up upon getting the Esc-Y signal.
	* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]		* Similarly, Vidtex (Compuserv's software) also had many control codes available; see page 44/Chapter 7 of the [https://colorcomputerarchive.com/repo/Documents/Manuals/Applications/VIDTEX%20%28CompuServe%29.pdf Vidtex manual]

			For these, create a file like this, named videotex.ti:
			videotex\|TRS-80 Videotex terminal program,
			am,
			cols#32, lines#16,
			bel=^G, clear=\EH\Ej, cub1=\ED, cud1=\EB, cuf1=\EC,
			cup=\EY%p1%' '%+%c%p2%' '%+%c, cuu1=\EA, ed=\EJ, el=\EK,
			home=\EH, kbs=^H, kcuu1=\^,

			Then compile this by running
			tic videotex.ti
			This will create a new file in ~/.terminfo/v/videotext. To use this entry, use
			export TERM=videotex

	=== File transfers in Linux ===		=== File transfers in Linux ===