The latest development version of this page may be more current than this released 2.3.0 version.

CONFIG_NATIVE_UART_AUTOATTACH_DEFAULT_CMD¶

Default command to attach the UART to a new terminal

Type: string

Help¶

If the native_posix executable is called with the –attach_uart command line option, this will be the default command which will be run to attach a new terminal to the 1st UART. Note that this command must have one, and only one, ‘%s’ as placeholder for the pseudoterminal device name (e.g. /dev/pts/35) This is only applicable if the UART_0 is configured to use its own PTY with NATIVE_UART_0_ON_OWN_PTY. The 2nd UART will not be affected by this option.

Direct dependencies¶

UART_NATIVE_POSIX && SERIAL

(Includes any dependencies from ifs and menus.)

Default¶

“xterm -e screen %s &”

Kconfig definition¶

At drivers/serial/Kconfig.native_posix:57

Included via Kconfig:8 → Kconfig.zephyr:32 → drivers/Kconfig:22 → drivers/serial/Kconfig:83

Menu path: (Top) → Device Drivers → Serial Drivers → UART driver for native_posix

config NATIVE_UART_AUTOATTACH_DEFAULT_CMD
    string "Default command to attach the UART to a new terminal"
    default "xterm -e screen %s &"
    depends on UART_NATIVE_POSIX && SERIAL
    help
      If the native_posix executable is called with the --attach_uart
      command line option, this will be the default command which will be
      run to attach a new terminal to the 1st UART.
      Note that this command must have one, and only one, '%s' as
      placeholder for the pseudoterminal device name (e.g. /dev/pts/35)
      This is only applicable if the UART_0 is configured to use its own
      PTY with NATIVE_UART_0_ON_OWN_PTY.
      The 2nd UART will not be affected by this option.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)