LVGL configured to work with /dev/fb0 on Linux. Also compiles as a windows simulator, which generates an additional target "ecu_sensor_spoofer" - see instructions at bottom.
The project has several dependencies that are pulled in at build time by CMake's "FetchContent" command.
git clone [email protected]:hptechdesign/rpi_ecu_display.git
cd rpi_ecu_display/
- MSYS2 (recommended):
- https://www.msys2.org/wiki/MSYS2-installation/
- Follow the installation instructions, then open the MSYS2 terminal [from start menu, or
C:\msys64\ucrt64.exe] - Type
pacman -Syuuto update all packages. If the terminal closes, run it again until all updates are complete. - Next install the following minimum packages:
- MINGW64 compiler toolchain:
pacman -S mingw-w64-ucrt-x86_64-toolchain
- CMAKE
pacman -S mingw-w64-x86_64-cmake
Download the pre-built windows toolchain for raspberry pi from here (select compatible version, e.g. Bullseye): https://gnutoolchains.com/raspberry/
Set up environment variable RPIDEV_LOC, and refer to the following document: https://www.codeproject.com/Articles/1279667/Toolset-to-Cross-Compile-Remote-Debug-Raspberry-fr
Using this information you should be able to modify the rpi_ecu_display project's launch.json and tasks.json to fit your environment.
Make sure that you delete the /build folder if you've previously used it to build for RPi. Any binaries generated previously will remain in the /bin folder. Navigate to the top of the cloned rpi_ecu_display directory and execute the following two commands:
- Generate:
cmake -B ./build -DCMAKE_BUILD_TYPE=Release -G "Ninja"
- Build:
cmake --build./build --config Release
The following executables will be placed in {workspace_dir}/bin:
- win_ecu_display
- The Windows display simulator, with a COM port serial interface
- ecu_sensor_spoofer
- A signal spooder which emulates the engine sensors and transmits the data via a COM port
Make sure that you delete the /build folder if you've previously used it to build for Windows. Any binaries generated previously will remain in the /bin folder.
- Open the
set_platform.cmakefile and ensiure the command isset(platform "rpi"). - Make sure that
set(platform "win")is commented out.
Navigate to the top of the cloned rpi_ecu_display directory and execute the following two commands:
- Generate:
cmake -B ./build -DCMAKE_BUILD_TYPE=Release -G "Ninja"
- Build:
cmake --build./build --config Release
The ecu_sensor_spoofer will not be built. Only the rpi_ecu_display executable is built, and placed in {workspace_dir}/bin.
Several debug launchers have been created.
On Windows, you can launch win_ecu_display, ecu_sensor_spoofer, or a compound launcher which launches both.
On RPI, you first need to ctrl-shft-'B', which transfers the binary to the PI, then you can launch the rpi_ecu_display debugger which will attach to the remote GDB session on the RPI.
- win_ecu_display
- The Windows simulator, asks for a COM port to receive serial data. If serial data is provided in the correct format (see src/serial module) then the meters and gauges will be updated at approx 30 Hz.
- ecu_sensor_spoofer
- Windows sensor emulator, asks for COM port to send serial data. Fake sensor readings are generated and will ramp up to an approx 75% maximum reading then hovering to within 3% using a random number generator. This can be used to interface either with the win_ecu_display, using two USB-RS232 serial converters and a null modem, or it can interface directly with the dev/ttyS0 serial port pin on the RPi.
- rpi_ecu_display
- The ECU is designed to run on an RPi with a 800x600 touchscreen interface. Serial data can be provided from the ecu_sensor_spoofer interfaced with the dev/ttyS0 serial port - tested on a RPi 3B running Raspbian but may also work on others.
The base display project was derived from the LVGL Framebuffer Demo project and its related sub modules: [https://github.com/lvgl/lv_port_linux_frame_buffer.git].
See this blog post for a step by step tutorial for deriving from scratch: [https://blog.lvgl.io/2018-01-03/linux_fb]