2. Basic operation

This section provides an overall description on basic usage of the device.

2.1 Login and passwords

By default, the system will boot to a default console and no graphical user interface is launched. For access, the login credentials as stated in Table 1 are required. Additional users can be added using the adduser Linux program.

Table 1: Default login credentials
Username	Password	Access
root	suseroot	Full administrator
ccs	default	Full administrator using sudo

Note

These passwords are publicly accessible and should be immediately changed on first boot in order to avoid security breaches. Issue the following commands using either SSH or on screen terminal.

Change password of root user:

*$ sudo passwd*

Change password of ccs user:

*$ sudo passwd ccs*

2.2 Using the graphical environment

CC Linux provides Weston/Wayland as the default graphical environment. However, it is up to the customer to choose the default bootup environment of the device so Weston does not start up by default on boot. Refer to chapter 6.2. on how to start and/or enable Weston on boot.

2.3 Using the touch screen

To use the touch screen, a graphical application or Weston will need to be enabled.

2.3.1 Weston and included demo

To test the touch, Weston includes a demo application Weston-smoke. Launch a console by touching the console icon on the top left of the screen in Weston. Then, launch Weston-smoke by typing:

*$ weston-smoke*

2.3.2 Crosscontrol demo applications

To install and use the demo applications, see chapter 5. Navigate the start-up screen application using the touch screen with a stylus or finger.

Tap the screen to perform an action equivalent to a left mouse click.

Two simultaneous touches can be recognized to implement pan, zoom and pinch, see chapter Error: Reference source not found for an example.

2.4 Print screen

It is possible to take screenshots using the weston-screenshooter included in the window manager. To take a screenshot, connect an external keyboard to the device and press Super+S (on Windows keyboards, the Super key is the Windows key). The resulting image will end up in the / directory.

2.5 Software deployment

There are several methods to add your own software to the device. The standard methods to transfer software to the device are to either copy files using a network connection or to use USB storage devices, with manual or automatic copy functions. To install the software, follow the instructions for the respective software.

Additionally, software can be deployed with remote access functions, see the operating system specific parts in this document for more information.

2.5.1 Device start-up behavior

At power on, the device has an internal microcontroller that monitors the power supply and performs start-up configurations and power settings, the System Supervisor (SS). The SS then supplies the main processor and peripherals with power; from there the device execution begins, starting with the BIOS and/or boot loader, depending on your device model. Most of these options can be configured from CCSettingsConsole. See chapter 4.1. for details. Additionally, the CCAux API can be used to configure these settings from a user application.

2.6 BIOS

The BIOS is a device specific BIOS, which performs the initial setup of the main processor and its on-board peripherals. Once finished, the operating system execution takes over.

During BIOS operation different start-up options can be accessed. The BIOS can for instance be used to occasionally boot from USB attached storage media by pressing the key F11. If other non-standard BIOS settings are desired, access the BIOS Settings menu by pressing the DEL key during BIOS start-up. BIOS settings changes should normally not be needed and can be affecting specific functions within the system, so any changes must be careful considered before applying.

2.7 Boot loader

The boot loader is the first software block that executes in the main processor. It serves the purpose of setting up the main processor peripherals and timings and will then load the Linux kernel into RAM memory. Once finished, the operating system execution takes over.

It is possible to connect to the boot loader through a debug serial port with special equipment attached to the device. The reason for connecting to the boot loader would be for debug purposes only, where specific settings are needed. Detailed information about the boot loader access can be requested from CrossControl if needed.

2.8 Linux system start-up specifics

The Linux operating system can be started in two different modes:

Main system (normal, default):

This is the main operation mode which includes all drivers to available hardware, system libraries, graphical applications and tools described in this and other documents.

Rescue system (backup):

This is only for device updates and recovery use. It contains only basic maintenance tools. Updating the main system should be done from rescue system. Most of the hardware is not accessible in the rescue system.

Both modes are completely separate Linux operating systems, each of which is a custom-built Linux version consisting of a kernel and a root file system with system binaries and configuration files. Such a system is started with the Linux kernel execution, which turns over the execution process to the systemd [11] in the root file system. That in turn loads drivers and programs according to the configuration files, and eventually loads the user applications. The startup time of the system is normally defined as the time from power on until the user application can begin to execute.

Depending on the level of functionality needed by the application, it can be started at different startup targets. A very fast startup level means that some of the hardware might not yet have been initialized properly, and thus the application needs to handle that properly. On the other hand, a slower startup level guarantees that the required functionality is available upon application initialization.

2.9 Status indication (LED and Buzzer)

The buzzer and/or status LEDs (or backlit soft keys, depending on your device model) will be used to indicate the different running states of the device. For a detailed description, refer to the device specific chapters 8.1. (VS), 9.1. (VI), 10.1. (X900), 11.1. (V700), 12.1. (V1x00/Vx10 and Yukon) and 13.1. (X1200).

For error indication, all device models behave the same, as described in 2.9.1 Error indication

2.9.1 Error indication

If an error occurs, the device will indicate the type of error by blinking the status LEDs (or backlit soft keys) or beeping the buzzer in different patterns. The device may be restarted by a button or ignition signal and, depending on whether the error is severe, the device may start normally or go back to error indication.

The reason for fatal error situations could be voltage levels out of range, temperature related problems or internal hardware errors. First steps should be to let the device cool off, and verify it has a correct power supply attached, before starting the device again.

Some devices will beep the buzzer in the same pattern as the LEDs in order to indicate the error.

See the Technical Manual of your device model for a more complete description of the error indication and a list of possible error codes.