I have bought a Cmod A7 Board, which looked nice for me.
One week ago I started to learn VHDL again using Vivado 2016.4. It worked nice.
I used the CmodA/_Master.xdc for the constraints and the board file provided by Digilent.
I made some blink led vhdl code and loaded it up directly to the FPGA.
Today I wanted to continue but it seems to be very hard to program the board again.
The board is recognized and sometimes I'm able to load up the bit file but the board disconnects in under 10 seconds so it is hard to select the file in this short time.
I've Vivado 2016.4 on two different WIndows 10 PCs. I tried all USB 3 and USB 2 Ports on both PCs. I tried eight different USB cables which I also use for debugging on Android and also
JTAG Targets (STM32 CPUs). The Cmod A7 is powered via USB of course.
I get following output:
program_hw_devices [lindex [get_hw_devices xc7a35t_0] 0]
[Labtools 27-3165] End of startup status: LOW
[Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210328A2B51CA.
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.
[Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210328A2B51CA
I tried now five hours on all different cables, reinstalling Vivado and drivers and two different machines.
Conclusion:
The Cmod A7 word last week without a problem.
This week without changing anything to the code the board connects and disconnects after some seconds.
The only thing I have done was to try to write the bin file to the SPI Flash like describe. But it disconnected during the transfer and so even the preprogrammed blink sample is lost.
Question
lawi
I have bought a Cmod A7 Board, which looked nice for me.
One week ago I started to learn VHDL again using Vivado 2016.4. It worked nice.
I used the CmodA/_Master.xdc for the constraints and the board file provided by Digilent.
I made some blink led vhdl code and loaded it up directly to the FPGA.
Today I wanted to continue but it seems to be very hard to program the board again.
The board is recognized and sometimes I'm able to load up the bit file but the board disconnects in under 10 seconds so it is hard to select the file in this short time.
I've Vivado 2016.4 on two different WIndows 10 PCs. I tried all USB 3 and USB 2 Ports on both PCs. I tried eight different USB cables which I also use for debugging on Android and also
JTAG Targets (STM32 CPUs). The Cmod A7 is powered via USB of course.
I get following output:
program_hw_devices [lindex [get_hw_devices xc7a35t_0] 0]
[Labtools 27-3165] End of startup status: LOW
[Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210328A2B51CA.
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.
[Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210328A2B51CA
I tried now five hours on all different cables, reinstalling Vivado and drivers and two different machines.
Conclusion:
The Cmod A7 word last week without a problem.
This week without changing anything to the code the board connects and disconnects after some seconds.
The only thing I have done was to try to write the bin file to the SPI Flash like describe. But it disconnected during the transfer and so even the preprogrammed blink sample is lost.
Any idea?
Link to comment
Share on other sites
14 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now