I'm using the Arrow Max 10 development board, which uses an FTDI 2232H for the USB interface and 'jtag_hw_arrow_usb_blaster.dll'.
My problem is that we'd like to now use the Max10 in a production product, but with the FTDI 4232H. The hardware (FTDI port A is mapped to the JTAG) is identical between the Max 10 development board and our production board.
Unfortunately, Quartus does not recognize the 4232H device as a Usb-Blaster.
In lieu of Arrow making the trivial modification to the dll's function (get_supported_hardware) to add the 4232H VID/PID (0x0403, 0x6011).. rather than just the 2232H VID/PID (0x403/0x6010)...
I'm assuming jtagserver.exe tells windows that the 2232H was spotted.. so is there a way to have jtagserver.exe do this when the 4232H is inserted instead? This way the 'get_supported_hardware' passes?
Is there any info on how jtagserver.exe works?
Quartus currently programs the Arrow Max 10 development board via the FTDI 2232H.
We've copied this Max 10 reference design for a product, but need to use the FTDI 4232H.
Is there a way to force 'jtagconfig' to --add a USB-Blaster without physically connecting to the USB?