In the old Android release R10.3.x for i.MX5x, I had followed the user guide instructions to install the USB driver and am able to setup the ADB connection successfully. Unfortunately, for the same PC, the ADB fails to detect my i.MX6SL EVK which is using R13.5. Updating the Android SDK tools cannot help.
The reason is the new Android device is using a different USB VID from the old release. So, to solve this problem, we need to update the ADB configuration to scan for the new vendor ID. Below are the steps to update the ADB configuration for Windows PC. These steps (and the steps for Linux PC as well) can also be found in the R10,3.x user guide.
1. Run the SDK's tools to generate an ADB configure file:
C:\Program Files\Android\android-sdk\tools> android.bat update adb
2. Modify the adb usb configure file to add the new vendor id 0x18d1.
File: X:\Profile\<your account>\.android\adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
3. Unpack the Freescale Android USB win driver "android_usb_fsl.zip" in your Android BSP release package. If you can't find this file in your current package, please get the R10.3.x release for i.MX5x and unpack it.
4. File "tetherxp.inf" in the unpacked "android_usb_fsl" may not be the updated one if the "android_usb_fsl.zip" is extracted from an old release. So, please overwrite the file "tetherxp.inf" in unpacked "android_usb_fsl.zip" by the new "tetherxp.inf" in your current Android BSP release.
5. Enable the "USB debugging" option on the i.MX6 device
System settings -> Developer options -> USB debugging
6. Connect the Android Device into PC, uninstall your old driver named "Android Phone" in the device manager, then re-install driver by scanning and locating .inf file under the directory you unpack the android_usb_fsl.zip manually.
7. Restart the ADB server
C:\Program Files\Android\android-sdk\platform-tools> adb kill-server
C:\Program Files\Android\android-sdk\platform-tools> adb start-server
8. Finally, test your ADB connection
C:\Program Files\Android\android-sdk\platform-tools> adb devices
List of devices attached
Congratulations! Your ADB is now working. If you have additional information about this topic, please feel free to comment.
Sometimes, following the above procedure still cannot get the ADB work. In such case, you have to uninstall the Android Composite ADB Interface device, remove the "Android Phone" driver package (oemxx.inf) from Windows and start all over again. More information about using command prompt utility "pnputil.exe" to remove the driver package can be found at Remove a Driver Package from the Driver Store.
Message was edited by: Peter Chan