...
The following table shows the device and configuration paths used for the two serial lines:
Charon-PAR 64-bit models | Charon-PAR 32-bit model 720 | Charon-PAR 32-bit model B132L | |||
---|---|---|---|---|---|
Serial line | Config. path | Serial line | Config. path | Serial line | Config. path |
1 = Console | serial.uart0.device | 1 = Console | asp.uart0.device | 1 = Console | gsc.lasi.uart.device |
2 | serial.uart2.device | 2 | asp.uart1.device | 2 | gsc.wax.uart.device |
Div | ||
---|---|---|
| ||
Serial port configuration options are specified using the following syntax:
...
The configuration file templates contain the following default configurations:
Line | Charon-PAR/PA3 | Charon-PAR/PA9 |
---|---|---|
Emulated serial console on port 30000 using the telnet protocol. PuTTY started automatically with preconfigured profile. | ||
1 | serial.uart0.device.type="telnet" serial.uart0.device.port=":30000" serial.uart0.device.command="putty -load PAR-Telnet" | PA9-64
PA9-32 (model 720)
PA9-32 (model B132L)
|
Emulated second serial line in raw mode on port 30002. | ||
2 | serial.uart2.device.type="socket" serial.uart2.device.port=":30002" | PA9-64
PA9-32 (model 720)
PA9-32 (model B132L)
|
...
class | pagebreak |
---|
HP-UX Interactive Login Activation
To enable interactive login on a non-console serial line in HP-UX, a GETTY process has to be started for the terminal line.
In versions before 11.31, you can add an additional terminal via SAM (Peripheral Devices > Terminals and Modems > Actions > Add Terminal). This will also add the necessary entries in to /etc/inittab.
You can also (as the root user) edit /etc/inittab to add the configuration manually or to modify an existing configuration.
To identify available serial lines, you can use the ioscan command:
# ioscan -fn -C tty
Class I H/W Path Driver S/W State H/W Type Description
...
Please note:
By default, pressing Ctrl+C in the Charon-PAR console is passed to the emulator's child processes and kills the PuTTY console process. If this is not desired, you can modify the command line to include the setsid command to start the telnet command in a new session.
For example: serial.uart0.device.command="setsid putty -telnet -P 30000 localhost"
Div | ||
---|---|---|
| ||
HP-UX Interactive Login Activation
To enable interactive login on a non-console serial line in HP-UX, a GETTY process has to be started for the terminal line.
In versions before 11.31, you can add an additional terminal via SAM (Peripheral Devices > Terminals and Modems > Actions > Add Terminal). This will also add the necessary entries in to /etc/inittab.
You can also (as the root user) edit /etc/inittab to add the configuration manually or to modify an existing configuration.
To identify available serial lines, you can use the ioscan command:
# ioscan -fn -C tty
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
...
Please note: Line-editing is very limited. To delete a character on the command-line, use CTRL+BACKSPACE. Note that the deleted character will still be visible until it is overwritten. Block-mode applications are not supported.
Using PuTTY
The PuTTY terminal emulator is the preferred method to use as the Charon-PAR/PA3 console. It does not, however, support the terminal escape sequences used by the legacy hardware, so any inverse or highlighted text codes will be ignored, and block mode applications cannot be run. Using PuTTY in telnet mode (as supplied) allows use of the Break key. PuTTY supports copy and paste. To copy text to the clipboard, just select it with the left mouse button (this automatically copies the selection to the clipboard). To paste the clipboard into a PuTTY window, use Shift-Ins . Unfortunately, PuTTY cannot be used to reliably paste large blocks of text (even with MPE type-ahead enabled), as data overruns can easily occur.
By default, the emulator configuration is set up to start PuTTY on the console port with a command similar to the following example:
serial.uart0.device.command="putty -load PAR-Telnet"
(default port 30000).
To start an terminal emulator manually, perform the following steps:
...
will still be visible until it is overwritten. Block-mode applications are not supported.
Using PuTTY
The PuTTY terminal emulator is the preferred method to use as the Charon-PAR/PA3 console. It does not, however, support the terminal escape sequences used by the legacy hardware, so any inverse or highlighted text codes will be ignored, and block mode applications cannot be run. Using PuTTY in telnet mode (as supplied) allows use of the Break key. PuTTY supports copy and paste. To copy text to the clipboard, just select it with the left mouse button (this automatically copies the selection to the clipboard). To paste the clipboard into a PuTTY window, use Shift-Ins . Unfortunately, PuTTY cannot be used to reliably paste large blocks of text (even with MPE type-ahead enabled), as data overruns can easily occur.
By default, the emulator configuration is set up to start PuTTY on the console port with a command similar to the following example:
serial.uart0.device.command="putty -load PAR-Telnet"
(default port 30000).
To start an terminal emulator manually, perform the following steps:
Step | Command / Action | ||
---|---|---|---|
1 | Make sure the preconfigured PuTTY profiles are in the directory .putty/sessions or .config/putty/sessions in your home directory. | (see Post-Installation Tasks in Charon-PAR Software Installation) | |
2 | Start PuTTY from the command-line. |
| |
3 | Should you get an error that a font was not found, change the font. | Start PuTTY from the command-line.
| |
4 | To connect from a remote host, change localhost in the template to the correct hostname or IP address. | Start PuTTY from the command-line. |
| -load PAR-Telnet
3 | Should you get an error that a font was not found, change the font. | Start PuTTY from the command-line.
| |
4 | To connect from a remote host, change localhost in the template to the correct hostname or IP address. | Start PuTTY from the command-line.
|
...
class | pagebreak |
---|
The image below shows a PuTTY terminal window connected to the guest MPE/iX system console:
Please note: Line-editing is very limited. To delete a character on the command-line, use BACKSPACE. Note that the deleted character will still be visible until it is overwritten. Block-mode applications are not supported.
...
class | pagebreak |
---|
Using xhpterm
The xhpterm terminal emulation (an X Windows version of freevt3k ) does not support many terminal escape sequences used by historic PA-RISC hardware for MPE/iX, but it can be used to run block-mode applications. It must be used on a serial line set up for raw mode.
Sample command (run on Charon host): /opt/charon/bin/xhpterm -port 30002 -clean -font 10x20
The following image shows an xhpterm window connected to the second serial line of an emulated MPE/iX system (running NMMGR):
...
class | pagebreak |
---|
Working without Block-Mode Enter key
If working without a block-mode Enter key, you can navigate using the function keys of your keyboard. They correspond to the selection fields at the bottom of the screen.
For example, in the above window,
- F1 would correspond to Open Config,
- F8 would correspond to Exit Program.
Mapping the Block-Mode Enter key
The primary purpose for including this terminal emulator is to allow block-mode applications (like NMMGR ) to be run from the Linux desktop. xhpterm uses the numeric keypad Enter key to simulate block-mode Enter. If your keyboard does not have a numeric key pad, the Enter key can be mapped to another key or key combination using xmodmap on Linux.
Example mapping the numeric key pad Enter key to Right-Ctrl:
Step | Command | |
---|---|---|
1 | Determine the key code of the Right-Ctrl key. |
You will receive an output similar to:
|
2 | Redefine the key code to the numeric keypad Enter key. | $ xmodmap -e "keycode 105 = KP_Enter" |
3 | If original key mapping is required, reverse step 2. | $ xmodmap -e "keycode 105 =
|
Div | ||
---|---|---|
| ||
The image below shows a PuTTY terminal window connected to the guest MPE/iX system console:
Please note: Line-editing is very limited. To delete a character on the command-line, use BACKSPACE. Note that the deleted character will still be visible until it is overwritten. Block-mode applications are not supported.
Div | ||
---|---|---|
| ||
Using xhpterm
The xhpterm terminal emulation (an X Windows version of freevt3k ) does not support many terminal escape sequences used by historic PA-RISC hardware for MPE/iX, but it can be used to run block-mode applications. It must be used on a serial line set up for raw mode.
Sample command (run on Charon host): /opt/charon/bin/xhpterm -port 30002 -clean -font 10x20
The following image shows an xhpterm window connected to the second serial line of an emulated MPE/iX system (running NMMGR):
Div | ||
---|---|---|
| ||
Working without Block-Mode Enter key
If working without a block-mode Enter key, you can navigate using the function keys of your keyboard. They correspond to the selection fields at the bottom of the screen.
For example, in the above window,
- F1 would correspond to Open Config,
- F8 would correspond to Exit Program.
Mapping the Block-Mode Enter key
The primary purpose for including this terminal emulator is to allow block-mode applications (like NMMGR ) to be run from the Linux desktop. xhpterm uses the numeric keypad Enter key to simulate block-mode Enter. If your keyboard does not have a numeric key pad, the Enter key can be mapped to another key or key combination using xmodmap on Linux.
Example mapping the numeric key pad Enter key to Right-Ctrl:
Step | Command | |
---|---|---|
1 | Determine the key code of the Right-Ctrl key. |
You will receive an output similar to:
|
2 | Redefine the key code to the numeric keypad Enter key. | $ xmodmap -e "keycode 105 = KP_Enter" |
3 | If original key mapping is required, reverse step 2. | $ xmodmap -e "keycode 105 = Control_R" |
Please note: these settings are not persistent across X-sessions. To always use a certain setting when running xhpterm, you could, for example, use a small script to set and reset the key mapping. An example (only for illustrative purposes only) is shown below.
Code Block | ||
---|---|---|
| ||
#!/usr/bin/bash # # parameter: -f <font> -p <port> # while getopts "f:p:" opt; do case "$opt" in (f) font="-font $OPTARG" ;; (p) port="-port $OPTARG" ;; (*) print "flag [$opt] unknown. abort." && exit 1 ;; esac done if [[ -z "$port" ]]; then echo "Port (-p) is mandatory" exit 1 fi xmodmap -e "keycode 105 = KP_Enter" /opt/charon/bin/xhpterm -clean $font $port xmodmap -e "keycode 105 = Control_R" |
Using Different Fonts
The default command-line to start xhpterm is: $ xhpterm -port 30000 -clean -font 10x20
...
Please note: When using xhpterm , avoid resizing the window - it can result in input and output fields in block-mode programs being misaligned. Changing the screen font will change the window size automatically, without causing this problem.
Div | ||
---|---|---|
| ||
Accessing Emulated Charon-PAR/PA9 Systems via Terminal Emulation
...
- Login via SSH to the Charon host.
- Start a local telnet session from the command-line (sample uses the default console port):
telnet localhost 30000
Div | ||
---|---|---|
| ||
Display PuTTY via X11 through an SSH Tunnel
...