You can use the reference image to understand how to build a system using
QNX Platform for ADAS or experiment with the default application.
The reference image is configured to run without additional hardware (sensors or
cameras) connected to the R-Car H3 Starter board. Here are the ways you can use the
reference image:
- Use it as a test and development platform. You can connect to the image to
develop and run applications you developed using the QNX Platform for ADAS. For example, you may have an
application and simply need a hardware platform
to perform testing. For more information see Connect to reference image in this chapter.
- Evaluate the type of features that can run on the hardware platform. You can run
applications that come with the reference image to see how features respond. For
more information, see Run Sample Applications in
this chapter.
- Evaluate how the platform works with different sensors and cameras. You can
connect different sensors and configure the image to use live data from a
connected sensor or camera. For more information, see Connect cameras and sensors in this chapter.
There may be limitations on the type of hardware you can connect to the R-Car H3 Starter board.
For information about the supported hardware that you can connect to this board, see
Supported hardware configurations in the About the
QNX Platform for ADAS chapter of this guide.
You can use file cameras and file data with this reference
image—usually for development and testing purposes. File cameras are
virtual cameras that play a video file to simulate a video stream from a camera.
Similarly, file data is sensor data that applications can consume to simulate the
data from a live sensor (radar, lidar) or a camera.
Configuration files
The following reference image configuration files lets the system know what sensors
and cameras are connected:
- Sensor configuration files
- The default file is located at
/etc/system/config/adas_example_capture.conf. It
configures file cameras and file data to simulate sensors and cameras
connected to the system. There are a number of other configuration files
located at /etc/system/config/.
- System Launch Configuration (SLM) file
- The main SLM file is located at
/etc/slm-config-platform-all.xml. It pulls specific
configuration from the /etc/slm-config-platform.xml
file. There are other SLM files in the /etc directory
that you can use to change the configuration easily.
- ADAS library configuration files
- The default file is located at
/etc/system/config/adas_sensors.conf. It
configures file cameras and file data to simulate sensors and cameras
connected to the system. There are a number of other configuration files
located at /etc/system/config/.
For information about how to change the configuration, see
Configuring ADAS Library chapter in the ADAS Library Developer's Guide and
Configure sensors and cameras on the reference image in this chapter.
Sample applications on the reference image
The reference image includes sample applications. The applications described in this guide are the ones that function on the reference image with predefined configurations. For more information about the applications and how to use them on this reference image, see Run Sample Applications in this chapter.
Understanding the reference image
The reference images are configured to be
an example you can refer to when you build your image.
The following is a list of things we have done to make
the reference image easier to use, but you may want to change in your final image:
- Filesystem is writable
- The filesystem that's mounted for the
reference image is writable. For a production system, you usually want
to boot it as read-only. To modify or create new files on the filesystem,
run the following command on the target to remount the filesystem and make
it writable:
mount -uw /base
- qconn
-
When you want to
use the QNX Momentics IDE to connect to your target, the
qconn service is started on the
target. The QNX Momentics IDE
is a useful tool to simplify the process of uploading binaries to the target
board, downloading files from your host, and modifying configuration files
on the reference image. The qconn service is included
with the reference image and should be run only on developer images, not
production images.
- If you don't have
qconn
running on the target, you can run it by running the following command on the target:
# qconn