4 USB-Blasters keep getting assigned different indexes when using quartus_jli.exe (system power cycle or not). How can I programmatically find out the correct index to use for each device?

Hi MUmbr2,

If you have similar ID for x4 JTAG cable with devices, I think the best option is as you idea above. Remove all the cables, then add them one by one, and identify their specific device index number (jtagconfig).

This is the best option you can do.

Thanks

Hi ShafiqY,

The only problem is that I don't know what to specify for the USB port. All the JTAG commands above specify ports as USB-0, USB-1 in sequence, which matches the indexes.

Is there definitely no one at Intel that could explain how this indexing works? Or could I call up for support?

Kind Regards,

Hi MUmbr2,

You can also try to use JTAG scripting here (on page 274):

https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/manual/tclscriptrefmnl.pdf#page=274

Thanks

Hi ShafiqY,

Those examples don't seem to run, as the "external_memif_toolkit" seems to not be present (sld_emitt.dll?). I found resources online that indicate it should be available for loading withing the quartus_sh.exe. For example, I try to run the tcl script from command lines as:

"C:\altera\12.1\qprogrammer\bin\quartus_sh.exe" -t "C:\Users\<Specific User>\Desktop\Test\JTAG Test.tcl"

It gives me the error:

ERROR: Quartus II Tcl command "get_hardware_names" belongs to the "::quartus::external_memif_toolkit" package which is currently not loaded. Please type "load_package external_memif_toolkit" to load the package before using this command.

while executing

"get_hardware_names"

invoked from within

"foreach hardware_name [get_hardware_names]"

After that I add the line "load_package external_memif_toolkit" to the begining of the script and get the following error:

ERROR: Can't load library: c:\altera\12.1\qprogrammer\bin\sld_emitt.dll. The operating system reports the following error: The specified module could not be found.

while executing

"load [file join $::quartus(binpath) sld_emitt] emitt"

invoked from within

"if [ catch { load "" emitt } load_result ] {

# If static load fails, load dynamic lib

set_dll_loading -dynamic

load [file join $::quartus(binpat..."

("package ifneeded ::quartus::external_memif_toolkit 1.0" script)

invoked from within

"package require ::quartus::external_memif_toolkit"

invoked from within

"load_package external_memif_toolkit"

Tried searching for the .dll with Search Everything and it's not present on my machine. It's worth noting, that I'm using the Lite version, to have a very basic solution to simply run .JAM files. Software version was chosen based on what my customers used (who gave me the .JAM files to run on their products). I really hope this is not a paid for feature, as we have purchased 4 USB Blaster Cables simply for running scripts and nothing more.

Kind Regards,

Hi MUmbr2,

Do you want to program a different design in x4 board? if not, why do you concern too much regarding to index number?

Can you explain more (if you can include screenshot, it would help)? maybe I did not understand better regarding your automated test system .

Thanks

Hi ShafiqY,

It can be a different design or the same design on all 4x products. To illustrate the problem, I made a couple of diagrams:

Let's say I run tests on all 4 Units Under Test (UUT) at the same time in parallel. I know that physically, JTAG1 is connected to the same UUT1, as all of my instruments under "Instruments1". I.e. I found through testing, that JTAG1 is USB-Blaster Index 1. And I can run the following setup 20 times without issues:

But let's say I run the setup for the 21st time and bam, this happens (there is no specific number of runs or system power cycles):

My USB Blaster Indexes get shuffled for some unknown reason to me. So my software ends up trying to use "Instruments1" with JTAG1, but actually the JTAG device connected to UUT1 is now indexed as "JTAG3". Obviously tests fail because of that, although physically the devices did not move. What's the only way to figure out the correct JTAG indexing? Switch on the the instruments for each UUT at a time and try running a script - if it runs, it's the correct index, if it errors - try another JTAG index.

This is absolutely unacceptable in a production environment.

For some reason you can set addresses/aliases/etc on any kind of COTS instruments, such as, LXI/GPIB/Serial/National Instruments/PLCs/etc, so I am hopping that the same is possible with Intel hardware... I either need a way to set the indexes myself so that the USB Blasters retain them or to be able to query the USB Blasters for some sort of unique identifiers. That way I could programmatically ensure I'm using the correct JTAG index for each UUT.

I have absolutely no clue how Quartus works in the background, but there must be documentation that describes how it indexes USB devices.

Kind Regards