Most 4DPi issues can easily be solved by ensuring that you are using a kernel package that matches or is closest to the Raspberry Pi OS kernel version you have.
Please refer to the filename of the package for the kernel version it is compiled with.
If you can’t find a matching kernel package and the closest version produces some issues, please contact our support team.
We only provide 4DPi kernel packages for the Raspberry Pi boards. However, it should be possible to edit the source code and build the drivers for your target hardware. Note that it is up to the user to get this to work.
Optionally, you can also contact our support team if you are interested in a customized software solution.
We only provide 4DPi kernel packages for the official Raspberry Pi OS (previously Raspbian OS). However, it should be possible to build the drivers for your target operating system from the source code provided.
Note that it is up to the user to get this to work.
Optionally, you can also submit a ticket to our support team if you are interested in a customized software solution.
If the latest OS released uses the same kernel version as the latest kernel package, there is a good chance that they will still work fine together. However, if there are any issues observed, feel free to contact our technical support.
We try to keep up with a new kernel package for every Raspberry Pi OS release. However, if our customers haven’t considered updating to a newer OS version, our team tends to allocate our development resources to other products.
If you ever need a need a new kernel package, you can either:
Our kernel packages include in their filename the kernel version of the Raspberry Pi OS used to build it. We recommend using the kernel package that matches the same kernel of your target OS version.
For both Raspberry Pi and Beaglebone Black, we use Primary to refer to displays that are able to display the desktop environment of the OS running in these Linux machines. These are essentially Monitors for these SBC’s (Single Board Computers) and show the desktop or terminal or direct to a custom application etc. as would a typical computer monitor. Primary displays typically interface to the host using SPI or raw RGB signals.
On the other hand, Secondary display solutions are not capable of the same feat in terms of displaying the Desktop but are programmed using our Workshop4 IDE to design attractive GUI’s which are then interfaced with the Host Raspberry Pi or Beaglebone Black. The Host can send values to the display to update the GUI widgets, and receive information back such as touch events or slider/knob/button input, or the GUI could be completely drawn by the host if programmed as a Slave. Secondary displays typically interface to the Host using a serial UART.
Primary display examples are gen4-4DPI-xx, 4DPi-xx, gen4-4DCAPE-xx, 4DCAPE-xx
Secondary display examples are gen4-uLCD-xx, uLCD-xx, uOLED-xx, pixxiLCD-xx
Copyright © 2025 4D Systems. All right reserved.