forked from sinara-hw/assembly
Update windows drivers instructions
Signed-off-by: Egor Savkin <es@m-labs.hk>
This commit is contained in:
parent
4d6d43299a
commit
e2ea70955c
Binary file not shown.
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
After Width: | Height: | Size: 18 KiB |
|
@ -14,5 +14,7 @@ On Windows, a third-party tool, Zadig, is necessary. Use it as follows:
|
||||||
3. Select the “Digilent Adept USB Device (Interface 0)” or “FTDI Quad-RS232 HS” (or similar) device from the drop-down list.
|
3. Select the “Digilent Adept USB Device (Interface 0)” or “FTDI Quad-RS232 HS” (or similar) device from the drop-down list.
|
||||||
4. Select WinUSB from the spinner list.
|
4. Select WinUSB from the spinner list.
|
||||||
5. Click “Install Driver” or “Replace Driver”.
|
5. Click “Install Driver” or “Replace Driver”.
|
||||||
|
6. After above steps done, you may see the devices in the Device Manager:
|
||||||
|
![after_zadig_devices.png](../img/win32/after_zadig_devices.png)
|
||||||
|
|
||||||
You may need to repeat these steps every time you plug the FPGA board into a port where it has not been plugged into previously on the same system.
|
You may need to repeat these steps every time you plug the FPGA board into a port where it has not been plugged into previously on the same system.
|
|
@ -26,7 +26,9 @@ until its fully loaded.
|
||||||
|
|
||||||
Use following instructions to set correct drivers for the COM ports.
|
Use following instructions to set correct drivers for the COM ports.
|
||||||
At choosing FTDI drivers stage you may have longer list of drivers.
|
At choosing FTDI drivers stage you may have longer list of drivers.
|
||||||
In that case, choose respective `USB Serial Converter X` (A for 0, B for 1, C for 2, D for 3) driver.
|
In that case, choose respective `USB Serial Converter X` (A for 0, B for 1, C for 2, D for 3) driver. In case you cannot
|
||||||
|
locate the devices, they may appear in the _Other devices_ section:
|
||||||
|
![other_devices_section.png](../img/win32/other_devices_section.png)
|
||||||
You may also need to reboot your PC after doing this.
|
You may also need to reboot your PC after doing this.
|
||||||
|
|
||||||
1. ![com_driver_set0.png](../img/win32/com_driver_set0.png)
|
1. ![com_driver_set0.png](../img/win32/com_driver_set0.png)
|
||||||
|
@ -37,6 +39,9 @@ You may also need to reboot your PC after doing this.
|
||||||
6. ![com_driver_set5.png](../img/win32/com_driver_set5.png)
|
6. ![com_driver_set5.png](../img/win32/com_driver_set5.png)
|
||||||
7. ![com_driver_set6.png](../img/win32/com_driver_set6.png)
|
7. ![com_driver_set6.png](../img/win32/com_driver_set6.png)
|
||||||
|
|
||||||
|
If you are here after [flashing firmware](flashing_firmware.md) stage, you may fail to see the devices in the described locations.
|
||||||
|
If you see them in the `Universal Serial Bus devices` section, you may need just to uninstall the third _Quad_ device and reconnect the
|
||||||
|
Kasli/Kasli-SoC to the PC.
|
||||||
|
|
||||||
#### Connecting with PuTTY
|
#### Connecting with PuTTY
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue