Windows sees USB blaster but Quartus doesn't, why?

In addition, I also presume that your target environment doesn't involve strong common mode noise (e.g. a power electronics controller) that might affect USB and JTAG interface operation. In this case a different PC or different PC power supply can matter a lot.

jtagconfig --serverinfo reports the server version

Hi,

Any further update?

Regards,

Aiman

Worked not too bad this morning, but lost interest this afternoon.

It's taken me 5 goes to log in to this forum so you'll have to forgive the slow response and a less than civil attitude. Nobody here seems to care about the customer experience.

Help still needed here!

Hi Oliver, from what I understand from your previous communication:

1. Your USB Blaster can configure the device successfully.
2. Your USB Blaster can detect the device in user mode.
3. Your USB Blaster can connect the board and signaltap successfully.
4. Only after some event, somehow the signaltap unable to connect.

from above problem statements, this is most probably on the signal integrity issue.

Trouble shooting steps:

1. Could you please scope shot your TCK signal during the failure?

regards,

Farabi

My problem is specific to my main development PC and only appeared after nearly a year of relatively reliable operation.

1. The target hardware hasn't changed (it's still the same PCB assembly)

2. The problem affects both of my USB blasters

3. There's no problem if I use my laptop

4. There's no problem if I use a colleages PC

5. Restarting the JTAG server doesn't fix it.

6. Restarting Windows does fix it (even without a power cycle)

Using a laptop isn't a long term solution, the screen is too small and the compile times are too long.

Hi Oliver,

From your explanation, it seems like it is PC problem not the USB blaster problem and not FPGA problem.

The best support that we can provide now is for you to reinstall your PC OS. And also you may try to reinstall the USB blaster driver.

Regards,

Aiman

Hi,

From the observation made so far, the root cause is high probably due to software issue on that particular PC as it is working fine on the other PC. As Fvm said earlier, the only way to move forward is to uninstall first and re-install back the related software.

Regards,

Aiman