--- Quote Start ---
Yes, I have a support request in (and also a back-channel email filtering through). I was hoping maybe someone else ran into this and had their own creative workaround. I may post one of my own if Altera doesn't fix this directly.
--- Quote End ---
Hopefully others will read this thread and post their work-arounds, if any.
--- Quote Start ---
As to the unique serial number issue, we renamed each module to match the target name. This way, jtagconfig reports all of the remote systems as "##) Blaster: <target name> ...". The only caveat with this is if I need to move that system to a direct Windows host, I have to either rename the usb-blaster or swap it for a stock device (Windows driver doesn't like the device to be renamed locally - works fine for remote).
--- Quote End ---
I've renamed the serial strings on several boards and used them fine under Windows. Its not as convenient as Linux, but it did work.
--- Quote Start ---
I wouldn't have even gone down this path if this part didn't work. Imagine running jtagconfig (or the Quartus gui) and seeing 20+ systems, all named USB Blaster. Worse than playing a shell game on a street corner.
--- Quote End ---
Indeed! Too many manufacturers do not appreciate that their USB development boards need to have serial strings you can change!
Good luck finding a solution.
If you need another FAE contact, email me off list (use my forum name), and I'll get you in touch with my Arrow contact.
Cheers,
Dave
Honored Contributor
