Module is not listed in the lspci output
Module is not listed in the lspci output
The module not being listed on the PCIe bus at all indicates that the problem is at the hardware level.Apply the steps below in order.
- Cut the power of the board and remove the module from its slot and insert it again. Make sure that the module is fully seated in the slot and that the retaining screw is tightened.
- Check that the power adapter you are using can supply the total consumption of the board and the module. Insufficient supply causes the module to fail to establish the PCIe link.
- Review whether there is an error related to the PCIe link in the kernel logs.
Driver modules are not loaded
Driver modules are not loaded
If the You can try loading the driver manually.
lsmod | grep dx command produces empty output, the driver has not been loaded into the kernel.First check whether the driver produces an error while it is being loaded.Permission denied error when accessing the device file
Permission denied error when accessing the device file
The For a permanent solution, you can inspect the owner and the permissions of the device file and add your
user to the relevant group.
Permission denied error indicates that the user does not have permission to access the device file
created by the driver.You can temporarily run the application as the privileged user.EFAULT error during inference
EFAULT error during inference
This error can be encountered in Python applications when the input buffer is created with
np.zeros().
All of the virtual memory pages allocated with np.zeros() point to the same physical page, and the
PCIe DMA driver produces an error when it sees the same physical page more than once.Create the input buffer in the following way.A version mismatch is reported while loading the model
A version mismatch is reported while loading the model
The DX-RT runtime verifies the compilation version of the loaded model. The model having been compiled
with a DX-COM version older than the runtime on the board causes this error.Check the installed versions.To solve the problem, you need to recompile the model using a DX-COM version that is compatible with the
runtime version.
Frame rate is lower than expected
Frame rate is lower than expected
The frame rate staying below expectations usually originates from the steps other than the NPU.First determine where the bottleneck is. You can use the benchmark tool to measure the pure performance
of the model on the NPU.If this measurement gives the expected values but your application runs slowly, the bottleneck is in the
pre-processing, post-processing or display steps. In that case you can consider the following.
- Use the asynchronous template instead of the synchronous one. This way the CPU can prepare the next frame while the NPU performs inference.
- Disable visualization.
- Use the C++ equivalents instead of post-processing steps written in Python.
The model runs correctly but the results are wrong
The model runs correctly but the results are wrong
The compilation process being successful does not guarantee that the model will produce correct results.
There are two most common reasons for this situation.
- Pre-processing mismatch: The pre-processing steps defined in the configuration file during compilation must be exactly the same as the steps applied during training. Differences in the color space conversion, the normalization values and the resizing method lead to incorrect results.
- Insufficiency of the calibration dataset: The images used during quantization not representing the environment in which the model will run causes the accuracy to drop noticeably.
Multiple applications cannot use the NPU at the same time
Multiple applications cannot use the NPU at the same time
If more than one process will use the NPU at the same time, the If the service is not running, start it and enable it so that it starts automatically at boot.
dxrt service that manages the resource
sharing must be running.Installing both an SSD and the accelerator into the M.2 slot
Installing both an SSD and the accelerator into the M.2 slot
There is a single M.2 2280 slot on the T3 Gemstone O1 development board. For this reason an NVMe SSD and
the DX-M1 accelerator module cannot be used at the same time.If you need additional storage space, you can use the microSD card slot or a storage device connected
over USB.

