Frequently Asked Questions

1. Adb devices shows “no permissions”

It’s possible, on new machines, that adb devices cannot access the board:

List of devices attached
0000000000000116        no permissions; see [http://developer.android.com/tools/device.html]

To fix this, add the following udev rules in /etc/udev/rules.d/70.ti_am62x.rules:

# adb access
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee7", MODE="0660", TAG+="uaccess"

Then reload the udev rules with:

$ sudo udevadm control --reload
$ sudo udevadm trigger

For the same reason as adb (udev), fastboot flashing might fail as well.

To fix this, add the following udev rules in /etc/udev/rules.d/70.ti_am62x.rules:

# fastboot access
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="6165", MODE="0660", TAG+="uaccess"

Then reload the udev rules with:

$ sudo udevadm control --reload
$ sudo udevadm trigger

For the same reason as adb (udev), fastboot flashing might fail as well.

To fix this, add the following udev rules in /etc/udev/rules.d/70.ti_am62x.rules:

# fastbootd access
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="4ee0", MODE="0660", TAG+="uaccess"

For the same reason as adb (udev), recovery access might fail as well

To fix this, add the following udev rules in /etc/udev/rules.d/70.ti_am62x.rules:

# adb recovery access
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d001", MODE="0660", TAG+="uaccess"