NOTES:
- These steps are only required if you want to perform inference on Intel® Vision Accelerator Design with Intel® Movidius™ VPUs.
- If you installed the Intel® Distribution of OpenVINO™ to the non-default install directory, replace
/opt/intel
with the directory in which you installed the software.
For Intel® Vision Accelerator Design with Intel® Movidius™ VPUs, the following additional installation steps are required.
NOTE: The
HDDL_INSTALL_DIR
variable is set to<openvino_install_dir>/deployment_tools/inference_engine/external/hddl
. If you installed the Intel® Distribution of OpenVINO™ to the default install directory, theHDDL_INSTALL_DIR
was set to/opt/intel/openvino//deployment_tools/inference_engine/external/hddl
.
Running inference with the MYRIAD Plugin after running with the HDDL Plugin is failed with the following error generated:
Possible solutions (use one of the following):
hddldaemon
) and reset all Intel® Movidius™ VPUs before running an application that uses the MYRIAD Plugin: When the application runs inference of a network with a big size(>4MB) of input/output or if the system is running out of the DMA buffer, the HDDL Plugin will fall back to use shared memory. In this case, if the application exits abnormally, the shared memory is not released automatically. To release it manually, remove files with the hddl_
prefix from the /dev/shm
directory:
Make sure that the following udev rules exist:
/etc/udev/rules.d/97-myriad-usbboot.rules
/etc/udev/rules.d/98-hddlbsl.rules
/etc/udev/rules.d/99-hddl-ion.rules
/etc/udev/rules.d/99-myriad-vsc.rules
Also make sure that the current user is included in the users groups. If not, run the command below to include:
setup.sh
doesn't install the driver binaries to /lib/modules
on CentOS systemsAs a temporary workaround, run the commands below to install the drivers. This issue will be fixed in future releases.
Symptom: Boot up the host machine, run the inference application with the HDDL plugin. System reboots in a uncertain time.
Root Cause: The I2C address of the reset device of the Intel® Vision Accelerator Design with Intel® Movidius™ VPUs conflicts with another device I2C address in 0x20-0x27 range. If the target Intel® Vision Accelerator Design with Intel® Movidius™ VPUs device needs to be reset (for example, in case of device errors), the libbsl
library, which is responsible for reset, expects that the target reset device I2C address is in the 0x20-0x27 range on SMBUS. If there is another device on SMBUS in this address range, libbsl
treats this device as the target reset device and writes an unexpected value to this address. This causes system reboot.
Solution: Detect if there is any I2C device on SMBUS with address in 0x20-0x27 range. If yes, do the following:
"autoscan": false
in ${HDDL_INSTALL_DIR}/config/bsl.json
0x21
) in ${HDDL_INSTALL_DIR}/config/bsl.json
Please contact your motherboard vendor to verify SMBUS pins are connected to the PCIe slot.
You may have run hddldaemon under another user. Run the command below and try again:
Run the following command to check if a SMBUS I801 adapter can be found:
Then run:
Check if myd_ion
kernel module is installed by running the following command:
If you do not see any output from the command, reinstall the myd_ion
module.
Check if myd_vsc kernel module is installed by running the following command:
If you do not see any output from the command reinstall the myd_vsc
module.
myd_ion
or myd_vsc
modulesRun the following commands: