Linux-3.14.52 Compiler Reference Manual v2.0

明远智睿Lan

Linux-3.14.52 Compiler Reference Manual v2.0 [Copy link]

Cross-compilation toolchain A9 series: Open the network disk to 2.2_OS_Linux-3.14.52 -> 03_toolchain and download the MY-IMX-A9 directory. Source code

u-boot: Open the network disk to 2.2_OS_Linux-3.14.52 -> 02_source, download u-boot-2016.03-*.tar.bz2 (The source code package version number must be svn315 and above). Kernel: Open the network disk to 2.2_OS_Linux-3.14.52 -> 02_source and download linux-3.14.52-*.tar.bz2 (the source package version number must be svn369 or above).

Install the cross-compilation toolchain

Execute the installation

=====> Input:./fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1.sh =====> Output: Enter target directory for SDK (default: /opt/fsl-imx-fb/3.14.52-1.1.1):=====> Input:/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1=====> Output: You are about to install the SDK to "/home/myzr/my-work/03_toolchain/fsl-imx-f b-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1". Proceed[Y/n]?======> Input:y=====> Output: Extracting SDK...doneSetting it up...doneSDK has been successfully set up and is ready to be used.

source Toolchain configuration file

=====> Input:source /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi

Verify cross-compilation tool installation

=====> Input:$CC -v=====> Output: Using built-in specs.COLLECT_GCC=arm-poky-linux-gnueabi-gccCOLLECT_LTO_WRAPPER=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86 _64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/lto-wrapperTarget: arm-poky-linux-gnueabiConfigured with: /home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/work-shared/gcc-4.9.2-r0/gcc-4.9.2/configure --build=x86_64-linux --host=x86_64-pokysdk-linux --target=arm-poky-linux-gn ueabi --prefix=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr --exec_prefix=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr --bindir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi --sbindir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-lin ux/usr/bin/arm-poky-linux-gnueabi --libexecdir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi --datadir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/share --sysconfdir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/etc --sharedstatedir= /opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/com --localstatedir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/var --libdir=/opt/fsl-imx-fb /3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/lib/arm-poky-linux-gnueabi --includedir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/include --oldincludedir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/include --infodir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/share/info --mandir=/opt/fsl-imx-fb/3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/sysroots/x86_64-nativesdk-pokysdk-linux --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --enable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=arm-poky-linux-gnueabi- --without-local-prefix --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libmudflap --with-system-zlib --with-linker-hash-style=gnu --enable-linker-build-id --with-ppl=no --with-cloog=no --enable-checking=release --enable-cheaders=c_global --with-gxx-include-dir=/not/exist/usr/include/c++/4.9.2 --with-build-time-tools=/home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/sysroots/x86_64-linux/usr/arm-poky-linux-gnueabi/bin --with-sysroot=/not/exist --with-build-sysroot=/home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/sysroots/imx6qdlsolo --enable-poison-system-directories --with-mpfr=/home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/sysroots/x86_64-nativesdk-pokysdk-linux --with-mpc=/home/myzr/my-yocto/imx-3.14.52-1.1.0_ga/imx6qdlsolo__fsl-imx-fb/tmp/sysroots/x86_64-nativesdk-pokysdk-linux --enable-nls --with-arch=armv7-aThread model: posixgcc version 4.9.2 (GCC)
u-boot编译编译前的准备

=====> Input:mkdir ~/my-work/02_source/ -p

=====> Input:tar xf u-boot-2016.03-svn*.tar.bz2 -C ~/my-work/02_source/编译u-boot目标文件

=====> Input:cd ~/my-work/02_source/u-boot-2016.03

生成目标开发板的 .config 文件

=====> Input:make myimx6ek200-6q-1g_defconfig=====> Output: HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf## configuration written to .config#

【Note】: The myimx6ek200-6q-1g_defconfig after make above should be changed to the configuration file corresponding to the development board model.

************ MY-IMX6-EK200 **********myimx6ek200-6q-1g_defconfig myimx6ek200-6q-2g_defconfig myimx6ek200-6q-512m_defconfig myimx6ek200-6u-1g_defconfig myimx6ek200-6u-2g_defconfig myimx 6ek200-6u-512m_defconfig myimx6ek200-6s-512m_defconfig myimx6ek200-6s-1g_defconfig myimx6ek200-6s-128m_defconfig myimx6ek200-6qp-1g_defconfig myimx6ek200-6qp-2g_defconfig myimx6ek200-6qp-512m_defconfig ********** MY-IMX6-EK314 **********myimx6ek314-6q-1g_defconfig myimx6ek314-6q-2g_defconfig myimx6ek314-6q-512m_defconfig myimx6ek314-6u-1g_defconfig myimx6ek314-6u-2g_ defconfig myimx6ek314-6u-512m_defconfig myimx6ek314-6s-512m_defconfig myimx6ek314-6s-1g_defconfig myimx6ek314-6s-128m_defconfig myimx6ek314-6qp-1g_defconfig myimx6ek314-6qp-2g_defconfig myimx6ek314-6qp-512m_defconfig ********** MY-IMX6-EK336 **********myimx6ek336-6q-1g_defconfig myimx6ek336-6q-2g_defconfig myimx6ek336-6q-512m_defconfig

Execute compilation

=====> Input:make =====> Output: scripts/kconfig /conf --silentoldconfig Kconfig CHK include/config.h UPD include/config.h GEN include/autoconf.mk GEN include/autoconf.mk.dep CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h CFG u-boot.cfg ...... LD u-boot OBJCOPY u-boot-nodtb.bin OBJCOPY u-boot.srec SYM u- boot.sym COPY u-boot.bin CFGS board/myzr/myimx6/myimx6a9-6q-ddr3.cfg.cfgtmp MKIMAGE u-boot.imx

Note: If there is a prompt "cc1: error", it is usually because the configuration of the cross-compilation tool has not taken effect. You can follow the "source tool chain configuration file" in the previous "cross-compilation tool chain installation" and then perform this step.

u-boot target fileu-boot.imx is the target file.

Compile u-boot environment variable script=====> Input:mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "myzr bootscripts" -d board/myzr/bootscripts/myimx6a9_l31452_script.cmd my_environment.scr=====> Output: Image Name: myzr bootscriptsCreated: Wed Jan 2 09:40:07 2019Image Type: ARM Linux Script (uncompressed)Data Size: 2327 Bytes = 2.27 kB = 0.00 MBLoad Address: 00000000Entry Point: 00000000Contents: Image 0: 2319 Bytes = 2.26 kB = 0.00 MBTarget file

u-boot.imx and my_environment.scr are the compiled target files. Save these two files

Kernel compilationPreparation before compilation

Create the compilation working directory

======> Input:mkdir ~/my-work/02_source/ -p

Unzip the source package to the working directory

======> Input:tar xf linux-3.14.52-svn*.tar.bz2 -C ~/my-work/02_source/Compile kernel target file

Enter the kernel source directory

======> Input:cd ~/my-work/02_source/linux-3.14.52

Generate .config file for the target platform

=====> Input:make myimx6a9_defconfig=====> Output: HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.=====> Input:make zImage=====> Output: scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release UPD =====> Input:make myimx6ek200-6q-1g.dtb=====> Output: DTC arch/arm/boot/dts/myimx6ek200-6q-1g.dtb

【Note】: The myimx6ek200-6q-1g.dtb after make above should be changed to the configuration file corresponding to the development board model.

************ MY-IMX6-EK200 **********myimx6ek200-6q-1g.dtb myimx6ek200-6q-2g.dtb myimx6ek200-6q-512m.dtb myimx6ek200-6u-1g.dtb myimx6ek200-6u-2g.d tb myimx6ek200-6u-512m.dtb myimx6ek200-6s-512m.dtb myimx6ek200-6s-1g.dtb myimx6ek200-6s-128m.dtb myimx6ek200-6qp-1g.dtb myimx6ek200-6qp-2g.dtb myimx6ek200-6qp-512m.dtb ********** MY-IMX6-EK314 **********myimx6ek314-6q-1g.dtb myimx6ek314-6q-2g.dtb myimx6ek314-6q-512m.dtb myimx6ek314-6u-1g.dtb myimx6ek314-6u-2g.dtb myimx6ek314-6u-512m.dtb myimx6ek314-6s-512m.dtb myimx6ek314-6s-1g.dtb myimx6ek314-6s-128m.dtb myimx6ek314-6qp-1g.dtb myimx6ek314-6qp-2g.dtb =myimx6ek314-6qp-512m.dtb ********** MY-IMX6-EK336 **********myimx6ek336-6q-1g.dtb myimx6ek336-6q-2g.dtb myimx6ek336-6q-512m.dtb

