Welcome to follow VxWorks567
Please indicate the source if forwarding!
VxWorks generally uses a Console at runtime, providing basic IO operations, such as displaying the output of printf() and providing Kernel Shell services, etc.
The Console uses the CONSOLE_TTY serial port by default, with a baud rate of CONSOLE_BAUD_RATE
What does TTY mean? It should be an abbreviation for Teletypewriter. However, this type of device is no longer used, and its meaning has become broader: from a service perspective, it is a Console (control console); from a usage perspective, it is a Terminal (terminal), and from a software perspective, it uses a Serial Device (serial device), providing a Shell (command line interpreter) to implement text-based IO (input and output) operations.
The IO system of VxWorks names this serial port – /tyCo/x
For Intel x86 or x64 targets, there is generally a VGA interface. In this case, VxWorks can include the component INCLUDE_PC_CONSOLE to use VGA as the default Console – /pcConsole
When debugging Vx5/Vx6, the Host Shell in Tornado/WorkBench is also used.
This Host Shell is a C interpreter by default, and it can also serve as a GDB interpreter, TCL interpreter, and a cmd interpreter for debugging RTP.
The Debug Shell provided by WorkBench4 used in Vx7 only offers a GDB-like command line.
Additionally, when debugging Vx5/Vx6, the Host side also has a redirected Console.
The most commonly used Console for the “public account VxWorks567” is actually Telnet. VxWorks includes the component INCLUDE_IPTELNETS.
The Host side can use the Telnet command to access the VxWorks Kernel Shell.
VxWorks also provides rlogin service. After including the component INCLUDE_RLOGIN, other UNIX-like systems can access VxWorks through the rlogin mechanism.
For example, accessing device 222 from device 111.
Do you know any other Consoles?
I am Taishan, focusing on VX for many years!
Let’s learn together and make progress together!
