![Lattice CrossLink-NX PCIe Скачать руководство пользователя страница 41](http://html1.mh-extra.com/html/lattice/crosslink-nx-pcie/crosslink-nx-pcie_user-manual_3825488041.webp)
CrossLink-NX PCIe Bridge Board Basic Demo
User Guide
© 2021 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at
All other brand or product names are trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-UG-02145-1.0
41
7.2.
Driver Installation and User Interface Launch for Windows
7.2.1.
Problem in Driver Installation
If the hardware IDs are not found in Device Manager, ensure that the board is properly installed in a PCIe slot.
Ensure that the board has a valid PCIe bitstream file loaded in the SPI Flash. Shut down the system and try another
slot. If the board is present, check the Properties and the Resource tab to verify if memory is assigned to it.
Also, verify if the Vendor ID and Device ID are valid, as seen by Windows Plug-n-Play. If the values are invalid,
perhaps the bitstream file is corrupt and needs to be reloaded into SPI flash. If the PCIe board is shown in the list of
Device Manager, install the driver manually.
If the driver is not being installed even though the device is present in the Device Manager, make sure that the
driver signature enforcement is disabled permanently. If not, follow the steps described in the
Signature Enforcement Permanently
7.2.2.
Problem with Launching User Interface
Ensure that the driver is installed properly. Otherwise, the Device Info section of the user interface displays the
message shown in
The Driver Open [FAILED] message is displayed if the driver is not installed properly. The Device information is present
if the drivers are installed properly.
Figure 7.3. User Interface with No Device Driver
If the device is not inserted in the system or the device driver is not installed, any read or write operation is not
executed. A sample error message is shown in