Forum Discussion
Hi Jos Huisken,
Can you try to use "jtagconfig -n" / "jtagconfig.exe -n" on NIOS 2 command shell? you should be able to distinguish the USB Blaster.
Regards,
YL
Dear Yuan,
I picked up again, after being idle for quite some time.
Thanks for your answer, it helped but I am still kind of struggling with it. Could you explain what happens below? It looks like jtagconfig changes the usb device type/identifier?
I'm puzzled somewhat.
$ lsusb|grep Altera
Bus 002 Device 054: ID 09fb:6810 Altera
Bus 002 Device 029: ID 09fb:6010 Altera
Bus 002 Device 022: ID 09fb:6010 Altera
Bus 002 Device 108: ID 09fb:6810 Altera
$ jtagconfig -n
1) DE-SoC [2-1.1.3]
4BA00477 SOCVHPS
02D010DD 5CSE(BA4|MA4)/5CSXFC4C6
2) DE-SoC [2-1.2.3]
4BA00477 SOCVHPS
02D020DD 5CSEBA6(.|ES)/5CSEMA6/..
$ lsusb|grep Altera
Bus 002 Device 105: ID 09fb:6010 Altera
Bus 002 Device 029: ID 09fb:6010 Altera
Bus 002 Device 022: ID 09fb:6010 Altera
Bus 002 Device 104: ID 09fb:6010 Altera
$ jtagconfig -n
1) DE-SoC [2-1.1.3]
4BA00477 SOCVHPS
02D010DD 5CSE(BA4|MA4)/5CSXFC4C6
2) DE-SoC [2-1.2.3]
4BA00477 SOCVHPS
02D020DD 5CSEBA6(.|ES)/5CSEMA6/..
3) DE-SoC [2-1.2.4.2]
4BA00477 SOCVHPS
02D120DD 5CSE(BA5|MA5)/5CSTFD5D5/..
4) USB-BlasterII [2-1.1.1]
4BA00477 SOCVHPS
02D020DD 5CSEBA6(.|ES)/5CSEMA6/..
020A40DD 5M(1270ZF324|2210Z)/EPM2210
Design hash 8053C739368EBD354AB3
+ Node 00406E01 Virtual JTAG #1
+ Node 00406E7B Virtual JTAG #123