/dev/
, those are cu.usbserial
and tty.usbserial
.getty
session attached to the terminal, since apparently you can't just either edit /etc/ttys
or run getty
by hand in modern OSXes.XON/XOFF
)getty
whether in a file or by hand were of the form /usr/libexec/getty std.19200 cu.usbserial
getty
by hand: No output. (Seems to validate the guide)/etc/ttys
: No output. (Again, validates the guide)/Library/LaunchDaemons
named console.plist
with the following content:getty
command and the terminal (from 9600 to 19200): No output.tty.usbserial
device rather than the cu.usbserial
device in combination with the above: No output.getty
running under launchd
with the above plistVT100
UTHx
appear, and then the Password prompt on the same line./bin/sh
.reset
command to clear the display to known-good settings. Typing reset and hitting return gives me a clean error 'Unknown terminal type: su (-1)'. With a prompt for Terminal type?
. getty
configured as described, and it Just Worked®, with no noise or garbage on the screen.getty
is causing issues with this terminal.screen
, pointed at the serial port like so:ls
results in garbled output. screen
, even if i do an export term='vt100'
- this means that most full screen terminal apps like vim
and mutt
drop a lot of control codes that the terminal can't handle, usually hanging it to the point a reset is necessary to gain input again./etc/ttys
, since this file is ignored in modern versions of OS X. This would be the way to go on Linux/BSD, but not here.std.19200
that's provided in /etc/gettytab
left the terminal set to su
for some reason, and nothing worked.vt220
. This will become important later.getty
, since that's restricted to launchd
. We have to make and load a daemon plist./Library/LaunchDaemons
, I added a serialconsole.plist
with the following contents:/etc/gettytab
. Also note the setting of KeepAlive
to true
- this means that when the process exits (say, we log out), a new instance will spawn. Without this, you have to manually start the job.DISP
menu, I set:gettytab
and the plist file you created.en_US.ISO-8859-1
. Have a look at the output of locale
, and work the command export LC_ALL='en_US.ISO-8859-1'
into a login script that checks your $TERM
variable. You really don't want to set this system wide, but only on sessions where your glass terminal is being used.terminal
.ls /dev/cu.usbserial-*
Note: If your device is not in the list, verify that your board is powered on and connected to your system. Select the appropriate link below:
|
screen /dev/xx.usbserial-XXXXXXXX 115200 –L
/dev/xx.usbserial-XXXXXXXX
is replaced by your device unique name. Using the example above, the command would be:screen -L /dev/cu.usbserial-A402YSYU 115200 –L
Note: Adding –L to the command, as shown above, turns on output logging so you can see the results of your commands. To end a session in Screen type Ctrl + A and then Ctrl + K to kill the session. You will be prompted to end the session. |
root
and press Enter.