C

Boundary Devices i.MX6 Boards Guide

To successfully set up the Boot to Qt software stack, you must closely follow the instructions in this section and perform all the described tasks.

In case of problems, see Troubleshooting.

Note: After you have installed the Boot to Qt software stack and want to connect to the target device with SSH or a serial cable, you can access the device by using the user root and an empty password.

1. Requirements for Development Host

Before you install the Boot to Qt software stack, you should install the required software on the development host:

2. Installing Boot to Qt Software Stack

The Boot to Qt software stack is available as a Qt Board Support Package (QBSP) that can be installed with the MaintenanceTool application or directly from the Qt online installer.

  • Download the QBSP file from the Qt Account Downloads page. QBSP files have either a .qbsp or .7z extension.
  • Start the MaintenanceTool application and select Add or Remove Components.
  • Select Browse QBSP Files, locate the downloaded file, and select Open.
  • The Select Components view is updated with content from the QBSP.

Select the Boot to Qt software stack for Boundary Devices i.MX6 with the following steps:

  • Select Qt > Qt for Device Creation.
  • Select the Boot to Qt software stack version.
  • Select Boundary Devices i.MX6.
  • Select Next.

To finish the installation, follow the instructions in the installation wizard.

Installation Content

The Boot to Qt software stack provides a system image (<target-device> Linux System) and a toolchain (<target-device> Linux Toolchain) for each target device. The system image contains the Boot to Qt software stack and needs to be flashed to the SD card or directly to the target device (see 3. Installing Boot to Qt on Target Device). building and developing applications for the target devices.

Note: Building the Boot to Qt system image and toolchain are not supported on Windows. Thus the sources of the Boot to Qt software stack are available only via the Linux online installer.

General Installation Issues for Linux

On Linux, remember to allow the execution of the installer binary. You can do this by using one of the following methods:

  • On the command line enter the chmod +x <filename> command.
  • Right-click the file, and select Properties > Permissions > Allow executing file as program.

Note: Do not execute the installer as a root user or with sudo.

Installation Directory

The installer will let you select a directory where the Boot to Qt software stack will be installed. In this documentation, the installation directory is referred to as <INSTALL_DIR>. The default installation directories are:

  • ~/Qt on Linux
  • C:\Qt on Windows

3. Installing Boot to Qt on Target Device

Before you can test your Qt applications on the target device, you must flash the target device with an image containing the Boot to Qt software stack.

Flash your Boundary Devices i.MX6 Boards with Flashing Wizard:

  • Connect your SD card reader to the development host. Make sure that the SD card size is at least 2 GB.
  • Launch Qt Creator.
  • Select Tools > Flash Boot to Qt Device, and follow the instructions in Flashing Wizard.

After flashing the device, you may need to update U-Boot:

Note: Sometimes U-Boot fails to select a suitable display for your target device and sets an incorrect display resolution. Configuring Display Resolution instructs how you can configure the display and resolution used in your target device.

Updating U-Boot

If you are updating from an older image, you may also need to update the version of U-Boot on the device.

The prebuilt image already contains U-Boot versions for most of the device variants from Boundary Devices, but the update needs to be done manually when first starting the device. Correct device type is selected by setting the uboot_defconfig U-Boot environment variable.

More information available from Boundary Devices.

Access the device's console and run the following commands on the U-Boot prompt:

setenv uboot_defconfig <device type>
setenv devnum 1 # or 0, if using SD slot
setenv devtype mmc
run upgradeu

Reset or power cycle the device to start the new U-Boot. To reset the U-Boot environment to new default values, enter the following commands in the U-Boot command line:

env default -a
saveenv

Setup for Nitrogen6_Lite Device

The boot script requires the environment variables, dtbname and gpumem, to identify the device as Nitrogen6_Lite. Otherwise, the device is booted with the default GPU memory setting of 512MiB, which is more than what is available on the Nitrogen_Lite devices (128MibB).

Use one of the two following options to enable the scripts boot the device with correct GPU memory setting:

  • Write a uEnv.txt file on to the boot partition of SD card with the following content:
    gpumem=67108864
    dtbname=imx6dl-nit6xlite.dtb
  • Access the device's console and run the following commands on the U-Boot prompt:
    U-Boot > setenv gpumem 67108864
    U-Boot > setenv dtbname imx6dl-nit6xlite.dtb
    U-Boot > saveenv

4. Configuring a Device Kit in Qt Creator

After you have prepared the target device, you must set up the development tools in Qt Creator for your device. That is, you must configure your target device to be used for each build and run kit.

Connect your device to the development host via USB and launch Qt Creator. In Qt Creator:

  1. Select Tools > Options > Build & Run > Kits.
  2. Select one of the predefined kits starting with Boot to Qt... that matches the type of your device.
  3. Select the correct device in the Device field.
  4. Select OK.

You are now ready to start developing with Qt for your device. For detailed information about how to deploy Qt projects to the device, see Tutorial: Deploying Your First Project with Boot to Qt.

Available under certain Qt licenses.
Find out more.