We are pleased to announce release an Boot2Qt embedded qt5 image and toolchain using Yocto 2.7, Warrior.
Below you will find the download link for the image as well as detailed instructions for the build.
For the Impatient
You can download the Boot2Qt Yocto images from here:
- For Nitrogen6x platform(nitrogen6x, nitrogen6x-lite, sabrelite, MAX, SOM2, SOM2_QP, nitrogen6_vm, nitrogen6QP_MAX):
- For Nitrogen6_SoloX platform:
- Coming soon
- For Nitrogen7 platform:
- Coming soon
- For Nitrogen8m platform:
- For Nitrogen8m Mini platform:
You can download the Boot2Qt Linux Toolchains from here (refer below for instructions on building the Windows toolchain):
- For Nitrogen6x platform(nitrogen6x, nitrogen6x-lite, sabrelite, MAX, SOM2, SOM2_QP, nitrogen6_vm, nitrogen6QP_MAX):
- For Nitrogen6_SoloX platform:
- Coming soon
- For Nitrogen7 platform:
- Coming soon
- For Nitrogen8m platform:
- For Nitrogen8m Mini platform:
As usual, you'll need to register on our site and agree to the EULA because it contains NXP content.
How to Burn
You can to program this image either using U-Boot USB Mass Storage Gadget or program the image onto an SD Card.
Instructions on programming the SW can be found below:
U-Boot USB Mass Storage Gadget
For i-mx6 and i-mx7:
For i-mx8
SD Card, USB Stick
You can flash the image onto an SD card or USB Stick using dd under Linux:
~$ sudo dd if=*boundary-image*.wic of=/dev/sdX bs=1M && sync
In addition, you can use the etcher utility to flash the SD Card or USB stick via Windows or Linux:
Build procedure
This image uses the warrior branch of the meta-boot2qt repo, which uses Qt version 5.14.0.
To build the image, you’ll need these packages installed as well as this repo tool that can be installed like this:
~$ sudo apt-get install repo
Then create your build directory and clone the meta-boot2qt repo
~$ mkdir ~/b2qt && cd b2qt
~/b2qt$ git clone git://code.qt.io/yocto/meta-boot2qt.git -b warrior
Next, run the b2qt-init-build-env script for your device. In this case we will use nitrogen8m
~/b2qt$ ./meta-boot2qt/b2qt-init-build-env init --device nitrogen8m
Then, export that device to the MACHINE variable
~/b2qt$ export MACHINE=nitrogen8m
Source the setup-environment script.
~/b2qt$ . ./setup-environment.sh
Finally, build the Boot2Qt Embedded Qt5 Image and Linux Toolchain ("boundary-b2qt-embedded-qt5-image" and "boundary-meta-toolchain-b2qt-embedded-qt5-sdk")
~/b2qt$ bitbake boundary-meta-b2qt-embedded-qbsp
Note: You can just build the Qt5 image by running "bitbake boundary-b2qt-embedded-qt5-image"
To build a toolchain for Windows platforms add the following line to local.conf:
SDKMACHINE = "i686-mingw32"
After some time this should build the same image as above.
The image file will deploy to tmp/deploy/images/{MACHINE}/b2qt-embedded-qt5-image-{MACHINE}.wic
.
The Linux toolchain will deploy to tmp/deploy/qbsp/meta-b2qt-embedded-qbsp-x86_64-{MACHINE}-5.14.0.qbsp
.
The Windows toolchain will deploy to tmp/deploy/sdk/b2qt-i686-mingw32-meta-toolchain-b2qt-embedded-qt5-sdk-{MACHINE}.7z
.
Display support
Please make sure your platform includes the latest U-Boot for i.MX8M:
This version of U-Boot supports the display configuration, allowing to use any of the following displays:
- HDMI display (up to 4k, 1080p recommended)
- 7" 1280x800 MIPI BD070LIC2_8M
- 8" 1920x1200 MIPI BD080MCC1
- 10" 1280x800 MIPI BD101LCC2_8M
Note that we've noticed that the NXP HDMI driver is picky when it comes to custom display timings (sometimes refuses to set the clock).
So if you are experiencing any issue with HDMI, please try entering the following commands in U-Boot in order to force the use of standard timings:
=> setenv cmd_custom 'setenv bootargs $bootargs drm_kms_helper.edid_firmware=HDMI-A-1:edid/1280x720.bin'
=> saveenv