Example 1: 51-yoctopuce.rules
This rule provides all the users with read and write access to the Yoctopuce USB peripherals. Access
rights for all other peripherals are not modified. If this scenario suits you, you only need to copy the
"
51-yoctopuce_all.rules
" file into the "
/etc/udev/rules.d
" directory and to restart your
system.
# udev rules to allow write access to all users
# for Yoctopuce USB devices
SUBSYSTEM=="usb", ATTR{idVendor}=="24e0", MODE="0666"
Example 2: 51-yoctopuce_group.rules
This rule authorizes the "yoctogroup" group to have read and write access to Yoctopuce USB
peripherals. Access rights for all other peripherals are not modified. If this scenario suits you, you
only need to copy the "
51-yoctopuce_group.rules
" file into the "
/etc/udev/rules.d
"
directory and restart your system.
# udev rules to allow write access to all users of "yoctogroup"
# for Yoctopuce USB devices
SUBSYSTEM=="usb", ATTR{idVendor}=="24e0", MODE="0664", GROUP="yoctogroup"
23.4. ARM Platforms: HF and EL
There are two main flavors of executable on ARM: HF (Hard Float) binaries, and EL (EABI Little
Endian) binaries. These two families are not compatible at all. The compatibility of a given ARM
platform with of one of these two families depends on the hardware and on the OS build. ArmHL and
ArmEL compatibility problems are quite difficult to detect. Most of the time, the OS itself is unable to
make a difference between an HF and an EL executable and will return meaningless messages
when you try to use the wrong type of binary.
All pre-compiled Yoctopuce binaries are provided in both formats, as two separate ArmHF et ArmEL
executables. If you do not know what family your ARM platform belongs to, just try one executable
from each family.
23.5. Powered module but invisible for the OS
If your Yocto-Display is connected by USB, if its blue led is on, but if the operating system cannot see
the module, check that you are using a true USB cable with data wires, and not a charging cable.
Charging cables have only power wires.
23.6. Another process named xxx is already using yAPI
If when initializing the Yoctopuce API, you obtain the "
Another process named xxx is already using
yAPI
" error message, it means that another application is already using Yoctopuce USB modules. On
a single machine only one process can access Yoctopuce modules by USB at a time. You can easily
work around this limitation by using a VirtualHub and the network mode
4
.
23.7. Disconnections, erratic behavior
If you Yocto-Display behaves erratically and/or disconnects itself from the USB bus without apparent
reason, check that it is correctly powered. Avoid cables with a length above 2 meters. If needed,
insert a powered USB hub
5
6
.
4
see: http://www.yoctopuce.com/EN/article/error-message-another-process-is-already-using-yapi
5
see: http://www.yoctopuce.com/EN/article/usb-cables-size-matters
6
see: http://www.yoctopuce.com/EN/article/how-many-usb-devices-can-you-connect
23. Troubleshooting
414
www.yoctopuce.com
Содержание Yocto-Display
Страница 1: ...Yocto Display User Manual...
Страница 2: ......
Страница 40: ...34 www yoctopuce com...
Страница 52: ...46 www yoctopuce com...
Страница 84: ...78 www yoctopuce com...
Страница 92: ...86 www yoctopuce com...
Страница 130: ...124 www yoctopuce com...
Страница 158: ...22 High level API Reference 152 www yoctopuce com On failure throws an exception or returns a negative error code...
Страница 422: ...416 www yoctopuce com...
Страница 424: ...24 Characteristics 418 www yoctopuce com...