summaryrefslogtreecommitdiffstats
path: root/src/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'src/doc/src')
-rw-r--r--src/doc/src/devices/qtee-bd-sl-imx6.qdoc59
-rw-r--r--src/doc/src/devices/qtee-nexus-7.qdoc105
-rw-r--r--src/doc/src/devices/qtee-supported-devices.qdoc77
-rw-r--r--src/doc/src/qtee-changelog.qdoc3
-rw-r--r--src/doc/src/qtee-customization.qdoc26
-rw-r--r--src/doc/src/qtee-index.qdoc71
-rw-r--r--src/doc/src/qtee-install-guide.qdoc2
-rw-r--r--src/doc/src/qtee-licenses.qdoc27
-rw-r--r--src/doc/src/qtee-troubleshooting.qdoc123
-rw-r--r--src/doc/src/shared/b2qt-post-install-setup.qdocinc35
10 files changed, 52 insertions, 476 deletions
diff --git a/src/doc/src/devices/qtee-bd-sl-imx6.qdoc b/src/doc/src/devices/qtee-bd-sl-imx6.qdoc
index e94835b..68f32cd 100644
--- a/src/doc/src/devices/qtee-bd-sl-imx6.qdoc
+++ b/src/doc/src/devices/qtee-bd-sl-imx6.qdoc
@@ -26,15 +26,14 @@
\list
\li \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}
{Boundary Devices BD-SL-i.MX6 (SABRE Lite)}
- (embedded Android and Linux)
\li \l{http://boundarydevices.com/product/nitrogen6x-copy/}
- {Boundary Devices Nitrogen6X} (embedded Linux only)
+ {Boundary Devices Nitrogen6X}
\li \l{http://boundarydevices.com/product/nitrogen6_lite/}
- {Boundary Devices Nitrogen6_Lite} (embedded Linux only)
+ {Boundary Devices Nitrogen6_Lite}
\li \l{http://boundarydevices.com/product/nitrogen6max/}
- {Boundary Devices Nitrogen6_MAX} (embedded Linux only)
+ {Boundary Devices Nitrogen6_MAX}
\li \l{http://boundarydevices.com/product/nitrogen6x-som/}
- {Boundary Devices Nitrogen6X_SOM} (embedded Linux only)
+ {Boundary Devices Nitrogen6X_SOM}
\endlist
\note It is important that you repeat the steps in this section after you
@@ -45,37 +44,10 @@
\section1 Preparing an SD Card
- For \B2QA, an SD card of at least 4 GB capacity is needed. For \B2QL,
- a card of at least 1 GB capacity is sufficient.
+ For \B2QL, an SD card of at least 1 GB capacity is needed.
\include detect-sd-card-device-name.qdocinc instructions
- \section1 Installing the Android Image
-
- \e{If installing} \B2QL, \e{you can skip this step and proceed to}
- \l{#Installing the Boot to Qt Image}{Installing the Boot to Qt Image}.
-
- Download the package \e{imx6-jb-20130628.tar.gz} from
- \l{http://boundarydevices.com/android-jellybean-on-i-mx6-with-no-disclaimers/}{Boundary
- Devices Android Jellybean i.MX6 images} (registration required).
-
- Use the following commands to create an SD card containing the
- downloaded image:
-
- \list 1
- \li Extract the downloaded package:
- \badcode
- ~/$ mkdir bd-android
- ~/$ cd bd-android
- ~/bd-android$ tar zxvf ~/Downloads/imx6-jb-20130628.tar.gz
- \endcode
- \li Run device/boundary/mksdcard.sh:
- \badcode
- ~/bd-android$ sudo device/boundary/mksdcard.sh /dev/<device_name>
- ~/bd-android$ sync
- \endcode
- \endlist
-
\section1 Installing the \B2Q Image
\include common.qdocinc wizard
@@ -91,21 +63,12 @@
\include detect-sd-card-device-name.qdocinc unmount
- Then, use one of the commands below, depending on whether you are developing
- for embedded Android or Linux:
+ Then, use the following command to install the embedded Linux image:
- \list
- \li \b{\B2QA}
- \badcode
- cd <INSTALL_DIR>
- ./Boot2Qt-4.x/generic-4.2-eAndroid/images/iMX6/deploy.sh /dev/<device_name>
- \endcode
- \li \b{\B2QL}
- \badcode
- cd <INSTALL_DIR>
- sudo ./Boot2Qt-4.x/iMX6-eLinux/images/deploy.sh /dev/<device_name>
- \endcode
- \endlist
+ \badcode
+ cd <INSTALL_DIR>
+ sudo ./Boot2Qt-4.x/iMX6-eLinux/images/deploy.sh /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.
@@ -116,7 +79,7 @@
\section1 Configuring a Device Kit in Qt Creator
- \include b2qt-post-install-setup.qdocinc configuring device kit android linux
+ \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-nexus-7.qdoc b/src/doc/src/devices/qtee-nexus-7.qdoc
deleted file mode 100644
index 54ba445..0000000
--- a/src/doc/src/devices/qtee-nexus-7.qdoc
+++ /dev/null
@@ -1,105 +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
-**
-****************************************************************************/
-/*!
- \target Nexus 7 (2012/2013) (embedded Android)
- \page qtee-preparing-hardware-nexus-7.html
- \title Preparing Nexus 7 (2012/2013)
- \previouspage qtee-installation-guide.html
- \nextpage qtee-building-and-running.html
-
- Take the following steps to prepare a
- \l{http://www.google.com/nexus/7/specs/}{Nexus 7 (2012/2013)} for
- \B2Q.
-
- \note The installation process will wipe the device. Make sure to
- backup any personal data. The device can later be restored to
- factory state, see \l{nexus-factory-reset}{Troubleshooting}.
-
- The Nexus 7 must have the same Android main version (e.g. \c{4.2}
- or \c{4.4}) as the generic \B2Q eAndroid stack that is to be
- installed. If needed, you can update the Android version either by
- using Android's upgrading tool, or by flashing a factory image of
- the right version. See \l{nexus-factory-reset}{Troubleshooting}.
-
- \section1 Enabling Developer Mode
-
- In order to install the \B2Q stack into the Nexus 7, you need to
- enable developer mode and USB debugging. This is only needed for
- the first time install.
-
- \note If for some reason the device does not boot up normally, it
- is also possible to install to a Nexus 7 started up in
- \c{fastboot} (bootloader) mode (see
- \l{nexus-factory-reset}{Troubleshooting}). Just skip this section
- and add the \c{-fastboot} argument to the \c{deploy.sh} command
- below.
-
- \list 1
- \li Power up the device.
- \li Open the \b{Settings} app and select the \b{About tablet} item.
- \li Press the \b{Build number} item seven times, until the message "You are now a developer!" appears.
-
- \li Back in the \b{Settings} menu, select \b{Developer options}.
- \li Press the \b{USB debugging} item and confirm that you allow USB debugging.
- \endlist
-
- You should now be able to establish USB connection to the device as follows.
-
- \section1 Setting up USB Access
-
- \include b2qt-post-install-setup.qdocinc setting up usb access
-
- \section1 Deploying the \B2Q Stack
-
- \include common.qdocinc wizard
-
- Depending on the edition of your Nexus 7 device, use one of the
- commands below to install the \B2Q stack. Replace \c{X.Y} with the
- device's Android version number, for example \c{4.2} or \c{4.4}.
-
- \note The deploy script will check that the connected Nexus device
- is of the expected type and Android version, and abort the
- installation if it is not.
-
- \list
- \li \b{Nexus 7 (2013):}
- \badcode
- cd <INSTALL_DIR>
- ./Boot2Qt-4.x/generic-X.Y-eAndroid/images/nexus7v2/deploy.sh
- \endcode
- \li \b{Nexus 7 (2012):}
- \badcode
- cd <INSTALL_DIR>
- ./Boot2Qt-4.x/generic-X.Y-eAndroid/images/nexus7/deploy.sh
- \endcode
- \endlist
-
- During the installation, the device may ask for confirmation to be
- unlocked. Press the power button once to confirm.
-
- The device will reboot during the process. Do not interact with it
- or unplug it until the process is fully completed.
-
- \section1 Configuring a Device Kit in Qt Creator
-
- \include b2qt-post-install-setup.qdocinc configuring device kit android
-
- 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
index a41a8bd..1b4cd4f 100644
--- a/src/doc/src/devices/qtee-supported-devices.qdoc
+++ b/src/doc/src/devices/qtee-supported-devices.qdoc
@@ -28,7 +28,6 @@
\B2Q stack. These steps vary from device to device:
\list
- \li \l{Nexus 7 (2012/2013) (embedded Android)}
\li \l{Boundary Devices i.MX6 Boards}
\li \l{SABRE SD i.MX6Quad (embedded Linux)}
\li \l{SABRE SD i.MX6Dual (embedded Linux)}
@@ -64,11 +63,6 @@
\li OpenGL ES 2.0 support
\endlist
- \B2QA requires hardware that has support for the Android operating
- system, version 4.2 or later. For rapid prototyping or feasibility testing,
- it is possible to install it on most programmable Android devices using
- \l {Android injection}.
-
\section1 Supported Device Groups
The reference devices are divided into three groups, based on level
@@ -82,43 +76,32 @@
need to be reproducible with Qt libraries for further investigation by
the support team.
- Pre-compiled images for group 1 devices are available via the Qt
- online installer.
+ Pre-compiled embedded Linux images for group 1 devices are available via
+ the Qt online installer.
\table
- \header \li Device \li eLinux \li eAndroid
+ \header \li Devices with GPU \li eLinux
\row \li \l{http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREBRD}
{Freescale® SABRE SD i.MX6} (Freescale® i.MX6)\br
ARM Cortex A9, Vivante GC2000 GPU, 1GB RAM
\li \image ok
- \li
\row \li \l{http://beagleboard.org/products/beaglebone%20black}
{BeagleBone Black}\br
TIAM335x 1GHz ARM® Cortex-A8, 512 MB RAM
\li \image ok
- \li
- \row \li \l{http://www.google.com/nexus/7/specs/}
- {Google Nexus 7 (2013)}\br
- Qualcomm Snapdragon S4 Pro APQ8064–1AA SoC (1.5 GHz\br
- quad-core Krait 300 and an Adreno 320 GPU, clocked at 400 MHz)
- \li
- \li \image ok
\row \li \b{\B2Q Emulator}\br
Included in the development environment
\li \image ok
- \li \image ok
- \header \li Devices Without GPU \li \li
+ \header \li Devices Without GPU \li
\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
\li \image ok
- \li
\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
\li \image ok
- \li
\endtable
\section2 Group 2
@@ -137,37 +120,27 @@
online installer.
\table
- \header \li Device \li eLinux \li eAndroid
- \row \li \l{http://www.google.com/nexus/7/specs/}
- {Google Nexus 7 (2012)}\br
- Nvidia Tegra 3 SoC (1.3 GHz Quad-Core ARM\br
- Cortex A9, Nvidia GeForce ULP GPU, 1GB RAM)
- \li
- \li \image ok
+ \header \li Devices with GPU \li eLinux
\row \li \l{http://boundarydevices.com/product-selector-guide/}
{Boundary Devices i.MX6 Boards}\br
Freescale® i.MX 6 based devices with\br
Vivante GC2000 GPU
\li \image ok
- \li
\row \li \l{http://www.silica.com/product/architech-tibidabo.html}
{SILICA ArchiTech Tibidabo}\br
Freescale® i.MX 6Q ARM Cortex™-A9 @800 MHz,\br
2GB DDR3, 128MB NOR, Vivante GC2000 GPU
\li \image ok
- \li
\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
\li \image ok
- \li
\row \li \l{http://www.raspberrypi.org/faqs}
{Raspberry Pi Model B}\br
700 Mhz ARM11, Broadcom videocode IV\br
@250MHz GPU, 512 MB (shared with GPU) RAM
\li \image ok
- \li
\endtable
\section2 Group 3
@@ -180,13 +153,12 @@
The Qt Company for consultancy services.
\table
- \header \li Device \li eLinux \li eAndroid \li Notes
+ \header \li Device \li eLinux \li Notes
\row \li \l{http://beagleboard.org/hardware-xM}
{BeagleBoard-xM}\br
1GHz ARM Cortex A8, PowerVR SGX530 GPU,\br
512MB RAM
\li \image ok
- \li \image ok
\li
\row \li \l{http://processors.wiki.ti.com/index.php/AM335x_Starter_Kit}
{Sitara AM335x Starter Kit}\br
@@ -194,28 +166,13 @@
with 4.3-inch LCD touchscreen
\li \image ok
\li
- \li
\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
\li \image ok
\li
- \li
- \row \li \l{http://beagleboard.org/products/beaglebone%20black}
- {BeagleBone Black} (eAndroid)\br
- TIAM335x 1GHz ARM® Cortex-A8, 512 MB RAM
- \li
- \li \image ok
- \li eLinux: See \l{Group 1}
\endtable
- \b Notes:
-
- Starting from \B2Q 4.0 release, the embedded Android platform
- is no longer tested and supported on the BeagleBone Black. It is,
- however, still tested and supported in the earlier 3.x releases.
- Also, it possible to install \B2QA on it using \l {Android injection}.
-
\section2 Supported Features on Reference Devices
The following features are supported without any modification on the
@@ -257,17 +214,6 @@
\li \image ok
\li \image ok
\li
- \row \li Google Nexus 7 (2013)
- \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 Colibri VF61
\li \image ok
\li \image ok
@@ -291,17 +237,6 @@
\li
\li \image ok
\header \li Group 2 \li \li \li \li \li \li \li \li \li \li
- \row \li Google Nexus 7 (2012)
- \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 Boundary Devices i.MX6 Boards
\li \image ok
\li \image ok
diff --git a/src/doc/src/qtee-changelog.qdoc b/src/doc/src/qtee-changelog.qdoc
index 9378f1a..8f90948 100644
--- a/src/doc/src/qtee-changelog.qdoc
+++ b/src/doc/src/qtee-changelog.qdoc
@@ -215,8 +215,7 @@
embedded Android and Linux. However, the Emulator target is
currently not supported
\li \l {Qt Quick Compiler} (Technology Preview) was added to the \B2Q stack
- \li \l{Preparing Nexus 7 (2012/2013)}{Nexus 7 (2013)} was added as a
- reference device for embedded Android
+ \li Nexus 7 (2013) was added as a reference device for embedded Android
\li \l{Preparing SABRE SD i.MX6}{Freescale SABRE SD i.MX6Quad} was
added as a reference device for embedded Linux
\li WiFi networking support and configuration were implemented on
diff --git a/src/doc/src/qtee-customization.qdoc b/src/doc/src/qtee-customization.qdoc
index df55528..fa3186c 100644
--- a/src/doc/src/qtee-customization.qdoc
+++ b/src/doc/src/qtee-customization.qdoc
@@ -26,9 +26,8 @@
\section1 Environment and Input
By default, the basic environment variables and startup options of
- \B2Q applications are set in the file \c
- {/system/bin/appcontroller.conf} in embedded Android devices and
- in \c{/etc/appcontroller.conf} in embedded Linux devices.
+ \B2Q applications are set in \c{/etc/appcontroller.conf} on embedded Linux
+ devices.
You can customize this file if you target a hardware device that
has other input devices than the ones that the \B2Q stack is configured
@@ -94,7 +93,7 @@
\li Under \b Deployment, click on \b {Add Deploy Step}, and select
\b {Make this application the default one}.
\li Re-deploy your project. In \b Edit mode, right-click on the
- project and select \b Deploy, or simply click
+ project and select \b Deploy, or click
\inlineimage qtcreator-run.png
(\b{Run}).
\endlist
@@ -106,7 +105,7 @@
<INSTALL_DIR>/Tools/b2qt/adb shell appcontroller --make-default <path>
\endcode
- Above, \c{<path>} is the install path of your application binary on the
+ Where \c{<path>} is the install path of your application binary on the
device.
To remove your application from the default startup, use the following
@@ -223,23 +222,6 @@
}
\endqml
- \section1 Disabling Screen Composer on Embedded Android
-
- By default, the \B2Q stack uses Android's screen composer, \e
- Surfaceflinger. It is required for Qt Multimedia functionality,
- i.e. video playback and camera. If that functionality is not
- required, Surfaceflinger may be disabled. This can in some
- situations improve performance.
-
- \list 1
- \li Edit \c {/system/bin/appcontroller.conf} to set the value of
- the environment variable \c QT_QPA_EGLFS_NO_SURFACEFLINGER to \c
- 1 instead of \c 0.
- \li Disable the startup of \c surfaceflinger at boot-up. Either
- change \c /init.rc, or simply rename the \c
- {/system/bin/surfaceflinger} executable.
- \endlist
-
\section1 Using Network Connection for ADB
By default, \B2Q uses USB cable for communication between device and Qt Creator.
diff --git a/src/doc/src/qtee-index.qdoc b/src/doc/src/qtee-index.qdoc
index b9f35b3..7deac5e 100644
--- a/src/doc/src/qtee-index.qdoc
+++ b/src/doc/src/qtee-index.qdoc
@@ -22,11 +22,10 @@
\nextpage qtee-overview.html
\title Qt 5.4 for Device Creation
- With commercially licensed Qt for device creation, you get a fully-integrated
- solution to get you started immediately with software development on your
- embedded device with a tailored user experience for embedded Linux and
- embedded Android. Qt libraries can also be manually configured to other
- operating systems or custom software stacks.
+ \e {Qt for Device Creation} is a commercial offering, providing a
+ fully-integrated solution for creating embedded Linux-based products. It
+ provides the complete toolchain required for faster software development,
+ enabling quicker time-to-market.
The Qt development environment for device creation consists of:
@@ -44,7 +43,6 @@
\li \l{Supported Platforms}
\li \l{Preparing Hardware}
\list
- \li \l{Preparing Nexus 7 (2012/2013)}{Nexus 7 (2012/2013) (embedded Android)}
\li \l{Boundary Devices i.MX6 Boards}
\li \l{Preparing SABRE SD i.MX6}{SABRE SD i.MX6Quad (embedded Linux)}
\li \l{Preparing SABRE SD i.MX6}{SABRE SD i.MX6Dual (embedded Linux)}
@@ -101,26 +99,24 @@
For overview about Qt libraries see the \l {Qt reference documentation}.
- \section1 Additional Embedded Libraries and Value-Add Components
+ \section1 Additional Embedded Libraries and Value-Adds
In addition to the Boot to Qt stack and a comprehensive development
- environment, \SDK comes with a set of components that bring new features and
- speed up the creation of high-performing, modern UI embedded applications:
+ environment, \SDK comes with a set of components that speed up the creation
+ of responsive embedded applications with modern UI:
\list
\li \l {Qt Virtual Keyboard} - complete virtual keyboard solution with
- word-prediction and multiple languages supported.
+ word-prediction and multiple languages support.
\li \l {Qt Quick Enterprise Controls} - a set of advanced UI controls
with an industry-specific look-and-feel.
- \li \l {Qt Quick Compiler} - enables compiling .qml source files into
- application binaries, improving load times and security for code
- assets.
+ \li \l {Qt Quick Compiler} - a QML complier that helps in securing the
+ code assets, and enables improved load time.
\li \l {Qt Charts} - UI Components for displaying visually pleasing
charts, driven by static or dynamic data models.
\li \l {Qt Data Visualization} - UI Components for creating stunning 3D
data visualizations.
- \li \l {Qt Quick 2D Renderer} - enables Qt Quick UIs on GPU-less
- devices.
+ \li \l {Qt Quick 2D Renderer} - Qt Quick renderer for GPU-less devices.
\endlist
\section1 About the Development Environment
@@ -148,9 +144,9 @@
\title About Boot to Qt
\e{\b{\B2Q}} is a light-weight, Qt-optimized, full software stack for
- embedded systems that is installed into the actual target device. This is
- done by flashing the device's memory card or internal memory directly with a
- pre-built image that comes with the online installer.
+ embedded Linux systems that is installed into the actual target device.
+ This is done by flashing the device's memory card or internal memory
+ directly with a pre-built image that comes with the online installer.
See the \l{Installation Guide} for details.
\B2Q is ideal for the following use cases:
@@ -158,46 +154,21 @@
\list
\li Evaluating Qt on real embedded environment using one of the provided
reference images.
- \li Getting an immediately working embedded development environment up
- and running as a starting point to production development. Later,
- the stack can be customized to production with
+ \li Getting the embedded development environment up and running in no
+ time. Later, the stack can be customized to production with
\e Build-Your-Own-Stack tooling, including proprietary Yocto Project
recipes.
- \li Creating embedded devices from off-the-shelf programmable Android
- devices using \l {Android injection}.
\endlist
\image build-your-own-stack.png
- Boot to Qt supports two different operating systems:
-
- \b{\B2QL}\br
\B2QL is using the traditional embedded Linux
kernel built with the Yocto Poky reference system (Yocto 1.6 Daisy release).
The embedded Linux variant is designed for great customization possibilities.
It contains only components required in the embedded device, resulting in
smaller image sizes while keeping valuable development tools available.
- \b{\B2QA}\br
- The embedded Android stack provides an easy way to create a full embedded
- device using off-the-shelf programmable Android devices,
- making the device run stripped-down, Qt-optimized OS and middleware stack.
- The device will then become an embedded device running Qt applications,
- instead of running the Android OS with Android applications.
-
- For just creating applications using the Qt libraries that run on the native
- Android OS, see \l {Qt for Android} in Qt reference documentation.
-
- \B2QA tries to strip down the Android stack to the
- bare minimum, relying only on basic Linux features. The majority of the
- Android stack, such as Dalvik virtual machine is not running in Boot to Qt,
- resulting in faster startup times, lower memory consumption and overall
- better performance.
-
- The embedded Android stack can be installed into programmable Android
- devices that are based on Android version 4.2 or higher.
-
- Both versions of \B2Q have been tested and verified on a number of different
+ \B2Q have been tested and verified on a number of different
hardware configurations. Usage of \B2Q is not limited to the devices used as
\l {Supported Platforms}{reference platforms}, it can be made to run on a
variety of hardware.
@@ -207,8 +178,7 @@
\B2QL is built using the tools and resources from the \l {Yocto Project},
and is based on Yocto's reference distribution (\e Poky). You can
use the same tools to build custom \B2Q images, and have control over
- which packages are included in the build and how the software stack
- is configured.
+ the packages included in the build and configure the software stack.
The process consist of three parts: Building the \B2Q image and the
external toolchain, building Qt libraries and add-ons, and configuring
@@ -221,7 +191,6 @@
\section1 Emulator
The \l {Emulator Manual}{emulator} running a \B2Q image enables you to
- test and debug applications in an environment practically identical to
- that of the device, without having a real device connected to the
- development host.
+ test and debug applications in an environment identical to that of the
+ device, without having a real device connected to the development host.
*/
diff --git a/src/doc/src/qtee-install-guide.qdoc b/src/doc/src/qtee-install-guide.qdoc
index 6ffc8e6..4fb097d 100644
--- a/src/doc/src/qtee-install-guide.qdoc
+++ b/src/doc/src/qtee-install-guide.qdoc
@@ -141,7 +141,7 @@
\section1 6. Configuring a Device Kit in Qt Creator
- \include b2qt-post-install-setup.qdocinc configuring device kit android linux
+ \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/qtee-licenses.qdoc b/src/doc/src/qtee-licenses.qdoc
index 791ec92..bd23fd5 100644
--- a/src/doc/src/qtee-licenses.qdoc
+++ b/src/doc/src/qtee-licenses.qdoc
@@ -34,17 +34,6 @@
The third-party licenses used in \SDK are listed in the file
\c {<INSTALL_DIR>/Licenses/ThirdPartySoftware_Listing.txt}.
- \section1 Embedded Android Images
-
- The embedded Android platform is built from the \e {Android Open Source Project},
- source code available at \l {http://android.googlesource.com/}. The open
- source licenses and notices are collected into the file
- \c {/etc/NOTICE.html.gz} in the target images.
-
- \B2QA installs additional 3rd party software on top of standard Android images. The listing
- of licensed files and corresponding license information are located in \c {/system/licenses}
- directory in the target images.
-
\section1 Embedded Linux Images
The embedded Linux platform is built using tools from the \l {Yocto Project}.
@@ -53,20 +42,4 @@
\li \c /usr/share/common-licenses/license.manifest
\li \c /usr/share/licenses/*
\endlist
-
- \section1 Android GNU C++ Run-time Licensing
-
- The Android platform does not provide a full implementation of the C++ run-time. Instead,
- apps that depend on features such as STL, exceptions, or RTTI, must include an additional
- native run-time library that provides the features they need.
-
- \B2QA uses the GNU libstdc++ library distributed as part of the \e {Android Open Source Project}.
- This library is included in the images for \B2QA, and will be loaded by the application
- on start-up to meet the run-time requirements of Qt.
-
- The GNU C++ run-time is licensed under the
- \l{http://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_gpl.html}{GNU General Public License version 3} with
- an exception which grants permission for run-time linking and usage of the library by an application which
- would otherwise violate the terms of the main license. For more information about this exception, see
- \l{http://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html}{the official license page}.
*/
diff --git a/src/doc/src/qtee-troubleshooting.qdoc b/src/doc/src/qtee-troubleshooting.qdoc
index 6561220..dc8a5fc 100644
--- a/src/doc/src/qtee-troubleshooting.qdoc
+++ b/src/doc/src/qtee-troubleshooting.qdoc
@@ -31,22 +31,18 @@
\row \li \l{ts-02}{I have problems deploying/launching a Qt or Qt Quick example application}
\row \li \l{ts-03}{I have problems launching or running applications on hardware after updating the SDK}
\row \li \l{ts-04}{Booting BD-SL-i.MX6 stops with '6x_bootscript not found' error}
- \row \li \l{nexus-factory-reset}{How do I restore my Nexus 7 to factory settings}
- \row \li \l{ts-06}{How do I shut down the Nexus 7?}
\row \li \l{ts-07}{How do I get HDMI output working properly on BeagleBone Black?}
- \row \li \l{ts-08}{Trying to build for the emulator target fails with error message 'make: i686-android-linux-g++: Command not found'}
\row \li \l{ts-09}{Something crashed!}
\row \li \l{ts-10}{Mouse or touch input does not work}
\row \li \l{ts-11}{Application stops with 'EGLFS: OpenGL windows cannot be mixed with others.'}
\row \li \l{ts-12}{I cannot edit the contents of appcontroller.conf on the device}
- \row \li \l{ts-13}{C++11 features do not work on Android}
+ \row \li \l{ts-13}{How to enable C++11 features}
\header \li \b {Connectivity Issues}
\row \li \l{ts-14}{I cannot connect to my hardware device via USB}
\row \li \l{ts-15}{adb fails with "error: more than one device and emulator"}
\row \li \l{ts-16}{The emulator cannot connect to the Internet}
\row \li \l{ts-17}{The emulator is stuck in \e{Waiting for display data} or fails to start properly}
\row \li \l{ts-18}{What are the user and password to access my embedded Linux device?}
- \row \li \l{ts-19}{Boundary Devices Android Jellybean i.MX6 image deployment issues}
\endtable
\section1 General Issues
@@ -89,36 +85,6 @@
\li \l http://boundarydevices.com/switching-u-boot-versions-on-i-mx6/
\endlist
- \target nexus-factory-reset
- \b{How do I restore my Nexus 7 to factory settings}
-
- Go to \l{https://developers.google.com/android/nexus/images} and
- download the correct file for your device. Unpack it, and then enter the
- following commands:
-
- \badcode
- <INSTALL_DIR>/Tools/b2qt/adb reboot bootloader
- <INSTALL_DIR>/Tools/b2qt/fastboot -w update <image-file>.zip
- \endcode
-
- \target ts-06
- \b{How do I shut down the Nexus 7?}
-
- If the \B2Q demo launcher is running, start the \b {Launcher
- Settings} app, and select \b {Shut Down} to power off the device.
-
- Otherwise, make sure the Nexus 7 is connected to the development host, and run
- the following command in a terminal:
- \badcode
- <INSTALL_DIR>/Tools/b2qt/adb shell reboot -p
- \endcode
-
- If the device is in the fastboot mode, use the volume button to display the
- \b {Power off} option and press the power button to power off the device.
-
- Alternatively, press and hold the power button for 10
- seconds. This will force a reboot.
-
\target ts-07
\b{How do I get HDMI output working properly on BeagleBone Black?}
@@ -130,14 +96,6 @@
More details and possible solutions can be found
\l {http://www.elinux.org/Beagleboard:BeagleBoneBlack_HDMI}{here}.
- \target ts-08
- \b{Trying to build for the emulator target fails with error message 'make: i686-android-linux-g++: Command not found'}
-
- You need to install support libraries in order to run 32-bit programs in a
- 64-bit Linux operating system.
-
- See \l{Installing 32-bit Support Libraries}.
-
\target ts-09
\b{Something crashed!}
@@ -156,9 +114,8 @@
See \l{Customization}.
- \note Hotplugging does not currently work on Embedded Android, and therefore,
- any input device must be present at boot time to be recognized. On Embedded Linux
- hotplugging is usually supported for mouse and keyboard devices.
+ \note On Embedded Linux hotplugging is usually supported for mouse and
+ keyboard devices.
\target ts-11
\b{Application stops with 'EGLFS: OpenGL windows cannot be mixed with others.'}
@@ -179,15 +136,9 @@
See \l{Customization}.
\target ts-13
- \b{C++11 features do not work on Android}
+ \b{How to enable C++11 features}
To enable C++11 features in the compiler, add \e{CONFIG += c++11} to the .pro file.
- On Embedded Linux this will be enough because there the toolchain contains a more
- recent version of gcc (4.8.x). On Embedded Android however the toolchain is based on
- gcc 4.6. This offers limited support for C++11 and Qt's own C++11 support is disabled,
- meaning that adding \e{c++11} to \e{CONFIG} will have no effect. There is still a
- possibility however to manually enable some level of C++11 support just for the
- application, by adding \e{QMAKE_CXXFLAGS += -std=c++11} to the .pro file.
\section1 Connectivity Issues
\target ts-14
@@ -198,7 +149,7 @@
\target ts-15
\b{adb fails with "error: more than one device and emulator"}
- You have to specify which Android device you want \c{adb} to talk
+ You have to specify which device you want \c{adb} to talk
to, using adb's \c{-s <serial-number>} option. Use the following
command to find to see the serial number of the connected
devices:
@@ -244,27 +195,6 @@
\b{What are the user and password to access my embedded Linux device?}
Embedded Linux devices can be accessed using user \c{root} and an empty password.
-
- \target ts-19
- \b{Boundary Devices Android Jellybean i.MX6 image deployment issues}
-
- On some hosts running the mksdcard.sh script results in the following failure messages:
-
- \badcode
- Cannot find device with major:minor 8:20: No such device
- cp: target ‘/media/BOOT/’ is not a directory
- \endcode
-
- This means that flashing an SD card has failed, even if the scripts seemingly runs to the end.
- The issue can be worked around by adding \c sleep call before \c {udisks --mount} loop (search at
- the end of the script):
-
- \badcode
- sleep 2
- for n in 1 2 4 ; do
- udisks --mount ${diskname}${prefix}${n}
- done
- \endcode
*/
/*!
@@ -277,20 +207,15 @@
\header \li \b {Common Issues}
\row \li \l{ki-01}{Qt Sensors: Sensor Support Depends on Hardware}
\row \li \l{ki-02}{Qt WebEngine: Widget-based Web View not Available}
- \row \li \l{ki-03}{Qt WebKit: No Support on Embedded Android}
- \row \li \l{ki-04}{No Sound on Embedded Android Devices}
\row \li \l{ki-05}{Limited Support for Multiple Top-Level Windows}
\row \li \l{ki-06}{QML Debugging not Functional with Qt Quick Compiler}
\row \li \l{ki-18}{Multi-process Support with the Wayland Windowing System}
\header \li \b {Device-Specific Issues}
\row \li \l{ki-07}{BD-SL-i.MX6: Device Stops Working After Disconnecting the Micro-USB Cable}
- \row \li \l{ki-08}{BD-SL-i.MX6: Internet Radio Demo Causes Device to Freeze}
\row \li \l{ki-11}{BeagleBone Black: Unstable HDMI output}
\header \li \b {Emulator-Specific Issues}
- \row \li \l{ki-12}{Networking on Embedded Android Emulator}
\row \li \l{ki-13}{Qt WebEngine not Available for Emulator}
\row \li \l{ki-15}{Switching Between Emulators from Different Boot to Qt Versions}
- \row \li \l{ki-16}{Emulator: Limited Support for Qt Multimedia}
\endtable
\section1 Common Issues
@@ -308,18 +233,6 @@
The QWidget-based equivalent, such as QWebEngineView, will become supported in a future
release. For the time being, use the WebEngineView QML type.
- \target ki-03
- \b{Qt WebKit: No Support on Embedded Android}
-
- Qt WebKit currently does not build on embedded Android.
-
- \target ki-04
- \b{No Sound on Embedded Android Devices}
-
- When connecting a headphone or speakers while the device is running, the
- audio may not be properly routed to the correct output. As a workaround,
- connect the headphone or speakers before turning on the device.
-
\target ki-05
\b{Limited Support for Multiple Top-Level Windows}
@@ -344,12 +257,6 @@
The device does not respond to touch input after connecting to a host computer via USB, and
then disconnecting the Micro-USB cable.
- \target ki-08
- \b{BD-SL-i.MX6: Internet Radio Demo Causes Device to Freeze}
-
- Trying to start playback in Internet Radio application from Qt 5 Everywhere demo causes the
- device to not react to touch input on embedded Android.
-
\target ki-11
\b{BeagleBone Black: Unstable HDMI output}
@@ -360,22 +267,10 @@
\section1 Emulator-Specific Issues
- \target ki-12
- \b{Networking on Embedded Android Emulator}
-
- Internet access on embedded Android emulator may not work by default, as the dhcpcd daemon
- unnecessarily adds a default route for the eth0 interface. As a workaround, this route can
- be removed manually. Start the emulator, and use the following command:
-
- \badcode
- <INSTALL_DIR>/Tools/b2qt/adb shell ip route del default dev eth0
- \endcode
-
\target ki-13
\b{Qt WebEngine not Available for Emulator}
- \l{Qt WebEngine} is not currently available for the emulators, neither embedded Linux
- nor embedded Android. This is planned to be addressed in a later release.
+ \l{Qt WebEngine} will not be available on the emulator.
\target ki-15
\b{Switching Between Emulators from Different Boot to Qt Versions}
@@ -384,12 +279,6 @@
emulator startup problems and graphical issues. To avoid these problems, close the previous
emulator before launching a new one.
- \target ki-16
- \b{Emulator: Limited Support for Qt Multimedia}
-
- The emulator for embedded Android does not properly support multimedia functionality
- (playback of audio and video, accessing camera).
-
\target ki-18
\b{Multi-process Support with the Wayland Windowing System}
diff --git a/src/doc/src/shared/b2qt-post-install-setup.qdocinc b/src/doc/src/shared/b2qt-post-install-setup.qdocinc
index 4de30e8..e73b8e7 100644
--- a/src/doc/src/shared/b2qt-post-install-setup.qdocinc
+++ b/src/doc/src/shared/b2qt-post-install-setup.qdocinc
@@ -75,25 +75,6 @@
//! [steps for device kit]
//! [configuring device kit]
-//! [android steps for dev kit]
- \list 1
- \li Select \b{Tools > Options > Build & Run > Kits}.
- \li Select the kit with the correct Android version
- (for example, \e {generic-4.2}).
- \li Select the correct device in the \b{Device} field.
- \li Select \b{OK}.
- \endlist
-
- If you have more than one development device that use the same Android
- version, clone the \e generic kit and rename it after the physical device:
-
- \list 1
- \li Select the generic Android kit and then \b Clone.
- \li Select the correct device in the \b{Device} field.
- \li Edit the name of the cloned kit and press \b OK.
- \endlist
-//! [android steps for dev kit]
-
//! [configuring network device]
After you have prepared the hardware, you must set up the development tools
in Qt Creator for your device. Connect your device to the network via an
@@ -115,18 +96,8 @@
//! [configuring network device]
-//! [configuring device kit android]
+//! [configuring device kit linux]
\include b2qt-post-install-setup.qdocinc common config device kit
- \include b2qt-post-install-setup.qdocinc android steps for dev kit
-//! [configuring device kit android]
-
-//! [configuring device kit android linux]
- \include b2qt-post-install-setup.qdocinc common config device kit
- \list
- \li \b{\B2QL}
- \include b2qt-post-install-setup.qdocinc steps for device kit
- \li \b{\B2QA}
- \include b2qt-post-install-setup.qdocinc android steps for dev kit
- \endlist
-//! [configuring device kit android linux]
+ \include b2qt-post-install-setup.qdocinc steps for device kit
+//! [configuring device kit linux]
*/
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-24 05:14:33 +0000