If you are using one of these boards on Linux and having “permission denied” even though you ought to have read/write permissions for the relevant TTY file, see this bug :
Basically, some versions of udev misidentify every device that uses an FTDI chip as one particular device, and attaches the tty to the powerd daemon.
To fix the problem, you just need to comment out the udev rule for that device (see the bug). Or, wait until your distro pushes udev with the updated rules.
If you are using one of these boards on Linux and having “permission denied” even though you ought to have read/write permissions for the relevant TTY file, see this bug :
Basically, some versions of udev misidentify every device that uses an FTDI chip as one particular device, and attaches the tty to the powerd daemon.
To fix the problem, you just need to comment out the udev rule for that device (see the bug). Or, wait until your distro pushes udev with the updated rules.
Product DEV-09873 | about 5 months ago
If you are using one of these boards on Linux and having “permission denied” even though you ought to have read/write permissions for the relevant TTY file, see this bug :
bug 586751
Basically, some versions of udev misidentify every device that uses an FTDI chip as one particular device, and attaches the tty to the powerd daemon.
To fix the problem, you just need to comment out the udev rule for that device (see the bug). Or, wait until your distro pushes udev with the updated rules.
Product DEV-09716 | about 5 months ago
If you are using one of these boards on Linux and having “permission denied” even though you ought to have read/write permissions for the relevant TTY file, see this bug :
bug 586751
Basically, some versions of udev misidentify every device that uses an FTDI chip as one particular device, and attaches the tty to the powerd daemon.
To fix the problem, you just need to comment out the udev rule for that device (see the bug). Or, wait until your distro pushes udev with the updated rules.