Details
-
Bug
-
Resolution: Done
-
P2: Important
-
Qt Creator 3.6.1
-
None
-
Windows 7
-
c520809ad0a6fec0e03549b39d27bf7b2718ec52
Description
I am setting up a FreeScale i.MX6 series SABRE board by following the instructions given at http://doc.qt.io/QtForDeviceCreation/qtee-preparing-hardware-imx6sabresd.html. Everything worked fine until I reached the step of Configuring a Device Kit in Qt Creator. The SABRE i.MX6 board was not detected. In Tools->Options->Devices, the board wasn't displayed in the combo box. The following messages were displayed in the General Messages tab when the Qt Creator launched:
Checking for license updates ...
Checking for updated license succeeded (1 licenses fetched)
Boot2Qt: adb server started.
Boot2Qt: Connected to adb server.
Boot2Qt: Retrieving platform info. Full command line is 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe s b2qt<device type>-<serial no.> shell "appcontroller --show-platform && appcontroller --version"'.
Boot2Qt: Platform retrieval failed for device with serial number ' b2qt-<device type>-<serial no.>': Failed to start adb..
Assuming it is not a Boot2Qt device.
The command of 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe s b2qt<device type>-<serial no.> shell "appcontroller --show-platform && appcontroller --version"" failed to run. It appears that the path of the adb.exe file containing spaces causes the adb failed to start. After I reinstalled the Android SDK Tools and gave the installation path without any spaces in it, the command ran successfully. The board was detected as a Boot2Qt device.
I installed Qt Creator 3.6.1 using the Qt online installer v2.0.3.
Attachments
For Gerrit Dashboard: QTCREATORBUG-16075 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
156092,3 | Boot2Qt: Correctly handle adb command with spaces. | 4.0 | qt-creator/tqtc-plugin-boot2qt | Status: MERGED | +2 | 0 |