Revision history
Rev |
Date |
Comments |
|---|---|---|
1.4.0 |
2018-11-19 |
Released. Document compatible with devices running CC Linux 1.4.x.x |
1.4.1 |
2019-08-26 |
Added information about peripherals needing reconfiguration after a resume from suspend event. Document compatible with devices running CC Linux 1.4.x.x |
1.4.2 |
2019-12-11 |
Added CCpilot X900 related information. |
2.0.0 |
2021-01-18 |
Document compatible with devices running CC Linux 2.0.x.x |
2.0.1 |
2021-10-18 |
Added V1000/V1200 related information. |
2.0.2 |
2022-03-03 |
Added Yukon development board related information, table for CC Linux 2.0 supported devices and Display MCU firmware update description. |
2.0.3 |
2022-04-27 |
Add a section for Triggers in Software configuration possibilities. |
2.0.4 |
2022-08-26 |
Minor Revisions. |
2.0.5 |
2023-03-03 |
Yukon now supports CfgIn and PWMOut |
2.0.6 |
2023-04-14 |
Document compatible with devices running CC Linux 3.x.x.x |
2.0.7 |
2023-10-30 |
Updated document with info about V510/V710 |
2.0.8 |
2024-08-19 |
Updated document with info about X1200 |
2.0.9 |
2024-11-11 |
Document compatible with devices running CC Linux 4.x.x.x |
2.0.10 |
2025-10-17 |
Updated document with info about V1090/V1290 |
2.0.11 |
2025-11-17 |
Document compatible with devices running CC Linux 4.2.x.x |
2.0.12 |
2026-06-01 |
Document compatible with devices running CC Linux 5.0.x.x |
1. Introduction
The devices supported by the CC Linux platforms are powerful display computers, communication devices and controllers with a rich set of integrated functions. Together with the CC Linux operating system, they form an open platform that facilitates easy implementation of reliable controls.
CC Linux 4.0 introduced major architectural overhauls to the system, which broke compatibility with previous releases of CC Linux. CC Linux 5.0 is primarily an incremental update building on that foundation, maintaining the same architecture while adding new features and improvements.
Software update via Fullup replaced by RAUC software update: One of the biggest changes in CC Linux 4.0 was the replacement of the in-house software update mechanism Fullup with the de-facto robust software update mechanism RAUC, since Fullup was non-robust, lacked security mechanisms and could only update software via USB. Also with Fullup, the system had to be booted into the rescue system to update the main system. With the replacement of the update mechanism with RAUC, software can be updated via USB or from a local server or from the cloud, and there is no longer a need to boot into the rescue system to update the software. Note that you have to set up the local server or cloud to host the update software; only the support to update from a local server or cloud has been provided.
Main/Rescue root filesystem replaced with A/B root filesystem: For redundancy and to comply with the RAUC software update mechanism, the Main/Rescue root filesystem was replaced with an A/B root filesystem. The A and B root filesystems are symmetrical where both filesystems hold the same folder structure, whereas the Main/Rescue systems on previous versions of CC Linux were asymmetrical. The symmetrical filesystem allows software updates to be done from one root filesystem to the other.
A/B application filesystem introduced: Previously, in CC Linux 3.0, user applications were inside the user data partition which had read-write access, meaning anyone had the possibility to change the working of applications. To protect access, separate application filesystems (A and B) holding user applications with read-only access were introduced. The application filesystems A and B are tightly coupled with root filesystems A and B. Application filesystem A is mounted when the system boots with root filesystem A; likewise, application filesystem B is mounted when the system boots with root filesystem B.
Read only root filesystem introduced: To enhance the security and to ensure data integrity, the root filesystem is mounted as read-only (immutable) on boot. With read-only root filesystem, you have no access to modify the root filesystem, which will prevent any malicious binaries to be written to the device.
Complete root filesystem overlay replaced with only etc folder overlay: The complete root filesystem overlay from CC Linux 3.0 was replaced with an etc-folder-only overlay in CC Linux 4.0, since most user configurations reside in the etc folder. The previous complete root filesystem overlay allowed overwriting any part of the root filesystem, which could lead to potential issues with the operating system. With the etc-only overlay, users can only change configurations, add or remove systemd services, and add or remove users and groups.
Factory reset functionality updated: The factory reset functionality was updated following the removal of the Main/Rescue filesystem. The factory reset can now be performed on the root filesystem from which the system booted, unlike previous versions of CC Linux where the factory reset could only be performed from the rescue system. With the replacement of the complete root filesystem overlay with the etc-only overlay, the factory reset removes only user-made changes or configurations in the overlay etc folder, unlike the previous version where any main system changes or factory-installed CrossControl applications or files could be removed.
Security layer enabled by default: In CC Linux 4.0, the security layer was enabled by default with the Cybersecurity 1.0 module. The network firewall (iptables) was enabled by default for public networks, dropping incoming connections, while private networks and the NAT firewall remained permissive with rules. The root user account was disabled, removing the possibility to log in as the root user.
With the introduction of CC Linux 5.0 the following additions are available:
OP-TEE available as technology preview: OP-TEE (Open Portable Trusted Execution Environment) is available as a technology preview in CC Linux 5.0. Note that there are known issues when using OP-TEE in combination with suspend/resume. NXP is aware of these issues.
For specific details in CC Linux, please refer to the programmer’s manual.
1.1 Scope
This document is intended for anyone handling a device running the CC Linux platform or developing software for such a device. This document is not intended as a complete reference documentation of the CC Linux devices, software, or software development tools. It is intended to introduce the development engineer to the hardware and software, by providing a top-down overview and summary of the device and a description of the intended use. It is also intended to introduce the reader to the software on the target and the host software development tools.
All devices included in the CC Linux platform (at the time of writing: CCpilot V700, CCpilot V1000, CCpilot V1200, CCpilot V510, CCpilot V710, CCpilot V1090, CCpilot V1290 and the Yukon development board) are covered within this document. Depending on which CC Linux device model you are using, some features mentioned in this document might be unsupported. If so, it will be clearly stated using a greyed-out icon as shown below. If no icons are used, the feature is supported by all device models.
V700 |
V1x00 |
Vx10 |
Yukon |
X1200 |
V1x90 |
|---|---|---|---|---|---|
No |
No |
Yes |
Yes |
Yes |
No |
There may be slight differences in behavior of supported features depending on your device model. If so, there will be device specific chapters covering the details at the end of this document. Any such occurrence will be clearly stated in the text.
1.1.1. Currently supported devices on CC Linux 5
This document, which is the Software Guide for CC Linux 5, contains information on what features, and functionalities are supported for each product as described in 1.1. Please contact CrossControl for information about roadmaps of operating system versions and corresponding support for any device of interest.
CC Linux 5 supported devices:
V700 |
V1x00 |
Vx10 |
Yukon |
X1200 |
V1x90 |
|---|---|---|---|---|---|
Yes |
Yes |
Yes |
No |
No |
Yes |
1.2 References
[1] CC Linux– Programmer’s Guide
[2] CC Linux- Rauc Guide
[3] CCpilot V700 – Technical Manual
[4] CCpilot V1000/1200 – Technical Manual
[5] CCpilot V510/V710 – Technical Manual
[6] CCpilot X1200 – Technical Manual
[7] CCAux API reference documentation
[8] http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/index.html
[9] https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt
[10] https://github.com/systemd/systemd
[11] https://www.freedesktop.org/software/systemd/man/latest/systemd.html
[12] https://crosscontrol.com/support/knowledge-base/solution-recipes/
[13] https://crosscontrol.com/software-solutions/connectivity/screen-sharing/#downloadarea
[14] CCpilot V1090/1290 – Technical Manual