Don't want to be stuck using SSH or the tiny Pocket to access simH? Add a serial terminal. A vintage serial terminal to access simH is the way to go.
Here are few notes These directions work for both the Pocket CHIP or bare CHIP.
In addition to the Pocket CHIP I also have a CHIP with an HDMI "DIP" add-on board whose Debian build does not default to support a USB as serial port. For the bare CHIP I decided to set it to boot into the CLI and scan for a serial connection via USB as the io device .
First I needed to confirm the USB to serial cable driver loads when detected, and the default baud rate of the tty USB is 9600. Also I needed to activate the USB port to be ready upon boot.
To start, boot your CHIP with the USB ro serial cable attached. Put a null modem adapter between your CHIP and the terminal.
You need to know the name the machine uses for the USB "tty" port This is what the system will call your USB to Serial connection:
$ dmesg | grep tty
(look for ttyUSB0, 1, 2, etc.in the output make a note of the name used)
Do you have the driver loaded and set for your USB to Serial cable? Here is a bash script that you can use, I found one that works and named it testUSB.sh, and put it in the /dev directory.
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
devname="$(udevadm info -q name -p $syspath)"
[[ "$devname" == "bus/"* ]] && continue
eval "$(udevadm info -q property --export -p $syspath)"
[[ -z "$ID_SERIAL" ]] && continue
echo "/dev/$devname - $ID_SERIAL"
The output I got was:
/dev/ttyUSB0 - Prolific_Technology_Inc._USB-Serial_Controller
(yours may vary, depending whether you use the Prolific USB to serial able or some other.)
If you don't get a response similar to this, you need to install the driver for your cable. Before you do that reboot with the cable installed, maybe the OS will recognize it.
Assuming you have a driver loaded.....
Run a command to check the status of your USB serial port. My CHIPs both use ttyUSB0 so the command is:
$ stty -F /dev/ttyUSB0
(the output will tell you the baud rate to set the terminal on the other end, etc)
If changes are needed, such as baud rate...
$ stty -F /dev/ttyUSB0 9600
After confirming one has the driver loaded and the correct serial connection settings, check the status of the USB to serial port to see if it's actively monitoring for serial console connections inbound:
systemctl status serial-getty@ttyUSB0.service
If it's not active, turn it on!
sudo systemctl start serial-getty@ttyUSB0.service
Test. Hopefully the result is a login prompt on the serial terminal.
If you want this USB Serial console to be available on boot, make it permanent:
systemctl enable serial-getty@ttyUSB0.service