Honored Contributor
Honored ContributorYes, 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.
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). 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.
