aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/linux-mobile/meegodev.qdoc
blob: 215a50f40ffcbd24adfe86f9b4aedd7d049b5feb (plain)
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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
/****************************************************************************
**
** Copyright (c) 2012 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/

    /*!

    \contentspage index.html
    \previouspage creator-developing-maemo.html
    \page creator-developing-meego.html
    \if defined(qcmanual)
    \nextpage creator-developing-qnx.html
    \else
    \nextpage creator-developing-maemo.html
    \endif

    \title Connecting MeeGo Harmattan Devices

    MeeGo Harmattan is a Linux-based software platform developed by Nokia for
    mobile devices. It allows developers to create applications using the Qt
    framework. You can install and configure the whole tool chain that you need
    to create, build, debug, run, and deploy Harmattan applications as part of
    the \QSDK.

    \if defined(qcmanual)
    For more information about the Harmattan platform, see
    \l{http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Harmattan_overview_5dcf.html}
    {Harmattan Overview} in the MeeGo 1.2 Harmattan Developer Library.
    \endif


    \note \QSDK does not contain the tool chains for building applications for
    other MeeGo devices than MeeGo Harmattan. You can try to run applications
    from \QC on other MeeGo devices, but it has not been extensively
    tested, and the instructions might not always apply.

    \note The only supported build system for Harmattan in \QC is qmake.

    \section1 Setting Up Connectivity in Harmattan Devices

    To build and run Qt applications for Harmattan, you need a Harmattan device:
    Nokia N950 or Nokia N9.

    You can connect your device to your development PC using either a USB or
    WLAN connection.

    For the device, you need to use the SDK Connectivity tool that is
    preinstalled on the device to create the device-side end point for USB and
    WLAN connections. It provides no diagnostics functions but is essential for
    creating connections between the device and your development PC.

    To use a WLAN connection, you must activate WLAN on the device and connect
    it to the same WLAN as the development PC. The network address is displayed
    in the connectivity tool.

    To use a USB connection, you might need to set up the device as a network
    device on the development PC. However, on Linux, Mac OS X, and Windows 7,
    the USB interface is usually automatically configured.

    \note If you plan to connect your development PC to the device only over
    WLAN, you can ignore the USB-specific parts in the following sections.

    \section2 Starting SDK Connectivity

    SDK Connectivity application is preinstalled in Harmattan devices and
    available in developer mode.

    To start SDK Connectivity:

    \list

        \o  On the device, select \gui {Settings > Security > Developer
            mode} to turn on developer mode.

        \o  Select \gui {Applications > SDK Connectivity} to start the SDK
            Connectivity application.

        \o  Select \gui {Select Connection} and then select the type of the
            connection to create: \gui WLAN or \gui USB.

        \o  For a USB connection, select the operating system of the
            development PC in \gui {Select Module}.

    \endlist

    \gui {Connectivity Details} displays the IP address and developer password.
    The address 192.168.2.15 is used by default. You must enter the password in
    \QC. For more information, see
    \l{Configuring Connections to Harmattan Devices}.

    \section1 Setting Up Network Connectivity on Development PC

    Use the network configuration tools on your platform to specify the
    connection to the device on the development PC. You need to do this
    only if you use a USB connection.

    The device uses the IP address 192.168.2.15 with the subnet 255.255.255.0
    for its USB connection by default, so you can create the network interface
    with a different address inside the same subnet too.

    \note If you have changed the IP address of the device in the connectivity
    tool, you need to reflect those changes in your development PC USB
    network settings.

    \section2 Linux

    The USB interface is automatically configured. If, for some reason, that is
    not the case, run the following command in a shell as root user to create a
    new network interface:

    \c{ifconfig usb0 192.168.2.14 up}

    \section2 Mac OS X

    The USB interface is automatically configured. If, for some reason, that is
    not the case, create a new network interface manually:

    \list

        \o  Open the network settings.

        \o  Click the + button on the network settings panel.

        \o  When the interface is available, select \gui {Configure IPv4 > Using
            DHCP with manual address}.

        \o Enter the address 192.168.2.14 into the IP address field.

        \o Click \gui Apply.

        The network connection between your device and workstation is now
        configured.

    \endlist

    \section2 Windows 7

    When you connect your device to your Windows 7 computer, Windows installs a
    driver for the Linux USB Ethernet connection automatically. If the
    installation does not start, unplug the USB cable and try another USB port
    on your computer.

    \note Driver installation takes some time.

    The USB interface is automatically configured. If, for some reason, that is
    not the case, create a new network interface manually:

    \list 1

        \o  Open the \gui {Network and Sharing Center} and select \gui {Change
            adapter settings}.

            The Linux USB Ethernet connection you just installed is displayed
            as a new \gui {Local Area Connection Linux USB Ethernet/RNDIS
            gadget}.

            \note If you cannot see \gui {Linux USB Ethernet/RNDIS gadget}, try
            to unplug and replug the USB cable.

        \o  Right-click \gui {Linux USB Ethernet/RNDIS gadget} and select
            \gui Properties.

    \o  Edit the \gui {Internet Protocol Version 4 (TCP/IPv4)} properties
        to specify the IP address for the connection. In the \gui {Use the
        following IP address} field, enter the following values:

        \list

           \o  \gui {IP Address}: \bold {192.168.2.14}
           \o  \gui SubnetMask: \bold {255.255.255.0}
           \o  \gui {Default gateway}: leave this field empty

        \endlist

    \endlist

    \section2 Windows XP

    If you develop on Windows XP and use a USB connection to run applications on
    the device, you need the Nokia USB drivers that are installed as part of the
    \QSDK.

    When you connect the device to your Windows PC, Windows tries to install a
    driver for the Linux USB Ethernet connection. In the
    \gui{Found New Hardware Wizard}, select \gui{No, not this time} in the
    first dialog and \gui{Install the software automatically} in the second
    dialog.

    To specify a network connection:

    \list 1

    \o  Open the Network Connections window.

    \o  Select the Linux USB Ethernet connection that is displayed as a new
        Local Area Connection.

    \o  Edit the \gui {Internet Protocol Version 4 (TCP/IPv4)} properties
        to specify the IP address for the connection. In the \gui {Use the
        following IP address} field, enter the following values:

        \list

           \o  \gui {IP Address}: \bold {192.168.2.14}
           \o  \gui SubnetMask: \bold {255.255.255.0}
           \o  \gui {Default gateway}: leave this field empty

        \endlist

    \endlist

    Depending on your version of Microsoft Windows you may have to unplug and
    re-plug the device to reload the driver with its configuration accordingly.

    \section1 Configuring Connections to Harmattan Devices

    To be able to run and debug applications on the emulator and devices, you
    must set up connections to the emulator and devices in the \QC build
    and run settings. If you install \QSDK, the connection to the emulator is
    configured automatically and you only need to configure a connection to the
    device.

    You use a wizard to create the connections. You can edit the settings later
    in \gui Tools > \gui Options > \gui Devices.

    \image qtcreator-meego-device-configurations.png "Devices dialog"

    By default, you create the connection as the \e developer user. This
    protects real user data on the device from getting corrupted during testing.
    If you write applications that use Qt Mobility APIs, you might want to test
    them with real user data. To create a connection as a user, specify the
    \gui Username and \gui Password in \QC. For more information, see
    \if defined(qcmanual)
    \l{Testing with User Data on MeeGo Devices}.
    \else
    \l{http://doc.qt.digia.com/qtcreator/creator-developing-meego.html#testing-with-user-data-on-meego-devices}
    {Testing with User Data on MeeGo Devices}.
    \endif


    You can protect the connections between \QC and a device by using
    either a password or an SSH key. If you use a password, you must generate it
    in the connectivity tool and enter it in \QC every time you start the
    connectivity tool.

    If you do not have an SSH key, you can create it in \QC. Encrypted
    keys are not supported. For more information, see
    \if defined(qcmanual)
    \l{Generating SSH Keys}.
    \else
    \l{http://doc.qt.digia.com/qtcreator/creator-developing-meego.html#generating-ssh-keys}
    {Generating SSH Keys}.
    \endif


    You can view processes running on devices and kill them. For more
    information, see
    \if defined(qcmanual)
    \l{Managing Device Processes}.
    \else
    \l{http://doc.qt.digia.com/qtcreator/creator-developing-meego.html#managing-device-processes}
    {Managing Device Processes}.
    \endif


    To configure connections between \QC and a device:

    \list 1

        \o  To deploy applications and run them remotely on devices,
            specify parameters for accessing devices:

            \list a

                \o  Connect your device to the development PC via a USB cable or
                    a WLAN. For a USB connection, you are prompted to select the
                    mode to use. Choose \gui{PC suite mode}.

                    \note If you experience connection problems due to a USB
                    port issue, switch to a different port or use WLAN to
                    connect to the device.

                \o  Select \gui Tools > \gui Options > \gui Devices > \gui Add.

                \o  Select \gui {MeeGo 1.2 Harmattan} > \gui {Start Wizard} to
                    add a new configuration for a device.

                    \image qtcreator-screenshot-devconf.png

                \o  In the \gui {The name to identify this configuration} field,
                    enter a name for the connection.

                \o  In the \gui {The kind of device} field, select
                    \gui {Hardware device}.

                \o  In the \gui {The device's host name or IP address} field,
                    enter the IP address from the connectivity tool on the
                    device.

                \o  In the \gui {The SSH server port} field, enter the port
                    number to use for SSH connections.

                \o  Click \gui Next.

                \o  Follow the instructions of the wizard to create the
                    configuration.

            \endlist

        \if defined(qcmanual)

        \o  To test applications on the emulator (QEMU), you must
            create a connection to it from the development PC. If you installed
            \QSDK, the connection is created automatically and you can omit this
            step.

            \list a

                \o  In \QC, select \gui Tools > \gui Options > \gui Devices >
                    \gui Add to add a new configuration.

                \o  Select \gui {MeeGo 1.2 Harmattan} > \gui {Start Wizard}.

                \o  In the \gui {The name to identify this configuration} field,
                    enter a name for the connection.

                \o  In the \gui {The kind of device} field, select
                    \gui Emulator.

                \o  Click \gui Next.

                \o  Follow the instructions of the wizard to create the
                    connection.

                    SDK Connectivity is not needed for emulator connections, and
                    therefore, you do not need to authenticate the emulator
                    connection.

            \endlist

        \endif

            \o  Select \gui Tools > \gui Options > \gui {Build & Run} >
                \gui Kits > \gui Add to add a kit for building for the device:

            \list a

                \o  In the \gui {Device type} field, select
                    \gui {MeeGo 1.2 Harmattan}.

                \o  In the \gui Device field, select the device that you added
                    above.

                \o  In the \gui Sysroot field, specify the path to the sysroot.
                    By default, the \QSDK installer places sysroot in the
                    following folder:
                    \c{QtSDK\Madde\bin\sysroots\harmattan_sysroot_10.2011.34-1_slim}.

                \o  In the \gui {Compiler type} field, select GCC.

                \o  In the \gui Compiler field, specify the path to the GCC
                    compiler. By default, the \QSDK installer places the
                    compiler in the following folder:
                    \c{QtSDK\Madde\targets\harmattan_10.2011.34-1_rt1.2\bin\}.

                \o  In the \gui Debugger field, specify the path to GDB. By
                    default, the \QSDK installer places the debugger
                    in the following folder:
                    \c{QtSDK\Madde\targets\harmattan_10.2011.34-1_rt1.2\bin\}.

                \o  In the \gui {Qt version} field, choose the MADDE Qt version
                    for MeeGo 1.2 Harmattan. By default, the \QSDK installer
                    places qmake in the following folder:
                    \c{QtSDK\Madde\targets\harmattan_10.2011.34-1_rt1.2\bin\}.

             \endlist

                You can leave the \gui {Qt mkspec} field empty.

                    \o  Open a project for an application you want to develop
                        for your device.

            \o  Select \gui Projects > \gui {Build & Run} > \gui {Add Kit} to
                add the kit that you specified above.

                \o  Select \gui Run to specify run settings for the project.

            \o  The Qt Quick project wizards automatically set the folder
                where the file is installed on the device in the \gui {Remote
                Directory} field. For example, \c {/opt/usr/bin}. If the text
                \gui {<no target path set>} is displayed, click it to specify a
                folder.

        \endlist

    \if defined(qcmanual)

    \section2 Testing with User Data on MeeGo Devices

    To run your application as the default user, you must first assign a
    password for the user account and then create the connection to the device
    as the user:

    \list 1

        \o  On the device, select \gui Terminal to open a
            terminal window.

        \o  To specify the password, enter the following command:
            \c{/usr/lib/mad-developer/devrootsh passwd user}

        \o  In \QC, select \gui Tools > \gui Options > \gui Devices.

        \o  Specify the username \c user and the password in the device
            configuration.

    \endlist

    \input linux-mobile/linuxdev-keys.qdocinc
    \input linux-mobile/linuxdev-processes.qdocinc

    \endif

    \section1 Troubleshooting Harmattan Connections

    The addresses used in this example might be reserved by some other
    application in your network. If you cannot establish a connection, try the
    following optional configurations:

    \table

        \header
            \o IP Address and Network on Device
            \o USB Network on Development PC
            \o Host Name in \QC Build Settings

        \row
            \o 172.30.7.15 255.255.255.0
            \o 172.30.7.14 255.255.255.0
            \o 172.30.7.15

        \row
            \o 10.133.133.15
            \o 10.133.133.14
            \o 10.133.133.15

        \row
            \o 192.168.133.15
            \o 192.168.133.14
            \o 192.168.133.15

            \note You cannot use the value localhost for connections to a
            device.

        \endtable

    \note VPN connections might block the device connection.

*/