Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Custom USB Blaster clone problem with quartus

GFOXZ
Beginner
‎05-01-2021 04:18 PM
1,509 Views
hello, i am making clone usb blaster with ft245 and epm7064. its work perfectly and recognized by quartus programmer 16.1

the problem started when i change device descriptor product from "USB-Blaster" to "MB Prog V2", now quartus not detecting any hardware. but when i rename device descriptor back again to "USB-Blaster" quartus will recognized the hardware .

i think its about jtag_hw_usb-blaster.dll, because some programmer give .dll like "arrow usb programmer" and "USB-JTAG MBFTDI"

anyone with reference how to start making .dll or just about how can custom jtag programmer can be recognized by quartus will be helpfull for me.

thank you .

Link Copied

1 Reply
YuanLi_S_Intel
Employee
‎05-04-2021 11:09 PM
1,479 Views

Apologize that we do not support custom USB Blaster. I am now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.


0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.