I do not do a great deal of FPGA stuff, this time last year I finished a project and have not touched the tools since. I now have a requirement to modify it for a different project. So I try to connect to my FPGA board with Impact and it is so sloooooooow and then fails.
So I do this:
billy@aurora:~/FPGA$ djtgcfg init -d JtagHs1
Initializing scan chain...
Found Device ID: 24001093
Found 1 device(s):
Device 0: XC6SLX ?
billy@aurora:~/FPGA$
The programming will not work (I assume because of the ?). The board is a Mojo with a XC6SLX9 on it. I have several of these and they all give the same result, same with a ValentF[x] LOGI-Bone (same FPGA). these all worked before, but at least a year ago. (All the boards work with their original content, the Mojos can be programmed using a Python program ) The Debian Linux will have been updated several times since!
I have a Nexys2 but that still works, no problems with Impact or Digilent command line.
I got an HS3 because I thought the HS1 may be defective, but same result.
Unrelated, but may use Adept runtime, I have a Digilent Analog Discovery and Digital Discovery and they both work fine.
My version of Debian is Buster, though this was also tried on Stretch.
libusb is 1.0.22-2
digilent.adept.runtime_2.19.2-amd64.deb
If anybody has had a similar problem and knows how to cure it I would be grateful if you could help.
I suspect the FTDI driver! This comes with adept runtime I think.
Question
billium
I do not do a great deal of FPGA stuff, this time last year I finished a project and have not touched the tools since. I now have a requirement to modify it for a different project. So I try to connect to my FPGA board with Impact and it is so sloooooooow and then fails.
So I do this:
billy@aurora:~/FPGA$ djtgcfg init -d JtagHs1 Initializing scan chain... Found Device ID: 24001093 Found 1 device(s): Device 0: XC6SLX ? billy@aurora:~/FPGA$
The programming will not work (I assume because of the ?). The board is a Mojo with a XC6SLX9 on it. I have several of these and they all give the same result, same with a ValentF[x] LOGI-Bone (same FPGA). these all worked before, but at least a year ago. (All the boards work with their original content, the Mojos can be programmed using a Python program ) The Debian Linux will have been updated several times since!
I have a Nexys2 but that still works, no problems with Impact or Digilent command line.
I got an HS3 because I thought the HS1 may be defective, but same result.
Unrelated, but may use Adept runtime, I have a Digilent Analog Discovery and Digital Discovery and they both work fine.
My version of Debian is Buster, though this was also tried on Stretch.
libusb is 1.0.22-2
digilent.adept.runtime_2.19.2-amd64.deb
If anybody has had a similar problem and knows how to cure it I would be grateful if you could help.
I suspect the FTDI driver! This comes with adept runtime I think.
Thanks
Billy
Link to comment
Share on other sites
19 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.