Skip to content

Latest commit

 

History

History

setting

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 

README.md

Hardware & Software Setting Guide

This document provides a guide for hardware assembly, setup, and software environment configuration. All contents of this project have been tested in the environment described below.

Requirements

Before starting this guide, you will need the following components:

  1. Raspberry Pi 4B
  2. 2-Channel CAN-BUS(FD) Shield (MCP2518FD)
  3. PiRacer AI Kit (PiRacer Standard)
  4. 7.9inch DSI LCD (400 x 1280)
  5. 7inch HDMI LCD (H) (1028 x 600)
  6. Gamepad controller
  7. Arduino UNO
  8. CAN-BUS Shield V2.0 (MCP2515)
  9. IR infrared Speed Sensor (LM393)

Precautions

  • To prevent electric shock, ensure that all assembly procedures are carried out with the power turned off.
  • Exercise care when assembling the components, as incorrect assembly may result in damage to the components.
  • When not in use, please safeguard the components and power them off.

Hardware Setting

hardware_architecture

  1. Assemble the Raspberry Pi board with the CAN-BUS shield and a 7.9inch LCD, and then attach it on the PiRacer.
  2. Assemble the Arduino board with the CAN-BUS shield and attach it to the front of the PiRacer.

arduino_assembly

  1. Fix the 7inch LCD onto the PiRacer using a robust material like a metal frame to position it above the Arduino.

display_assembly

  1. Fix the speed sensor's rotor in a way that it aligns and rotates with the PiRacer's rear tires.

speed_sensor_assembly

  1. Connect the receiver of the gamepad controller to one of the USB ports on the Raspberry Pi.

gamepad_controller

  1. (Optional) Install an auxiliary battery to provide additional power during PiRacer operation. Create a case for the auxiliary battery and position it at the rear of the PiRacer vehicle.

power_bank

power_bank_assembly

  1. Final result.

overall_hardware

overall_hardware

final_result

Software Setting

This project was conducted in Yocto, so for accurate testing, please refer to our meta-infotainment repo. However, if you wish to test it on Raspbian, please follow the settings below.

CommonAPI and vsomeip

Step 1: Install Boost Library

sudo apt-get install libboost-all-dev

Step 2: Build the CommonAPI Runtime Library

cd ~
mkdir build-commonapi
cd build-commonapi
git clone https://github.com/GENIVI/capicxx-core-runtime.git
cd capicxx-core-runtime/
git checkout 3.2.0
mkdir build
cd build
cmake ..
make -j4

Step 3: Build the vsomeip Library

cd ~
git clone https://github.com/COVESA/vsomeip.git
cd vsomeip
git checkout 3.1.20.3
mkdir build
cd build
cmake -DENABLE_SIGNAL_HANDLING=1 -DDIAGNOSIS_ADDRESS=0x10 ..
make -j4
sudo make install

Step 4: Build the CommonAPI SOME/IP Runtime Library

cd ~/build-commonapi
git clone https://github.com/GENIVI/capicxx-someip-runtime.git
cd capicxx-someip-runtime/
git checkout 3.2.0
mkdir build
cd build
cmake -DUSE_INSTALLED_COMMONAPI=OFF ..
make -j4

Step 4: Install code generator for Franca files (The architecture of the Raspberry Pi does not support the code generator, so this step must be executed on a laptop.)

cd ~
mkdir generator
cd generator

wget https://github.com/COVESA/capicxx-core-tools/releases/download/3.2.0.1/commonapi_core_generator.zip
unzip commonapi_core_generator.zip -d core-generator
cd core-generator
chmod +x commonapi-core-generator-linux-x86_64

cd ~/generator
wget https://github.com/COVESA/capicxx-someip-tools/releases/download/3.2.0.1/commonapi_someip_generator.zip
unzip commonapi_someip_generator.zip -d someip-generator
cd someip-generator
chmod +x commonapi-someip-generator-linux-x86_64

For more detail about CommonAPI and vsomeip, visit here

For the remaining software installation and configuration code, please consult the following link

Display configuration

In this project, we will be using two platforms, eglfs and linuxfb, to simultaneously interface a DSI display and an HDMI display. After completing the installation as per the above procedure, you may notice that part of the 7.9inch display is not visible. This issue arises because the 7inch display's specifications restrict the screen area. To resolve this, you can modify the code written in /boot/config.txt as follows.

hdmi_cvt 1024 1280 60 6 0 0 0

Note that the 7inch display's specifications are recognized as larger than the actual hardware, so you may need to adjust the source files to align the application with the visible area. Typically, for applications developed for a 1024 x 600 screen size in Qt, reducing the scale by x0.5 will display the content correctly.

display_configuration