Ieee 1394 Host Controller Driver
Yufei Labbe
Although much of this information has already been posted, it's scattered among several camera-specific threads, so I thought I'd create a more search-friendly thread with a more general title. Most here have read the excellent studio1productions.com article on the subject here. I've gone through the studio1 steps as carefully as I could, yet still encountered a number of issues on a new Windows 10 Pro 64-bit system with all current updates (full system-specs are in my signature):
I first bought a $59 StarTech IEEE1394 low-profile PCIe interface card from B+H. Note that this card has the TI-chipset, which the studio1 article doesn't recommend. I downloaded and installed the Windows 64-bit legacy driver linked on the site. Though the installation only resulted in "successful" dialog boxes from Windows after each step, the card never appears in device manager (note: I never attempted to connect a powered-on FireWIre device to the StarTech card):
Next, I bought a generic-branded FireWire PCIe card ("Godshark") from Amazon for $16.99. I made sure this one had the VIA-chipset as the studio1 article recommends. Again, after following the studio1 instructions, Windows' device manager failed to recognize the legacy driver. Every time I boot the computer, the VIA driver is already installed. So I again attempt to uninstall the VIA driver. However, when I attempt to manually install the Windows' 64-bit legacy driver (even though the initial "installation" prompted no error messages), the VIA driver continues to re-appear in device manager and the already "installed" Legacy1394.inf driver never appears.
Even the motherboard's BIOS got confused (which I never altered) and booted in an odd resolution (which a single re-boot "fixed"). I tried every troubleshooting task I could think of (e.g., removing devices, uninstalling drivers/reinstalling drivers, etc.). Prior to starting this whole process, I had no error messages in device manager and a clean-install of Windows 10 Pro 64-bit with only Vegas Movie Studio, FXhome Intensity, and Blackmagic Media Express installed.
Lastly, I pulled the Blackmagic Intensity Pro 4K HDMI capture card from the system. Neither of Vegas' two capture tools see the device. I have downloaded and run the WinDV free capture utility and no device is found. The only other board remaining in the system is the display adapter which shipped with the computer.
Note that according to Windows' device manager, under "IEEE 1394 host controllers," the "VIA 1394 OHCI Compliant Host Controller" general dialogue box continues to indicate, "This device is working properly," which it always says when the VIA driver is installed. When attempting to manually install the 64-bit legacy driver, Windows overrides my installation and re-installs the VIA driver, saying "Windows has determined this driver to be the best." There are no '!' marks or error messages under IEEE 1394 host controllers and I am unable to permanently remove the VIA host controller driver which simply reappears after every re-boot.
I know the next step is to go back to ground-zero and start all over again (i.e., pull every board, and uninstall every piece of software and driver). However, I cannot eliminate the ominous-sounding "Poisoned TLP on slot X" POST-error. This happens no matter which slot I install the VIA card into, so it's as if the VIA hardware itself is causing some kind of basic POST-issue.
Windows had also alerted me to a "PCI-to-PCI bridge" error at some point (I don't recall exactly where), which I can only guess is related to the POST-error. I'm assuming that until I resolve this, nothing else is going to move forward.
Now, this VIA card is exactly like the one pictured in the studio1 article, and when installed, device manager shows no errors whatsoever (i.e.,"this device is working properly"). Yet the POST-error only occurs when the card is in the machine, and no other Windows apps (other than device manager) is able to see the card. Perhaps try another VIA card?
Holy crap! I can't believe I got it to work. When I attempted to install the VIA card again today, my PC lost all internet connectivity (I have it hard-wired to an Ethernet switch). After about a dozen re-boots, BIOS downloads, and system patches, everything finally worked again. Doesn't capture correctly in WinDV, and not at all in VEGAS Capture, but it works in Vegas' "capture video" applet (located under Vegas' project menu). Here's the highlights:
I was super-surprised that everything worked even after getting the "poisoned TLP slot" error again. But it did. Now, I'm crossing my fingers that my Blackmagic Intensity Pro 4K card will work once I reinstall it.
Also, the ghosting appears to be a pulldown-error. At a 1/48th shutter-speed, some motion-blur is to be expected, but the motion appears slightly artifacted (i.e., unnatural), which may suggest an incompatible 3:2-pulldown algorithm somewhere in the chain.
And now . . . it doesn't work. I captured one clip using Vegas' "capture video" applet directly into Vegas and it worked. One re-boot later, and the darned VIA 1394 driver re-appeared in device manager. Again, I "searched for drivers on my PC" and re-installed the Windows' 64-bit legacy driver. Reboot. Now Vegas' ingest tool shows only a black screen while tape is playing back in my DVCAM VTR. It senses the VTR's position, and its counter "knows" when I'm playing, rewinding, etc. (though, no device-control), but NO VIDEO!
1. Re-installed the legacy driver in device manager.
2. PC immediately re-boots on its own (as it did before).
3. PC boots into a POST-error: "Poisoned TLP slot."
4. Vegas' "capture video" tool sees the device, but no image.
5. Uninstalled the legacy driver.
6. Reboot into POST-error.
7. Windows automatically replaces the legacy driver in device manager.
8. Still no video in capture window.
While I was typing this, I turned to the screen and I see video in Vegas' capture video display! As I hot-swapped the FireWIre cable in and out of the VIA-card's two inputs, Vegas continually "found" the "Sony camcorder/VTR" device, but the screen remained black and captured zero frames. Odd. But it's working now (at least for the moment).
I remember problems similar to what you described when either the fire cable or the connectors on the camera were bad. Try another cable. If the connectors on the camera are going bad, not sure what you can do.
I use a firewire card with ti chipset to connect my pc, I use windows 10, with a tascam dm3200, but i don't have legacy driver and "1394 ohci compliant host controller" and"texas instruments 1394 ohci compliant host controller" drivers give me some audio dropout. how I can solve it? if possible to download legacy driver?
thank you.
I have install win XP SP3 on my desktop AcerPower F2 computer and it kept asking for this driver. It always shows on other device system interrupts controller. Please what else do you think i can do to solve this issue
I have installed the driver for the capture card from the manufacturer's website but after i install the driver for DV/AVTWins, it kept asking for driver for system interrupt controller and my capture card is not geting signal from any DV camcoder i pluged in through fire wire cable IEEE 1394.
A USB and Firewire Host Controller Interface (UFHC) is a register-level interface that enables a host controller for USB or IEEE 1394 hardware to communicate with a host controller driver in software. The driver software is typically provided with an operating system of a personal computer, but may also be implemented by application-specific devices such as a microcontroller.
On the expansion card or motherboard controller, this involves much custom logic, with digital logic engines in the motherboard's controller chip, plus analog circuitry managing the high-speed differential signals. On the software side, it requires a device driver (called a Host Controller Driver, or HCD).
When applied to an IEEE 1394 (also known as FireWire; i.LINK or Lynx) card, OHCI means that the card supports a standard interface to the PC and can be used by the OHCI IEEE 1394 drivers that come with all modern operating systems. Because the card has a standard OHCI interface, the OS does not need to know in advance exactly who makes the card or how it works; it can safely assume that the card understands the set of well-defined commands that are defined in the standard protocol.
The OHCI standard for USB is similar to the OHCI standard for IEEE 1394, but supports USB 1.1 (full and low speeds) only; so as a result its register interface looks completely different. Compared with UHCI, it moves more intelligence into the controller, and thus is accordingly much more efficient; this was part of the motivation for defining it. If a computer provides non-x86 USB 1.1, or x86 USB 1.1 from a USB controller that is not made by Intel or VIA, it probably uses OHCI (e.g. OHCI is common on add-in PCI Cards based on an NEC chipset). It has many fewer intellectual property restrictions than UHCI.[2] It only supports 32-bit memory addressing,[3] so it requires an IOMMU or a computationally expensive bounce buffer to work with a 64-bit operating system.[citation needed] OHCI interfaces to the rest of the computer only with memory-mapped I/O.[3]
Universal Host Controller Interface (UHCI) is a proprietary interface created by Intel for USB 1.x (full and low speeds). It requires a license from Intel. A USB controller using UHCI does little in hardware and requires a software UHCI driver to do much of the work of managing the USB bus.[2] It only supports 32-bit memory addressing,[4] so it requires an IOMMU or a computationally expensive bounce buffer to work with a 64-bit operating system.[citation needed] UHCI is configured with port-mapped I/O and memory-mapped I/O, and also requires memory-mapped I/O for status updates and for data buffers needed to hold data that needs to be sent or data that was received.[4]
64591212e2