Usb-blaster Driver Windows 10 Download
Mckenzie Witting
Did you look in /dev for something of the form /dev/ttyUSBx when you attach it?
Almost every FTDI device I've ever hooked to my box works. Even one that my dad bought that was apparently built using a counterfeit chip. The Windows driver on his Windows box refused to use it, It worked swimmingly in Linux.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Every FTDI I've used also works well in archlinux - but they usually show up as /dev/ttyACMx (eg /dev/ttyACM0). But regardless of what it displays as, just check /dev/ before and after plugging it in and look for anything different. You can save each listing to a file then diff the "pre" and "post" files.
From the information provided so far, it sounds like the device is fine and linux is fine - but you got some sample code that doesn't work. The problem is likely in the sample code. If you post (or link to) it, we can see if anything jumps out.
Also, if you haven't done any configuration of groups or user permissions, you'd need to run that example code as root. It's definitely safer and better to set up permissions well, but one or the other will be needed for the sample code to use the FTDI.
I've been rereading this thread as I think I may completely misunderstand. But after rereading this is not becoming more clear. I thought you had one device that worked in windows, but doesn't in arch. But now it seems a FTDI device works in linux (good, same here) but there is some "other device" that doesn't. I'm confused on what this other device is. Do you have more than one FTDI?
Thanks for the code, but it seems a lot of the interesting stuff is handled by other code. There is a reference to a header file ... is there somewhere you downloaded this code from where we could also get it?
I have an FPGA dev board with an FTDI usb interface. The FTDI sample code works on windows but not in linux, however the programming software that is supposed to be used with the dev board works in linux.
Also, I've already run through the process and gotten the USB blaster set up in linux. That's not my problem. My problem is talking to the FTDI chip. In Windows, I can talk to either the FTDI chip or the usb-blaster simultaneously without issue.
FYI, I'm trying to access the system level debug information without using the Altera software, so that I can get data off of my FPGA dev board on any computer, even if the 2 Gb of altera software is not installed.
This guide is provided "as is" and free of charge. There is no warranty or support of any kind. By using this guide, you acknowledge and agree that you do so at your sole risk. The author is not liable for any damages and claims arising from the use of this guide.
This guide will help you install VxD drivers for Sound Blaster Live! cards under Windows 98SE or Windows ME, including proper support for DOS gaming. I have personally tested this method with a Sound Blaster Live! 5.1 (model SB0100). Later on, other people have tested it with additional SBLive models as well, and all information about that has been summarized in this post. For reference, by using this guide, you get the following features from your SBLive card under Win9x:
Note that soundfonts only work when DOS games are running from within Windows 98/ME. If you go to pure DOS (by choosing Start > Shutdown > Restart in MS-DOS mode) then the card will use the (worse sounding) ECW sets instead. To my knowledge, there is no way to use .SF2 based soundfonts in pure DOS with an SBLive card.
Lastly, this guide and the modified driver pack that it uses are tailored to the US English version of Windows 98SE or Windows ME. Installing these drivers on a non-English system may cause the volume control screen (and possibly other aspects of the OS) to appear in English.
1.1 Certain chipsets have compatibility issues with VxD drivers and Creative's SB16 emulation. If you have a motherboard based on an Nvidia nForce chipset or an Intel ICH10+ chipset, then your system might not be compatible with this guide. Additionally, certain motherboards based on VIA chipsets may have compatibility issues with SBLive cards. For better stability on VIA systems, I recommend using an Audigy 2 or ZS card instead of a SBLive, and following this guide
1.2 Upon booting up your system, enter the BIOS and disable all COM and LPT ports in order to free up additional resources. If your motherboard has an integrated sound card, network card or any other integrated device that you are not using, disable it in the BIOS as well. Lastly, if you are not using USB, disable that too
1.3 During the driver installation process, the SBLive should be the only sound card in your system. Using a second sound card may cause the driver installation to fail
1.4 This guide has only been tested on Windows 98SE and Windows ME. A clean install of Windows must be performed before attempting the driver installation procedure. Do not use any "unofficial service packs". Only install the drivers for your motherboard and graphics card until you complete all the steps in this guide
1.5 A Sound Blaster Live! requires one free IRQ for the card itself. The value assigned to this IRQ varies from system to system, but it should not be the same as the IRQ assigned to the SB16 emulation device. Additionally, the SB16 emulation device requires three I/O ports, one IRQ and two DMA channels. The default values are: I/O ports 220, 330 and 388, IRQ 5, DMA 1 and DMA 5. If any of those resources are not free, the driver installation may fail. To determine if your system has enough free resources, under Windows 98SE click Start > Programs > Accessories > System Tools > System Information > Hardware Resources and check the IRQ, DMA and I/O sections
2.1 Download the modified SBLive driver CD image, and burn it to a disc
2.2 Place the disc in the CD-ROM drive on your Win98SE/ME machine, and cancel the autorun installer in case it starts
2.3 This guide assumes that your CD-ROM drive resides at D: (default location). If it's using a different letter, simply substitute that letter each time you come across D: in this guide
3.1 Run D:\CTShared\LaunchApp\SysInfo\Setup.exe which will install the Creative System Information utility and update the InstallShield Engine (important later)
3.2 Run D:\DirectX\dxsetup.exe which will install DirectX 9.0a and restart your computer (if you already have a newer version installed, skip this step)
3.3 Run D:\Audio\Drivers\CTZAPXX.exe and select "Driver Installation" and "VXD Drivers" then click Ok
3.4 Driver installation will take several minutes, don't interrupt the process until you are prompted to Restart then click Ok
3.5 After the restart, wait until the installer finishes, then go to Start > Settings > Control Panel > Multimedia > Audio > Playback > Advanced Properties > Performance > Sample Rate Conversion Quality > move the slider to "Best"
3.6 Start > Run > sndvol32.exe > Ok. Note that all the volume sliders are currently at 50% which is fairly quiet. You might want to move the sliders to a higher value and also mute any unused inputs
4.1 Run D:\Audio\AudioHQ\Setup.exe and install Creative AudioHQ (if you get an InstallShield Engine error here, repeat step 3.1)
4.2 Run D:\Audio\Diagnose\Setup.exe and install Creative Diagnostics
4.3 Run D:\Audio\Restore\Setup.exe and install Creative Restore Defaults
4.4 Run D:\Audio\SurMix2\Setup.exe and install Creative Surround Mixer
4.5 Start > Programs > Creative > Creative AudioHQ > Speaker and select the speaker setup that you are using, then click "Test" (in the screenshot below I'm using 5.1 speakers)
5.1 Run D:\DOSDRV\Setup.exe and restart when prompted
5.2 Wait until the Creative SB16 Emulation drivers are fully installed (this may take a few minutes)
5.3 During the boot process you might see a "Config file incomplete" error. Restart your computer one more time and it should disappear
For reference, here's how your games will sound with Creative's CT8MGM soundfont. Essentially, with this step complete, you can now select any soundfont that you like for General MIDI playback in DOS games. For example, if you want to use a soundfont which more closely resembles a Roland Sound Canvas see this post. Alternatively, if you want to play games which use GS instruments, see this post.
That said, these drivers also allow your SBLive to emulate FM Synthesis, should you want that. Of course, this sounds different from a genuine OPL3 chip, but it may still be somewhat usable, depending on the game that you're playing.
93ddb68554