diff options
Diffstat (limited to 'src/doc/src/devices')
-rw-r--r-- | src/doc/src/devices/qtee-bd-sl-imx6.qdoc | 137 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-beaglebone-black.qdoc | 80 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-imx53.qdoc | 70 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-kontron-smarc-samx6i.qdoc | 88 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-raspberry-pi.qdoc | 66 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-sabre-sd-imx6.qdoc | 71 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-supported-devices.qdoc | 343 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-toradex-apalis.qdoc | 106 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-toradex-colibri-imx6.qdoc | 99 | ||||
-rw-r--r-- | src/doc/src/devices/qtee-toradex-colibri-vf.qdoc | 110 |
10 files changed, 0 insertions, 1170 deletions
diff --git a/src/doc/src/devices/qtee-bd-sl-imx6.qdoc b/src/doc/src/devices/qtee-bd-sl-imx6.qdoc deleted file mode 100644 index d958660..0000000 --- a/src/doc/src/devices/qtee-bd-sl-imx6.qdoc +++ /dev/null @@ -1,137 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \page qtee-preparing-hardware-imx6.html - \title Boundary Devices i.MX6 Boards - \previouspage qtee-installation-guide.html - - Take the following steps when preparing these boards for \B2Q: - - \list - \li \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/} - {Boundary Devices BD-SL-i.MX6 (SABRE Lite)} - \li \l{http://boundarydevices.com/product/nitrogen6x-copy/} - {Boundary Devices Nitrogen6X} - \li \l{http://boundarydevices.com/product/nitrogen6_lite/} - {Boundary Devices Nitrogen6_Lite} - \li \l{http://boundarydevices.com/product/nitrogen6max/} - {Boundary Devices Nitrogen6_MAX} - \li \l{http://boundarydevices.com/product/nitrogen6x-som/} - {Boundary Devices Nitrogen6X_SOM} - \endlist - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for the device are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - For \B2QL, an SD card of at least 1 GB capacity is needed. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - Make sure you have the required tools installed in your development machine: - - \badcode - sudo apt-get install u-boot-tools - \endcode - - Then, upgrade the SD card with \B2Q. First, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, use the following command to install the embedded Linux image: - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/nitrogen6x/images/b2qt-embedded-qt5-image-nitrogen6x.img of=/dev/<device_name> - \endcode - - After the installation is complete, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \b {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 \c uboot_defconfig U-Boot environment variable. More information available from - \l{https://boundarydevices.com/compiling-latest-u-boot-for-i-mx6-2015-edition/}{Boundary Devices}. - - Access the device's console and run the following commands on the U-Boot prompt: - - \badcode - setenv uboot_defconfig <device type> - run upgradeu - \endcode - - 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 - - \badcode - env default -a - saveenv - \endcode - - \b {Setup for Nitrogen6_Lite Device} - - The boot script requires the environment variables, \c dtbname and \c 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: - - \list - \li Write a \c uEnv.txt file on to the boot partition of SD card with the following - content: - - \badcode - gpumem=67108864 - dtbname=imx6dl-nit6xlite.dtb - \endcode - - \li Access the device's console and run the following commands on the U-Boot prompt: - \badcode - U-Boot > setenv gpumem 67108864 - U-Boot > setenv dtbname imx6dl-nit6xlite.dtb - U-Boot > saveenv - \endcode - \endlist - - \section1 Setting up USB Access - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit linux - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-beaglebone-black.qdoc b/src/doc/src/devices/qtee-beaglebone-black.qdoc deleted file mode 100644 index b0ea563..0000000 --- a/src/doc/src/devices/qtee-beaglebone-black.qdoc +++ /dev/null @@ -1,80 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword BeagleBone Black - \page qtee-preparing-hardware-beaglebone.html - \title Preparing BeagleBone Black - \previouspage qtee-installation-guide.html - - Take the following steps to prepare a - \l{http://beagleboard.org/products/beaglebone%20black}{BeagleBone Black} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for BeagleBone Black are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - First, ensure that no partitions on the SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, use the following command: - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/beaglebone/images/b2qt-embedded-qt5-image-beaglebone.img of=/dev/<device_name> - \endcode - - After the installation is complete, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Setting up USB Access - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \b {Windows 7 and 8 users:} - If the device is not showing in ADB and Windows Device Manager lists the device under Other Devices, try the following: - \list 1 - \li Install the latest Samsung ADB drivers from \l {http://developer.samsung.com/technical-doc/view.do?v=T000000117} {Samsung Developers site}. - \li Restart the computer. The drivers might not show up if the computer is not restarted. - \li Go to \e {Device Manager}, find your device and select \e {Update Driver Software}. - \li Select \e {Browse my computer for driver software} and then \e {Let me pick from a list of device drivers on my computer}. - \li Select \e {ADB Interface} from the list, click \e {Next} and select \e {SAMSUNG Android ADB Interface}. If there is no ADB Interface in the list, - select \e {Show All Devices}, select \e {Samsung} from manufacturer list and select \e {SAMSUNG Android ADB Interface}. - \li The device should be working now. - \endlist - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-imx53.qdoc b/src/doc/src/devices/qtee-imx53.qdoc deleted file mode 100644 index a6108cf..0000000 --- a/src/doc/src/devices/qtee-imx53.qdoc +++ /dev/null @@ -1,70 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword i.MX53 Quick Start Board - \page qtee-preparing-hardware-imx53qsb.html - \title Preparing i.MX53 Quick Start Board - \previouspage qtee-installation-guide.html - \nextpage qtee-building-and-running.html - - Take the following steps to prepare a - \l{http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB} {i.MX53 Quick Start Board} - for \B2Q. - - \note Ethernet networking is required to connect the device to Qt Creator. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - As i.MX53 Quick Start Board is not a \SDK reference board, there is no ready-made - image containing a \B2Q stack available. Instead, you must build it yourself using - the Yocto recipes and build scripts from the \B2Q source packages. - For more information, see \l{Building Your Own Embedded Linux Image}. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, - - \badcode - cd <QtBuildDir> - sudo deploy.sh /dev/<device_name> - \endcode - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring network device - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ - diff --git a/src/doc/src/devices/qtee-kontron-smarc-samx6i.qdoc b/src/doc/src/devices/qtee-kontron-smarc-samx6i.qdoc deleted file mode 100644 index f64b264..0000000 --- a/src/doc/src/devices/qtee-kontron-smarc-samx6i.qdoc +++ /dev/null @@ -1,88 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword Kontron SMARC-sAMX6i - \page qtee-preparing-hardware-smarc-samx6i.html - \title Preparing Kontron SMARC-sAMX6i - \previouspage qtee-installation-guide.html - - Take the following steps to prepare a - \l{http://www.kontron.com/products/boards-and-standard-form-factors/smarc/smarc-samx6i.html} - {Kontron SMARC-sAMX6i} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for Kontron SMARC-sAMX6i are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/smarc-samx6i/images/b2qt-embedded-qt5-image-smarc-samx6i.img of=/dev/<device_name> - \endcode - - By default, the Kontron SMARC-sAMX6i boots from its internal eMMC. In order to boot from - the external SD card, the U-Boot environment needs to be updated. Connect a serial cable - to the device and enter into the U-Boot environment by pressing any key before the autoboot. - Enter following commands into U-Boot: - - \badcode - setenv mmcdev 1 - setenv mmcpart 2 - setenv bootcmd 'mmc dev ${mmcdev}; if mmc rescan; then if run loadfdt; then if run loaduimage; then run mmcboot; else run netboot; fi; else run netboot; fi; else run netboot; fi;' - setenv uimage /boot/uImage - setenv fdtfile /boot/imx6q-smx6-lcd.dtb - setenv mmcroot /dev/mmcblk2p2 rootwait rw - setenv mmcargs 'setenv bootargs video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 fbmem=28M console=${console},${baudrate} root=${mmcroot}' - saveenv - \endcode - - New U-Boot commands are now stored into the device, and you can start \B2Q. - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Setting up USB Access - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-raspberry-pi.qdoc b/src/doc/src/devices/qtee-raspberry-pi.qdoc deleted file mode 100644 index d634be2..0000000 --- a/src/doc/src/devices/qtee-raspberry-pi.qdoc +++ /dev/null @@ -1,66 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword Raspberry Pi 3 Model B - \page qtee-preparing-hardware-rasberrypi.html - \title Preparing Raspberry Pi 3 - \previouspage qtee-installation-guide.html - \nextpage qtee-building-and-running.html - - Take the following steps to prepare a \l{https://www.raspberrypi.org/products/raspberry-pi-3-model-b/} - {Raspberry Pi 3} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The image containing \B2Q stack for Raspberry Pi 3 is included in the SDK, - ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, enter the following command to deploy the image: - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/raspberrypi3/images/b2qt-embedded-qt5-image-raspberrypi3.img of=/dev/<device_name> - \endcode - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring network device - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-sabre-sd-imx6.qdoc b/src/doc/src/devices/qtee-sabre-sd-imx6.qdoc deleted file mode 100644 index cac6bda..0000000 --- a/src/doc/src/devices/qtee-sabre-sd-imx6.qdoc +++ /dev/null @@ -1,71 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword SABRE SD i.MX6Quad - \page qtee-preparing-hardware-imx6sabresd.html - \title Preparing SABRE SD i.MX6Quad - \previouspage qtee-installation-guide.html - - Take the following steps to prepare - \l {http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREBRD} - {Freescale SABRE SD i.MX6Quad} for \B2Q: - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for the above devices are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - To deploy the image, enter the following commands: - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/imx6qsabresd/images/b2qt-embedded-qt5-image-imx6qsabresd.img of=/dev/<device_name> - \endcode - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Setting up USB Access - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ - diff --git a/src/doc/src/devices/qtee-supported-devices.qdoc b/src/doc/src/devices/qtee-supported-devices.qdoc deleted file mode 100644 index f4acda9..0000000 --- a/src/doc/src/devices/qtee-supported-devices.qdoc +++ /dev/null @@ -1,343 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ - -/*! - \page qtee-preparing-hardware.html - \title Preparing Hardware - \previouspage qtee-supported-platforms.html - \nextpage qtee-building-and-running.html - - Before you can deploy and test your Qt application on hardware, you must - flash the target device with an image that contains the - \B2Q stack. These steps vary from device to device: - - \list - \li \l{Boundary Devices i.MX6 Boards} - \li \l{SABRE SD i.MX6Quad} - \li \l{Toradex Apalis iMX6} - \li \l{Toradex Colibri iMX6} - \li \l{Toradex Colibri VF50 and VF61} - \li \l{Kontron SMARC-sAMX6i} - \li \l{BeagleBone Black} - \li \l{Raspberry Pi 3 Model B} - \li \l{Intel NUC} - \li \l{NVIDIA DRIVE CX} - \endlist - - If you use only the emulator, you can skip this step - and continue straight to \l {Building and Running an Example}. -*/ - -/*! - \page qtee-supported-platforms.html - \title Supported Platforms - \previouspage qtee-installation-guide.html - \nextpage qtee-preparing-hardware.html - - \section1 Supported Reference Devices - - The \B2Q stack can be made to run on a variety of hardware. For \SDK license - holders, tooling is provided to customize the contents of the stack as well - as to take it into desired production hardware. For more information on how - to customize the stack for embedded Linux, see - \l {Building Your Own Embedded Linux Image}. - - Approximate minimal hardware requirements for running \B2Q are: - \list - \li 256 MB of RAM - \li 500 MHz CPU, 1 GHz preferred for 60-FPS velvet-smooth UI - \li OpenGL ES 2.0 support * - \endlist - - * On GPU-less hardware, \l {Qt Quick 2D Renderer} can replace the - OpenGL ES 2.0 requirement (with some limitations on graphics capabilities). - - \section1 Support Lifecycle Policy - - The Qt Company will continue providing support for this release of \SDK - two years after the release date of a version that supercedes it. - - Release dates and support end-of-life dates for each version are listed - in the ChangeLog. - - \section2 Emulator Support - - Support for the emulator is limited to the \SDK release and pre-compiled - emulator images it shipped with. Using the emulator application to run - images from previous releases is not supported. - - \section1 Supported Device Groups - - The reference devices are divided into three groups, based on level - of support The Qt Company provides for the device: - - \section2 Group 1 - - Qt is fully supported unless otherwise stated due to limitations on the - platform level. Support can help with any issues relating to the Qt - libraries and tools, but not the third party elements. Any problems found - need to be reproducible with Qt libraries for further investigation by - the support team. - - Pre-compiled embedded Linux images for group 1 devices are available via - the Qt online installer. - - \table - \header \li Devices with GPU - \row \li \l{http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREBRD} - {Freescale® SABRE SD i.MX6Quad} (Freescale® i.MX6)\br - 4x ARM Cortex A9, Vivante GC2000 GPU, 1GB RAM - \row \li \l{http://beagleboard.org/products/beaglebone%20black} - {BeagleBone Black}\br - TIAM335x 1GHz ARM® Cortex-A8, 512 MB RAM - \row \li \b{\B2Q Emulator}\br - Included in the development environment - \header \li Devices with GPU (Qt Automotive) - \row \li \l{http://www.nvidia.com/object/drive-cx.html} - {NVIDIA DRIVE™ CX}\br - Tegra X1 - \header \li Devices Without GPU - \row \li \l{https://www.toradex.com/products/colibri-arm-computer-modules/freescale-vybrid-VF6xx-computer-module} - {Toradex Colibri VF61}\br - Dual-core (ARM Cortex-A5 + ARM Cortex-M4)\br - solution with 1 MB on-chip SRAM - \row \li \l{https://www.toradex.com/products/colibri-arm-computer-modules/freescale-vybrid-VF5xx-computer-module} - {Toradex Colibri VF50}\br - Single-core (ARM Cortex-A5) solution with 1.5 MB on-chip SRAM - \endtable - - \section2 Group 2 - - Qt is fully supported unless otherwise stated due to limitations on the - platform level. Support can help with any issues relating to the Qt - libraries and tools, but not the third party elements. Any problems found - need to be reproducible with Qt libraries. - - If an issue is reproducible on either the desktop or a group 1 platform, - then it will be investigated further by the support team. Otherwise, a - bug report will be created, to be handled by the party responsible for the - Qt port to the platform. - - Pre-compiled images for group 2 devices are available via the Qt - online installer. - - \table - \header \li Devices with GPU - \row \li \l{http://boundarydevices.com/product-selector-guide/} - {Boundary Devices i.MX6 Boards}\br - Freescale® i.MX 6 based devices with\br - Vivante GC880 or GC2000 GPU - \row \li \l{http://www.toradex.com/products/apalis-arm-computer-modules/freescale-imx-6-computer-module} - {Toradex Apalis iMX6}\br - Freescale® i.MX 6Q ARM Cortex™-A9 @1 GHz,\br - 1GB DDR3, 4GB eMMC, Vivante GC2000 GPU - \row \li \l{http://developer.toradex.com/product-selector/colibri-imx6} - {Toradex Colibri iMX6}\br - Freescale® i.MX6S or i.MX6DL ARM Cortex™-A9 @800MHz - 1GHz,\br - 256MB (single core), 512MB (dual core) DDR3, 4GB eMMC,\br - Vivante 2D/3D GPU - \row \li \l{http://www.kontron.com/products/boards-and-standard-form-factors/smarc/smarc-samx6i.html} - {Kontron SMARC-sAMX6i}\br - Freescale® i.MX 6 ARM Cortex™-A9 @800MHz - 1.2GHz,\br - 2GB DDR3, 2-64GB eMMC, Vivante GC2000 GPU - \row \li \l{https://www.raspberrypi.org/products/raspberry-pi-3-model-b/} - {Raspberry Pi 3 Model B}\br - 1.2 Ghz ARM Cortex™-A53, Broadcom VideoCore IV\br - @400MHz GPU, 1GB LPDDR2 SDRAM - \row \li \l {http://www.intel.com/content/www/us/en/nuc/overview.html} - {Intel® NUC}\br - Intel® Core i3, i5, or i7\br - Up to 32GB DDR4\br - Intel® Iris™ Graphics - \endtable - - \section2 Group 3 - - No support provided. If a Qt related problem is found and reproducible with - the Qt libraries on either desktop or a group 1 platform then it will be - investigated further by the support team. - - To use these devices, you need to build images by yourself or contact - The Qt Company for consultancy services. - - \table - \header \li Device - \row \li \l{http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREBRD} - {Freescale® SABRE SD i.MX6Dual} (Freescale® i.MX6)\br - 2x ARM Cortex A9, Vivante GC2000 GPU, 1GB RAM - \row \li \l{http://beagleboard.org/hardware-xM} - {BeagleBoard-xM}\br - 1GHz ARM Cortex A8, PowerVR SGX530 GPU,\br - 512MB RAM - \row \li \l{http://processors.wiki.ti.com/index.php/AM335x_Starter_Kit} - {Sitara AM335x Starter Kit}\br - 720 MHZ ARM Cortex™-A8 Starter Kit\br - with 4.3-inch LCD touchscreen - \row \li \l{http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX53QSB} - {Freescale® iMX53 Quick Start Board}\br - 1GHz ARM Cortex™-A8 - \row \li \l{https://www.raspberrypi.org/products/model-b/} - {Raspberry Pi Model B}\br - 700 Mhz ARM11, Broadcom VideoCore IV\br - @250MHz GPU, 512 MB (shared with GPU) RAM - \row \li \l{https://www.raspberrypi.org/products/raspberry-pi-2-model-b/} - {Raspberry Pi 2 Model B}\br - 900 Mhz ARM Cortex™-A7, Broadcom VideoCore IV\br - @250MHz GPU, 1GB LPDDR2 SDRAM - \endtable - - \section2 Supported Features on Reference Devices - - The following features are supported without any modification on the - pre-built images available for the reference devices: - - \table - \header \li Device - \li Touchscreen - \li ADB via Network - \li ADB via USB - \li HDMI - \li HW Accelerated \br Video Playback - \li Virtual Keyboard - \li B2Qt WiFi Module - \li B2Qt Utils Module - \li OpenGL ES 2.0 - \li Qt Quick \br 2D Renderer - - \header \li Group 1 \li \li \li \li \li \li \li \li \li \li - \row \li Freescale SABRE SD i.MX6 - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li BeagleBone Black - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li Toradex Colibri VF61 - \li \image ok - \li \image ok - \li \image ok - \li - \li - \li \image ok - \li \image ok - \li \image ok - \li - \li \image ok - \row \li Toradex Colibri VF50 - \li \image ok - \li \image ok - \li \image ok - \li - \li - \li \image ok - \li \image ok - \li \image ok - \li - \li \image ok - \row \li NVIDIA DRIVE CX - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \header \li Group 2 \li \li \li \li \li \li \li \li \li \li - \row \li Boundary Devices i.MX6 Boards - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li Toradex Apalis/Colibri i.MX6 - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li Kontron SMARC-sAMX6i - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li Raspberry Pi 3 - \li \image ok - \li \image ok - \li - \li \image ok - \li - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \row \li Intel NUC - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li \image ok - \li - \endtable - - \section1 Supported Development Environment - - The development environment supported by \SDK is Ubuntu Linux 64-bit (12.04 LTS or later). - - \sa {Requirements for Development Host} - -*/ diff --git a/src/doc/src/devices/qtee-toradex-apalis.qdoc b/src/doc/src/devices/qtee-toradex-apalis.qdoc deleted file mode 100644 index 84fa350..0000000 --- a/src/doc/src/devices/qtee-toradex-apalis.qdoc +++ /dev/null @@ -1,106 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword Toradex Apalis iMX6 - \page qtee-preparing-hardware-apalis-imx6.html - \title Preparing Toradex Apalis iMX6 - \previouspage qtee-installation-guide.html - - Take the following steps to prepare a - \l{http://www.toradex.com/products/apalis-arm-computer-modules/freescale-imx-6-computer-module} - {Toradex Apalis iMX6} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for Toradex Apalis iMX6 are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/apalis-imx6/images/b2qt-embedded-qt5-image-apalis-imx6.img of=/dev/<device_name> - \endcode - - By default, the Toradex Apalis iMX6 boots from its internal eMMC. In order to boot from - the external SD card, the U-Boot needs to be updated. Connect a serial cable - to the device and enter into the U-Boot environment by pressing any key before the autoboot. - Enter following commands into U-Boot: - - \badcode - setenv drive 2 - setenv setupdate 'fatload mmc ${drive}:1 ${loadaddr} flash_mmc.img; source' - - run setupdate - run update_uboot - \endcode - - 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 - - \badcode - env default -a - saveenv - \endcode - - - New U-Boot commands are now stored into the device, and you can start \B2Q. For more information - about the boot process on Toredex Apalis iMX6, see - \l{http://developer.toradex.com/software-resources/arm-family/linux/linux-booting}{Toradex Linux Booting}. - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Setting up USB Access - - The \e {Ixora Carrier Board} on Toradex Apalis iMX6 includes a USB 2.0 port - that can be used for an \c adb connection between the device and the - development host, provided it's configured for USB OTG. To enable USB OTG - connectivity, ensure that jumper JP2, located next to the USB ports, is open. - - For more information, see datasheet for - \l{https://www.toradex.com/products/carrier-boards/ixora-carrier-board} - {Ixora Carrier Board}. - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-toradex-colibri-imx6.qdoc b/src/doc/src/devices/qtee-toradex-colibri-imx6.qdoc deleted file mode 100644 index f6a035b..0000000 --- a/src/doc/src/devices/qtee-toradex-colibri-imx6.qdoc +++ /dev/null @@ -1,99 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword Toradex Colibri iMX6 - \page qtee-preparing-hardware-colibri-imx6.html - \title Preparing Toradex Colibri iMX6 - \previouspage qtee-installation-guide.html - - Take the following steps to prepare a - \l{http://developer.toradex.com/product-selector/colibri-imx6} - {Toradex Colibri iMX6} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for Toradex Colibri iMX6 are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/colibri-imx6/images/b2qt-embedded-qt5-image-colibri-imx6.img of=/dev/<device_name> - \endcode - - By default, the Toradex Colibri iMX6 boots from its internal eMMC. In order to boot from - the external SD card, the U-Boot needs to be updated. Connect a serial cable - to the device and enter into the U-Boot environment by pressing any key before the autoboot. - Enter following commands into U-Boot: - - \badcode - run setupdate - run update_uboot - \endcode - - 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 - - \badcode - env default -a - saveenv - \endcode - - - New U-Boot commands are now stored into the device, and you can start \B2Q. For more information - about the boot process on Toradex Colibri iMX6, see - \l{http://developer.toradex.com/software-resources/arm-family/linux/linux-booting}{Toradex Linux Booting}. - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Setting up USB Access - - The \l {http://developer.toradex.com/hardware-resources/arm-family/colibri-carrier-boards} - {carrier boards} for Toradex Colibri iMX6 include a USB 2.0 port - that can be used for an \c adb connection between the device and the - development host. - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ diff --git a/src/doc/src/devices/qtee-toradex-colibri-vf.qdoc b/src/doc/src/devices/qtee-toradex-colibri-vf.qdoc deleted file mode 100644 index 55d8122..0000000 --- a/src/doc/src/devices/qtee-toradex-colibri-vf.qdoc +++ /dev/null @@ -1,110 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2014 Digia Plc -** All rights reserved. -** For any questions to Digia, please use the contact form at -** http://www.qt.io -** -** This file is part of Qt Enterprise Embedded. -** -** Licensees holding valid Qt Enterprise licenses may use this file in -** accordance with the Qt Enterprise License Agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and Digia. -** -** If you have questions regarding the use of this file, please use -** the contact form at http://www.qt.io -** -****************************************************************************/ -/*! - \keyword Toradex Colibri VF50 and VF61 - \page qtee-preparing-hardware-colibri-vf.html - \title Preparing Toradex Colibri VF50 and VF61 - \previouspage qtee-installation-guide.html - - Take the following steps to prepare a - \l{https://www.toradex.com/products/colibri-arm-computer-modules/freescale-vybrid-VF6xx-computer-module} - {Toradex Colibri VF61} or - \l{https://www.toradex.com/products/colibri-arm-computer-modules/freescale-vybrid-VF5xx-computer-module} - {Toradex Colibri VF50} for \B2Q. - - \note It is important that you repeat the steps in this section after you - update \SDK. - - The images containing the \B2Q stack for Toradex Colibri-VF devices are included - in \SDK, ready to be copied to an SD card. - - \section1 Preparing an SD Card - - An SD card of at least 1 GB capacity is sufficient. - - \include detect-sd-card-device-name.qdocinc instructions - - \section1 Installing the \B2Q Image - - \include common.qdocinc wizard - - To write the image to the SD card, ensure that no partitions on the - SD card are mounted: - - \include detect-sd-card-device-name.qdocinc unmount - - Then, - - \badcode - cd <INSTALL_DIR> - sudo dd bs=4k if=5.7/Boot2Qt/colibri-vf/images/b2qt-embedded-qt5-image-colibri-vf.img of=/dev/<device_name> - \endcode - - By default, the Toradex Colibri VF devices boot from their internal NAND memory. In order to boot from - an external SD card, the U-Boot needs to be modified. Connect a serial cable - to the device and enter into the U-Boot environment by pressing any key before the autoboot. - Enter following commands into U-Boot: - - \badcode - run setupdate - run update_uboot - \endcode - - Reset or power cycle the device to continue. - To reset the U-Boot environment to new default values, enter the following commands - in the U-Boot command line - - \badcode - env default -a - saveenv - \endcode - - - New U-Boot commands are now stored into the device, and you can start \B2Q. For more information - about the boot process on Toradex Colibri iMX6, see - \l{http://developer.toradex.com/software-resources/arm-family/linux/linux-booting}{Toradex Linux Booting}. - - After the image has been deployed, insert the SD card, power on the device and check that - the \B2Q welcome screen and/or demo appear. - - \section1 Using the Toradex Capacitive Multi-Touch Adapter - - It is possible to use the \l{http://developer.toradex.com/product-selector/capacitive-multi-touch-display} - {Toradex Capacitive Multi-Touch Adapter} with \B2Q. First follow the instuctions for setting up - your screen \l{http://developer.toradex.com/knowledge-base/capacitive-multi-touch-display-(linux)} - {here}. To enable touch support for your screen in \B2Q append the following lines to /etc/appcontroller.conf and uncomment line for the VF module being used. - - \badcode - #VF50 - #env=QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event1 - #VF61 - env=QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event0 - \endcode - - \section1 Setting up USB Access - - \include b2qt-post-install-setup.qdocinc setting up usb access - - \section1 Configuring a Device Kit in Qt Creator - - \include b2qt-post-install-setup.qdocinc configuring device kit - - You are now ready to start developing for your device. For more information, - see \l{Building and Running an Example}. -*/ |