Intel NUC

Take the following steps when preparing an Intel NUC for Boot to Qt:

Note: It is important that you repeat the steps in this section after you update Qt for Device Creation.

The images containing the Boot to Qt stack for the device are included in Qt for Device Creation. In these instructions, we prepare a USB device (a flash drive or an external USB hard drive) to boot from.

Preparing a USB Boot Device

For Boot to Qt, a USB drive of at least 2 GB capacity is needed.

Plug in the USB storage device to the development host, and use the following command on Linux to find out its device name:

lsblk -d

Removable devices such as flash drives have the value '1' in the RM column. The full device path is /dev/ followed by the name.

On Windows, use the following command to get the device name:

wmic logicaldisk where "drivetype=2 and access=0" get deviceid, volumename

Warning: Make sure to select the correct device, because selecting the wrong one can result in a wiped hard drive.

Installing the Boot to Qt Image

Install Using the Flashing Wizard

Qt for Device Creation includes an easy to use application for setting up a supported device for Boot to Qt. In Qt Creator, select Tools > Flash Boot to Qt Device and follow the step-by-step instructions.

On Linux, you can alternatively install the image from the command line using the instructions below.

Install from the Command Line

Install the Boot to Qt image onto the USB device. First, ensure that no partitions are mounted:

umount /dev/<device_name>

Then, use the following command to install the image:

sudo dd bs=4k if=5.7/Automotive/intel-corei7-64/images/b2qt-embedded-qt5-image-intel-corei7-64.img of=/dev/<device_name>

After the installation is complete, connect the USB drive to the device, power it on, and enter the BIOS setup (F2). Follow the instructions on Operating System Installation for Intel® NUC for how to select the USB drive as a boot device.

Press F10 to save your changes and exit BIOS setup. After reboot, check that the Boot to Qt welcome screen and/or demo appear.

Setting up USB Access

On Ubuntu Linux, the development user account must have access to plugged in devices. To allow the development user access to the device via USB, create a new udev rule:

  1. Run the following command in a shell:
    echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", TAG+="udev-acl", TAG+="uaccess"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules
  2. Connect the running device to the development host with a USB cable. If the device is already connected, disconnect and reconnect the USB cable after running the command above.

The system log files /var/log/udev and /var/log/syslog may provide relevant information in case of connection problems.

You can confirm that the connection is working by running the following command on Linux:

<INSTALL_DIR>/Tools/b2qt/adb devices -l

Or the following command on Windows:

<Android-SDK-Tools-install-dir>\platform-tools\adb.exe devices -l

The output should be a list of connected Boot to Qt (and Android) devices, identified with a serial number and a name. If your device is missing from the list, or the serial number is ??????, the connection is not working properly. Check that the device is powered on, and disconnect and reconnect the USB cable.

The emulator may be listed as well. Its serial number is its IP and the port number:

Configuring a Device Kit in Qt Creator

After you have prepared the hardware, you must perform one final step to set up the development tools in Qt Creator for your device. That is, you must configure the correct 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 for your device. For more information, see Building and Running an Example.

Available under certain Qt licenses.
Find out more.