Search the Community
Showing results for tags 'adept'.
I'm working with ARTY-A7 FPGA board and ADEPT v2.19.2 in Windows 10. At first, the system often lost contact with the board, but after reinstalling digilent.adept.system_v2.19.2, the connection was restored. Now reinstalling no longer helps. What can be a reason?
Recently we started using a Genesys2 board to emulate our SoC design. To program and control the board, we are using the Adept utility on a Windows 10 PC. This utility allows us to download the bitstream on the FPGA via JTAG, followed by connecting to the chip via an I2C interface. The "software part" (including downloading the firmware) is done using python scripts from the command line. But it seems like we need to re-program the FPGA every time we want to download a new FW version, or just restart the program. For automation purposes, I am looking for a way to program the FPGA bitstream from command line as well. Looking at the provided user manual, I could not find command line options for the Adept GUI. So, is it possible to configure and program the FPGA from the PC command line using the Adept program (or any other method)?
I left my board connected to my laptop and power to the board was abruptly cut off when the laptop died. I tried to connect the board to a different computer and realized that it no longer turned on. The computer's device manager shows that something is plugged in, but Adept and Vivado are unable to recognize that a device is connected. I was planning to restore the board to it's default setting on Vivado by using a .bin file but received the following error message: "ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210292AA77E6A. Check cable connectivity and that the target board is powered up then use the disconnect_hw_server and connect_hw_server to re-register this hardware target. ERROR: [Common 17-39] 'open_hw_target' failed due to earlier err." I used a voltmeter to test the voltage across the on/off switch and was getting around 3.3V but now get 0.003V. When I tested the switches that control the on-board LEDS, the also produced around 0.003V. Is there a solution to help me with this as the board is brand new?