VAR-SOM-MX6 B2QT: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | --> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | ||
--> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_B2QT_MORTY_V1.0_VAR-SOM-MX6}}}} <!-- | --> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_B2QT_MORTY_V1.0_VAR-SOM-MX6}}}} <!-- | ||
--> {{PageHeader|{{#var:MACHINE_NAME}} - Boot to QT {{#var:B2QT_BSP_VERSION}} based on Yocto {{#var:YOCTO_NAME}} {{DocImage|category1={{#var:MACHINE_NAME}}|category2= | --> {{PageHeader|{{#var:MACHINE_NAME}} - Boot to QT {{#var:B2QT_BSP_VERSION}} based on Yocto {{#var:YOCTO_NAME}} {{DocImage|category1={{#var:MACHINE_NAME}}|category2=Boot2Qt}} }}__toc__ | ||
Revision as of 09:10, 27 May 2018
About Boot to Qt
Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device.
The stack can be customized to production with Build-Your-Own-Stack tooling, including proprietary Yocto Project recipes.
The full B2QT documentation is available at Qt for Device Creation official page.
Requirements
You should be familiar with the Yocto tools and the concept of recipes. For more information, see Yocto Project documentation.
To get started, you need the following:
- Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required:
sudo apt-get install gawk curl git-core diffstat unzip p7zip texinfo \ gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison \ g++-multilib
Setting Up Yocto Build Environment
Run the setup script that initializes the Yocto environment. Using Variscite VAR-SOM-MX6 as an example:
mkdir ~/var-b2qt cd ~/var-b2qt git clone -b cd meta-variscite-boot2qt ./b2qt-init-build-env init --device <target>
b2qt-init-build-env has the following additional command line options:
- list-devices: show all supported devices that can be used for a Boot to Qt build
- mirror: create a local mirror of the yocto repositories. This enables you to use the same repository downloads for multiple build environments, when initializing with init --reference <mirror path>.
For all command line options, see:
./b2qt-init-build-env help
Building the Image and Toolchain
After the Yocto environment is set up, you need to configure the build environment for your target device:
MACHINE= source ./setup-environment.sh
The following table lists the MACHINE values for our reference platforms:
SoMs & boards | target |
---|---|
VAR-SOM-SOLO/DUAL/MX6, DART-MX6 and related board configurations | var-som-mx6 |
DART-6UL and related board configurations | imx6ul-var-dart |
VAR-SOM-MX7 and related board configurations | imx7-var-som |
Yocto recipes for Boot to Qt for embedded Linux have two main targets to build: The target image, and the external toolchain that can be used with Qt Creator for building Qt applications.
MACHINE= bitbake b2qt-embedded-qt5-image MACHINE= bitbake meta-toolchain-b2qt-embedded-qt5-sdk
The target rootfs image is located in the
~/var-b2qt/meta-variscite-boot2qt/build-/tmp/deploy/images//b2qt-embedded-qt5-image-.img
and the new toolchain is in
~/var-b2qt/meta-variscite-boot2qt/build-/tmp/deploy/sdk/b2qt-x86_64-meta-toolchain-b2qt-embedded-qt5-sdk-.sh
Flashing the SD card image
Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
$ sudo umount /dev/sdX* $ sudo dd if=tmp/deploy/images//b2qt-embedded-qt5-image-.img of=/dev/sdX bs=1M && sync Replace /dev/sdX with your actual device name, e.g. /dev/sdb
Creating an extended SD card
Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card. The script copies the NAND/eMMC flash burning scripts and relevant binaries for your convenience.
Later, you will be able to follow either the more automatic Yocto Recovery SD card guide to burn your images to NAND flash or eMMC.
Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
$ cd ~/var-b2qt/meta-variscite-boot2qt $ sudo MACHINE= sources/meta-variscite-fslc/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh /dev/sdX Replace /dev/sdX with your actual device name, e.g. /dev/sdb