The New Development Board adb under Ubuntu cannot identify and solve the problem

Generally, developers in development companies have different development boards at the same time because of Project iteration requirements. However, the USB of different development boards is different, which makes the adb unidentifiable. The following is a solution for Ubuntu. Step 1: Open the terminal and enter the usb id of our new development board at on lsusb. If you do not know how to identify it, you can find out the changed value through repeated plugging. We need to copy: 2207 of the prefix and add it to the configuration file. Step 2: Modify 51-android

Generally, developers in development companies have different development boards at the same time because of Project iteration requirements. However, the USB of different development boards is different, which makes the adb unidentifiable. The following is a solution for Ubuntu.

Step 1:

Open the terminal and enter lsusb

The above is the usb id of our new development board. If you do not know how to identify it, you can find the change value through repeated plugging. We need to copy: 2207 of the prefix and add it to the configuration file.

Step 2:

Modify the configuration file 51-Android.ruls

Enter sudo vim/etc/udev/rules. d/51-android.rules on the terminal to view the following data.

Copy and replace the two rows of data. Modify the data of SYSFS {idVendor} To 2207, as shown in the following figure:

Step 3:

Modify the adb_usb.ini configuration file

Enter vim. android/adb_usb.ini on the terminal, which has a value similar to 0x2218. Enter 0x2207 in another line. For example:

Now, after completing the above steps, you can view the result by using adb devices.

Good luck.