Linux5.10.160_User’s Compilation Manual_V1.0
Document classification: □ Top secret □ Secret □ Internal information ■ Open
Copyright
The copyright of this manual belongs to Baoding Folinx Embedded Technology Co., Ltd. Without the written permission of our company, no organizations or individuals have the right to copy, distribute, or reproduce any part of this manual in any form, and violators will be held legally responsible.
Forlinx adheres to copyrights of all graphics and texts used in all publications in original or license-free forms.
The drivers and utilities used for the components are subject to the copyrights of the respective manufacturers. The license conditions of the respective manufacturer are to be adhered to. Related license expenses for the operating system and applications should be calculated/declared separately by the related party or its representatives. 1. VMware Virtual Machine Software Installation
1. VMware Virtual Machine Installation
This chapter mainly introduces the installation of the VMware virtual machine, using VMware Workstation 15 Pro v15.1.0 as an example to demonstrate the operating system installation and configuration process.
1.1 Downloading and Purchasing VMware Software
Visit the VMware official website at https://www.vmware.com/cn.html to download Workstation Pro and obtain the product key. VMware is paid software that requires individual purchase, or you can choose to use a trial version Version.
After the download is complete, double-click the setup file to launch the installer.
1.2 VMware Software Installation
Double-click the setup file to enter the installation wizard.
Click “Next.”
Check “I accept the terms in the license agreement” and click “Next.”
Modify the installation location to the partition on your computer where software is typically installed, then click “Next.”
Check, then click “Next.”
Check “Add shortcuts” and click “Next.”
Click “Install.”
Wait for the installation to complete.
After clicking “Finish,” you can start the trial. For long-term use, please purchase from the official website and enter the license key.
2. Loading an Existing Ubuntu Development Environment
Note:
It is recommended that beginners directly use the virtual machine environment pre-configured by Forlinx, which already has the cross-compiler and Qt environment installed. After reviewing this chapter, you can skip directly to the compilation chapters;
Development Environment Account: forlinx; password: forlinx.
There are two ways to use the virtual machine environment in VMware: one is to directly load an existing environment, and the other is to create a new environment. First explain how to load an existing environment.
First, download the development environment provided by Forlinx. The development environment package includes an MD5 checksum file. After downloading the package, you should verify the integrity of the compressed file by performing an MD5 checksum check. You can either use an online MD5 verification tool or download a dedicated MD5 verification tool, depending on your preference. Compare the checksum that you generate with the one listed in the checksum file. If they match, the downloaded file is intact. If they do not match, the file may be corrupted, and you will need to download it again.
Extract the Compressed File:
After the extraction is complete, select the .vmx file as the virtual machine file to open.
Open the virtual machine and choose the extracted 3588 development environment.vmx file.
Once it has finished loading, click to start the virtual machine, and you will be able to run it and enter the system interface.”
The development environment account is: forlinx, and the password is : forlinx. After entering the password, select Sign in to log in
3. Setting Up a New Ubuntu Development Environment
Note: It is not recommended for beginners to build the system by themselves. It is recommended to use the existing virtual machine environment. This section can be skipped if there is no need to build the environment.
3.1 Ubuntu System Setup
3.1.1 Creating an Ubuntu Virtual Machine
Open the VMware software and click “Create a New Virtual Machine”. Enter the following interface:
Select ‘’Custom’’ and click ‘’Next.’’
Choose the compatibility for the corresponding VMware version. The version can be found under Help ->About VMware Workstation. Click ‘’Next.’’
Select install the operation later and click Select ‘’I will install the operating system later’’ and click ‘’Next.’’
Keep the default settings and click ‘’Next.’’
Modify the virtual machine’s name and installation location, then click ‘’Next.’’
Set the number of processors according to your needs.
Similarly, set the memory size according to your needs. It is recommended to use 16GB.
Set the network type, the default is NAT mode, and click “Next.” Subsequent steps remain at their default values until the disk capacity step is specified.
Choose the default LSI for the IO controller type.
Similarly, select SCSI as the default here.
Choose to create a new virtual disk:
Set the disk size to 200GB and select the disk’s format, then click ‘Next’ to complete.
Specify the disk file, the default setting is fine here.
Click ‘’Finish’’ by default to complete.
At this point, the virtual machine creation is complete.
The installation process on a physical machine is similar to the one on a virtual machine, but here we will focus on installing Ubuntu in the virtual machine.
3.1.2 System Installation
The installed Ubuntu version is 20.04. First, go to the official Ubuntu website to download the Ubuntu 20.04 64-bit ISO image. The download link is: http://sources.ubuntu.com/20.04/
. Download the version ubuntu-20.04.6-desktop-amd64.iso.
Right-click the Ubuntu 64-bit virtual machine that was created and select “Settings” from the context menu.
The “Virtual Machine Settings Menu” will pop up as shown in the image below.
Click on CD/DVD (SATA), select Use ISO image file, then browse and select the previously downloaded Ubuntu ISO image, and click “OK”.
After configuring the image, ensure that the network is working, and then start the virtual machine to begin installing the Ubuntu image.
Once the virtual machine starts, wait for the installation interface to appear as shown below.
Select the language on the left side and click “Install Ubuntu.” A language selection screen will pop up.
By default, Ubuntu’s language is English, but you can also select Chinese. The selected language can be changed later during the installation. Once you’ve selected the language, click “Continue”.
Next, choose the default option, click Continue to proceed with the installation. The process will take some time. Then click Continue again.
Click “Install Now” by default, and a prompt will appear. Click “Continue” to proceed.
Choose your timezone. Here, you can click Shanghai or type Shanghai to select the timezone (choose a different timezone based on your location if needed), and click Continue. Finally, set up your username and password. Click Continue, and the installation will begin automatically.
The installation process is shown in the figure below. If the network is not good, you can skip it without affecting the installation.
After the installation is completed, as shown in the following figure, click “Restart Now” Restart “ (or click” Restart Client “):
After restarting and logging in, the system interface is as shown below:
3.1.3 Basic Configuration of Ubuntu
After installing the Ubuntu 20.04 operating system, some configurations need to be done.
VMware Tools Installation：
Next, install VMware Tools. Without this tool, you won’t be able to copy and paste or drag files between the Windows host and the virtual machine. First, click on Virtual Machine in the VMware navigation bar, then select Install VMware Tools from the dropdown menu.
After this, go to the Ubuntu desktop, where you will see the VMware Tools disk icon. Click to open it.
Inside, you will see a compressed file named VMwareTools-10.3.10-12406962.tar.gz (the version number may vary depending on the VMware version).
Copy the file to the home directory (i.e., the personal username directory).
Open a terminal by pressing Ctrl + Alt + T, and use the tar command to extract the VMware Tools installation package. Use sudo to run the command (you will be prompted to enter your password. Linux passwords do not show any feedback when typed, so ensure the password is correct and press Enter to confirm).
forlinx@ubuntu:~$ sudo tar -xvf VMwareTools-10.3.10-12406962.tar.gz
[sudo] password for forlinx:
After the extraction, use the ls command to check, and you should see a vmware-tools-distrib directory. Enter this directory.
forlinx@ubuntu:~$ ls
Desktop examples.desktop nfs snap tftp VMwareTools-10.3.10-12406962.tar.gz vmware-tools-distrib work
forlinx@ubuntu:~$ cd vmware-tools-distrib/ //Use the CD command to enter the directory
forlinx@ubuntu:~/vmware-tools-distrib$ ls //View the files in this directory
bin caf doc etc FILES INSTALL installer lib vgauth vmware-install.pl
In the current directory, type sudo ./vmware-install.pl to start the installation. After pressing Enter, input your password, and the installation process will begin. If you are prompted with [yes]/[no], type yes, and for other prompts, press Enter to go with the default installation options.
forlinx@ubuntu:~/vmware-tools-distrib$ sudo ./vmware-install.pl
[sudo] password for forlinx: //Enter the password of the forlinx account, no response, cannot see the input content
The installation process may take some time, and this part is skipped in the instructions.
open-vm-tools packages are available from the OS vendor and VMware recommends
using open-vm-tools packages. See http://kb.vmware.com/kb/2073803 for more
information.
Do you still want to proceed with this installation? [no] yes //输入yes
... ...
After installation, VMware Tools will enable file copy/paste between Windows and Ubuntu, as well as full-screen adjustments for the virtual machine. If the virtual machine is not displaying in full-screen mode, click View, select Auto-resize guest display, and choose Fit Guest Now to solve the full-screen issue. This means VMware Tools has been successfully installed.
Basic Configuration:
Most system settings can be configured in the location shown in the figure. Many settings requirements on Ubuntu can be completed here.
3.1.4 Network Configuration of Ubuntu
NAT Mode
Before using the network, make sure that your virtual machine can connect to the internet. Open the virtual machine settings, and change the network adapter’s network bridging mode to NAT Mode:
In the virtual machine, when the VMware virtual network adapter is set to NAT mode, the network in the Ubuntu environment should be set to dynamic IP. In this mode, the virtual NAT device and the host network card are connected. This is the most commonly used method to connect the virtual machine to the external network.
The network is set to dynamic IP.
Bridge Mode：
If using servers like TFTP or SFTP, you need to set the virtual machine’s network connection to Bridged Mode. When Vmware virtual network card is set to bridged mode, the host network card and the virtual machine network card communicate through a virtual bridge, and you need to ensure that the IP address of Ubuntu is in the same subnet as the host machine.
Set the static IP. At this time, the Ubuntu IP and the host IP should be set in the same network segment.
Note: The IP and DNS settings mentioned in the network configuration section should be configured based on the user’s actual environment. The manual provides examples for illustration.
3.1.5 USB Device Loading
Open the virtual machine settings, go to USB Controller, and in the compatibility section, choose USB 3.0, then click OK. As shown below, most modern computers support USB 3.0 ports. If not configured, the USB 3.0 device will not be connected to the virtual machine when inserted. As shown in the figure:
After the virtual machine starts, insert the USB flash drive. An icon similar to a “USB drive” will appear in the lower-right corner of the virtual machine. Right-click it and select Connect. Then, you should see a new directory in the file system, indicating that the USB drive has been successfully loaded, as shown below:
3.1.6 Basic Library Installation for the Virtual Machine
Before development, some other necessary libraries need to be installed. Use the following commands to install them one by one. Make sure the network is functioning properly and can connect to the internet before installing.
forlinx@ubuntu:~$ sudo apt-get update # Update the package source information
forlinx@ubuntu:~$ sudo apt-get install build-essential # Install essential software packages for compiling programs
forlinx@ubuntu:~$ sudo apt-get install libncurses* # Install libraries for generating text-based user interfaces
forlinx@ubuntu:~$ sudo apt-get install lzop # Install Lzo-based compression and decompression tool
forlinx@ubuntu:~$ sudo apt-get install net-tools # Install network configuration tools
3.1.7 Installation of Necessary Libraries for Compiling OK3568 Linux Source Code
forlinx@ubuntu:~$ sudo apt-get update # Update the apt-get package sources
forlinx@ubuntu:~$ sudo apt-get install openssh-server vim git fakeroot # Install essential tool packages
forlinx@ubuntu:~$ sudo apt-get install repo git ssh make gcc libssl-dev liblz4-tool expect g++ patchelf chrpath gawk texinfo chrpath diffstat binfmt-support qemu-user-static live-build bison flex fakeroot cmake gcc-multilib g++-multilib unzip device-tree-compiler python-pip libncurses5-dev
forlinx@ubuntu:~$ sudo apt-get install libgmp-dev libmpc-dev libicu-dev bsdmainutils
These libraries are required when setting up the 3568 Linux compilation environment and preparing to compile the Linux source code. If you’re not setting up the OK3568 Linux development environment, you can skip this step.
3.1.8 Increasing Swap Partition Size
Please check the current system swap partition size. If the swap partition is insufficient, it can cause source code compilation to fail. It is recommended to have 16GB for the swap partition. It is also suggested to adjust the development environment memory to 16GB.
1. Check the Swap Partition:
forlinx@ubuntu:~$ cat /proc/swaps
The virtual machine provided by Forlinx has already configured the swap partition. If you are using another virtual machine, you can increase the swap partition size by creating a swap file.
forlinx@ubuntu:~$ sudo swapoff /swapfile
forlinx@ubuntu:~$ sudo fallocate -l 10G /swapfile
forlinx@ubuntu:~$ sudo chmod 600 /swapfile
forlinx@ubuntu:~$ sudo mkswap /swapfile
forlinx@ubuntu:~$ sudo swapon /swapfile
forlinx@ubuntu:~$ sudo vim /etc/fstab
Add the following content at the end of the /etc/fstab file:
forlinx@ubuntu:~$ /swapfile none swap sw 0 0
2. Memory Adjustment:
It is recommended to adjust the development environment memory to 16GB. Low memory may cause compilation failure.
3.2 Qt Creator Installation
Copy the file qt-creator-opensource-linux-x86_64-4.7.0.run to any directory in the current user’s home directory and execute the following command.
Path: OK3568-C (Linux) User Data\Linux\Source\qt-creator-opensource-linux-x86_64-4.7.0.run
forlinx@ubuntu:~$ ./qt-creator-opensource-linux-x86_64-4.7.0.run
This will open a graphical installation window. Follow the prompts to install:
Online users need to register for a Qt account. Existing Qt account holders can log in directly. The Qt password requires a mix of uppercase letters, lowercase letters, and numbers. After registering and logging in successfully, click Next.
Offline users can click Skip.
Click “Next”:
You can set the installation path according to your preferences; here use the default here. Click “Next”.
Choose Complete Installation and click “Next”.
Click Install and wait for the installation to complete.
After installation, click Finish. The Qt interface will automatically open, or you can launch it from the command line. To open Qt Creator in the background, use the following command, replacing it with your actual installation path:
forlinx@ubuntu:~$ cd /home/forlinx/qtcreator-4.7.0/bin
forlinx@ubuntu:~$ ./qtcreator &
The Qt Creator tool interface will appear. Qt Creator installation is now complete.
4. Compilation of Related Code
This section mainly describes the compilation methods for the development board-related source code, including kernel source code compilation and application program compilation.
4.1 Preparation Before Compilation
4.1.1 Environment Description
Recommended Development OS: Ubuntu 22.04 64-bit
Cross-Toolchain: aarch64-linux-gnu
Bootloader Version for Development Board: u-boot-2017.09
Kernel Version for Development Board: linux-5.10.160
Qt Version Ported to Development Board: QT 5.15.8
4.1.2 Copying the Source Code
Program Source Code: User Data\Linux\Source\ OK3568_Linux_fs.tar.bz2.0*
Create Working Directory:
forlinx@ubuntu:~$ mkdir -p /home/forlinx/3568 //Create the working directory in order
Copy the source code file OK3568_Linux_fs.tar.bz2.0* from User Data to /home/forlinx/3568 on the virtual machine.
forlinx@ubuntu:~$ cd /home/forlinx/3568 //Switch to the working directory
forlinx@ubuntu:~/3568$ cat OK3568_Linux_fs.tar.bz2.0* > OK3568_Linux_fs.tar.bz2
forlinx@ubuntu:~/3568$ tar -xvf OK3568_Linux_fs.tar.bz2 //Decompress the compressed packet in the current location
Wait for the copy process to complete after running the command.
Toolchain Path: OK3568-Linux5.10.160-User Data\Linux\Source\dl.tar.bz2
When compiling Buildroot, the toolchain will be downloaded from the official website based on the configuration. To save time, download and unzip dl.tar.bz2 from User Data into the Buildroot directory.
4.2 Kernel Compilation
Note:
After extracting the kernel source code for the first time, you need to perform a full compilation of the source code;
After the initial full compilation, you can proceed with individual compilations based on the actual situation;
This source code compilation requires at least 16GB of RAM in the development environment. Please do not modify the provided VM configuration;
To shorten the initial compilation time, we use pre-compiled file system images and do not rebuild the file system.
4.2.1 Full Compilation Test
Switch to the extracted source code directory in the terminal:
forlinx@ubuntu:~$ cd /home/forlinx/3568/OK3568_Linux_fs
The following operations should be performed in the source code directory. For the first compilation, specify the chip you are using:
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$./build.sh chip
"/* After executing, there will be options to input, as follows: */"
Log saved at /home/forlinx/work/3568/OK3568_Linux_fs/output/sessions/2023-10-21_16-45-26
Pick a chip:
1. OK3568
2. rk3566_rk3568
3. rk3588
Which would you like? [1]: 1 "/* Enter 1 and press Enter to continue. */"
Pick a defconfig:
1. OK-x-U40-linux_defconfig
2. OK3568-C-linux_defconfig
Which would you like? [1]: 1 "/* Enter 1 and press Enter to continue. */"
Switching to defconfig: /home/forlinx/work/3568/OK3568_Linux_fs/device/rockchip/.chip/OK-x-U40-linux_defconfig
make: Entering directory '/home/forlinx/work/3568/OK3568_Linux_fs/device/rockchip/common'
#
# configuration written to /home/forlinx/work/3568/OK3568_Linux_fs/output/.config
#
make: Leaving directory '/home/forlinx/work/3568/OK3568_Linux_fs/device/rockchip/common'
After that, you can proceed with the compilation. The default file system used is from the linuxfs directory (OK3568-C file system, which is adapted for the OK3568-C motherboard). To compile the OK3568-UP4 file system, you must compile Buildroot separately first. If you need to recompile Buildroot, refer to the separate compilation instructions.
forlinx@forlinx-ubuntu:~/work/3568/OK3568_Linux_fs$ ./build.sh
The final compilation result will look like the image below (paths may vary based on the actual situation).
After compilation, corresponding build files will be generated in the OK3568_Linux_fs/rockdev folder. You can find the image files there.
**Note: **
update.img is packaged for full flashing using OTG or TF card. Other files are for step-by-step flashing.
Important: The 3568 5.10 SDK contains a precompiled file system, located in the OK3568_Linux_fs/linuxfs directory.
When running the full compilation script, linuxfs/rootfs.img will be copied to buildroot/output/OK3568/images to generate the compiled file system results, reducing the time to generate update.img in the first compilation.
If you need to compile the file system, do so separately, and after compiling, replace linuxfs/rootfs.img with the new rootfs.img. Subsequent executions of build.sh will continue using linuxfs/rootfs.img.
4.2.2 Individual Compilation Test
Before performing an individual compilation, you must have completed a full compilation. Perform the following in the kernel source code directory:
To compile Buildroot individually, you must modify the following files:
Remove depends on BR2_PACKAGE_DWKEYBOARD from OK3568_Linux_fs/buildroot/package/forlinx/flapp/Config.in and save.
Remove DWKeyboard from the FLAPP_DEPENDENCIES parameter in OK3568_Linux_fs/buildroot/package/forlinx/flapp/flapp.mk and save.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh uboot # Compile uboot separately
# This will generate uboot.img, and the path is /OK3568_Linux_fs/u-boot/uboot.img
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh kernel # Compile the kernel separately
# This will generate boot.img, and the path is /OK3568_Linux_fs/kernel/boot.img
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh buildroot # Compile the Buildroot file system separately
# This will generate rootfs.ext2, and the path is /OK3568-linux-source/output/OK3568/image/rootfs.ext2
# Note: The 3568 5.10 SDK includes a factory rootfs.img in the linuxfs directory. Running Buildroot separately will overwrite it.
# Users who need to roll back to the factory file system should back up before performing this step.
# Recompiling the file system can take a long time, usually 4-6 hours. Please be patient if there is no error message at exit.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh recovery # Compile the recovery file system separately
# This will generate rootfs.cpio.gz, and the path is /OK3568_Linux_fs/output/recovery/rootfs.cpio.gz
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh updateimg # Generate update.img separately
# This will use the paths above (uboot.img, boot.img, rootfs.ext2) to generate update.img, and the path is rockdev/update.img
After compilation, the kernel in update.img will not be updated. Flash the boot.img file from OK3568_Linux_fs/kernel/ step-by-step. For detailed flashing steps, refer to Section 5.1.3 “OTG Step-by-Step Flashing Test” in the user manual.
Note:
After modifying kernel configuration through the graphical interface (e.g., adding USB-to-serial driver for CH340), run ./build.sh kernel and flash the boot.img image;
If the graphical configuration doesn’t take effect after booting the development board, you can use one of the following methods to resolve it:
Method 1: Directly write the configuration to the kernel default configuration file: /OK3568_Linux_fs/kernel/arch/arm64/configs/OK3568-C-linux_defconfig.
CONFIG_USB_SERIAL_CH341=y
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh kernel
Method 2: Use the graphical interface to configure the kernel, and comment out the command in source/device/rockchip/common/scripts/mk-kernel.sh.
Edit the kernel/Makefile file.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs/kernel$ make ARCH=arm64 menuconfig
Configure the kernel according to the requirements, write the configuration to the .config file, then save and exit.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh kernel
Note:
After modifying the Buildroot configuration (e.g., adding Python3 support), run ./build.sh buildroot and flash the rootfs.ext2 image.
If the graphical configuration doesn’t take effect after booting the development board, you can use one of the following methods to resolve it:
Method 1: Directly write the configuration to the Buildroot default configuration file: /OK3568_Linux_fs/buildroot/configs/OK3568_defconfig.
BR2_PACKAGE_PYTHON3=y
BR2_PACKAGE_PYTHON3_PY_PYC=y
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh buildroot
During compilation, when prompted:
Found old config, override it? (y/n): y
Choose ‘y’ to indicate that you want to overwrite the previous .config file.
Method 2: Use the graphical interface to configure Buildroot, and comment out the corresponding command in device/rockchip/common/scripts/mk-buildroot.sh.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs/buildroot/output/OK3568$ make menuconfig
Configure the kernel according to the requirements, write the configuration to the .config file, then save and exit.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs$ ./build.sh buildroot
During compilation, when prompted:
Found old config, override it? (y/n): y
Choose ‘y’ to indicate that you want to overwrite the previous .config file.
4.2.3 Cross-Compilation Toolchain Location
Driver Compilation Toolchain Source Path:
OK3568-linux-sdk5.10/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
File System Application (QT, etc.) Compilation Toolchain Source Path:
OK3568-linux-sdk5.10/buildroot/output/OK3568/host/bin/aarch64-linux-
These paths are generated after running ./build.sh buildroot. If you use the preset host.tar.bz2 to compile the whole package, unpack host.tar.bz2 in these paths after compilation to get the cross-compilation toolchain.
4.3 Use of Image Files
update.img is packaged for full flashing using OTG or TF card.
Other files are for step-by-step flashing.
The image files generated by individual compilation will not update update.img and should be flashed step-by-step (refer to the OTG flashing section in the user manual).
4.4 Qt Creator Environment Configuration
Qt is a cross-platform graphics development library that supports multiple operating systems. Before compilation, you need to configure the Qt Creator environment for cross-compilation.
4.4.1 Cross-Compiler Configuration
**Note: **
**The path to the cross-compiler used by Qt Creator should be generated after full compilation. For convenience, we placed the host.tar.bz2 package in /OK3568-C (Linux) User Data/Tools. **
You can check the HostPrefix path recorded in the /host/bin/qt.conf file inside, and create an absolute path that matches the HostPrefix after extracting host.tar.bz2 to the corresponding location. Continue with this section after extraction.
It is strongly recommended to complete the full compilation before proceeding with this section.
In Qt Creator, click Tools -> Options -> Kits -> Compilers, then click Add -> GCC -> C;
Name it GCC;
For Compiler Path, click Browse and select the cross-compiler path: aarch64-linux-gcc and aarch64-linux-g++ as shown below; Path: OK3568_Linux_fs/buildroot/output/OK3568/host/bin
Note: The output directory under Buildroot must be generated after full compilation.
Add the GCC C++ compiler in the same way by clicking Add -> GCC -> C++. As shown below:
4.4.2 Qt Versions Configuration
Click Tools -> Options -> Qt Versions in Qt Creator;
Click Add, then select OK3568_Linux_fs/buildroot/output/OK3568/host/bin/qmake;
Click Open to add it;
Return to the Qt Version configuration window, and you can change the Version name;
Click “Apply and OK”.
4.4.3 Kits Configuration
Kits are used to build and select the development environment for compiling projects. They are useful for projects with multiple Qt libraries.
Click Tools -> Options -> Kits in Qt Creator, then click Add to configure a new kit;
Change the Name as desired.;
Choose GCC for the Compiler;
Select the Qt version that you entered in the previous step;
Click “Apply and OK.”
4.5 Application Compilation and Running
4.5.1 Compile and Run Command-Line Application
This subsection uses the watchdog test program, and the default program is copied to /home/forlinx/3568.
Use the cd command to navigate to the /home/forlinx/work directory.
forlinx@ubuntu:~$ cd /home/forlinx/3568/OK3568_Linux_fs/app/forlinx/forlinx_cmd/fltest_watchdog
Add the cross-compiler path and use make for cross-compilation.
forlinx@ubuntu: ~/3568/OK3568_Linux_fs/app/forlinx/forlinx_cmd/fltest_watchdog$ export PATH=/home/forlinx/3568/OK3568_Linux_fs/buildroot/output/OK3568/host/bin/:$PATH
forlinx@ubuntu: ~/3568/OK3568_Linux_fs/app/forlinx/forlinx_cmd/fltest_watchdog$ make
aarch64-linux-gcc watchdog.c -o fltest_watchdog
generate fltest_watchdog success!!!
Use the file command to check the generated file information.
forlinx@ubuntu:~/3568/OK3568_Linux_fs/app/forlinx/forlinx_cmd/fltest_watchdog$
file fltest_watchdog
fltest_watchdog: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, not stripped
The result will show that the compiled file is 64-bit and ARM-based.
Copy the compiled fltest_watchdog file to the board via USB or FTP, for example to the /forlinx directory, and run the test (using TF card as an example).
[root@ok3568:/]# cp /run/media/mmcblk1p1/fltest_watchdog /home/forlinx
[root@ok3568:/]# cd /home/forlinx
[root@ok3568:/home/forlinx]# ./fltest_watchdog
Watchdog Ticking Away!
Refer to the user manual “Watchdog Test” section for testing.
4.5.2 Compile and Run Qt Application
In the development environment, open Qt Creator (open according to your actual path). Click File -> Open File or Project, then select /3568/OK3568_Linux_fs/app/forlinx/forlinx_qt/watchdog/watchdog.pro.
After opening the project, the interface should appear as shown. If the page doesn’t change automatically, follow the screenshot instructions.
Click Configure Project, which will adapt to the compilation environment built in the “Qt Creator Environment Configuration” section.
Then click Build -> Clean All to clean up the previous build files.
(If intermediate files are not cleaned, you can delete them manually.)
Uncheck Shadow build in the Projects section.
Click Build -> Build All to compile.
Once the build progress bar completes, the new executable file fltest_qt_watchdog will be located in the /app/forlinx/forlinx_qt/watchdog directory.
