--- Quote Start ---
These modules are entirely custom and designed to sit in the second cpu socket of an Intel Xeon DP server. We already have built and deployed a few hundred now. Redesign is not an option. Future platforms will have a better program flow through the processor directly and will be programmed by the bios at power on (adds ~20-30 seconds to the boot time). When we get to production stage of that design, we will no longer need jtag for everything, although we will likely need it for internal development/debug.
--- Quote End ---
Ok, thanks for the clarification.
--- Quote Start ---
My theory for 1 server, multiple targets was that it reduces the overhead per rack cabinet. Our current production system is based on a 4U server, and the next generation will allow for 1U or 2U server (same motherboard for 1U/2U). Each server already uses 2 IP addresses (1 OS, 1 Remote Management). Having a third for each system (jtag server) is not easy without moving internally to a new subnet.
--- Quote End ---
One server for multiple FPGA targets via multiple USB-Blaster connections seems reasonable. The one caveat is that USB-Blaster's ship with the same USB serial string, so you typically need to reprogram their USB strings via FTDIs FT_PROG tool. That way your JTAG server will present the same USB-Blaster identification each time the system boots, or when different numbers of USB-Blasters are connected.
--- Quote Start ---
Except for the multi-threaded connection issue, my design is fairly optimal and easy to automate for allocation, and allows for scaling. I even have a full web front end for managing and allocating systems in the pool, complete with time expiration alerts and auto-logoff (for the developers that forget they are on a system and go on vacation).
--- Quote End ---
I agree that multiple USB-Blaster connections should be supported via a single jtagd server.
I have several USB-Blasters, and could likely reproduce your problem, but I doubt that will help you :)
This forum is maintained by Altera users, not by Altera (although several Altera employees do answer questions). Have you filed a Service Request with Altera directly? Another useful person to contact is your local Altera FAE (Field Applications Engineer), eg., at Arrow Electronics or whoever you buy your Altera devices from. Let them know which operating system you are using and which version of Quartus.
Cheers,
Dave
Honored Contributor
