1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
/****************************************************************************
**
** Copyright (C) 2014 Digia Plc
** All rights reserved.
** For any questions to Digia, please use the contact form at
** http://www.qt.io
**
** This file is part of Qt Enterprise Embedded.
**
** Licensees holding valid Qt Enterprise licenses may use this file in
** accordance with the Qt Enterprise License Agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia.
**
** If you have questions regarding the use of this file, please use
** the contact form at http://www.qt.io
**
****************************************************************************/
/*!
//! [setting up usb access]
On Ubuntu Linux, the development user account must have access to plugged in
devices. To allow the development user access to the device via USB, create
a new \e{udev} rule:
\list 1
\li Run the following command in a shell:
\badcode
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", TAG+="udev-acl", TAG+="uaccess"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules
\endcode
\li Connect the running device to the development host with a USB
cable. If the device is already connected, disconnect and reconnect the USB
cable after running the command above.
\endlist
The system log files \c{/var/log/udev} and \c{/var/log/syslog} may
provide relevant information in case of connection problems.
You can confirm that the connection is working by running the following command on Linux:
\code
<INSTALL_DIR>/Tools/b2qt/adb devices -l
\endcode
Or the following command on Windows:
\code
<Android-SDK-Tools-install-dir>\platform-tools\adb.exe devices -l
\endcode
The output should be a list of connected \B2Q (and Android) devices,
identified with a serial number and a name. If your device is missing from
the list, or the serial number is \c{??????}, the connection is
not working properly. Check that the device is powered on, and disconnect
and reconnect the USB cable.
The emulator may be listed as well. Its serial number is its IP and the port
number: \c{192.168.56.101:5555}.
//! [setting up usb access]
//! [configuring device kit]
//! [common config device kit]
After you have prepared the hardware, you must perform one final step
to set up the development tools in Qt Creator for your device. That is,
you must configure the correct device to be used for each build and run
\e{kit}. Connect your device to the development host via USB and launch
Qt Creator. In Qt Creator:
//! [common config device kit]
//! [steps for device kit]
\list 1
\li Select \b{Tools > Options > Build & Run > Kits}.
\li Select one of the predefined kits starting with \e{Boot to Qt...}
that matches the type of your device.
\li Select the correct device in the \b{Device} field.
\li Select \b{OK}.
\endlist
//! [steps for device kit]
//! [configuring device kit]
//! [configuring network device]
After you have prepared the hardware, you must set up the development tools
in Qt Creator for your device. Connect your device to the network via an
Ethernet cable and launch Qt Creator. In Qt Creator:
\list 1
\li Select \b{Tools > Options > Devices > Add}.
\li Select \b{Boot2Qt Device} > \b{Start Wizard}.
\li Enter the device name and network address (IPv4). You can check the
device address in the \e{Launcher Settings} when the device is running
the \B2Q demo.
\li Select \b{Finish}.
\endlist
You also have to configure the correct device to be used for each build and
run \e{kit}:
\include b2qt-post-install-setup.qdocinc steps for device kit
//! [configuring network device]
//! [configuring device kit linux]
\include b2qt-post-install-setup.qdocinc common config device kit
\include b2qt-post-install-setup.qdocinc steps for device kit
//! [configuring device kit linux]
*/
|
