That said, I have since found the Sno boards, from Aloriumtech, which are actually a better fit.
Linux sees the board, and even correctly displays its ID as a Bemicro Cyclone III, but it doesn't know how to split the interface into an A and B port, so even the Linux version of Quartus doesn't see it as a programmer.
Supposedly, there were signed drivers created by someone at Arrow years ago, but they have disappeared off the face of the Earth since Intel bought Altera and absorbed the forums into their own.
A clever little design, but no one ever signed the drivers.
This little board used a FTDI FT2232D chip to create both a virtual USB blaster and a USB to serial port converter. There have been various different USB IDs:Ġ9fb:6001 / 6002 / 6003: original USB Blaster (USB 1.1)Ġ9fb:6810 (USB Blaster 2 boots up as this, before firmware is downloaded)Ġ9fb:6010 (USB Blaster 2 when firmware has been downloaded)Īnd they should all be covered by the USB Blaster drivers in Quartus. What errors do you get if you try to talk to On Linux, there hasn't been a lot of changes since 13.1 - the mainĭifference is some of the older versions looked for /dev/bus/usb whereas
You were to install the Windows drivers from a later version of Quartus it However, the USB Blaster interface hasn't really changed since then, so if There, which should have the driver integrated. The last supported version of Quartus for the Cyclone III is 13.1 Is that the drivers for the USB Blaster JTAG interface, or for something
> older tools - including old versions of Quartus for supporting other I do, however, have a Windows 7 64-bit VM I used for They are all running either Windows 10 64-bit > Unfortunately, none of my current machines are capable of running the > an ancient board, but this project doesn't need much, and this old device > happen to have a use for it - if I can get it running again. There are no ads in this search engine enabler service.> I found my old BeMicro Cyclone III board laying around the other day and GitHub blocks many GitHub Wikis from search engines. ℹ️About GitHub Wiki SEE, a search engine enabler for GitHub Wikis as A fix is here ?️ Page Index for this GitHub Wiki On Linux if you get errors trying to do anything from Quartus or Programmer check the permissions on the USB Byte Blaster device drivers. Use Quartus "SignalTap II Logic Analyzer" to debug the core using the USB Blaster.Quartus > Tools > Programmer, select USB Blaster in Hardware Setup, make sure the core sof is listed and press 'Start' to program the MiST.Drivers should automatically be installed. Connect USB Byte Blaster to the JTAG on the MiST, and connect to the PC.If using the webedition of Quartus 13.1 make sure Talkback is enabled in options.With the DIP switch 1 in the ON position using a Byte Blaster cableīecomes very easy. The IO controller increases some debug output and e.g.The IO controller tries to monitor the FPGA for JTAG uploads and tries to reset itself whenever it detects that the FPGA config has changed.The IO controller does not attempt to reconfigure the FPGA on its own reboot.When being switched ON the DIP switch 1 causes several things: The solution to this is DIP swtch 1 on the MIST board. Unfortunately upon reset the IO controller will automatically upload a newĬonfiguration to the FPGA overwriting anything that might have been SD card slot to re-establish its connection to the FPGA. IO controller needs to be restarted using the push button next to the Internal state with respect to the newly installed FPGA configuration.
It thus will not know that it needs to update its The download process and thus cannot know that the FPGA has freshlyīeen configured. When using a Byte Blaster cable the IO controller is not involved in In that case the IOĬontroller of course knows that the FPGA has been configured and will react Usually the IO controller configures the FPGA. Mounting it in the wrong direction my damage the MISTĪnd/or the USB Blaster. Straight box header which needs to be soldered to SV1 at the left PCB The required connector is a standard 10 pin 0.1" Matching plug is not present on the standard MIST boards but canĮasily be added. The USB Byte Blaster cable comes with a 10 pin flat ribbon cable. Monitoring and debugging of signals inside the FPGA. It canīe used to download FPGA configurations directly from the PC to theįPGA without using the SD card. The USB Byte Blaster Cable is a cable that connects a host PC via USBĭirectly to the MISTs FPGA using a so-called JTAG connection.