2.4. Telematics API
Some CCpilot devices support the external add-on telematics device CrossLink AI. The interfaces
provided by this board are not accessed via the CCAux API, but through the separate Telematics
API instead. This API is included in both the BSP and SDK and its functions are called in the same
way as in CCAux API. Please refer to the Telematics API reference documentation for more
information about the functions available.
3. Board Support Package
In order to create custom Linux images for CCpilot devices, a board support package (BSP) has
been created. The BSP is a Yocto-project build system that produces complete Linux images for the
CCpilot devices. It also includes necessary application and driver code, as well as example or
template code that may serve as a basis for further application and driver development.
The open-source Yocto system has built-in package support with many thousands of maintained
packages available, while also providing a set of standard tools and build guidelines. The BSP adds
necessary drivers and applications required for the CCpilot board images. For more information
regarding the Yocto project, please refer to the Yocto Project reference manual at
www.yoctoproject.org/docs/2.2/dev-manual/dev-manual.html
3.1. Downloading and installing the BSP
The BSP package comes in the form of a gzipped tar archive which can be acquired from the
CrossControl support site. The BSP was created on an x86-64 machine running Ubuntu 14.04.5
LTS and must be unpacked to a Linux host machine/build server. Much disk space (at least several
hundred gigabytes) and memory is required for the Yocto system, as the folder structure tends to
grow quickly in size. Please refer to the Yocto Project reference manual mentioned earlier for
information about required dependencies.
3.2. BSP structure
This chapter will go through the structure of the BSP, covering CrossControl specific parts. For
other third party components (Qt, OpenEmbedded, Yocto, etc.), please refer to their respective
reference documentation.
Initially, the BSP base directory only contains CrossControl folders. All other required third party
tools are provided as hash-files which will be downloaded from remote repositories upon first
build. The following subsections will describe these initial folders.
Internet connection is required to build BSP.
While most components in the BSP are released under various open source licenses,
others are of proprietary nature and protected under the CrossControl Software
License. Be aware of which license applies and comply with the license terms.
VS is the internal CrossControl code name for the CCpilot VS architecture/platform; therefore the
BSP contains references to the VS platform such as “PLATFORM_VS”. The same applies for other
CCpilot devices. Additionally, CrossControl specific components are named “cc”, such as “meta-cc”
and “recipes-cc”.