From 82671c1cb36a0406e5a90a92dd17dedff02b206a Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 16:57:59 +0200 Subject: Doc: Fix umount instructions umount /media/* will not work if the stuff is automounted under /media/username. Try to unmount in both places. Change-Id: Icdb212e81ff04d6efe4ac0885c733e63a48fe316 Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 8969292..21fd1f0 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -495,7 +495,7 @@ \endcode \li Run device/boundary/mksdcard.sh: \code - ~/bd-android$ sudo umount /media/* + ~/bd-android$ sudo umount /media/* /media/$USER/* ~/bd-android$ sudo device/boundary/mksdcard.sh /dev/XXX ~/bd-android$ sync \endcode -- cgit v1.2.3 From eaad2e769b37755a95ef030744ff39becc74472b Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 16:52:17 +0200 Subject: Doc: 32-bit support libs are only needed on 64-bit systems Change-Id: I5e22dff017a7a7f0efb5f0798c4a2f675d5d8efd Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 21fd1f0..04c41a4 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -133,10 +133,10 @@ \target Installing 32-bit Support Libraries \section1 1. Installing 32-bit Support Libraries - Some of the build tools in \B2Q are 32-bit programs, and they - require that support libraries for running 32-bit code are present - in the system. To install the required packages in Ubuntu, use the - following command in a terminal: + Some of the build tools in \B2Q are 32-bit programs, and on 64-bit + systems they require that support libraries for running 32-bit + code are present in the system. To install the required packages + in Ubuntu, use the following command in a terminal: \code sudo apt-get install g++-multilib ia32-libs -- cgit v1.2.3 From 1bf40bf81992559737c21d9bd922a378487f0067 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 16:50:57 +0200 Subject: Doc: SurfaceFlinger may be running. Remove it. Change-Id: I8a34ee4092fa0a368a801ed826ce324f5d3e1ce3 Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 04c41a4..0283f23 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -101,7 +101,7 @@ \b{\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 - \e{SurfaceFlinger} or \e{DalvikVM} is not running in \B2Q, + \e{Dalvik virtual machine} is not running in \B2Q, resulting in faster startup times, lower memory consumption and overall better performance. -- cgit v1.2.3 From 50c37d9e095a2cbf0f7b40ce6f0041684b05b813 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 17:08:25 +0200 Subject: Doc: Make deploy.sh executable to be safe For some reason the deploy.sh I got was not executable. The safest is to update the documentation with a chmod +x step. Change-Id: I68400429426031992d614aac135a263768284a56 Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 1 + 1 file changed, 1 insertion(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 0283f23..be8c8b0 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -518,6 +518,7 @@ Then, upgrade the micro-SD Card with \B2QA: \code + chmod +x /Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX \endcode -- cgit v1.2.3 From 8b72d8990033af83b7b44871d5af3e61c965fc72 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 16:01:59 +0200 Subject: Enhance the docs about window limitations and input devices Task-number: QTRD-2421 Task-number: QTRD-2429 Change-Id: Ie47053f20d8587a84925d41e5a62cbd9ca88cbb4 Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 27 ++++++++++++++++++++++----- 1 file changed, 22 insertions(+), 5 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index be8c8b0..341dfac 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -594,16 +594,23 @@ /Tools/b2qt/adb remount \endcode - In the \c{appcontroller.conf} file, the input devices are + In the \c{appcontroller.conf} file the input devices are specified by the lines similar to these: \code env=QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event0 \endcode - The mouse pointer can be turned on and off by removing or adding this line: - \code - env=QT_QPA_EGLFS_HIDECURSOR=1 - \endcode + Usually there is no need to change this setting. USB input devices like + keyboards and mice are automatically recognized. The mouse pointer is shown + automatically if a mouse is connected. + + Note however that hotplugging may not work, meaning that the input + devices, like keyboard and mouse, have to be connected at boot + time. + + On some devices, for example the i.MX6 Sabre Lite, the touchscreen device is + specified explicitly in QT_QPA_GENERIC_PLUGINS. This is necessary because + the automatic device discovery would fail to find the touchscreen. \section1 Booting to a Custom Application @@ -777,6 +784,16 @@ Note that hotplugging does not currently work; any input device must be present at boot time to be recognized. + \section2 Application stops with \e{EGLFS: OpenGL windows cannot be mixed with others.} + + In OpenGL and Qt Quick 2 applications there can only be one + fullscreen window existing at a time. Trying to create another + OpenGL window or trying to mix an OpenGL window with raster ones + will abort the application with the message shown above. + + For raster (software rendered, e.g. QtWidget or QPainter-based + content) windows there is no such limitation. + \section2 I cannot edit the contents of appcontroller.conf on the device The file system where this file is located may be mounted as read-only. -- cgit v1.2.3 From 7281b8851573c325a72da008245d54e06516e2d2 Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Fri, 11 Oct 2013 11:46:45 +0300 Subject: Doc: Add documentation for raspberry Pi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: If57154ba74595a1f52802d81908d333924319e7d Reviewed-by: Topi Reiniö Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 69 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 341dfac..2489a54 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -33,6 +33,7 @@ \li \l{Preparing Nexus 7}{Nexus 7 (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} + \li \l{Preparing Raspberry Pi}{Raspberry Pi (embedded Linux)} \endlist \li \b {\l{Building and Running an Example}} \li \b {\l{Customization}} @@ -232,6 +233,7 @@ \li \l{Nexus 7 (embedded Android)} \li \l{Sabre Lite i.MX 6 (embedded Android)} \li \l{BeagleBoard-xM (embedded Android and Linux)} + \li \l{Raspberry Pi (embedded Linux)} \endlist If you are only using the emulator, you can skip this step @@ -541,6 +543,73 @@ See \l{Building and Running an Example} */ +/*! + \target Raspberry Pi (embedded Linux) + \page b2qt-preparing-hardware-rasberrypi.html + \title Preparing Raspberry Pi + \previouspage b2qt-installation-guide.html + \nextpage b2qt-building-and-running.html + + When using a \l{http://www.raspberrypi.org/}{Raspberry Pi} as a + development device, following steps are required to prepare it for + \B2Q. + + \note \b{It is important that the steps in this section are repeated + every time after updating the \B2Q SDK.} + + The images containing \B2Q stack for Raspberry Pi is included in the SDK, + ready to be copied to a micro-SD card. + + \section1 Preparing a Micro-SD Card + + For \B2QL, a card of at least 512MB capacity is sufficient. + + Plug the micro-SD card/reader into the development host PC and use + the following command to find out its device path + (i.e. \c{/dev/XXX}, where \c{XXX} typically is \c{sdb}): + + \code + df -h + \endcode + + Alternatively, if the micro-SD card is unformatted, run the following + command immediately after inserting the card to see its device + path: + + \code + dmesg | tail + \endcode + + Now make sure the micro-SD card is not mounted: + + \code + umount /dev/XXX + \endcode + + \section1 Installing the \B2Q Image + + Write the image to the micro-SD card: + + \code + cd + Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX + \endcode + + \warning \b{Make very sure you select the right device. Selecting the wrong + one can result in a wiped hard drive}. + + After the image has been deployed, power up the device and confirm that it shows + a \B2Q welcome screen and/or demo. + + \section1 Configuring a Device Kit in Qt Creator + + \include b2qt-post-install-setup.qdocinc configuring network device + + \b {You are now ready to start developing for your device!} + + See \l{Building and Running an Example} +*/ + /*! \page b2qt-building-and-running.html \title Building and Running an Example -- cgit v1.2.3 From 84732e0ef58b3ed8d06f688d4076757ac2dfbb82 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 16:48:45 +0200 Subject: Doc: Update Android version in introduction Change-Id: Iba58ead0f1529dd458026dd88a22448d7f504b67 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 2489a54..be4b8ba 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -50,7 +50,7 @@ two different operating systems: \list - \li \b{\B2QA} places Qt on top of an Android (version 4.0 or 4.1) + \li \b{\B2QA} places Qt on top of an Android (version 4.1 or higher) kernel/baselayer. \li \b{\B2QL} places Qt on top of an Linux kernel/baselayer, built -- cgit v1.2.3 From 58099ab120d14f8c37636bfe61392fadd3a6d617 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 18:09:51 +0200 Subject: Doc: Add some words about deployment paths It's very nice that new projects generated by Creator deploy properly but we really need to say a few words about running existing projects (for example Qt's own examples). The Qt examples, say shadereffects from qtdeclarative, won't deploy by default since target.path is garbage. It has to be manually updated to /data/user/qt/whatever. Document this. Change-Id: I8d09c091d449b8b4ad519210a938f9b56195bb60 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index be4b8ba..c5808b8 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -636,6 +636,28 @@ connected device. \li To build and run the project, click \inlineimage qtcreator-run.png \endlist + + \section1 Setting up an already existing project for deployment + + The projects generated by Qt Creator will always have the correct settings + for deployment on the device or emulator. Existing projects may need some + changes however. + + As a general rule, application binaries and content (like QML files) are + deployed under /data/user/qt/. This means that deployment + settings in .pro files like the following: + + \code + target.path = ... + INSTALLS += target + \endcode + + should be migrated to + + \code + target.path = /data/user/qt/ + INSTALLS += target + \endcode */ /*! -- cgit v1.2.3 From 57f8992447ce305485e1ba58c010d050b86656bf Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Mon, 14 Oct 2013 09:32:43 +0300 Subject: Docs: linux deploy script requires sudo Change-Id: I7f39eeb3fc9b5733260ca79b98203ccc785cc280 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index c5808b8..d7fafb5 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -413,7 +413,7 @@ \li \b{\B2QL} \code cd - Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/XXX + sudo Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/XXX \endcode \endlist @@ -592,7 +592,7 @@ \code cd - Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX + sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX \endcode \warning \b{Make very sure you select the right device. Selecting the wrong -- cgit v1.2.3 From 439ed058c0285033e41330bd51ada939d18dff6b Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Mon, 14 Oct 2013 13:20:45 +0300 Subject: Revert "Doc: Make deploy.sh executable to be safe" Instead of documenting workaround, bug was fixed. Change-Id: I79130b0e9e06ca708bafe408e918569fe73accfa Reviewed-by: Laszlo Agocs --- src/doc/src/b2qt.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index d7fafb5..694dcc5 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -520,8 +520,8 @@ Then, upgrade the micro-SD Card with \B2QA: \code - chmod +x /Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh - /Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX + cd + Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX \endcode \warning \b{Make very sure you select the right device. Selecting the wrong -- cgit v1.2.3 From 395e7ff2a25216988b43aa310261b0e4204e1b7c Mon Sep 17 00:00:00 2001 From: Gatis Paeglis Date: Fri, 11 Oct 2013 16:50:10 +0200 Subject: [Doc] Update "Installing Proprietary Drivers" section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I1f20b9ebe2a9dd3ab2d10314bed618d14f1e1d03 Reviewed-by: Topi Reiniö Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 29 +++++++++++++---------------- 1 file changed, 13 insertions(+), 16 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 694dcc5..059338d 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -299,15 +299,13 @@ \section1 Installing Proprietary Drivers - Download the proprietary drivers for your Nexus 7 - \l{https://developers.google.com/android/nexus/drivers#grouperjdq39}{here}. - - \note Make sure you have read the license terms at the beginning of the - driver download page. - - Select the links in the \b{Graphics}, \b{Camera, Sensors, DRM} and \b{Orientation Sensor} rows from the table - \e{"Nexus 7 (Wi-Fi) binaries for Android 4.2.2"}, download and save the files - to the installation directory of the \B2Q SDK. + Download the proprietary drivers for your Nexus 7. The following script will download the third + party drivers from \l{https://developers.google.com/android/nexus/drivers#grouperjdq39} + {https://developers.google.com/android/nexus/drivers#grouperjdq39} + \code + cd + ./Boot2Qt-1.0/nexus7-eAndroid/images/download.sh + \endcode \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" will work with the current Boot to Qt image. @@ -315,25 +313,24 @@ and is connected to the computer via USB. Then, follow these steps to update the Nexus 7: + \note Make sure you have read the license terms enclosed in each individual extractor \list 1 - \li Extract the downloaded files, and run the extracted installers. For example, + \li Run the driver extractors: \code - cd - tar xf nvidia-grouper-jdq39-738059f9.tgz + cd Boot2Qt-1.0/nexus7-eAndroid/images/drivers ./extract-nvidia-grouper.sh - tar xf asus-grouper-jdq39-b6907aa5.tgz ./extract-asus-grouper.sh - tar xf invensense-grouper-jdq39-28df082f.tgz ./extract-invensense-grouper.sh + cd - \endcode \li Find out the serial number of the connected Nexus 7 device: \code - /Tools/b2qt/adb devices + ./Tools/b2qt/adb devices \endcode \li Deploy the drivers to your device using the following command: \code - /Boot2Qt-1.0/nexus7-eAndroid/images/deploy.sh + ./Boot2Qt-1.0/nexus7-eAndroid/images/deploy.sh \endcode \endlist -- cgit v1.2.3 From e7724d5a213aa0bb6c4d50a9f9fc7cab2f6cb3cd Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 11 Oct 2013 11:56:52 +0200 Subject: Doc: Rewrite instructions for finding out SD card device path Rewrite the instructions and move them to a separate qdocinc file. Also move the warning about potential HDD-wipe to this step, as that's when you have to pay attention to it. Change-Id: I812ceca23c26587876c9ea66049b72fcce8561c9 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 81 ++------------------------------------------------- 1 file changed, 3 insertions(+), 78 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 059338d..978d6b9 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -372,27 +372,7 @@ For \B2QA, a micro-SD card of at least 2GB capacity is needed. For \B2QL, a card of at least 512MB capacity is sufficient. - Plug the micro-SD card/reader into the development host PC and use - the following command to find out its device path - (i.e. \c{/dev/XXX}, where \c{XXX} typically is \c{sdb}): - - \code - df -h - \endcode - - Alternatively, if the micro-SD card is unformatted, run the following - command immediately after inserting the card to see its device - path: - - \code - dmesg | tail - \endcode - - Now make sure the micro-SD card is not mounted: - - \code - umount /dev/XXX - \endcode + \include detect-sd-card-device-name.qdocinc instructions \section1 Installing the \B2Q Image @@ -414,9 +394,6 @@ \endcode \endlist - \warning \b{Make very sure you select the right device. Selecting the wrong - one can result in a wiped hard drive}. - After the image has been deployed, power up the device and confirm that it shows a \B2Q welcome screen and/or demo. @@ -454,27 +431,7 @@ For \B2QA, a micro-SD card of at least 4GB capacity is needed. - Plug the micro-SD card/reader into the development host PC and use - the following command to find out its device path - (i.e. \c{/dev/XXX}, where \c{XXX} typically is \c{sdb}): - - \code - df -h - \endcode - - Alternatively, if the micro-SD card is unformatted, run the following - command immediately after inserting the card to see its device - path: - - \code - dmesg | tail - \endcode - - Next, make sure the micro-SD card is not mounted: - - \code - umount /dev/XXX - \endcode + \include detect-sd-card-device-name.qdocinc instructions \section1 Installing the Android image @@ -500,12 +457,6 @@ \endcode \endlist - Make sure to replace the device path (\c{"/dev/XXX"}) with your micro-SD - card's device path that was found in the previous step. - - \warning \b{Make very sure you select the right device. Selecting the wrong - one can result in a wiped hard drive.} - \section1 Installing the \B2QA Image Make sure you have the required tools installed in your development machine: @@ -521,9 +472,6 @@ Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX \endcode - \warning \b{Make very sure you select the right device. Selecting the wrong - one can result in a wiped hard drive}. - After the installation is complete, power up the device and confirm that it shows a \B2Q welcome screen and/or demo. @@ -561,27 +509,7 @@ For \B2QL, a card of at least 512MB capacity is sufficient. - Plug the micro-SD card/reader into the development host PC and use - the following command to find out its device path - (i.e. \c{/dev/XXX}, where \c{XXX} typically is \c{sdb}): - - \code - df -h - \endcode - - Alternatively, if the micro-SD card is unformatted, run the following - command immediately after inserting the card to see its device - path: - - \code - dmesg | tail - \endcode - - Now make sure the micro-SD card is not mounted: - - \code - umount /dev/XXX - \endcode + \include detect-sd-card-device-name.qdocinc instructions \section1 Installing the \B2Q Image @@ -592,9 +520,6 @@ sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX \endcode - \warning \b{Make very sure you select the right device. Selecting the wrong - one can result in a wiped hard drive}. - After the image has been deployed, power up the device and confirm that it shows a \B2Q welcome screen and/or demo. -- cgit v1.2.3 From e38a3dc3a660eb36f519d37496763bbef24cdd50 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Mon, 14 Oct 2013 11:45:08 +0200 Subject: Doc: Update the usage of SDK / Boot to Qt names - Create a macro for Qt for Embedded Enterprise SDK - Readability: Use italics for the long platform-specific Boot to Qt names to separate them from the rest of the text - Update information about installation file naming, default install path Change-Id: Iee27da56d378846803bf193c15b9b76766533a25 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 48 ++++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 24 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 978d6b9..e06bef7 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -44,7 +44,7 @@ \section1 What is \B2Q? - \b{\B2Q} is a light-weight UI stack for embedded systems, based on the + \e{\b{\B2Q}} is a light-weight UI stack for embedded systems, based on the \l{http://qt.digia.com/}{Qt Framework} by Digia, offering an elegant means of developing beautiful and performant embedded devices. It supports two different operating systems: @@ -61,8 +61,10 @@ hardware configurations. \B2Q support is not limited to the devices used as reference platforms, it can be made to run on a variety of hardware. - \B2Q SDK provides a complete software development package for - creating applications on embedded devices. It comes with + \section1 \SDK + + \SDK includes the \B2Q stack, providing a complete software development + package for creating applications on embedded devices. It comes with the Qt Creator IDE with preconfigured build targets for hardware platforms as well as an \l{Emulator}{emulator}. @@ -94,7 +96,7 @@ \image b2qt-vs-qt-for-android.png - \b{Qt for Android} is a port of the Qt Framework to be used for application + \e{\b{Qt for Android}} is a port of the Qt Framework to be used for application development on the Android platform. Its purpose is to enable development of applications that can run on Android devices. For developers writing applications for the Android ecosystem, Qt for Android is the right choice. @@ -117,7 +119,7 @@ \previouspage index.html \nextpage b2qt-preparing-hardware.html - \e{IMPORTANT: The \B2Q SDK requires the following installation steps to be followed closely.} + \e{IMPORTANT: The \SDK requires the following installation steps to be followed closely.} In case of problems, see the \l{Troubleshooting} information and the \l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/} @@ -126,10 +128,10 @@ \target Requirements for Development Host \section1 0. Requirements for Development Host - A 64-bit Linux system is required to install and use \B2Q - SDK. Instructions in this documentation assume Ubuntu Linux 64-bit - 12.04 LTS or later. Other Linux distributions may work, but have - not been tested. C/C++ build essentials must be installed. + A 64-bit Linux system is required to install and use \SDK. Instructions + in this documentation assume Ubuntu Linux 64-bit 12.04 LTS or later. + Other Linux distributions may work, but have not been tested. C/C++ build + essentials must be installed. \target Installing 32-bit Support Libraries \section1 1. Installing 32-bit Support Libraries @@ -167,12 +169,11 @@ \li Change both the lower and upper address bounds to 192.168.56.101. \endlist - \section1 3. Installing the \B2Q SDK + \section1 3. Installing the \SDK - If you have not already installed the \B2Q SDK, do it as follows. + If you have not already installed the SDK, do it as follows. - After downloading the \B2Q SDK binary installer (the file named - something like \c{Boot2QtSDK-evaluation-64bit-2013xxxxxx}), + After downloading the binary installer for the SDK, make sure it is executable either by \list @@ -183,11 +184,10 @@ Run the installer and follow its instructions. - The installer will let you select a directory where the entire, - self-contained \B2Q SDK will be installed. In the rest of this - documentation, that directory is referred to as - \c{}. By default, it is - \tt{/home/\e{yourusername}/Boot2QtSDK}. + The installer will let you select a directory where the SDK will be + installed. In the rest of this documentation, that directory is referred + to as \b{\c{}}. The default installation directory is + \tt{~/Qt}. \target Installing Boot to Qt on Target Devices \section1 4. Install \B2Q on Target Devices @@ -271,7 +271,7 @@ \section1 Updating a Nexus 7 with \B2Q Images \note \b{It is important that the steps in this section are repeated - every time after updating the \B2Q SDK.} + every time after updating the \SDK.} An unlocked Nexus 7 device can now be updated with a \B2Q image. @@ -307,7 +307,7 @@ ./Boot2Qt-1.0/nexus7-eAndroid/images/download.sh \endcode - \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" will work with the current Boot to Qt image. + \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" will work with the current \B2Q image. Make sure your Nexus 7 is powered up, is \e{not} in fastboot mode, and is connected to the computer via USB. @@ -362,7 +362,7 @@ \B2Q. \note \b{It is important that the steps in this section are repeated - every time after updating the \B2Q SDK.} + every time after updating the \SDK.} The images containing \B2Q stack for BeagleBoard-xM is included in the SDK, ready to be copied to a micro-SD card. @@ -377,7 +377,7 @@ \section1 Installing the \B2Q Image The commands used in this step vary depending on whether you are developing - for \B2QA or embedded Linux. + for embedded Android or embedded Linux. Write the image to the micro-SD card: @@ -422,7 +422,7 @@ to prepare it for \B2QA. \note \b{It is important that the steps in this section are repeated - every time after updating the \B2Q SDK.} + every time after updating the \SDK.} The images containing \B2Q stack for Sabre Lite i.MX 6 is included in the SDK, ready to be copied to a micro-SD card. @@ -457,7 +457,7 @@ \endcode \endlist - \section1 Installing the \B2QA Image + \section1 Installing the \B2Q Image Make sure you have the required tools installed in your development machine: -- cgit v1.2.3 From 28658cad21b654039424025fadfddbe7974b24f0 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 15 Oct 2013 12:36:07 +0200 Subject: Doc: Document Model B as the supported version of Raspberry Pi Change-Id: Iec1c3873a6fa125529ec07ae503dd971fec68c4f Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e06bef7..e2f6d43 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -33,7 +33,7 @@ \li \l{Preparing Nexus 7}{Nexus 7 (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} - \li \l{Preparing Raspberry Pi}{Raspberry Pi (embedded Linux)} + \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} \endlist \li \b {\l{Building and Running an Example}} \li \b {\l{Customization}} @@ -233,7 +233,7 @@ \li \l{Nexus 7 (embedded Android)} \li \l{Sabre Lite i.MX 6 (embedded Android)} \li \l{BeagleBoard-xM (embedded Android and Linux)} - \li \l{Raspberry Pi (embedded Linux)} + \li \l{Raspberry Pi Model B (embedded Linux)} \endlist If you are only using the emulator, you can skip this step @@ -489,7 +489,7 @@ */ /*! - \target Raspberry Pi (embedded Linux) + \target Raspberry Pi Model B (embedded Linux) \page b2qt-preparing-hardware-rasberrypi.html \title Preparing Raspberry Pi \previouspage b2qt-installation-guide.html @@ -499,15 +499,19 @@ development device, following steps are required to prepare it for \B2Q. + Note that Ethernet networking is required to connect the device to Qt Creator. + This means that the support is currently limited to Raspberry Pi Model B which + includes an Ethernet port. + \note \b{It is important that the steps in this section are repeated - every time after updating the \B2Q SDK.} + every time after updating the \SDK.} The images containing \B2Q stack for Raspberry Pi is included in the SDK, ready to be copied to a micro-SD card. \section1 Preparing a Micro-SD Card - For \B2QL, a card of at least 512MB capacity is sufficient. + An SD card of at least 512MB capacity is sufficient. \include detect-sd-card-device-name.qdocinc instructions @@ -693,19 +697,19 @@ \li Android 4.0+ compatible hardware \endlist - For the technology preview release, the following devices have - been used as reference and are tested to work: + The following devices have been used as reference and are tested to work: \list \li \l{http://www.google.com/nexus/7/specs/}{Google/Asus Nexus 7} \li \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} \li \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Freescale i.MX6 Sabre Lite board (Boundary Devices)} + \li \l{http://www.raspberrypi.org/faqs}{Raspberry Pi Model B} \endlist \section1 Supported Development Environment - The development environment supported in \B2Q Technology Preview - release is Ubuntu Linux 64-bit (12.04 LTS or 12.10). See the - \l{Requirements for Development Host}. + The development environment supported by \B2Q is Ubuntu Linux 64-bit (12.04 LTS or 12.10). + + \sa {Requirements for Development Host} */ -- cgit v1.2.3 From 0048bdabca4635b403da538d7745d69245ac9de3 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 16 Oct 2013 09:59:13 +0200 Subject: Doc: Various minor fixes Change-Id: I2d00db1985a50021af704f8f52c1fd78cadc9536 Reviewed-by: Laszlo Agocs --- src/doc/src/b2qt.qdoc | 39 +++++++++++++++++++++------------------ 1 file changed, 21 insertions(+), 18 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e2f6d43..b7a696c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -440,7 +440,7 @@ Devices Android Jellybean i.MX6 images} (registration required). Use the following commands to create a micro-SD card containing the - dowloaded image: + downloaded image: \list \li Extract the downloaded package @@ -553,7 +553,7 @@ \list 1 \li Open \b{File > New File or Project}, select - \b{Qt Quick 2 Application (Built-in Types)} and click \b{Next}. + \b{Qt Quick 2 Application (Built-in Types)} and click \b{Choose...}. \li In \b{Kit Selection} dialog, select the kit(s) for your devices. You can also select the emulator kit to test running the project in the emulator. @@ -563,22 +563,25 @@ \li To build and run the project, click \inlineimage qtcreator-run.png \endlist - \section1 Setting up an already existing project for deployment + \section1 Setting Up an Already Existing Project for Deployment The projects generated by Qt Creator will always have the correct settings - for deployment on the device or emulator. Existing projects may need some - changes however. + for deployment on the device or emulator. However, existing projects may + need some changes. - As a general rule, application binaries and content (like QML files) are - deployed under /data/user/qt/. This means that deployment - settings in .pro files like the following: + As a general rule, application binaries and resources (such as QML files and + images) are deployed under \c {/data/user/qt/} directory. + Therefore, the \c path variable for \c INSTALLS target(s) need to be adjusted + accordingly in .pro files: + + For example, the following: \code target.path = ... INSTALLS += target \endcode - should be migrated to + should be migrated to: \code target.path = /data/user/qt/ @@ -626,7 +629,7 @@ time. On some devices, for example the i.MX6 Sabre Lite, the touchscreen device is - specified explicitly in QT_QPA_GENERIC_PLUGINS. This is necessary because + specified explicitly in \c QT_QPA_GENERIC_PLUGINS. This is necessary because the automatic device discovery would fail to find the touchscreen. \section1 Booting to a Custom Application @@ -724,14 +727,14 @@ \section1 General Issues - \section2 I have a problem deploying/launching the application in Qt Creator + \section2 I have problems deploying/launching the application in Qt Creator Check if the device is properly connected to the PC via USB. See \l{Connectivity Issues}. If using the emulator, see \l{Installing VirtualBox}{Configuring VirtualBox}. - \section2 I have a problem deploying/launching a Qt or Qt Declarative example application + \section2 I have problems deploying/launching a Qt or Qt Quick example application Because of a technical peculiarity in \c{qmake}, it is not possible to get correct deployment setup for any application that @@ -741,7 +744,7 @@ outside the Qt source tree, and open this copy of the example application instead. - \section2 I have a problem launching or running applications on hardware after updating \B2Q SDK + \section2 I have problems launching or running applications on hardware after updating the SDK Remember to repeat the process of updating also your device with the latest version of \B2Q. See \l{Installing Boot to Qt on Target Devices}. @@ -803,13 +806,13 @@ \section2 Application stops with \e{EGLFS: OpenGL windows cannot be mixed with others.} - In OpenGL and Qt Quick 2 applications there can only be one + OpenGL and Qt Quick 2 applications can only have one fullscreen window existing at a time. Trying to create another - OpenGL window or trying to mix an OpenGL window with raster ones - will abort the application with the message shown above. + OpenGL window, or trying to mix an OpenGL window with a raster one + will display the above message and abort the application. - For raster (software rendered, e.g. QtWidget or QPainter-based - content) windows there is no such limitation. + \note For raster windows (software rendered content based on QWidget or + QPainter), there is no such limitation. \section2 I cannot edit the contents of appcontroller.conf on the device -- cgit v1.2.3 From adaa8544b8c358786f7a106e1c243a0e561cb6b7 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 16 Oct 2013 16:01:00 +0200 Subject: Doc: Remove confusing umount command from i.MX6 instructions The SD card was unmounted already in the 'Preparing a Micro-SD Card' step, trying to do it again will print out an error. Task-number: QTRD-2446 Change-Id: I71e50a12d0ebef6b7936fab4ed2ab1c87f7b4a9f Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 1 - 1 file changed, 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index b7a696c..d0f708c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -451,7 +451,6 @@ \endcode \li Run device/boundary/mksdcard.sh: \code - ~/bd-android$ sudo umount /media/* /media/$USER/* ~/bd-android$ sudo device/boundary/mksdcard.sh /dev/XXX ~/bd-android$ sync \endcode -- cgit v1.2.3 From 600056668b9d0970465e3302dc6f9ffec11091b7 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 17 Oct 2013 15:58:25 +0200 Subject: Doc: Use Qt Enterprise Embedded as the product name - Update the documentation to use 'Qt Enterprise Embedded' as the product / SDK name. - Update the html files to use prefix 'qee' instead of 'b2qt'. - Remove discussion about 'SDK', only use the above name Change-Id: Icc7e326df98e6f3053869e4aa3b8aa2ab446ecbc Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 152 +++++++++++++++++++++++++------------------------- 1 file changed, 75 insertions(+), 77 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index d0f708c..03a1c75 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -16,10 +16,10 @@ ****************************************************************************/ /*! - \contentspage{index.html}{Boot to Qt} + \contentspage{index.html}{Qt Enterprise Embedded} \page index.html - \nextpage b2qt-installation-guide.html - \title Boot to Qt Introduction + \nextpage qee-installation-guide.html + \title Qt Enterprise Embedded \e{\b{IMPORTANT:} Make sure to follow the \l{Installation Guide} closely!} @@ -27,20 +27,26 @@ \section1 Contents \list - \li \b {\l{Installation Guide}} - \li \b {\l{Preparing Hardware}} + \li \l{Installation Guide} + \li \l{Preparing Hardware} \list \li \l{Preparing Nexus 7}{Nexus 7 (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} \endlist - \li \b {\l{Building and Running an Example}} - \li \b {\l{Customization}} - \li \b {\l{Supported Platforms}} - \li \b {\l{Troubleshooting}} + \li \l{Building and Running an Example} + \li \l{Customization} + \li \l{Supported Platforms} + \li \l{Troubleshooting} \endlist + \section1 About \SDK + + \SDK includes the \B2Q stack, providing a complete software development + package for creating applications on embedded devices. It comes with + the Qt Creator IDE with preconfigured build targets for hardware + platforms as well as an \l{Emulator}{emulator}. \section1 What is \B2Q? @@ -61,14 +67,6 @@ hardware configurations. \B2Q support is not limited to the devices used as reference platforms, it can be made to run on a variety of hardware. - \section1 \SDK - - \SDK includes the \B2Q stack, providing a complete software development - package for creating applications on embedded devices. It comes with - the Qt Creator IDE with preconfigured build targets for hardware - platforms as well as an \l{Emulator}{emulator}. - - \section1 About Qt \l{http://qt.digia.com/}{Qt} is a full development framework with tools @@ -114,16 +112,16 @@ */ /*! - \page b2qt-installation-guide.html + \page qee-installation-guide.html \title Installation Guide \previouspage index.html - \nextpage b2qt-preparing-hardware.html + \nextpage qee-preparing-hardware.html - \e{IMPORTANT: The \SDK requires the following installation steps to be followed closely.} + \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} In case of problems, see the \l{Troubleshooting} information and the \l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/} - {Boot to Qt Known Issues} page. + {Qt Enterprise Embedded Known Issues} page. \target Requirements for Development Host \section1 0. Requirements for Development Host @@ -136,7 +134,7 @@ \target Installing 32-bit Support Libraries \section1 1. Installing 32-bit Support Libraries - Some of the build tools in \B2Q are 32-bit programs, and on 64-bit + Some of the build tools in \SDK are 32-bit programs, and on 64-bit systems they require that support libraries for running 32-bit code are present in the system. To install the required packages in Ubuntu, use the following command in a terminal: @@ -148,7 +146,7 @@ \target Installing VirtualBox \section1 2. Installing VirtualBox - The emulator in \B2Q relies on VirtualBox virtualization software. You can + The \B2Q emulator in \SDK relies on VirtualBox virtualization software. You can download it from \l{https://www.virtualbox.org/wiki/Linux_Downloads} or install it from the command line with the following command: @@ -169,12 +167,11 @@ \li Change both the lower and upper address bounds to 192.168.56.101. \endlist - \section1 3. Installing the \SDK + \section1 3. Installing \SDK - If you have not already installed the SDK, do it as follows. + If you have not already installed \SDK, do it as follows. - After downloading the binary installer for the SDK, - make sure it is executable either by + After downloading the binary installer, make sure it is executable either by \list \li Using \c{chmod +x } command, or @@ -184,9 +181,9 @@ Run the installer and follow its instructions. - The installer will let you select a directory where the SDK will be + The installer will let you select a directory where \SDK will be installed. In the rest of this documentation, that directory is referred - to as \b{\c{}}. The default installation directory is + to as \b{\c{}}. The default installation directory is \tt{~/Qt}. \target Installing Boot to Qt on Target Devices @@ -220,10 +217,10 @@ */ /*! - \page b2qt-preparing-hardware.html + \page qee-preparing-hardware.html \title Preparing Hardware - \previouspage b2qt-installation-guide.html - \nextpage b2qt-building-and-running.html + \previouspage qee-installation-guide.html + \nextpage qee-building-and-running.html Before deploying and testing your Qt application on hardware, the target device needs to be flashed with an image that contains the @@ -242,10 +239,10 @@ /*! \target Nexus 7 (embedded Android) - \page b2qt-preparing-hardware-nexus-7.html + \page qee-preparing-hardware-nexus-7.html \title Preparing Nexus 7 - \previouspage b2qt-installation-guide.html - \nextpage b2qt-building-and-running.html + \previouspage qee-installation-guide.html + \nextpage qee-building-and-running.html When using a \l{http://www.google.com/nexus/7/specs/}{Nexus 7} as a development device, following steps are required to prepare it for @@ -262,7 +259,7 @@ \li Start the Nexus up in \e{fastboot} mode: Press the power button for a second, and then keep the Volume Down key pressed, until you see a screen with a green robot with its front panel open. Note: If you get the ordinary startup screen instead, just power it down and try again. \li On the development host, give the command \code - sudo /Tools/b2qt/fastboot oem unlock + sudo /Tools/b2qt/fastboot oem unlock \endcode The Nexus screen will ask if you want to unlock the bootloader. Press power button to confirm. \li Wait a few seconds, and check that the text line stating the \c{LOCK STATE} now says \c{UNLOCKED}. @@ -271,7 +268,7 @@ \section1 Updating a Nexus 7 with \B2Q Images \note \b{It is important that the steps in this section are repeated - every time after updating the \SDK.} + every time after updating \SDK.} An unlocked Nexus 7 device can now be updated with a \B2Q image. @@ -282,7 +279,7 @@ device, using the following commands in the order they are listed: \code - cd + cd sudo ./Tools/b2qt/fastboot flash boot Boot2Qt-1.0/nexus7-eAndroid/images/boot.img sudo ./Tools/b2qt/fastboot flash system Boot2Qt-1.0/nexus7-eAndroid/images/system.img sudo ./Tools/b2qt/fastboot flash userdata Boot2Qt-1.0/nexus7-eAndroid/images/data.img @@ -303,7 +300,7 @@ party drivers from \l{https://developers.google.com/android/nexus/drivers#grouperjdq39} {https://developers.google.com/android/nexus/drivers#grouperjdq39} \code - cd + cd ./Boot2Qt-1.0/nexus7-eAndroid/images/download.sh \endcode @@ -352,17 +349,17 @@ /*! \target BeagleBoard-xM (embedded Android and Linux) - \page b2qt-preparing-hardware-beagleboard.html + \page qee-preparing-hardware-beagleboard.html \title Preparing BeagleBoard-xM - \previouspage b2qt-installation-guide.html - \nextpage b2qt-building-and-running.html + \previouspage qee-installation-guide.html + \nextpage qee-building-and-running.html When using a \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} as a development device, following steps are required to prepare it for \B2Q. \note \b{It is important that the steps in this section are repeated - every time after updating the \SDK.} + every time after updating \SDK.} The images containing \B2Q stack for BeagleBoard-xM is included in the SDK, ready to be copied to a micro-SD card. @@ -384,12 +381,12 @@ \list \li \b{\B2QA} \code - cd + cd sudo dd if=Boot2Qt-1.0/beagleboard-eAndroid/images/sdcard.img of=/dev/XXX bs=1M \endcode \li \b{\B2QL} \code - cd + cd sudo Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/XXX \endcode \endlist @@ -412,9 +409,9 @@ /*! \target Sabre Lite i.MX 6 (embedded Android) - \page b2qt-preparing-hardware-imx6.html + \page qee-preparing-hardware-imx6.html \title Preparing Sabre Lite i.MX 6 - \previouspage b2qt-installation-guide.html + \previouspage qee-installation-guide.html When using a \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Sabre @@ -422,7 +419,7 @@ to prepare it for \B2QA. \note \b{It is important that the steps in this section are repeated - every time after updating the \SDK.} + every time after updating \SDK.} The images containing \B2Q stack for Sabre Lite i.MX 6 is included in the SDK, ready to be copied to a micro-SD card. @@ -467,7 +464,7 @@ Then, upgrade the micro-SD Card with \B2QA: \code - cd + cd Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX \endcode @@ -489,10 +486,10 @@ /*! \target Raspberry Pi Model B (embedded Linux) - \page b2qt-preparing-hardware-rasberrypi.html + \page qee-preparing-hardware-rasberrypi.html \title Preparing Raspberry Pi - \previouspage b2qt-installation-guide.html - \nextpage b2qt-building-and-running.html + \previouspage qee-installation-guide.html + \nextpage qee-building-and-running.html When using a \l{http://www.raspberrypi.org/}{Raspberry Pi} as a development device, following steps are required to prepare it for @@ -503,7 +500,7 @@ includes an Ethernet port. \note \b{It is important that the steps in this section are repeated - every time after updating the \SDK.} + every time after updating \SDK.} The images containing \B2Q stack for Raspberry Pi is included in the SDK, ready to be copied to a micro-SD card. @@ -519,7 +516,7 @@ Write the image to the micro-SD card: \code - cd + cd sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX \endcode @@ -536,12 +533,12 @@ */ /*! - \page b2qt-building-and-running.html + \page qee-building-and-running.html \title Building and Running an Example - \previouspage b2qt-installation-guide.html - \nextpage b2qt-customization.html + \previouspage qee-installation-guide.html + \nextpage qee-customization.html - Once the installation and configuration steps for the SDK and the + Once the installation and configuration steps for \SDK and the target device(s) are completed, it's time to test the setup. First, make sure your device is powered up and connected to the @@ -589,10 +586,10 @@ */ /*! - \page b2qt-customization.html + \page qee-customization.html \title Customization - \previouspage b2qt-building-and-running.html - \nextpage b2qt-supported-platforms.html + \previouspage qee-building-and-running.html + \nextpage qee-supported-platforms.html \section1 Environment and Input @@ -610,7 +607,7 @@ remounted read-write to allow modification. The following command does that: \code - /Tools/b2qt/adb remount + /Tools/b2qt/adb remount \endcode In the \c{appcontroller.conf} file the input devices are @@ -639,7 +636,7 @@ To remove your application from the default startup use the following command: \code - /Tools/b2qt/adb shell appcontroller --remove-default + /Tools/b2qt/adb shell appcontroller --remove-default \endcode \section1 Switching Between Portrait and Landscape Views @@ -681,15 +678,16 @@ */ /*! - \page b2qt-supported-platforms.html + \page qee-supported-platforms.html \title Supported Platforms - \previouspage b2qt-customization.html - \nextpage b2qt-troubleshooting.html + \previouspage qee-customization.html + \nextpage qee-troubleshooting.html \section1 Supported Target Devices - \B2Q can be made to run on hardware that has support for - the Android operating system, version 4.0 or later. + The \B2Q stack can be made to run on a variety of hardware. \B2QA + requires hardware that has support for the Android operating system, + version 4.0 or later. Approximate minimal hardware requirements for running \B2Q are: \list @@ -709,20 +707,20 @@ \section1 Supported Development Environment - The development environment supported by \B2Q is Ubuntu Linux 64-bit (12.04 LTS or 12.10). + The development environment supported by \SDK is Ubuntu Linux 64-bit (12.04 LTS or 12.10). \sa {Requirements for Development Host} */ /*! - \page b2qt-troubleshooting.html + \page qee-troubleshooting.html \title Troubleshooting - \previouspage b2qt-supported-platforms.html + \previouspage qee-supported-platforms.html \note An updated version of this information may be available in the Digia customer portal. - See also \b{\l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/}{Boot to Qt Known Issues}.} + See also \b{\l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/}{Qt Enterprise Embedded Known Issues}.} \section1 General Issues @@ -765,8 +763,8 @@ download the correct file for your device. Unpack it, and then \code - /Tools/b2qt/adb reboot bootloader - /Tools/b2qt/fastboot -w update .zip + /Tools/b2qt/adb reboot bootloader + /Tools/b2qt/fastboot -w update .zip \endcode \section2 How do I shut down the Nexus 7? @@ -777,7 +775,7 @@ Otherwise, make sure the Nexus 7 is connected to your PC with USB, and run the following command in a terminal: \code - /Tools/b2qt/adb shell reboot -p + /Tools/b2qt/adb shell reboot -p \endcode Alternatively, press and hold the power button for 10 @@ -793,7 +791,7 @@ The following command shows the system log: \code - /Tools/b2qt/adb logcat + /Tools/b2qt/adb logcat \endcode \section2 Mouse or touch input does not work @@ -832,7 +830,7 @@ devices: \code - /Tools/b2qt/adb devices + /Tools/b2qt/adb devices \endcode \section2 What is the user and password to access my embedded Linux device -- cgit v1.2.3 From dc0dc3fae6cbeadef05ed10c0d0197f9f00a76a8 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 18 Oct 2013 12:18:03 +0200 Subject: Doc: Reintroduce i.MX6-eLinux setup instructions Change-Id: Ibe167ff7949e50dfd22a8f45fc6fd3dc2739a86a Reviewed-by: Andy Nichols --- src/doc/src/b2qt.qdoc | 37 +++++++++++++++++++++++++------------ 1 file changed, 25 insertions(+), 12 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 03a1c75..1822921 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -31,7 +31,7 @@ \li \l{Preparing Hardware} \list \li \l{Preparing Nexus 7}{Nexus 7 (embedded Android)} - \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android)} + \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android and Linux)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} \endlist @@ -228,7 +228,7 @@ \list \li \l{Nexus 7 (embedded Android)} - \li \l{Sabre Lite i.MX 6 (embedded Android)} + \li \l{Sabre Lite i.MX 6 (embedded Android and Linux)} \li \l{BeagleBoard-xM (embedded Android and Linux)} \li \l{Raspberry Pi Model B (embedded Linux)} \endlist @@ -408,7 +408,7 @@ */ /*! - \target Sabre Lite i.MX 6 (embedded Android) + \target Sabre Lite i.MX 6 (embedded Android and Linux) \page qee-preparing-hardware-imx6.html \title Preparing Sabre Lite i.MX 6 \previouspage qee-installation-guide.html @@ -416,22 +416,26 @@ When using a \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Sabre Lite i.MX 6} as a development device, following steps are required - to prepare it for \B2QA. + to prepare it for \B2Q. \note \b{It is important that the steps in this section are repeated every time after updating \SDK.} - The images containing \B2Q stack for Sabre Lite i.MX 6 is included in the SDK, - ready to be copied to a micro-SD card. + The images containing the \B2Q stack for Sabre Lite i.MX 6 are included + in the SDK, ready to be copied to a micro-SD card. \section1 Preparing a Micro-SD Card - For \B2QA, a micro-SD card of at least 4GB capacity is needed. + For \B2QA, a micro-SD card of at least 4GB capacity is needed. For \B2QL, + a card of at least 512MB capacity is sufficient. \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}. + 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). @@ -461,12 +465,21 @@ sudo apt-get install u-boot-tools \endcode - Then, upgrade the micro-SD Card with \B2QA: + Then, upgrade the micro-SD Card with \B2Q. Use one of the commands below, + depending on whether you're developing for embedded Android or Linux: - \code - cd - Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX - \endcode + \list + \li \b{\B2QA} + \code + cd + Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX + \endcode + \li \b{\B2QL} + \code + cd + Boot2Qt-1.0/iMX6-eLinux/images/deploy.sh /dev/XXX + \endcode + \endlist After the installation is complete, power up the device and confirm that it shows a \B2Q welcome screen and/or demo. -- cgit v1.2.3 From 9b55e06ac99cc06594ed973d2bb7cbfd46b31162 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 18 Oct 2013 15:21:44 +0200 Subject: Doc: Add troubleshooting sections for emulator connectivity Change-Id: I167aa827d594d143a5c86dcf31324ac4e64675ac Reviewed-by: Laszlo Agocs --- src/doc/src/b2qt.qdoc | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 1822921..21187cf 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -846,6 +846,37 @@ /Tools/b2qt/adb devices \endcode + \section2 The emulator cannot connect to the internet + + By default, the Virtualbox is configured to use host-only network, so external + connections do not work in the emulator. + + You may be able to enable internet connectivity with another + virtual network adapter in NAT mode by adapting + \l{http://askubuntu.com/questions/293816/in-virtualbox-how-do-i-set-up-host-only-virtual-machines-that-can-access-the-in}{these} + instructions. + + \section2 The emulator is stuck in 'Waiting for display data' or fails to start properly + + Check the output of the following command: + + \code + /Tools/b2qt/adb devices + \endcode + + If the emulator (192.168.56.101) is not listed there, try connecting to it: + + \code + /Tools/b2qt/adb connect 192.168.56.101 + \endcode + + If the emulator is already listed, try disconnecting it: + \code + /Tools/b2qt/adb disconnect 192.168.56.101 + \endcode + + And then close the emulator and retry. + \section2 What is the user and password to access my embedded Linux device Embedded Linux devices can be accessed using user \c{root} and an empty password. -- cgit v1.2.3 From 0a774cd83d57f47c15603baa002c08b6353ea1fe Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 18 Oct 2013 15:31:12 +0200 Subject: Doc: remove URLs to Known Issues page Change-Id: Ida9153a36f60a9001b44e854a4e8467d2f3629ad Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 21187cf..e2cec14 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -120,8 +120,8 @@ \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} In case of problems, see the \l{Troubleshooting} information and the - \l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/} - {Qt Enterprise Embedded Known Issues} page. + Known Issues in Qt Enterprise Embedded product page in Digia customer + portal. \target Requirements for Development Host \section1 0. Requirements for Development Host @@ -731,9 +731,8 @@ \title Troubleshooting \previouspage qee-supported-platforms.html - \note An updated version of this information may be available in the Digia customer portal. - - See also \b{\l{http://qt.digia.com/en/Product/Boot-to-Qt/Boot-to-Qt-Known-Issues/}{Qt Enterprise Embedded Known Issues}.} + \note An updated version of this information may be available in Digia customer portal, + see Known Issues in Qt Enterprise Embedded product page. \section1 General Issues -- cgit v1.2.3 From 9d3f20ff59c6d0868464681697cf5699ed09526f Mon Sep 17 00:00:00 2001 From: Rainer Keller Date: Thu, 14 Nov 2013 09:23:28 +0100 Subject: Make it clean where to configure the network settings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I7f03d3734e9b1f7761614a01c6a43e288fef544d Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e2cec14..dde3f18 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -156,7 +156,8 @@ \b{Configuring VirtualBox} - Open VirtualBox network settings: Select \b{File > Preferences...} + Open the VirtualBox user interface. + Open the network settings: Select \b{File > Preferences...} and click on the \b{Network} tab. Create a new network named \e{vboxnet0} and edit its properties: -- cgit v1.2.3 From 67e2838be9799821e0ac605ea5177e660e4be925 Mon Sep 17 00:00:00 2001 From: Rainer Keller Date: Mon, 18 Nov 2013 13:20:52 +0100 Subject: Doc: Add note about firewall MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Ifad434e8b9c17b11f1aee2bd608293cdb09c597a Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index dde3f18..7c643a6 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -168,6 +168,9 @@ \li Change both the lower and upper address bounds to 192.168.56.101. \endlist + Configure your system firewall to allow TCP and UDP packets between your host and + the virtual machine. + \section1 3. Installing \SDK If you have not already installed \SDK, do it as follows. -- cgit v1.2.3 From bd9e9d0d12536b26adf8ee212dadc4b939871dfe Mon Sep 17 00:00:00 2001 From: Rainer Keller Date: Thu, 21 Nov 2013 13:40:22 +0100 Subject: Doc: Match QtCreator 3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I99a4a09ccc3eb0ef0efddf38691f070e9e36d3c1 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 7c643a6..2e85688 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -566,7 +566,9 @@ \list 1 \li Open \b{File > New File or Project}, select - \b{Qt Quick 2 Application (Built-in Types)} and click \b{Choose...}. + \b{Qt Quick 2 Application} and click \b{Choose...}. + \li Choose a location for your new project. + \li In \b{Qt Quick Component Set} dialog, select \b{Qt Quick 2.0}. \li In \b{Kit Selection} dialog, select the kit(s) for your devices. You can also select the emulator kit to test running the project in the emulator. -- cgit v1.2.3 From 9c0ce6cd0cdced483152d631163da4c313daf0b5 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 22 Oct 2013 14:07:56 +0200 Subject: Doc: Change html prefixes again Change prefixes from 'qee' to 'qtee'. Change-Id: I82da3a811cb1b4fa888d46f208881a8461abfe54 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 56 +++++++++++++++++++++++++-------------------------- 1 file changed, 28 insertions(+), 28 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e2cec14..e1e3b4b 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -18,7 +18,7 @@ /*! \contentspage{index.html}{Qt Enterprise Embedded} \page index.html - \nextpage qee-installation-guide.html + \nextpage qtee-installation-guide.html \title Qt Enterprise Embedded \e{\b{IMPORTANT:} Make sure to follow the \l{Installation Guide} @@ -112,10 +112,10 @@ */ /*! - \page qee-installation-guide.html + \page qtee-installation-guide.html \title Installation Guide \previouspage index.html - \nextpage qee-preparing-hardware.html + \nextpage qtee-preparing-hardware.html \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} @@ -217,10 +217,10 @@ */ /*! - \page qee-preparing-hardware.html + \page qtee-preparing-hardware.html \title Preparing Hardware - \previouspage qee-installation-guide.html - \nextpage qee-building-and-running.html + \previouspage qtee-installation-guide.html + \nextpage qtee-building-and-running.html Before deploying and testing your Qt application on hardware, the target device needs to be flashed with an image that contains the @@ -239,10 +239,10 @@ /*! \target Nexus 7 (embedded Android) - \page qee-preparing-hardware-nexus-7.html + \page qtee-preparing-hardware-nexus-7.html \title Preparing Nexus 7 - \previouspage qee-installation-guide.html - \nextpage qee-building-and-running.html + \previouspage qtee-installation-guide.html + \nextpage qtee-building-and-running.html When using a \l{http://www.google.com/nexus/7/specs/}{Nexus 7} as a development device, following steps are required to prepare it for @@ -349,10 +349,10 @@ /*! \target BeagleBoard-xM (embedded Android and Linux) - \page qee-preparing-hardware-beagleboard.html + \page qtee-preparing-hardware-beagleboard.html \title Preparing BeagleBoard-xM - \previouspage qee-installation-guide.html - \nextpage qee-building-and-running.html + \previouspage qtee-installation-guide.html + \nextpage qtee-building-and-running.html When using a \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} as a development device, following steps are required to prepare it for @@ -409,9 +409,9 @@ /*! \target Sabre Lite i.MX 6 (embedded Android and Linux) - \page qee-preparing-hardware-imx6.html + \page qtee-preparing-hardware-imx6.html \title Preparing Sabre Lite i.MX 6 - \previouspage qee-installation-guide.html + \previouspage qtee-installation-guide.html When using a \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Sabre @@ -499,10 +499,10 @@ /*! \target Raspberry Pi Model B (embedded Linux) - \page qee-preparing-hardware-rasberrypi.html + \page qtee-preparing-hardware-rasberrypi.html \title Preparing Raspberry Pi - \previouspage qee-installation-guide.html - \nextpage qee-building-and-running.html + \previouspage qtee-installation-guide.html + \nextpage qtee-building-and-running.html When using a \l{http://www.raspberrypi.org/}{Raspberry Pi} as a development device, following steps are required to prepare it for @@ -546,10 +546,10 @@ */ /*! - \page qee-building-and-running.html + \page qtee-building-and-running.html \title Building and Running an Example - \previouspage qee-installation-guide.html - \nextpage qee-customization.html + \previouspage qtee-installation-guide.html + \nextpage qtee-customization.html Once the installation and configuration steps for \SDK and the target device(s) are completed, it's time to test the setup. @@ -599,10 +599,10 @@ */ /*! - \page qee-customization.html + \page qtee-customization.html \title Customization - \previouspage qee-building-and-running.html - \nextpage qee-supported-platforms.html + \previouspage qtee-building-and-running.html + \nextpage qtee-supported-platforms.html \section1 Environment and Input @@ -691,10 +691,10 @@ */ /*! - \page qee-supported-platforms.html + \page qtee-supported-platforms.html \title Supported Platforms - \previouspage qee-customization.html - \nextpage qee-troubleshooting.html + \previouspage qtee-customization.html + \nextpage qtee-troubleshooting.html \section1 Supported Target Devices @@ -727,9 +727,9 @@ */ /*! - \page qee-troubleshooting.html + \page qtee-troubleshooting.html \title Troubleshooting - \previouspage qee-supported-platforms.html + \previouspage qtee-supported-platforms.html \note An updated version of this information may be available in Digia customer portal, see Known Issues in Qt Enterprise Embedded product page. -- cgit v1.2.3 From 40fdfebd2ceff38b9edd32f063bf6218e156e462 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 22 Oct 2013 15:02:26 +0200 Subject: Doc: Add license information page Discuss the product licensing and third-party license info. Change-Id: I750f95f57a006ee23c342d15a915710caee510da Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e1e3b4b..3fc385b 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -38,6 +38,7 @@ \li \l{Building and Running an Example} \li \l{Customization} \li \l{Supported Platforms} + \li \l{License Information} \li \l{Troubleshooting} \endlist @@ -694,7 +695,7 @@ \page qtee-supported-platforms.html \title Supported Platforms \previouspage qtee-customization.html - \nextpage qtee-troubleshooting.html + \nextpage qtee-licenses.html \section1 Supported Target Devices @@ -726,6 +727,31 @@ */ +/*! + \page qtee-licenses.html + \title License Information + \previouspage qtee-supported-platforms.html + \nextpage qtee-troubleshooting.html + + \section1 Licensing + + \SDK is licensed under the Qt Enterprise commercial license. For more information, + see \l {http://qt.digia.com/licensing}. Evaluation licenses are also available, + see \l {http://qt.digia.com/Products/Qt-Enterprise-Embedded}. + + \section1 3rd Party Software Licenses + + The third-party licenses used in \SDK are listed in the file + \c {/Licenses/ThirdPartySoftware_Listing.txt}. + + \section2 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. +*/ + /*! \page qtee-troubleshooting.html \title Troubleshooting -- cgit v1.2.3 From 27d1ec0a2f4f5d2ee21c9b275ccdd70391eebe16 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 22 Oct 2013 14:14:03 +0200 Subject: Doc: Clarify Supported Nexus 7 model We support the Nexus 7 model from 2012. Change-Id: Icd61b3b5bb15de16b086ae174487cdca26f023c9 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 3fc385b..4b8b437 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -30,7 +30,7 @@ \li \l{Installation Guide} \li \l{Preparing Hardware} \list - \li \l{Preparing Nexus 7}{Nexus 7 (embedded Android)} + \li \l{Preparing Nexus 7}{Nexus 7 (2012) (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android and Linux)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} @@ -228,7 +228,7 @@ \B2Q stack. These steps vary from device to device: \list - \li \l{Nexus 7 (embedded Android)} + \li \l{Nexus 7 (2012) (embedded Android)} \li \l{Sabre Lite i.MX 6 (embedded Android and Linux)} \li \l{BeagleBoard-xM (embedded Android and Linux)} \li \l{Raspberry Pi Model B (embedded Linux)} @@ -239,13 +239,13 @@ */ /*! - \target Nexus 7 (embedded Android) + \target Nexus 7 (2012) (embedded Android) \page qtee-preparing-hardware-nexus-7.html \title Preparing Nexus 7 \previouspage qtee-installation-guide.html \nextpage qtee-building-and-running.html - When using a \l{http://www.google.com/nexus/7/specs/}{Nexus 7} as a + When using a \l{http://www.google.com/nexus/7/specs/}{Nexus 7 (2012)} as a development device, following steps are required to prepare it for \B2Q. @@ -713,7 +713,7 @@ The following devices have been used as reference and are tested to work: \list - \li \l{http://www.google.com/nexus/7/specs/}{Google/Asus Nexus 7} + \li \l{http://www.google.com/nexus/7/specs/}{Google/Asus Nexus 7 (2012)} \li \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} \li \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Freescale i.MX6 Sabre Lite board (Boundary Devices)} \li \l{http://www.raspberrypi.org/faqs}{Raspberry Pi Model B} -- cgit v1.2.3 From c03fcde202a0dea22e753b3a380081415861d9da Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 22 Nov 2013 12:04:18 +0100 Subject: Add license headers Add an Enterprise License header to source files. Change-Id: I373886dade31ce00d4c10c64ebaf8ba226d5a62d Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4b8b437..dd71d52 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -1,17 +1,19 @@ /**************************************************************************** ** -** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies). +** Copyright (C) 2013 Digia Plc +** All rights reserved. +** For any questions to Digia, please use the contact form at +** http://qt.digia.com/ ** -** Qt and Qt logos are trademarks of of Digia Corporation in Finland and/or -** other countries worldwide. All other trademarks are property of their -** respective owners. +** 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. ** -** Licensees holding valid Qt Commercial licenses may use this document in -** accordance with the Qt Commercial 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://qt.digia.com/ ** ****************************************************************************/ -- cgit v1.2.3 From 6571cbdc59025b54de648f1d87d3578a4612d962 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Thu, 5 Dec 2013 14:09:51 +0100 Subject: Doc: move overview info to a new topic MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add some information from the Qt Enterprise Embedded site to explain the basic concepts that the reader will encounter in the installation chapter. Change-Id: I0d6ed724bb1e502850035744ac099f9ca9546b1a Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 86 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 62 insertions(+), 24 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index dd71d52..0bb03b5 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -20,15 +20,25 @@ /*! \contentspage{index.html}{Qt Enterprise Embedded} \page index.html - \nextpage qtee-installation-guide.html + \nextpage qtee-overview.html \title Qt Enterprise Embedded + \SDK provides 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. \SDK contains the tools + you need for fast, easy, and fully-integrated embedded device application + development. It comes with \B2Q, a light-weight UI stack for embedded + systems, and the Qt Creator integrated development environment (IDE) with + preconfigured build targets for hardware platforms, as well as an emulator + for testing the applications. + \e{\b{IMPORTANT:} Make sure to follow the \l{Installation Guide} closely!} \section1 Contents \list + \li \l{About Qt Enterprise Embedded} \li \l{Installation Guide} \li \l{Preparing Hardware} \list @@ -43,27 +53,59 @@ \li \l{License Information} \li \l{Troubleshooting} \endlist +*/ - \section1 About \SDK - - \SDK includes the \B2Q stack, providing a complete software development - package for creating applications on embedded devices. It comes with - the Qt Creator IDE with preconfigured build targets for hardware - platforms as well as an \l{Emulator}{emulator}. +/*! + \contentspage{index.html}{Qt Enterprise Embedded} + \page qtee-overview.html + \previouspage index.html + \nextpage qtee-installation-guide.html - \section1 What is \B2Q? + \title About Qt Enterprise Embedded - \e{\b{\B2Q}} is a light-weight UI stack for embedded systems, based on the - \l{http://qt.digia.com/}{Qt Framework} by Digia, offering an elegant - means of developing beautiful and performant embedded devices. It supports - two different operating systems: + \SDK has two main parts: \list - \li \b{\B2QA} places Qt on top of an Android (version 4.1 or higher) - kernel/baselayer. + \li Development environment that is installed on a Linux development + desktop by using an online installer. + \li \B2Q + \endlist - \li \b{\B2QL} places Qt on top of an Linux kernel/baselayer, built - using Yocto 1.4 'Dylan' release. + \section1 About the Development Environment + + The development is done with the Qt Enterprise libraries and device + deployment can be done with one click directly from Qt Creator to a device + connected via USB. Alternatively, you can deploy the application locally + directly to the \B2Q Emulator that is running the full target software stack + as in the device. + + As with any Qt based application, the same application can be deployed to + desktop and mobile OS targets as well. + + \section1 About \B2Q + + \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 device's internal memory + directly with a pre-built image that comes with the development environment. + + \B2Q supports two different operating systems: + + \list + \li \b{\B2QA} where the software stack is based on the Android Kernel + (version 4.1 or higher) and selected middleware. It includes a lean + software stack where Qt/QML replaces the top Java graphical layer + and removes the Zygote process layer as well the Android home screen + enabling better and faster development where modern UIs are at the + forefront. + + \li \b{\B2QL} where the software stack is using the traditional embedded + Linux kernel built with the Yocto Poky reference system (Yocto 1.4 + \e Dylan release). Because of its Yocto compliance, 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. \endlist Both versions have been tested and verified on a number of different @@ -74,7 +116,7 @@ \l{http://qt.digia.com/}{Qt} is a full development framework with tools designed to streamline the creation of applications and user interfaces - for desktop, embedded and mobile platforms. + for desktop, embedded, and mobile platforms. \list \li \b{Qt Framework} - intuitive APIs for C++ @@ -88,8 +130,8 @@ \endlist With Qt, you can reuse code efficiently to target multiple platforms - with one code base. The modular C++ class library and developer tools - enables developers to create applications for one platform and easily + with one code base. The modular C++ class library and development tools + enable developers to create applications for one platform and easily build and run to deploy also on other platforms. @@ -108,16 +150,12 @@ \e{Dalvik virtual machine} is not running in \B2Q, resulting in faster startup times, lower memory consumption and overall better performance. - - \b{\B2QL} is build from scratch using Yocto 1.4 tools - to contain only components required in the embedded device, resulting - in smaller image sizes while keeping valuable development tools available. */ /*! \page qtee-installation-guide.html \title Installation Guide - \previouspage index.html + \previouspage qtee-overview.html \nextpage qtee-preparing-hardware.html \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} -- cgit v1.2.3 From 62e3601a82c60cfa41c3b7b6981c3f6bdca7d546 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Thu, 5 Dec 2013 14:52:52 +0100 Subject: Doc: move related sections together in TOC MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Place License Information last. Change-Id: If5122f5bf0c9aeee544fe999cb44442729f26abe Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 0bb03b5..378f092 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -40,6 +40,7 @@ \list \li \l{About Qt Enterprise Embedded} \li \l{Installation Guide} + \li \l{Supported Platforms} \li \l{Preparing Hardware} \list \li \l{Preparing Nexus 7}{Nexus 7 (2012) (embedded Android)} @@ -49,9 +50,8 @@ \endlist \li \l{Building and Running an Example} \li \l{Customization} - \li \l{Supported Platforms} - \li \l{License Information} \li \l{Troubleshooting} + \li \l{License Information} \endlist */ @@ -156,7 +156,7 @@ \page qtee-installation-guide.html \title Installation Guide \previouspage qtee-overview.html - \nextpage qtee-preparing-hardware.html + \nextpage qtee-supported-platforms.html \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} @@ -260,7 +260,7 @@ /*! \page qtee-preparing-hardware.html \title Preparing Hardware - \previouspage qtee-installation-guide.html + \previouspage qtee-supported-platforms.html \nextpage qtee-building-and-running.html Before deploying and testing your Qt application on hardware, the @@ -589,7 +589,7 @@ /*! \page qtee-building-and-running.html \title Building and Running an Example - \previouspage qtee-installation-guide.html + \previouspage qtee-preparing-hardware.html \nextpage qtee-customization.html Once the installation and configuration steps for \SDK and the @@ -643,7 +643,7 @@ \page qtee-customization.html \title Customization \previouspage qtee-building-and-running.html - \nextpage qtee-supported-platforms.html + \nextpage qtee-troubleshooting.html \section1 Environment and Input @@ -734,8 +734,8 @@ /*! \page qtee-supported-platforms.html \title Supported Platforms - \previouspage qtee-customization.html - \nextpage qtee-licenses.html + \previouspage qtee-installation-guide.html + \nextpage qtee-preparing-hardware.html \section1 Supported Target Devices @@ -770,8 +770,7 @@ /*! \page qtee-licenses.html \title License Information - \previouspage qtee-supported-platforms.html - \nextpage qtee-troubleshooting.html + \previouspage qtee-troubleshooting.html \section1 Licensing @@ -795,7 +794,8 @@ /*! \page qtee-troubleshooting.html \title Troubleshooting - \previouspage qtee-supported-platforms.html + \previouspage qtee-customization.html + \nextpage qtee-licenses.html \note An updated version of this information may be available in Digia customer portal, see Known Issues in Qt Enterprise Embedded product page. -- cgit v1.2.3 From f4e22adea13f4d9b0fbbe1c407aacb9d5584dd97 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 9 Dec 2013 09:58:08 +0100 Subject: Doc: edit the installation instructions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove excessive formatting as it reduces readability. Use numbered lists to describe processes. Use active voice instead of passive voice. Edit for grammar and style. Change-Id: I1e5f9636c57898ea09633167e022a3195a2967d6 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 76 +++++++++++++++++++++++++++------------------------ 1 file changed, 40 insertions(+), 36 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 378f092..f682f13 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -158,14 +158,15 @@ \previouspage qtee-overview.html \nextpage qtee-supported-platforms.html - \e{IMPORTANT: \SDK requires the following installation steps to be followed closely.} + To successfully set up \SDK, you must closely follow the instructions in + this section and perform all the described tasks. In case of problems, see the \l{Troubleshooting} information and the - Known Issues in Qt Enterprise Embedded product page in Digia customer + \e {Known Issues} on the Qt Enterprise Embedded product page in the Digia customer portal. \target Requirements for Development Host - \section1 0. Requirements for Development Host + \section1 Requirements for Development Host A 64-bit Linux system is required to install and use \SDK. Instructions in this documentation assume Ubuntu Linux 64-bit 12.04 LTS or later. @@ -176,8 +177,8 @@ \section1 1. Installing 32-bit Support Libraries Some of the build tools in \SDK are 32-bit programs, and on 64-bit - systems they require that support libraries for running 32-bit - code are present in the system. To install the required packages + systems they require support libraries for running 32-bit code. To install + the required packages in Ubuntu, use the following command in a terminal: \code @@ -195,56 +196,60 @@ sudo apt-get install virtualbox \endcode - \b{Configuring VirtualBox} + To configure VirtualBox: - Open VirtualBox network settings: Select \b{File > Preferences...} - and click on the \b{Network} tab. Create a new network named - \e{vboxnet0} and edit its properties: - - \list - \li Change IPv4 address to 192.168.56.1 and IPv4 network mask to 255.255.255.0. - \li Check \b{Enable Server} in \b{DCHP Server} tab. - \li Change server address to 192.168.56.1. - \li Change both the lower and upper address bounds to 192.168.56.101. + \list 1 + \li Start the VirtualBox user interface. + \li Select \b{File > Preferences} > \b{Network} to open VirtualBox + network settings. + \li Create a new network named \e{vboxnet0} and edit its properties: + + \list 1 + \li Change the IPv4 address to \c{192.168.56.1} and the IPv4 network + mask to \c{255.255.255.0}. + \li In the \b{DCHP Server} tab, select the \b{Enable Server} check + box. + \li Change the server address to \c{192.168.56.1}. + \li Change both the lower and upper address bounds to + \c{192.168.56.101}. + \endlist \endlist \section1 3. Installing \SDK - If you have not already installed \SDK, do it as follows. + \list 1 - After downloading the binary installer, make sure it is executable either by + \li Download the binary \SDK installer, and make sure it is executable + by using one of the following methods: \list - \li Using \c{chmod +x } command, or - \li Right-clicking on the file, selecting \b{Properties}, and checking - \b{Allow executing file as program} on the \b{Permissions} tab. + \li Enter the \c{chmod +x } command. + \li Right-click the file, and select \b{Properties} > + \b{Permissions} > \b{Allow executing file as program}. \endlist - Run the installer and follow its instructions. + \li Run the installer and follow its instructions. + + \endlist The installer will let you select a directory where \SDK will be - installed. In the rest of this documentation, that directory is referred + installed. In this documentation, the installation directory is referred to as \b{\c{}}. The default installation directory is \tt{~/Qt}. \target Installing Boot to Qt on Target Devices \section1 4. Install \B2Q on Target Devices - \e{If targeting only the emulator, this step may be skipped} + \e{If you target only the emulator, you can skip this step.} - Before deploying and testing your Qt application on hardware, the - target device needs to be flashed with an image that contains the - \B2Q stack. These steps vary from device to device. See the - following chapter and follow the instructions specific to - your device. - - \list - \li \l {Preparing Hardware} - \endlist + 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. The steps vary from device to device. Follow the instructions + specific to your device in \l {Preparing Hardware}. \section1 5. Setting up USB Access to Embedded Devices - \e{If targeting only the emulator, this step may be skipped} + \e{If you target only the emulator, you can skip this step.} \include b2qt-post-install-setup.qdocinc setting up usb access @@ -252,9 +257,8 @@ \include b2qt-post-install-setup.qdocinc configuring device kit - \b {You are now ready to start developing for your device!} - - See \l{Building and Running an Example} + You are now ready to start developing for your device. + For more information, see \l{Building and Running an Example}. */ /*! -- cgit v1.2.3 From 8beaad9609ce1bf51069450b2a95117b957c1e2f Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 9 Dec 2013 12:56:07 +0100 Subject: Doc: edit the supported devices topic MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix the capitalization of units of measurement and use spaces between the units and the numbers. Edit the leading sentence to the list of supported devices. Change-Id: I440a55f855d687ce46d3188373a4624b775529a0 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index f682f13..a11a561 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -749,13 +749,13 @@ Approximate minimal hardware requirements for running \B2Q are: \list - \li 256Mb of RAM - \li 500Mhz CPU, 1Ghz preferred for 60 FPS velvet-smooth UI + \li 256 MB of RAM + \li 500 MHz CPU, 1 GHz preferred for 60-FPS velvet-smooth UI \li OpenGL ES 2.0 support \li Android 4.0+ compatible hardware \endlist - The following devices have been used as reference and are tested to work: + \B2Q has been tested to work on the following reference devices: \list \li \l{http://www.google.com/nexus/7/specs/}{Google/Asus Nexus 7 (2012)} \li \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} -- cgit v1.2.3 From 5160df08e58a7901eb0836649184afcc9d492b05 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 9 Dec 2013 13:00:27 +0100 Subject: Doc: edit troubleshooting topic MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Edit for grammar and style. Use QDoc commands consistently. Change-Id: I2faf83811632b1640b504f538a714d0d7a9243b6 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 41 ++++++++++++++++++++++------------------- 1 file changed, 22 insertions(+), 19 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index a11a561..c6a7769 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -801,17 +801,18 @@ \previouspage qtee-customization.html \nextpage qtee-licenses.html - \note An updated version of this information may be available in Digia customer portal, - see Known Issues in Qt Enterprise Embedded product page. + \note An updated version of this information may be available in the Digia + customer portal, in the \e{Known Issues} section on the \SDK product page. \section1 General Issues \section2 I have problems deploying/launching the application in Qt Creator - Check if the device is properly connected to the PC via USB. + Check that the device is properly connected to the development host via USB + or Ethernet (depending on the device). See \l{Connectivity Issues}. - If using the emulator, see \l{Installing VirtualBox}{Configuring VirtualBox}. + If using the emulator, see \l{Installing VirtualBox}. \section2 I have problems deploying/launching a Qt or Qt Quick example application @@ -831,8 +832,8 @@ \section2 Booting Sabre Lite i.MX 6 stops with \e {6x_bootscript not found} error Check the U-Boot version number. It should start with either \c{2012} or \c{2013}. - If it is \c{2009.xx}, an upgrade of the bootloader is required. See information and - instructions here: + If it is \c{2009.xx}, an upgrade of the bootloader is required. For more + information, see: \list \li \l http://boundarydevices.com/6q_bootscript/ @@ -841,8 +842,9 @@ \section2 How do I restore my Nexus 7 to factory settings? - Goto \l{https://developers.google.com/android/nexus/images} and - download the correct file for your device. Unpack it, and then + 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: \code /Tools/b2qt/adb reboot bootloader @@ -851,10 +853,10 @@ \section2 How do I shut down the Nexus 7? - If the \B2Q demo launcher is running, start the "Launcher - Settings" app, and press the "Power Off" button. + If the \B2Q demo launcher is running, start the \b {Launcher + Settings} app, and press the power button to power off the device. - Otherwise, make sure the Nexus 7 is connected to your PC with USB, and run + Otherwise, make sure the Nexus 7 is connected to the development host, and run the following command in a terminal: \code /Tools/b2qt/adb shell reboot -p @@ -865,7 +867,8 @@ \section2 Trying to build for the emulator target fails with error message \e{make: i686-android-linux-g++: Command not found} - You need to install proper libraries in order to run 32-bit programs in 64-bit Linux operating system. + 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}. @@ -880,7 +883,7 @@ See \l{Customization}. - Note that hotplugging does not currently work; any input device + \note Hotplugging does not currently work, and therefore, any input device must be present at boot time to be recognized. \section2 Application stops with \e{EGLFS: OpenGL windows cannot be mixed with others.} @@ -906,7 +909,7 @@ \section2 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 Android device you want \c{adb} to talk to, using adb's \c{-s } option. Use the following command to find to see the serial number of the connected devices: @@ -915,17 +918,17 @@ /Tools/b2qt/adb devices \endcode - \section2 The emulator cannot connect to the internet + \section2 The emulator cannot connect to the Internet - By default, the Virtualbox is configured to use host-only network, so external + By default, the VirtualBox is configured to use a host-only network, so external connections do not work in the emulator. - You may be able to enable internet connectivity with another + You may be able to enable Internet connectivity with another virtual network adapter in NAT mode by adapting \l{http://askubuntu.com/questions/293816/in-virtualbox-how-do-i-set-up-host-only-virtual-machines-that-can-access-the-in}{these} instructions. - \section2 The emulator is stuck in 'Waiting for display data' or fails to start properly + \section2 The emulator is stuck in \e{Waiting for display data} or fails to start properly Check the output of the following command: @@ -946,7 +949,7 @@ And then close the emulator and retry. - \section2 What is the user and password to access my embedded Linux device + \section2 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. -- cgit v1.2.3 From d3fc80299709a9a872acacfc7cc2c9a8934ec53b Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 9 Dec 2013 16:35:37 +0100 Subject: Doc: edited the customization topic MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Edited for style and grammar. Change-Id: I57a9f72db0300c475b752a20bb613caa9a41b570 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index c6a7769..704600e 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -656,30 +656,29 @@ {/system/bin/appcontroller.conf} in embedded Android devices and in \c{/etc/appcontroller.conf} in embedded Linux devices. - This file can be customized if targeting a hardware device that - has different input devices than what the \B2Q stack is configured + 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 for by default. - Note that on some devices, the root file system (where this file - resides) is mounted read-only at boot time. It needs to be - remounted read-write to allow modification. The following command - does that: + On some devices, the root file system (where this file + resides) is mounted read-only at boot time. To allow modification, + remount it read-write by entering the following command: \code /Tools/b2qt/adb remount \endcode - In the \c{appcontroller.conf} file the input devices are + In the \c{appcontroller.conf} file, the input devices are specified by the lines similar to these: \code env=QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/event0 \endcode - Usually there is no need to change this setting. USB input devices like - keyboards and mice are automatically recognized. The mouse pointer is shown + Usually, you do not need to change this setting. USB input devices, such as + keyboards and mice, are automatically recognized. The mouse pointer is shown automatically if a mouse is connected. - Note however that hotplugging may not work, meaning that the input - devices, like keyboard and mouse, have to be connected at boot + However, hotplugging may not work, which means that the input + devices, such as a keyboard and mouse, have to be connected at boot time. On some devices, for example the i.MX6 Sabre Lite, the touchscreen device is @@ -688,18 +687,21 @@ \section1 Booting to a Custom Application - After you have deployed your own application to the device it will be launched instead - of the \B2Q demo launcher on boot. To prevent this behavior you have to remove - this step from the build steps of your project's run configuration. + After you have deployed your own application to the device, it will be + launched on boot, instead of the \B2Q demo launcher. To prevent this + behavior, remove the \b {Make this application the default one} step from + the \b{Run Settings} for your project in the Qt Creator \b Projects mode. - To remove your application from the default startup use the following command: + To remove your application from the default startup, use the following + command: \code /Tools/b2qt/adb shell appcontroller --remove-default \endcode \section1 Switching Between Portrait and Landscape Views - Depending on a device screen dimensions and application requirements it might be desirable + Depending on device screen dimensions and application requirements, it might + be desirable to change the default view orientation. The following example shows how to rotate your application in QML. -- cgit v1.2.3 From 11daeacb2580a36e8cf267d370d7f40195a16e58 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Mon, 9 Dec 2013 12:34:22 +0100 Subject: Doc: edit the building and running topi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Edit for grammar and style. Change-Id: I61bdbd5dbd4adc8badfe7e5aebe0c43f2a7a875e Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 32 +++++++++++++++----------------- 1 file changed, 15 insertions(+), 17 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 704600e..7a96856 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -596,19 +596,17 @@ \previouspage qtee-preparing-hardware.html \nextpage qtee-customization.html - Once the installation and configuration steps for \SDK and the - target device(s) are completed, it's time to test the setup. - - First, make sure your device is powered up and connected to the - development host via USB. - - Then, follow these steps to create and run a simple \l{Qt Quick} - application on the device: + After you complete the installation and configuration steps for \SDK and the + target devices, you can test the setup by creating a simple \l{Qt Quick} + application and running it on the device: \list 1 - \li Open \b{File > New File or Project}, select - \b{Qt Quick 2 Application (Built-in Types)} and click \b{Choose...}. - \li In \b{Kit Selection} dialog, select the kit(s) for your + \li Make sure that your device is powered up and connected to the + development host. + \li In Qt Creator, select \b{File > New File or Project} > + \b Applications > \b{Qt Quick 2 Application (Built-in Types)} > + \b{Choose}. + \li In the \b{Kit Selection} dialog, select the kits for your devices. You can also select the emulator kit to test running the project in the emulator. \li Click \b{Next} and finish the wizard. @@ -619,23 +617,23 @@ \section1 Setting Up an Already Existing Project for Deployment - The projects generated by Qt Creator will always have the correct settings + The projects generated by Qt Creator always have the correct settings for deployment on the device or emulator. However, existing projects may need some changes. As a general rule, application binaries and resources (such as QML files and - images) are deployed under \c {/data/user/qt/} directory. - Therefore, the \c path variable for \c INSTALLS target(s) need to be adjusted - accordingly in .pro files: + images) are deployed to the \c {/data/user/qt/} directory. + Therefore, the \c path variable for the \c INSTALLS targets needs to be adjusted + accordingly in .pro files. - For example, the following: + For example, change the following \c target.path value: \code target.path = ... INSTALLS += target \endcode - should be migrated to: + to: \code target.path = /data/user/qt/ -- cgit v1.2.3 From c56c9bc0107bced7635bc93edd8521f415e005c7 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Tue, 10 Dec 2013 12:26:21 +0100 Subject: Doc: edit the sections about preparing devices MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Edit for grammar and style. Use standard wording in lists. Use active voice instead of passive voide. Use lists for all processes. Use the term "SD card" everywhere instead of "micro-SD card". Replace XXX with . Change-Id: Ie300dac911b42120de5e236676aa7b43c39f27d7 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 185 ++++++++++++++++++++++++++------------------------ 1 file changed, 95 insertions(+), 90 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 7a96856..4169cff 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -267,8 +267,8 @@ \previouspage qtee-supported-platforms.html \nextpage qtee-building-and-running.html - Before deploying and testing your Qt application on hardware, the - target device needs to be flashed with an image that contains the + 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 @@ -278,7 +278,7 @@ \li \l{Raspberry Pi Model B (embedded Linux)} \endlist - If you are only using the emulator, you can skip this step + If you use only the emulator, you can skip this step and continue straight to \l {Building and Running an Example}. */ @@ -289,39 +289,45 @@ \previouspage qtee-installation-guide.html \nextpage qtee-building-and-running.html - When using a \l{http://www.google.com/nexus/7/specs/}{Nexus 7 (2012)} as a - development device, following steps are required to prepare it for + Take the following steps to prepare a + \l{http://www.google.com/nexus/7/specs/}{Nexus 7 (2012)} for \B2Q. \section1 Unlocking Nexus 7 Bootloader - The Nexus 7 Bootloader has to be unlocked to allow custom software - to be installed. This has to be done only once. + You must unlock the Nexus 7 Bootloader to be able to install custom + software. You need to do this only once. \list 1 \li Power down the device. - \li Connect it to the development host with a USB cable. - \li Start the Nexus up in \e{fastboot} mode: Press the power button for a second, and then keep the Volume Down key pressed, until you see a screen with a green robot with its front panel open. Note: If you get the ordinary startup screen instead, just power it down and try again. - \li On the development host, give the command + \li Connect the device to the development host with a USB cable. + \li To start the Nexus up in \e{fastboot} mode, press the power button + for a second, and then keep the \b {Volume Down} key pressed down, + until you see a screen with a green robot with its front panel open. + \note If the ordinary startup screen appears instead, power down the + device and try again. + \li On the development host, enter the following command: \code sudo /Tools/b2qt/fastboot oem unlock \endcode - The Nexus screen will ask if you want to unlock the bootloader. Press power button to confirm. + \li Press the power button to confirm that you want to unlock the + bootloader when the prompt appears on the Nexus screen. \li Wait a few seconds, and check that the text line stating the \c{LOCK STATE} now says \c{UNLOCKED}. \endlist \section1 Updating a Nexus 7 with \B2Q Images - \note \b{It is important that the steps in this section are repeated - every time after updating \SDK.} + \note It is important that you repeat the steps in this section after you + update \SDK. - An unlocked Nexus 7 device can now be updated with a \B2Q image. + To update an unlocked Nexus 7 device with a \B2Q image: - To do so, first make sure that the device is in \e{fastboot} mode - (see above), and connected to the development host via USB. + \list 1 + \li Make sure that the device is in \e{fastboot} mode and that it is + connected to the development host via USB. - Then, re-flash the \e{boot}, \e{system}, and \e{userdata} partitions on the - device, using the following commands in the order they are listed: + \li Re-flash the \e{boot}, \e{system}, and \e{userdata} partitions on the + device, by entering the following commands in the following order: \code cd @@ -330,18 +336,21 @@ sudo ./Tools/b2qt/fastboot flash userdata Boot2Qt-1.0/nexus7-eAndroid/images/data.img \endcode - Once the flashing is completed successfully, reboot the device: + \li Once the flashing is completed successfully, reboot the device: \code sudo ./Tools/b2qt/fastboot reboot \endcode - \note Until the next step is performed, the Nexus 7 will not - boot correctly (the screen will only show the "Google" logo). + \endlist + + \note You must install proprietary drivers for the Nexus 7 to boot + correctly. Until then, the screen will only show the "Google" logo, + instead of the \B2Q welcome screen or demo. \section1 Installing Proprietary Drivers - Download the proprietary drivers for your Nexus 7. The following script will download the third + Download the proprietary drivers for your Nexus 7. The following script downloads the third party drivers from \l{https://developers.google.com/android/nexus/drivers#grouperjdq39} {https://developers.google.com/android/nexus/drivers#grouperjdq39} \code @@ -349,15 +358,14 @@ ./Boot2Qt-1.0/nexus7-eAndroid/images/download.sh \endcode - \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" will work with the current \B2Q image. - - Make sure your Nexus 7 is powered up, is \e{not} in fastboot mode, - and is connected to the computer via USB. + \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" works with the + current \B2Q image. - Then, follow these steps to update the Nexus 7: - \note Make sure you have read the license terms enclosed in each individual extractor + To install the drivers to Nexus 7: \list 1 + \li Power up the device and connect it to the development host via USB. + Also check that the device is \e{not} in fastboot mode. \li Run the driver extractors: \code cd Boot2Qt-1.0/nexus7-eAndroid/images/drivers @@ -366,18 +374,20 @@ ./extract-invensense-grouper.sh cd - \endcode + \note Carefully read the license terms enclosed in each individual + extractor. \li Find out the serial number of the connected Nexus 7 device: \code ./Tools/b2qt/adb devices \endcode - \li Deploy the drivers to your device using the following command: + \li Deploy the drivers to your device: \code ./Boot2Qt-1.0/nexus7-eAndroid/images/deploy.sh \endcode \endlist - After the installation is complete, power up the device and confirm that it shows - a \B2Q welcome screen and/or demo. + After the installation is complete, power up the device and check that + the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -387,9 +397,8 @@ \include b2qt-post-install-setup.qdocinc configuring device kit - \b {You are now ready to start developing for your device!} - - See \l{Building and Running an Example} + You are now ready to start developing for your device. For more information, + see \l{Building and Running an Example}. */ /*! @@ -399,20 +408,20 @@ \previouspage qtee-installation-guide.html \nextpage qtee-building-and-running.html - When using a \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} as a - development device, following steps are required to prepare it for + Take the following steps to prepare a \l{http://beagleboard.org/hardware-xM} + {BeagleBoard-xM} for \B2Q. - \note \b{It is important that the steps in this section are repeated - every time after updating \SDK.} + \note It is important that you repeat the steps in this section after you + update \SDK. - The images containing \B2Q stack for BeagleBoard-xM is included in the SDK, - ready to be copied to a micro-SD card. + The images containing \B2Q stack for BeagleBoard-xM are included in \SDK, + ready to be copied to an SD card. - \section1 Preparing a Micro-SD Card + \section1 Preparing an SD Card - For \B2QA, a micro-SD card of at least 2GB capacity is needed. For \B2QL, - a card of at least 512MB capacity is sufficient. + For \B2QA, an SD card of at least 2 GB capacity is needed. For \B2QL, + a card of at least 512 MB capacity is sufficient. \include detect-sd-card-device-name.qdocinc instructions @@ -421,23 +430,23 @@ The commands used in this step vary depending on whether you are developing for embedded Android or embedded Linux. - Write the image to the micro-SD card: + To write the image to the SD card: \list \li \b{\B2QA} \code cd - sudo dd if=Boot2Qt-1.0/beagleboard-eAndroid/images/sdcard.img of=/dev/XXX bs=1M + sudo dd if=Boot2Qt-1.0/beagleboard-eAndroid/images/sdcard.img of=/dev/ bs=1M \endcode \li \b{\B2QL} \code cd - sudo Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/XXX + sudo Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/ \endcode \endlist - After the image has been deployed, power up the device and confirm that it shows - a \B2Q welcome screen and/or demo. + After the image has been deployed, power up the device and check that + the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -447,9 +456,8 @@ \include b2qt-post-install-setup.qdocinc configuring device kit - \b {You are now ready to start developing for your device!} - - See \l{Building and Running an Example} + You are now ready to start developing for your device. For more information, + see \l{Building and Running an Example}. */ /*! @@ -458,21 +466,20 @@ \title Preparing Sabre Lite i.MX 6 \previouspage qtee-installation-guide.html - When using a + Take the following steps to prepare a \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Sabre - Lite i.MX 6} as a development device, following steps are required - to prepare it for \B2Q. + Lite i.MX 6} for \B2Q. - \note \b{It is important that the steps in this section are repeated - every time after updating \SDK.} + \note It is important that you repeat the steps in this section after you + update \SDK. The images containing the \B2Q stack for Sabre Lite i.MX 6 are included - in the SDK, ready to be copied to a micro-SD card. + in \SDK, ready to be copied to an SD card. - \section1 Preparing a Micro-SD Card + \section1 Preparing an SD Card - For \B2QA, a micro-SD card of at least 4GB capacity is needed. For \B2QL, - a card of at least 512MB capacity is sufficient. + For \B2QA, an SD card of at least 4 GB capacity is needed. For \B2QL, + a card of at least 512 MB capacity is sufficient. \include detect-sd-card-device-name.qdocinc instructions @@ -485,11 +492,11 @@ \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 a micro-SD card containing the + Use the following commands to create an SD card containing the downloaded image: - \list - \li Extract the downloaded package + \list 1 + \li Extract the downloaded package: \code ~/$ mkdir bd-android ~/$ cd bd-android @@ -497,7 +504,7 @@ \endcode \li Run device/boundary/mksdcard.sh: \code - ~/bd-android$ sudo device/boundary/mksdcard.sh /dev/XXX + ~/bd-android$ sudo device/boundary/mksdcard.sh /dev/ ~/bd-android$ sync \endcode \endlist @@ -510,24 +517,24 @@ sudo apt-get install u-boot-tools \endcode - Then, upgrade the micro-SD Card with \B2Q. Use one of the commands below, - depending on whether you're developing for embedded Android or Linux: + Then, upgrade the SD card with \B2Q. Use one of the commands below, + depending on whether you are developing for embedded Android or Linux: \list \li \b{\B2QA} \code cd - Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/XXX + Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/ \endcode \li \b{\B2QL} \code cd - Boot2Qt-1.0/iMX6-eLinux/images/deploy.sh /dev/XXX + Boot2Qt-1.0/iMX6-eLinux/images/deploy.sh /dev/ \endcode \endlist - After the installation is complete, power up the device and confirm that it shows - a \B2Q welcome screen and/or demo. + After the installation is complete, power up the device and check that + the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -537,9 +544,8 @@ \include b2qt-post-install-setup.qdocinc configuring device kit - \b {You are now ready to start developing for your device!} - - See \l{Building and Running an Example} + You are now ready to start developing for your device. For more information, + see \l{Building and Running an Example}. */ /*! @@ -549,45 +555,44 @@ \previouspage qtee-installation-guide.html \nextpage qtee-building-and-running.html - When using a \l{http://www.raspberrypi.org/}{Raspberry Pi} as a - development device, following steps are required to prepare it for + Take the following steps to prepare a \l{http://www.raspberrypi.org/} + {Raspberry Pi} for \B2Q. - Note that Ethernet networking is required to connect the device to Qt Creator. - This means that the support is currently limited to Raspberry Pi Model B which + \note Ethernet networking is required to connect the device to Qt Creator. + This means that the support is currently limited to Raspberry Pi Model B, which includes an Ethernet port. - \note \b{It is important that the steps in this section are repeated - every time after updating \SDK.} + \note It is important that you repeat the steps in this section after you + update \SDK. - The images containing \B2Q stack for Raspberry Pi is included in the SDK, - ready to be copied to a micro-SD card. + The image containing \B2Q stack for Raspberry Pi is included in the SDK, + ready to be copied to an SD card. - \section1 Preparing a Micro-SD Card + \section1 Preparing an SD Card - An SD card of at least 512MB capacity is sufficient. + An SD card of at least 512 MB capacity is sufficient. \include detect-sd-card-device-name.qdocinc instructions \section1 Installing the \B2Q Image - Write the image to the micro-SD card: + To write the image to the SD card: \code cd - sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/XXX + sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/ \endcode - After the image has been deployed, power up the device and confirm that it shows - a \B2Q welcome screen and/or demo. + After the image has been deployed, power up 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 - \b {You are now ready to start developing for your device!} - - See \l{Building and Running an Example} + You are now ready to start developing for your device. For more information, + see \l{Building and Running an Example}. */ /*! -- cgit v1.2.3 From 46a143c9fef70647a1d06ce4fc1b9ef85e796bc9 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Tue, 10 Dec 2013 14:11:04 +0100 Subject: Doc: unify punctuation of list items MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove the period from the end of the first list item for consistency. Change-Id: I8926473a804be175c50ddf2dd0923bcc8e98c37c Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4169cff..a6515e4 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -67,7 +67,7 @@ \list \li Development environment that is installed on a Linux development - desktop by using an online installer. + desktop by using an online installer \li \B2Q \endlist -- cgit v1.2.3 From 59649939d06664d722046cd54e0933c5b402e9a9 Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Tue, 10 Dec 2013 14:33:36 +0100 Subject: Doc: use power off/on consistently MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify the options to power off Nexus 7. Change-Id: I13fe92c6cdc00d9033a603edd2bde334aacf8a77 Reviewed-by: Rainer Keller Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index a6515e4..61635d6 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -299,12 +299,12 @@ software. You need to do this only once. \list 1 - \li Power down the device. + \li Power off the device. \li Connect the device to the development host with a USB cable. \li To start the Nexus up in \e{fastboot} mode, press the power button for a second, and then keep the \b {Volume Down} key pressed down, until you see a screen with a green robot with its front panel open. - \note If the ordinary startup screen appears instead, power down the + \note If the ordinary startup screen appears instead, power off the device and try again. \li On the development host, enter the following command: \code @@ -364,7 +364,7 @@ To install the drivers to Nexus 7: \list 1 - \li Power up the device and connect it to the development host via USB. + \li Power on the device and connect it to the development host via USB. Also check that the device is \e{not} in fastboot mode. \li Run the driver extractors: \code @@ -386,7 +386,7 @@ \endcode \endlist - After the installation is complete, power up the device and check that + After the installation is complete, power on the device and check that the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -445,7 +445,7 @@ \endcode \endlist - After the image has been deployed, power up the device and check that + After the image has been deployed, power on the device and check that the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -533,7 +533,7 @@ \endcode \endlist - After the installation is complete, power up the device and check that + After the installation is complete, power on the device and check that the \B2Q welcome screen and/or demo appear. \section1 Setting up USB Access @@ -584,7 +584,7 @@ sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/ \endcode - After the image has been deployed, power up the device and check that + After the image has been deployed, power on the device and check that the \B2Q welcome screen and/or demo appear. \section1 Configuring a Device Kit in Qt Creator @@ -606,7 +606,7 @@ application and running it on the device: \list 1 - \li Make sure that your device is powered up and connected to the + \li Make sure that your device is powered on and connected to the development host. \li In Qt Creator, select \b{File > New File or Project} > \b Applications > \b{Qt Quick 2 Application (Built-in Types)} > @@ -859,7 +859,7 @@ \section2 How do I shut down the Nexus 7? If the \B2Q demo launcher is running, start the \b {Launcher - Settings} app, and press the power button to power off the device. + 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: @@ -867,6 +867,9 @@ /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. -- cgit v1.2.3 From 6873ff8924ff9adcb065bddfd772eb71054b5b73 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 21 Jan 2014 10:37:56 +0100 Subject: Doc: Bump B2Qt version in the docs to 2.0.0 Set the b2qt version in the docs to 2.0.0. Also add dependencies to other doc modules, which may be useful in the future. Change-Id: I2034c893a3cce7d19c4a7198a34ebfc532aecddb Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e7ef357..34ae33d 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -335,9 +335,9 @@ \code cd - sudo ./Tools/b2qt/fastboot flash boot Boot2Qt-1.0/nexus7-eAndroid/images/boot.img - sudo ./Tools/b2qt/fastboot flash system Boot2Qt-1.0/nexus7-eAndroid/images/system.img - sudo ./Tools/b2qt/fastboot flash userdata Boot2Qt-1.0/nexus7-eAndroid/images/data.img + sudo ./Tools/b2qt/fastboot flash boot Boot2Qt-2.x/nexus7-eAndroid/images/boot.img + sudo ./Tools/b2qt/fastboot flash system Boot2Qt-2.x/nexus7-eAndroid/images/system.img + sudo ./Tools/b2qt/fastboot flash userdata Boot2Qt-2.x/nexus7-eAndroid/images/data.img \endcode \li Once the flashing is completed successfully, reboot the device: @@ -359,7 +359,7 @@ {https://developers.google.com/android/nexus/drivers#grouperjdq39} \code cd - ./Boot2Qt-1.0/nexus7-eAndroid/images/download.sh + ./Boot2Qt-2.x/nexus7-eAndroid/images/download.sh \endcode \note Only the version "Android 4.2.2 (JDQ39 to JDQ39E)" works with the @@ -372,7 +372,7 @@ Also check that the device is \e{not} in fastboot mode. \li Run the driver extractors: \code - cd Boot2Qt-1.0/nexus7-eAndroid/images/drivers + cd Boot2Qt-2.x/nexus7-eAndroid/images/drivers ./extract-nvidia-grouper.sh ./extract-asus-grouper.sh ./extract-invensense-grouper.sh @@ -386,7 +386,7 @@ \endcode \li Deploy the drivers to your device: \code - ./Boot2Qt-1.0/nexus7-eAndroid/images/deploy.sh + ./Boot2Qt-2.x/nexus7-eAndroid/images/deploy.sh \endcode \endlist @@ -440,12 +440,12 @@ \li \b{\B2QA} \code cd - sudo dd if=Boot2Qt-1.0/beagleboard-eAndroid/images/sdcard.img of=/dev/ bs=1M + sudo dd if=Boot2Qt-2.x/beagleboard-eAndroid/images/sdcard.img of=/dev/ bs=1M \endcode \li \b{\B2QL} \code cd - sudo Boot2Qt-1.0/beagleboard-eLinux/images/deploy.sh /dev/ + sudo Boot2Qt-2.x/beagleboard-eLinux/images/deploy.sh /dev/ \endcode \endlist @@ -528,12 +528,12 @@ \li \b{\B2QA} \code cd - Boot2Qt-1.0/iMX6-eAndroid/images/deploy.sh /dev/ + Boot2Qt-2.x/iMX6-eAndroid/images/deploy.sh /dev/ \endcode \li \b{\B2QL} \code cd - Boot2Qt-1.0/iMX6-eLinux/images/deploy.sh /dev/ + Boot2Qt-2.x/iMX6-eLinux/images/deploy.sh /dev/ \endcode \endlist @@ -585,7 +585,7 @@ \code cd - sudo Boot2Qt-1.0/raspberrypi-eLinux/images/deploy.sh /dev/ + sudo Boot2Qt-2.x/raspberrypi-eLinux/images/deploy.sh /dev/ \endcode After the image has been deployed, power on the device and check that -- cgit v1.2.3 From 0e71a8a6df15433715fb9c6b54ad5962527f3126 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 30 Jan 2014 12:16:05 +0100 Subject: Doc: Remove embedded Android support for Beagleboard B2Qt 2.0 will support only embedded Linux on Beagleboard. Task-number: QTEE-303 Change-Id: Id9b0058a929ab7f441bcb17795ff5c562facb89f Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 30 +++++++++--------------------- 1 file changed, 9 insertions(+), 21 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 34ae33d..5c8ea7e 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -45,7 +45,7 @@ \list \li \l{Preparing Nexus 7}{Nexus 7 (2012) (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android and Linux)} - \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Android and Linux)} + \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Linux)} \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} \endlist \li \l{Building and Running an Example} @@ -278,7 +278,7 @@ \list \li \l{Nexus 7 (2012) (embedded Android)} \li \l{Sabre Lite i.MX 6 (embedded Android and Linux)} - \li \l{BeagleBoard-xM (embedded Android and Linux)} + \li \l{BeagleBoard-xM (embedded Linux)} \li \l{Raspberry Pi Model B (embedded Linux)} \endlist @@ -406,7 +406,7 @@ */ /*! - \target BeagleBoard-xM (embedded Android and Linux) + \target BeagleBoard-xM (embedded Linux) \page qtee-preparing-hardware-beagleboard.html \title Preparing BeagleBoard-xM \previouspage qtee-installation-guide.html @@ -419,35 +419,23 @@ \note It is important that you repeat the steps in this section after you update \SDK. - The images containing \B2Q stack for BeagleBoard-xM are included in \SDK, + The image containing \B2Q stack for BeagleBoard-xM are included in \SDK, ready to be copied to an SD card. \section1 Preparing an SD Card - For \B2QA, an SD card of at least 2 GB capacity is needed. For \B2QL, - a card of at least 512 MB capacity is sufficient. + An SD card of at least 512 MB capacity is needed. \include detect-sd-card-device-name.qdocinc instructions \section1 Installing the \B2Q Image - The commands used in this step vary depending on whether you are developing - for embedded Android or embedded Linux. - To write the image to the SD card: - \list - \li \b{\B2QA} - \code - cd - sudo dd if=Boot2Qt-2.x/beagleboard-eAndroid/images/sdcard.img of=/dev/ bs=1M - \endcode - \li \b{\B2QL} - \code - cd - sudo Boot2Qt-2.x/beagleboard-eLinux/images/deploy.sh /dev/ - \endcode - \endlist + \code + cd + sudo Boot2Qt-2.x/beagleboard-eLinux/images/deploy.sh /dev/ + \endcode After the image has been deployed, power on the device and check that the \B2Q welcome screen and/or demo appear. -- cgit v1.2.3 From ca32a427ba15ddcf410e84069416757d366612f4 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 31 Jan 2014 11:24:35 +0100 Subject: Doc: Remove comment about Yocto compliance Task-number: QTEE-311 Change-Id: Ibf4052919e6235c569345d96c4244743a843b758 Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 5c8ea7e..e2322de 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -101,11 +101,10 @@ \li \b{\B2QL} where the software stack is using the traditional embedded Linux kernel built with the Yocto Poky reference system (Yocto 1.4 - \e Dylan release). Because of its Yocto compliance, 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. + \e Dylan 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. \endlist Both versions have been tested and verified on a number of different -- cgit v1.2.3 From 5be3cb521cdd67eeeac18e7f252fe89e2050e6b8 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 31 Jan 2014 10:21:21 +0100 Subject: Doc: Add BeagleBone Black Task-number: QTEE-302 Change-Id: I1c608ea0934a69244077a87de0f843993a3fc8d0 Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 86 +++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 84 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e2322de..1b29b5a 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -45,6 +45,7 @@ \list \li \l{Preparing Nexus 7}{Nexus 7 (2012) (embedded Android)} \li \l{Preparing Sabre Lite i.MX 6}{Sabre Lite i.MX 6 (embedded Android and Linux)} + \li \l{Preparing BeagleBone Black}{BeagleBone Black (embedded Android and Linux)} \li \l{Preparing BeagleBoard-xM}{BeagleBoard-xM (embedded Linux)} \li \l{Preparing Raspberry Pi}{Raspberry Pi Model B (embedded Linux)} \endlist @@ -277,6 +278,7 @@ \list \li \l{Nexus 7 (2012) (embedded Android)} \li \l{Sabre Lite i.MX 6 (embedded Android and Linux)} + \li \l{BeagleBone Black (embedded Android and Linux)} \li \l{BeagleBoard-xM (embedded Linux)} \li \l{Raspberry Pi Model B (embedded Linux)} \endlist @@ -524,7 +526,7 @@ \endcode \endlist - After the installation is complete, power on the device and check that + 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 @@ -575,7 +577,7 @@ sudo Boot2Qt-2.x/raspberrypi-eLinux/images/deploy.sh /dev/ \endcode - After the image has been deployed, power on the device and check that + 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 @@ -586,6 +588,85 @@ see \l{Building and Running an Example}. */ +/*! + \target BeagleBone Black (embedded Android and Linux) + \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 + + For \B2QA, an SD card of at least 2 GB capacity is needed. For \B2QL, + a card of at least 512 MB capacity is sufficient. + + \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}. + + Download the package \e{TI_Android_JB_4.2.2_DevKit_4.1.1_beagleboneblack.tar.gz} from + \l{http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html} + {Texas Instruments} (search for \e {BeagleBone Black} in the list of download packages). + + Use the following commands to create an SD card containing the + downloaded image: + + \list 1 + \li Extract the downloaded package: + \code + ~$ tar zxvf ~/Downloads/TI_Android_JB_4.2.2_DevKit_4.1.1_beagleboneblack.tar.gz + \endcode + \li Run beagleboneblack/mkmmc-android.sh: + \code + ~$ cd beagleboneblack + ~/beagleboneblack$ sudo ./mkmmc-android.sh /dev/ + \endcode + \endlist + + \section1 Installing the \B2Q Image + + Then, upgrade the SD card with \B2Q. Use one of the commands below, + depending on whether you are developing for embedded Android or Linux: + + \list + \li \b{\B2QA} + \code + cd + ./Boot2Qt-2.x/beaglebone-eAndroid/images/deploy.sh /dev/ + \endcode + \li \b{\B2QL} + \code + cd + sudo ./Boot2Qt-2.x/beaglebone-eLinux/images/deploy.sh /dev/ + \endcode + \endlist + + 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 + + \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}. +*/ + /*! \page qtee-building-and-running.html \title Building and Running an Example @@ -756,6 +837,7 @@ \list \li \l{http://www.google.com/nexus/7/specs/}{Google/Asus Nexus 7 (2012)} \li \l{http://beagleboard.org/hardware-xM}{BeagleBoard-xM} + \li \l{http://beagleboard.org/products/beaglebone%20black}{BeagleBone Black} \li \l{http://boundarydevices.com/products/sabre-lite-imx6-sbc/}{Freescale i.MX6 Sabre Lite board (Boundary Devices)} \li \l{http://www.raspberrypi.org/faqs}{Raspberry Pi Model B} \endlist -- cgit v1.2.3 From 7d7611c59bb762632de26408306afd4d9201e8a4 Mon Sep 17 00:00:00 2001 From: Rainer Keller Date: Tue, 4 Feb 2014 12:57:26 +0100 Subject: Remove unnecessary sudo Change-Id: I8f02a214a328f2bc7010b1e2b7ddec7a4417abf2 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 1b29b5a..4627d38 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -493,7 +493,7 @@ \code ~/$ mkdir bd-android ~/$ cd bd-android - ~/bd-android$ sudo tar zxvf ~/Downloads/imx6-jb-20130628.tar.gz + ~/bd-android$ tar zxvf ~/Downloads/imx6-jb-20130628.tar.gz \endcode \li Run device/boundary/mksdcard.sh: \code -- cgit v1.2.3 From bd7d57e8d1729f5fb749f857d9d739ba0a1877d8 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 5 Feb 2014 14:15:52 +0100 Subject: Doc: Fix external links Fix links to external pages and separate them as their own qdoc file. Change-Id: Ia41b53f7480b9a9d76d8785d478d3e07c384670e Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4627d38..3fcf594 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -87,8 +87,8 @@ \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 device's internal memory - directly with a pre-built image that comes with the development environment. + done by flashing the device's memory card or internal memory directly with a + pre-built image that comes with the development environment. \B2Q supports two different operating systems: @@ -162,8 +162,7 @@ this section and perform all the described tasks. In case of problems, see the \l{Troubleshooting} information and the - \e {Known Issues} on the Qt Enterprise Embedded product page in the Digia customer - portal. + \l {Known Issues} in \SDK \l {product page}. \target Requirements for Development Host \section1 Requirements for Development Host @@ -859,7 +858,7 @@ \SDK is licensed under the Qt Enterprise commercial license. For more information, see \l {http://qt.digia.com/licensing}. Evaluation licenses are also available, - see \l {http://qt.digia.com/Products/Qt-Enterprise-Embedded}. + see \l {product page}{\SDK} on qt.digia.com. \section1 3rd Party Software Licenses @@ -880,8 +879,8 @@ \previouspage qtee-customization.html \nextpage qtee-licenses.html - \note An updated version of this information may be available in the Digia - customer portal, in the \e{Known Issues} section on the \SDK product page. + \note An updated version of this information may be available in Digia customer portal, + see \l {Known Issues} in \SDK \l {product page}. \section1 General Issues -- cgit v1.2.3 From ee9274a7de9a48d02c4a160499510a79dec2e658 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 5 Feb 2014 14:19:27 +0100 Subject: Doc: Bump Yocto release version in documentation Change-Id: I50cde4aa039fcbf800e4a24f984a62dc377fa01c Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 3fcf594..e6676c2 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -101,8 +101,8 @@ forefront. \li \b{\B2QL} where the software stack is using the traditional embedded - Linux kernel built with the Yocto Poky reference system (Yocto 1.4 - \e Dylan release). The Embedded Linux variant is designed for great + Linux kernel built with the Yocto Poky reference system (Yocto 1.5 + \e Dora 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. -- cgit v1.2.3 From 1b6fd6de76b4491902f519438ca0b8ed7582daa9 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Tue, 4 Feb 2014 14:15:49 +0100 Subject: Doc: Add Android GCC run-time licensing information Add license information specific to the libstdc++ library used in the embedded Android images to the documentation. Task-number: QTEE-306 Change-Id: I31cf6c1667a1af1638ff1d1b984321712d50ab26 Reviewed-by: Samuli Piippo Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index e6676c2..c85513b 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -865,12 +865,28 @@ The third-party licenses used in \SDK are listed in the file \c {/Licenses/ThirdPartySoftware_Listing.txt}. - \section2 Embedded Android Images + \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. + + \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}. */ /*! -- cgit v1.2.3 From 94a21c6ea25c6d363cfc7d5a402638de40e9b254 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 5 Feb 2014 14:21:13 +0100 Subject: Doc: Add changelog Change-Id: Iba235b61d96981765fb2e94be572e46a31a93b82 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 84 +++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 81 insertions(+), 3 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index c85513b..4bbc5f5 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -51,6 +51,7 @@ \endlist \li \l{Building and Running an Example} \li \l{Customization} + \li \l{ChangeLog} \li \l{Troubleshooting} \li \l{License Information} \endlist @@ -722,7 +723,7 @@ \page qtee-customization.html \title Customization \previouspage qtee-building-and-running.html - \nextpage qtee-troubleshooting.html + \nextpage qtee-changelog.html \section1 Environment and Input @@ -816,7 +817,7 @@ \page qtee-supported-platforms.html \title Supported Platforms \previouspage qtee-installation-guide.html - \nextpage qtee-preparing-hardware.html + \nextpage qtee-changelog.html \section1 Supported Target Devices @@ -889,10 +890,87 @@ \l{http://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html}{the official license page}. */ +/*! + \page qtee-changelog.html + \title ChangeLog + \previouspage qtee-customization.html + \nextpage qtee-troubleshooting.html + + \section1 \B2Q 2.0.0 + + \list + \li Release date: February 2014 + \endlist + + \section2 Changes + \b {New Features}: + \list + \li \B2Q stack was updated to use Qt 5.2.1 on embedded Android and Linux + \li Building your own \B2Q embedded Linux stack was enabled + \li Emulator graphics performance and quality was improved (GL-streaming) + \li BeagleBone Black was added as a reference device + \li \l {Qt Virtual Keyboard} was integrated into \B2Q + \li \l {Qt Quick Enterprise Controls} was added to the \B2Q stack + \li \l {Qt Charts} was added to the \B2Q stack + \li \B2Q source code was made available via online installer + \li WiFi networking support/configuration were implemented on embedded Android + \li Ethernet connectivity was enabled on embedded Android + \endlist + + \b {Improvements}: + \list + \li Updated GDB for embedded Android toolchain + \li Enterprise demos (Charts, Enterprise Controls) were added + \li Embedded Linux: Moved to use Yocto 1.5 (Dora) + \li Demos available as examples in Qt Creator + \li Embedded Android emulator updated to Android 4.2.2 + \endlist + + \b {Fixed Bugs}: + \list + \li Embedded Android emulator: Missing Mesa headers + \li Embedded Linux emulator: Black screen in camera demo + \li Emulator tries to load host plugins + \li Sensors not working in emulators + \li Empty \c HOME environment variable in processes launched by appcontroller + \li Black screen after exiting the last Qt application on Nexus 7 + \li Embedded Android emulator: C++ debugging fails + \li Qt add-ons not installed to host + \endlist + + \b {Fixed Known Issues}: + \list + \li Qt SQL: QML LocalStorage Fails to Connect to Database on Embedded Android + \li Qt XML Patterns: Module not Available on embedded Android + \li Qt Multimedia: Audio is Muted on Nexus 7 + \li Unnecessary Warnings Displayed by the Installer + \li Virtual Keyboard: Backspace Removes Two Characters + \endlist + + \section1 \B2Q 1.0.1 + + \list + \li Release date: Dec. 5, 2013 + \endlist + + \section2 Changes + \list + \li Emulator: Remote control widget version shown together with emulator version + \li Emulator: Mouse events are sent instead of touch events + \li Emulator: Raster window support added + \li Emulator: emulatorproxyd shows its version on startup + \li Emulator: Detect some network problems + \li Emulator: Fixed issues related to startup + \li Emulator: Updated source code license headers + \li Emulator: Show all VirtualBox errors + \li Emulator: Video playback support on embedded Linux + \endlist +*/ + /*! \page qtee-troubleshooting.html \title Troubleshooting - \previouspage qtee-customization.html + \previouspage qtee-changelog.html \nextpage qtee-licenses.html \note An updated version of this information may be available in Digia customer portal, -- cgit v1.2.3 From b3eff1babcc6d45e10c80078c0c27ce7782c9695 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Mon, 10 Feb 2014 13:50:08 +0100 Subject: Doc: ChangeLog: Remove 'black screen after exit' from bugfixes This bug still exists for 2.0 Change-Id: I6703e247a9d890276163dfed7ecc99c59bee4592 Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 1 - 1 file changed, 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4bbc5f5..39c9f95 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -933,7 +933,6 @@ \li Emulator tries to load host plugins \li Sensors not working in emulators \li Empty \c HOME environment variable in processes launched by appcontroller - \li Black screen after exiting the last Qt application on Nexus 7 \li Embedded Android emulator: C++ debugging fails \li Qt add-ons not installed to host \endlist -- cgit v1.2.3 From 0aa007f78b412ca5591b8d8c07039166055037d9 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 12 Feb 2014 11:00:18 +0100 Subject: Doc: Fix the 2.0 release date Change-Id: I329ce97d32a1d1745fc5da1a939603c500940b00 Reviewed-by: Kalle Viironen --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 39c9f95..4e14b8c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -899,7 +899,7 @@ \section1 \B2Q 2.0.0 \list - \li Release date: February 2014 + \li Release date: Feb. 25, 2014 \endlist \section2 Changes -- cgit v1.2.3 From b7347b14ba53a3d847ec783855a2c46101fafac3 Mon Sep 17 00:00:00 2001 From: aavit Date: Tue, 11 Feb 2014 13:48:34 +0100 Subject: Update copyright year MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Ic818e79d7bfca04bd8a8d8aa12b3ff70ea26a7a3 Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4e14b8c..3ee3a0a 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -1,6 +1,6 @@ /**************************************************************************** ** -** Copyright (C) 2013 Digia Plc +** Copyright (C) 2014 Digia Plc ** All rights reserved. ** For any questions to Digia, please use the contact form at ** http://qt.digia.com/ -- cgit v1.2.3 From 7a67c281301590b0f6305fc2cf118d28216b5362 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Wed, 12 Feb 2014 11:01:17 +0100 Subject: Doc: Document building your own embedded linux stack Task-number: QTEE-176 Change-Id: I9641ea529f651fe5a19cfa0f0abff48096b26381 Reviewed-by: Eirik Aavitsland Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 3ee3a0a..41e3065 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -811,6 +811,72 @@ } } \endcode + + \section1 Building Your Own Embedded Linux Image + + \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. + + \section2 Requirements + + You should be familiar with the Yocto tools and the concept of + \e {recipes}. For more information, see Yocto Project + \l{https://www.yoctoproject.org/documentation/current}{documentation}. + + To get started, you need the following: + + \list + \li Install the \B2Q \e source packages. You can + find these by running the \e MaintenanceTool application + located in the \SDK installation directory and selecting + \e {Package Manager}. The \e {Yocto meta layer} package + contains the additional recipes required to make the image + compatible with \B2Q. + \li Install the dependencies for the Yocto tools. In Ubuntu, + the following packages are required: + \code + sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \ + build-essential chrpath libsdl1.2-dev xterm + \endcode + \endlist + + \section2 Setting Up Yocto Build Environment + + Run the setup script that initializes the Yocto environment: + + \code + cd + /Boot2Qt-2.x/sources/b2qt-yocto-meta/scripts/b2qt-init-build-env . + \endcode + + \section2 Building the Image and Toolchain + + After the Yocto environment is set up, you need to configure the + build environment for your target device. Using Raspberry Pi as + an example: + + \code + export TEMPLATECONF=meta-b2qt/conf + export MACHINE=raspberrypi + source poky/oe-init-build-env build-raspberrypi + \endcode + + Yocto recipes for \B2QL have two main targets to build: The target image, + and the external toolchain that is used for building the Qt framework and + applications. + + \code + bitbake b2qt-embedded-image + bitbake meta-toolchain-b2qt-embedded-sdk + \endcode + + \note The generated target image does not yet include Qt libraries, + you need to build Qt and add it into the image yourself. The + file \c {embedded-linux/build_qt.sh} from the \e {Build scripts} source + package can be used as reference on how to configure and build Qt. */ /*! -- cgit v1.2.3 From b0f603852172c5a1a1f0be62bb171cd1fa65d8ae Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 13 Feb 2014 10:04:41 +0100 Subject: Doc: Troubleshooting entry for BeagleBone Black HDMI issues Task-number: QTEE-329 Change-Id: If2d305c0e2b4165fca7c00910bb498124ade3abb Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 41e3065..b1a3e60 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -1105,6 +1105,16 @@ Alternatively, press and hold the power button for 10 seconds. This will force a reboot. + \section2 How do I get HDMI output working properly on BeagleBone Black? + + Depending on the HDMI monitor, the cable, and the build variant of + the BeagleBone Black device, it may not be able to drive an HDMI display in a + stable way; the image may disappear or stutter. These issues are not caused by + the \B2Q stack. + + More details and possible solutions can be found + \l {http://www.elinux.org/Beagleboard:BeagleBoneBlack_HDMI}{here}. + \section2 Trying to build for the emulator target fails with error message \e{make: i686-android-linux-g++: Command not found} You need to install support libraries in order to run 32-bit programs in a -- cgit v1.2.3 From 69e4deb9dc7432d6c3cbff371f5fa3016d517c93 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 13 Feb 2014 10:41:11 +0100 Subject: Doc: Add instructions for building Boot2Qt demos Document where to find the demos in Qt Creator and fix the template name used in the example building instructions. Task-number: QTEE-350 Change-Id: I8b132920d3e63d9813c65338d50db4eb66c465de Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index b1a3e60..694dc7c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -681,7 +681,7 @@ \li Make sure that your device is powered on and connected to the development host. \li In Qt Creator, select \b{File > New File or Project} > - \b Applications > \b{Qt Quick 2 Application } > \b{Choose}. + \b Applications > \b{Qt Quick Application} > \b{Choose}. \li Choose a location for your new project. \li In the \b{Qt Quick Component Set} dialog, select \b{Qt Quick 2.0}. \li In the \b{Kit Selection} dialog, select the kits for your @@ -693,6 +693,19 @@ \li To build and run the project, click \inlineimage qtcreator-run.png \endlist + \section1 Building and Running \B2Q Demos + + You can find the \B2Q demo applications in Qt Creator. + + \list 1 + \li Go to \b Welcome > \b Examples. + \li Select a \e Boot2Qt Qt version from the drop-down list. + \li Select a demo you want to build. + \li In \b{Projects > Build & Run}, select the correct kit for your + connected device or emulator. + \li To build and run the project, click \inlineimage qtcreator-run.png + \endlist + \section1 Setting Up an Already Existing Project for Deployment The projects generated by Qt Creator always have the correct settings -- cgit v1.2.3 From 912758262e2036f55c4e36e43d4acc3564759e29 Mon Sep 17 00:00:00 2001 From: aavit Date: Mon, 17 Feb 2014 14:48:01 +0100 Subject: Doc: Explain about disabling surfaceflinger MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Ib4dbfc3d5f62ba3792f44b191143039c63d880df Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 694dc7c..80be1d3 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -825,6 +825,23 @@ } \endcode + \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 Building Your Own Embedded Linux Image \B2QL is built using the tools and resources from the \l {Yocto Project}, -- cgit v1.2.3 From f80e4d4811e4c4f38c65fa7bbc2ec6df9c0283c0 Mon Sep 17 00:00:00 2001 From: Rainer Keller Date: Tue, 18 Feb 2014 14:29:12 +0100 Subject: Doc: Add instructions how to install newer VirtualBox MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I54899c905d334215c40a9dcb4a4035d173cc625b Reviewed-by: Kalle Viironen Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 80be1d3..0107d7e 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -190,10 +190,21 @@ The \B2Q emulator in \SDK relies on VirtualBox virtualization software. You can download it from \l{https://www.virtualbox.org/wiki/Linux_Downloads} or - install it from the command line with the following command: + install it via distribution tools. + If you have older Ubuntu versions such as 12.04 you have to install a newer + version of VirtualBox than your distribution does provide. + You have to add a foreign package source: + + \code + wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add - + echo "deb http://download.virtualbox.org/virtualbox/debian $(lsb_release -sc) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list + sudo apt-get update + \endcode + + Now install VirtualBox on your computer \code - sudo apt-get install virtualbox + sudo apt-get install virtualbox-4.3 \endcode To configure VirtualBox: -- cgit v1.2.3 From f6d8f83364c013da0dfeb7247a17271b56a69491 Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Wed, 19 Feb 2014 15:14:51 +0200 Subject: doc: add quide how to use b2qt_build_scripts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I08cc79fe34cc45a96c3387370a78060541cd3d1d Reviewed-by: Andy Nichols Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 0107d7e..9416260 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -915,9 +915,35 @@ \endcode \note The generated target image does not yet include Qt libraries, - you need to build Qt and add it into the image yourself. The - file \c {embedded-linux/build_qt.sh} from the \e {Build scripts} source - package can be used as reference on how to configure and build Qt. + you need to build Qt and add it into the image yourself. + + \section2 Building Qt and addons + + \e {Build scripts} source package contains scripts that can be used to + build Qt and all additional Qt addons that are part of \B2QL image. + To setup build environment for your target hardware, create new build + directory and run the initialization script. Using Raspberry Pi as + an example: + + \code + cd + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-common/init_build_env.sh \ + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + \endcode + + You can use following scripts to build different parts of the \B2Q stack. + + \code + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_qt.sh \ + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_extras.sh \ + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_image.sh \ + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + \endcode + + After \e {embedded-linux/build_image.sh} has finished, you can flash the devices with + the updated image located in the build folder. */ /*! -- cgit v1.2.3 From 385333ee85fd336d610861017b4c180ba0e60c39 Mon Sep 17 00:00:00 2001 From: aavit Date: Thu, 20 Feb 2014 10:47:18 +0100 Subject: Doc: Fixed 32bit package install command for newer ubuntu versions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit QTEE-414 Change-Id: I79e0e2f2191d02bf5859338ba1583567eb430284 Reviewed-by: Laszlo Agocs Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 9416260..a85ecf8 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -177,9 +177,15 @@ \section1 1. Installing 32-bit Support Libraries Some of the build tools in \SDK are 32-bit programs, and on 64-bit - systems they require support libraries for running 32-bit code. To install - the required packages - in Ubuntu, use the following command in a terminal: + systems they require support libraries for running 32-bit code. To + install the required packages in recent versions of Ubuntu, use + the following command in a terminal: + + \code + sudo apt-get install g++-multilib zlib1g:i386 + \endcode + + For older Ubuntu versions such as 12.04, instead do: \code sudo apt-get install g++-multilib ia32-libs -- cgit v1.2.3 From 788e5c1b3526dd6ad5c26a9918a733564764392d Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 20 Feb 2014 10:46:51 +0100 Subject: Doc: Fix missing sudo for i.MX6 embedded Linux deployment Task-number: QTEE-406 Change-Id: I146c189ba2996fe8c7b79ea4aef5c8c2716bb7bf Reviewed-by: Eirik Aavitsland --- src/doc/src/b2qt.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index a85ecf8..5c1d81c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -534,12 +534,12 @@ \li \b{\B2QA} \code cd - Boot2Qt-2.x/iMX6-eAndroid/images/deploy.sh /dev/ + ./Boot2Qt-2.x/iMX6-eAndroid/images/deploy.sh /dev/ \endcode \li \b{\B2QL} \code cd - Boot2Qt-2.x/iMX6-eLinux/images/deploy.sh /dev/ + sudo ./Boot2Qt-2.x/iMX6-eLinux/images/deploy.sh /dev/ \endcode \endlist -- cgit v1.2.3 From f5abf901305804a64516a5ec9ebc3c151ab0c51b Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Thu, 20 Feb 2014 12:40:44 +0100 Subject: Doc: Clarify which Qt Creator templates work out of the box A quick fix for QTEE-399 - we'll need better instructions what changes are needed for example Qt Widgets projects. Task-number: QTEE-399 Change-Id: I5d4999d2d5d5a3af5a4966e7253094966f387410 Reviewed-by: Kalle Viironen --- src/doc/src/b2qt.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 5c1d81c..4150b23 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -725,8 +725,8 @@ \section1 Setting Up an Already Existing Project for Deployment - The projects generated by Qt Creator always have the correct settings - for deployment on the device or emulator. However, existing projects may + New Qt Quick application projects generated by Qt Creator always have the correct + settings for deployment on the device or emulator. However, other projects may need some changes. As a general rule, application binaries and resources (such as QML files and -- cgit v1.2.3 From 6dd8882f595fb6545badcf735e371c77a47906f8 Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Fri, 21 Feb 2014 10:02:46 +0200 Subject: doc: minor changes to customization inline code blocks MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit formatting changes and one path correction. Change-Id: I7a358f7dd210d84d67ea10257bfa2a91cd97bb1f Reviewed-by: Topi Reiniö --- src/doc/src/b2qt.qdoc | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 4150b23..d589020 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -885,8 +885,7 @@ \li Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required: \code - sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \ - build-essential chrpath libsdl1.2-dev xterm + sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath libsdl1.2-dev xterm \endcode \endlist @@ -896,7 +895,7 @@ \code cd - /Boot2Qt-2.x/sources/b2qt-yocto-meta/scripts/b2qt-init-build-env . + /Boot2Qt-2.x/sources/b2qt-yocto-meta/b2qt-init-build-env . \endcode \section2 Building the Image and Toolchain @@ -933,22 +932,18 @@ \code cd - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-common/init_build_env.sh \ - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-common/init_build_env.sh /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi \endcode You can use following scripts to build different parts of the \B2Q stack. \code - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_qt.sh \ - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_extras.sh \ - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_image.sh \ - /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_qt.sh /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_extras.sh /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi + /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/build_image.sh /Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi \endcode - After \e {embedded-linux/build_image.sh} has finished, you can flash the devices with + After \e {embedded-linux/build_image.sh} has finished, you can flash the device with the updated image located in the build folder. */ -- cgit v1.2.3 From 4738811e35a559d238ba20703eb792fca8f5756b Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Fri, 21 Feb 2014 10:10:10 +0100 Subject: Doc: Document support services for Yocto recipes Task-number: QTEE-427 Change-Id: I1f10fed48cbca8144b866cd50d3d7eaeb8caf2ac Reviewed-by: Kalle Viironen Reviewed-by: Samuli Piippo --- src/doc/src/b2qt.qdoc | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) (limited to 'src/doc/src/b2qt.qdoc') diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index d589020..6f2d44c 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -922,7 +922,7 @@ \note The generated target image does not yet include Qt libraries, you need to build Qt and add it into the image yourself. - \section2 Building Qt and addons + \section2 Building Qt and Addons \e {Build scripts} source package contains scripts that can be used to build Qt and all additional Qt addons that are part of \B2QL image. @@ -945,6 +945,14 @@ After \e {embedded-linux/build_image.sh} has finished, you can flash the device with the updated image located in the build folder. + + \section2 Note About Support Services for Yocto Tools + + By default, Digia will only provide customer support for the Yocto + recipes on the reference platforms, as delivered with \SDK, and + setting up the development environment for them. Receiving support + for any other configuration requires a separate service agreement + between a customer and Digia. */ /*! -- cgit v1.2.3