Forum Discussion
ContributorTwo instances of Quartus can't seem to use two JTAG pods
Hello,
I don't experience problems accessing multiple JTAG adapters from multiple Quartus instances. Last checked with Quartus 19.1 and 21.1, Windows 10.
A known restriction is that you can't enumerate new programming hardware when another instance is presently communicating, e.g. SignalTap waiting for trigger or Source&Probe continuously reading data. Also device names of adapters without unique name may change when connecting a new adapter. Therefore you should plug in all adapters and perform the setup of all debug instances before starting debug action.
Which step actually fails in your test?
Enumerating the adapters in setup?
Selecting debug hardware?
Communicating with adapter?
Regards,
Frank
Super ContributorHello,
I don't experience problems accessing multiple JTAG adapters from multiple Quartus instances. Last checked with Quartus 19.1 and 21.1, Windows 10.
A known restriction is that you can't enumerate new programming hardware when another instance is presently communicating, e.g. SignalTap waiting for trigger or Source&Probe continuously reading data. Also device names of adapters without unique name may change when connecting a new adapter. Therefore you should plug in all adapters and perform the setup of all debug instances before starting debug action.
Which step actually fails in your test?
Enumerating the adapters in setup?
Selecting debug hardware?
Communicating with adapter?
Regards,
Frank
- Oliver_I_Sedlacek
So I did get it to work. Problem is perhaps just lack of patience as I left the second instance loading SignalTap with the cursor just spinning whilst I had a lunch break. Came back and it had sprung to life after who knows how long.