Copy device tree target file

=====> Input:cp arch/arm/boot/dts/myimx6ek200-6q-1g.dtb ./Compile kernel module package

Execute compilation

=====> Input:make modules=====> Output: CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.hmake[1]: "include/generated/mach-types.h" is up to date. =====> Input:make modules_install INSTALL_MOD_PATH=./modules=====> Output: INSTALL crypto/tcrypt.ko INSTALL drivers/i2c/algos/i2c-algo-pca.ko ...... INSTALL sound/usb/snd-usbmidi-lib.ko DEPMOD 3.14.52-myimx6-svn369

Package kernel module files

=====> Input:make modules_install INSTALL_MOD_PATH=./modules=====> Output: INSTALL crypto/tcrypt.ko INSTALL drivers/i2c/algos/i2c-algo-pca.ko ...... INSTALL sound/usb/snd-usbmidi-lib.ko DEPMOD 3.14.52-myimx6-svn369

Package kernel module files

=====> Input:tar cjf kernel-modules.tar.bz2 -C modules libTarget file

zImage、myimx6ek*.dtb and kernel-modules.tar.bz2 are the compiled target files. Save these three files.

Linux C program compilationPrepare source code

Open the network disk to 5_MY-Demo -> MY-Linux-C-Demo, download the hello.c file, and copy it to the virtual machine. =====> Input:$CC hello.c -o hello.out Note: If there is a message of "command not found", it is because the configuration of the cross-compilation tool chain has not taken effect. You can press the "source tool chain configuration file" in the previous "cross-compilation tool chain installation" and then execute this step again. Run the Linux C target program. Copy the compiled hello.out to the development board. Run the Linux C target program on the development board. =====> Input:chmod +x ./hello.out./hello.out =====> Output:MYZR Technology Co.,Ltd.Web: : http://www.myzr.com.cn/Wiki: http://wiki.myzr.com.cn/BBS: http://bbs.myzr.com.cn/Tel: 0756-3628023/3628021E-mail: service@myzr.com.cn Linux QT5 program compilationPrepare source code

Open the network disk to 5_MY-Demo, download the MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 file, and copy it to the virtual machine.

Unzip the source code package to the working directory

=====> Input:tar xf MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 -C ~/my-work/02_source/QT program compilation

Enter the source code directory

=====> Input:cd ~/my-work/02_source/AboutUs/

Generate Makefile file

=====> Input:qmake

Note: If there is a message "'qamke' command not found", it is because the configuration of the cross-compilation toolchain has not taken effect. You can press the "source toolchain configuration file" in the previous "Cross-compilation toolchain installation" =====> Input:make=====> Output: /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic widget.ui -o ui_widget.h......arm-poky-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o AboutUs main.o widget.o qrc_source.o moc_widget.o -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lEGL -lpthread Run on MY-IMX6-A9 device

Compile the AboutUs Copy to the development board
Run the QT5 target program on the development board
=====> Input:chmod +x ./AboutUs./AboutUs -platform eglfsRunning results
You can see that the MYZR logo and some information are output on the development board display.
If there is a message of "command not found", it is because the configuration of the cross-compilation tool chain has not taken effect. You can follow the "source tool chain configuration file" in the previous "cross-compilation tool chain installation" and then perform this step

Run the Linux C target program

Copy the compiled hello.out to the development board
Run the Linux C target program on the development board

=====> Input:chmod +x ./hello.out./hello.out=====> Output:MYZR Technology Co.,Ltd.Web: http://www.myzr.com.cn/Wiki: http://wiki.myzr.com.cn/BBS: http://bbs.myzr.com.cn/Tel: 0756-3628023/3628021E-mail: service@myzr.com.cn Linux QT5 program compilationPrepare source code

Open the network disk to 5_MY-Demo, download the MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 file, and copy it to the virtual machine.

Unzip the source code package to the working directory

=====> Input:tar xf MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 -C ~/my-work/02_source/QT program compilation

Enter the source code directory

