source: rtems-docs/user/testing/consoles.rst @ 8b67c91

5
Last change on this file since 8b67c91 was 8b67c91, checked in by Chris Johns <chrisj@…>, on 05/19/18 at 20:32:42

user: Add RTEMS executable and test documentation.

  • Property mode set to 100644
File size: 2.9 KB
Line 
1.. comment SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. comment: Copyright (c) 2018 Chris Johns <chrisj@rtems.org>
4.. comment: All rights reserved.
5
6.. _tester-consoles:
7
8Consoles
9--------
10
11The RTEMS Tester uses the target's console output to determine the state of a
12test. Console interfaces vary depending on the testing mode, the BSP, and the
13target hardware.
14
15Consoles for simulator work best if mapped to the simulator's ``stdout``
16interface. The RTEMS Tester can capture and process the ``stdout`` data from a
17simulator while it is running.
18
19Target hardware console interfaces can vary. The most universal and stable
20interface target hardware is a UART interface. There are a number of physical
21interfaces for UART data these days. They are:
22
23#. RS232
24
25#. TTL
26
27#. USB
28
29RS232 is still present on a number of targets. The best solution is to use a
30RS232 to USB pod and convert the port to USB.
31
32TTL is common on a number of boards where cost is important. A console
33interface is typically a development tool and removing the extra devices need
34to convert the signal to RS232 or directly to USB is not needed on production
35builds of the target. There is a standard header pin out for TTL UART consoles
36and you can purchase low cost cables with the header and a built in UART to USB
37converter. The cables come is different voltage levels so make sure you check
38and use the correct voltage level.
39
40The USB interface on a target is typcially a slave or OTG interface and all you
41need to a standard USB cable.
42
43We recommend a low cost and low power device to be a terminal server. A
44Raspberry Pi or similar low cost computer running Linux can be set up quickly
45and with a powered USB hub and can support a number of USB UART ports. A USB
46hub with a high power port is recommended that can suppy the Raspberry Pi.
47
48The open source daemon ``ser2net`` is easy to configure to map the USB UART
49ports to the Telnet protocol. There is no need for security because a typical
50test environment is part of a lab network that should be partitioned off from
51an enginnering or corportate network and not directly connected to the
52internet.
53
54A test set up like this lets you place a terminal server close to your target
55hardware providing you with the flexibility to select where you run the RTEMS
56Tester. It could be your desktop or an expensive fast host machine in a server
57rack. None of this equipment needs to directly interface to the target
58hardware.
59
60The RTEMS Tester directly supports the telnet protcol as a console and can
61interface to the ``ser1net`` server. The telnet console will poll the server
62waiting for the remote port to connect. If the terminal server ``ser2net`` does
63not have a ``tty`` device it will not listen on the port assigned to that
64``tty``. A USB ``tty`` can come and go depending on the power state of the
65hardware and the target hardware's design and this can cause timing issues if
66the target hardware is power cycled as part of a reset process.
Note: See TracBrowser for help on using the repository browser.