=====> Input:cd ~/my-work/02_source/AboutUs/

Generate Makefile file

=====> Input:qmake

Note: If there is a message "'qamke' command not found", it is because the configuration of the cross-compilation toolchain has not taken effect. You can press the "source toolchain configuration file" in the previous "Cross-compilation toolchain installation" =====> Input:make=====> Output: /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic widget.ui -o ui_widget.h......arm-poky-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o AboutUs main.o widget.o qrc_source.o moc_widget.o -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lEGL -lpthread Run on MY-IMX6-A9 device

Compile the AboutUs Copy to the development board
Run the QT5 target program on the development board
=====> Input:chmod +x ./AboutUs./AboutUs -platform eglfsRunning results
You can see that the MYZR logo and some information are output on the development board display.
If there is a message of "command not found", it is because the configuration of the cross-compilation tool chain has not taken effect. You can follow the "source tool chain configuration file" in the previous "cross-compilation tool chain installation" and then perform this step

Run the Linux C target program

Copy the compiled hello.out to the development board
Run the Linux C target program on the development board

=====> Input:chmod +x ./hello.out./hello.out=====> Output:MYZR Technology Co.,Ltd.Web: http://www.myzr.com.cn/Wiki: http://wiki.myzr.com.cn/BBS: http://bbs.myzr.com.cn/Tel: 0756-3628023/3628021E-mail: service@myzr.com.cn Linux QT5 program compilationPrepare source code

Open the network disk to 5_MY-Demo, download the MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 file, and copy it to the virtual machine.

Unzip the source code package to the working directory

=====> Input:tar xf MY-Linux-QT5-Demo-AboutUs-svn*.tar.bz2 -C ~/my-work/02_source/QT program compilation

Enter the source code directory

=====> Input:cd ~/my-work/02_source/AboutUs/

Generate Makefile file

=====> Input:qmake

Note: If there is a message "'qamke' command not found", it is because the configuration of the cross-compilation toolchain has not taken effect. You can press the "source toolchain configuration file" in the previous "Cross-compilation toolchain installation" =====> Input:make=====> Output: /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic widget.ui -o ui_widget.h......arm-poky-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o AboutUs main.o widget.o qrc_source.o moc_widget.o -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lEGL -lpthread Run on MY-IMX6-A9 device

Compile the AboutUs Copy to the development board
Run the QT5 target program on the development board
=====> Input:chmod +x ./AboutUs./AboutUs -platform eglfsRunning results
You can see that the MYZR logo and some information are output on the development board display.
qmake
Note: If there is a message "'qamke' command not found", it is because the configuration of the cross-compilation toolchain has not taken effect. You can press the "source toolchain configuration file" in the previous "cross-compilation toolchain installation" and then execute this step

Compile target file
======> Input:make======> Output: /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic widget.ui -o ui_wid get.h......arm-poky-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o AboutUs main.o widget.o qrc_source.o moc_widget.o -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lEGL -lpthread Run on MY-IMX6-A9 device

Compile the AboutUs Copy to the development board
Run the QT5 target program on the development board
=====> Input:chmod +x ./AboutUs./AboutUs -platform eglfsRunning results
You can see that the MYZR logo and some information are output on the development board display.
qmake
Note: If there is a message "'qamke' command not found", it is because the configuration of the cross-compilation toolchain has not taken effect. You can press the "source toolchain configuration file" in the previous "cross-compilation toolchain installation" and then execute this step

Compile target file
======> Input:make======> Output: /home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/x86_64-pokysdk-linux/usr/bin/qt5/uic widget.ui -o ui_wid get.h......arm-poky-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/myzr/my-work/03_toolchain/fsl-imx-fb-glibc-x86_64-meta-toolchain-qt5-cortexa9hf-vfp-neon-toolchain-3.14.52-1.1.1/sysroots/cortexa9hf-vfp-neon-poky-linux-gnueabi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o AboutUs main.o widget.o qrc_source.o moc_widget.o -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lEGL -lpthread Run on MY-IMX6-A9 device

Compile the AboutUs Copy to the development board
Run the QT5 target program on the development board
=====> Input:chmod +x ./AboutUs./AboutUs -platform eglfsRunning results
You can see that the MYZR logo and some information are output on the development board display.