I have an Arduino Duemilanove with an Atmega 328. I am working on Ubuntu 12.04, and the Arduino IDE's version is 1.0. Recently, I tried to upload a few of the sample sketches onto it, such as the Blink one. However, none of my attempts are working and they result in the same error every time I try it - avrdude: stk500recv: programmer is not responding. I have enabled '/dev/ttyUSB0' under Tools - Serial Port. I have also selected the correct board (Duemilanove with Atmega 328) from the list.

1. Driver Usb Serial Port Op Commands

Yet, I am not able to resolve the issue. I have searched online as well and none of the other responses for this problem seem to be working for me. Could someone tell me why I am encountering this issue and help me resolve it?

Update: I tried turning the onboard Atmega and fitting it in the other direction. Now, I encounter no problems uploading, but nothing happens afterwards. The onboard LED also does not seem to be blinking. I had this problem with a Crowduino, running the Arduino IDE on OSX.

Jun 15, 2016. The DirecTV D11/H20 Satellite set top box contains a USB port that can be used as a serial port to change channels and perform other tasks on the box. This STB works as well using the H20 commands, version 1.9 of the script and the USB to USB cable set from but it.

The solution for me was to switch on verbose output during upload (in the arduino IDE preferences pane). Then, when uploading, you can see avrdude sending three packets avrdude: Send: 0 30 20 (with corresponding RX flashes on the board) right before the avrdude: serrecv: programmer is not responding error.

USB to Serial Adapter in Win10 Using Prolific USB to Serial adapter for TNC. I then switched the comm port I was plugging the Prolific USB Serial Adapter into, to the older driver, and everything worked fine again. Installing the driver and rolling the driver back to this 2009 driver for the comm port your connecting the outdated. I generally use an OnTime event to send a command to the device requesting its current reading and the data is sent along and pasted into Excel. As more laptops are delivered without serial ports, device manufacturers are moving to communicate through USB ports. The writing is on the wall. I am going to have to retrieve data from a USB port.

The trick is to hit the reset button on the board immediately before these three packets are sent. Then the program will be uploaded successfully. I know this is an old post, but there is some voodoo-talk in the answers around here amongst good ideas, let's try to be a bit more real about what's happening and sum up the good stuff to check: Basically, when that happens, it is a good idea to enable verbose mode for avrdude, to get a better idea of what's happening. To do so, you only need to go in the preferences and check the verbose mode box. It's also a good idea to move away from the arduino IDE, and launch a console to be more comfortable on reading avrdude's output, that you'll get on clicking on the upload button.

What's important here to put 3 or 4 -v to the command call. Here's how looks like such avrdude commands, with made up parameters as they are totally dependent on how the Arduino has been installed: avrdude -v -v -v -v -C /path/to/avrdude.conf -patmega328 -P/dev/usbport -U flash:w:/path/to/firmware.hex A good way to get the correct command line to use is to copy it from the verbose output of the Arduino IDE output log when verbosity has been enabled.

When you get avrdude: stk500recv: programmer is not responding, it basically means that something wrong is happening, before the flashing actually begins. Basically you have to check (from hardware to software, low level to high level):. if the cable and/or connectors does not have microcuts;. if no solder points are short circuiting (i.e. Touching something metallic around), that means:. if there is no short circuit on the PCB between Rx and Tx (usually pins 1 and 0);. if there is no contact with a metallic element below the board, or tiny bits between a component's legs (like the FTDI, the atmega chip or any other);.

if the atmega chip is not out of power (GND/VCC shortcut or cut or VCC input being dead);. if the 1 and 0 pins of the Arduino are not being used by some shield or custom design ( /! Does not apply to the leonardo as it has independent USB handling);.

if the USB to UART converter does not have a problem ( FTDI on older duemilanove or Atmega16U2 on newer Unos);. if the Atmega328 chip is fried or wrongly installed;. if the bootloader has been overwritten or is failing;. if the right baudrate is applied for entering the bootloader;.

if the right settings are set for the target MCU and Board; usually the avrdude -v -v -v -v can help a lot find at which stage it is failing. Whether it can't make a USB connection at all (cable failing, USB/UART, PCB), or it is a bootloader problem. Update: I tried turning the onboard Atmega and fitting it in the other direction.

Now, I encounter no problems uploading, but nothing happens afterwards. The onboard LED also does not seem to be blinking. I'm afraid that if you reversed the position of the atmega, and then it does not work, the fact that you placed the power source on digital pins may have burnt your chip. On Windows 7, I had this problem multiple times, each time with different error messages. Basically, the IDE is sending to the wrong port. To fix this, simply go to 'Tools' - 'Ports' - select the COM port that your board is on.

Make sure to double check your board's port: 1) Start the device manager 2) Make sure, your Arduino driver is listed under the port matching your IDE's port settings (mentioned above) 3) My board is listed under port COM1. If you want, you can simply change the port in the driver's advanced settings.

'Firewire' redirects here. For other uses, see. IEEE 1394 Interface Type Production history Designer (1394a/b), IEEE P1394 Working Group Designed 1986; 31 years ago ( 1986) Manufacturer Various Produced 1994–2013 Superseded by and General specifications Length 4.5 meters maximum Width 1 Hot pluggable Yes Daisy chain Yes, up to 63 devices Audio signal No Video signal No Pins 4, 6, 9 Electrical Max. Voltage 30 V Max. Current 1.5 A Data Data signal Yes Bitrate 400–3200 /s (50–400 MB/s) IEEE 1394 is an for a for high-speed communications and real-time data transfer. It was developed in the late 1980s and early 1990s by, which called it FireWire.

The 1394 interface is also known by the brands i.LINK , and Lynx. The copper cable it uses in its most common implementation can be up to 4.5 metres (15 ft) long. Power is also carried over this cable allowing devices with moderate power requirements to operate without a separate power supply. FireWire is also available in and versions. The 1394 interface is comparable to, though USB requires a master controller and has greater market share. A pair of 6-conductor alpha connectors on the edge of an FireWire is Apple's name for the IEEE 1394 High Speed Serial Bus.

It was initiated by Apple (in 1986 ) and developed by the IEEE P1394 Working Group, largely driven by contributions from Apple, although major contributions were also made by engineers from, Sony, and /SGS (now ). IEEE 1394 is a serial architecture for high-speed data transfer. FireWire is a bus, meaning that information is transferred one bit at a time. Buses utilize a number of different physical connections, and as such are usually more costly and typically heavier. IEEE 1394 fully supports both and applications. Apple intended FireWire to be a serial replacement for the parallel bus while providing connectivity for digital audio and video equipment.

Apple's development began in the late 1980s, later presented to the IEEE, and was completed in January 1995. In 2007, IEEE 1394 was a composite of four documents: the original IEEE Std. 1394-1995, the amendment, the amendment, and the amendment.

On June 12, 2008, all these amendments as well as errata and some technical updates were incorporated into a superseding standard, IEEE Std. Apple first included on-board FireWire in some of its 1999 Macintosh models (though it had been a build-to-order option on some models since 1997), and most Apple Macintosh computers manufactured in the years 2000 through 2011 included FireWire ports.

However, in February 2011 Apple introduced the first commercially available computer with. Apple released its last computers featuring FireWire late 2012. By 2014 Thunderbolt had become a standard feature across Apple's entire line of computers effectively becoming the to FireWire in the Apple ecosystem. Sony's implementation of the system, i.LINK, used a smaller connector with only four signal conductors, omitting the two conductors that provide power for devices in favor of a separate power connector. This style was later added into the 1394a amendment. This port is sometimes labeled S100 or S400 to indicate speed in Mbit/s. The system was commonly used to connect and (digital video) cameras, but was also popular in industrial systems for and systems.

Many users preferred it over the more common for its then greater effective speed and power distribution capabilities. Benchmarks show that the sustained data transfer rates are higher for FireWire than for USB 2.0, but lower than. Results are marked on Apple but more varied on. Intellectual property considerations Implementation of IEEE 1394 is said to require use of 261 issued international patents held by 10 corporations. Use of these patents requires licensing; use without license generally constitutes patent.

Companies holding IEEE 1394 IP formed a with, LLC as the license administrator, to whom they licensed patents. MPEG LA sublicenses these patents to providers of equipment implementing IEEE 1394. Under the typical patent pool license, a royalty of US$0.25 per unit is payable by the manufacturer upon the manufacture of each 1394 finished product; no royalties are payable by users. A person or company may review the actual 1394 Patent Portfolio License upon request to MPEG LA. Implementors would thereby ordinarily reveal some interest to MPEG LA early in the design process. MPEG LA does not provide assurance of protection to licensees beyond its own patents.

At least one formerly licensed patent is known to be removed from the pool, and other hardware patents exist that reference 1394-related hardware and software functions related to use in IEEE 1394. In total, over 1770 patents issued in the 20 years (the WIPO minimum) preceding 2011 contain 'IEEE 1394' in their titles alone, placing 1500 unavailable from MPEG LA. The 1394 High Performance Serial Bus Trade Association (the '1394 TA') was formed to aid marketing of IEEE 1394. Its bylaws prohibit dealing with intellectual property issues. The 1394 Trade Association operates on an individual no cost membership basis to further enhancements to 1394 standards. The Trade Association also is the library source for all 1394 documentation and standards available.

Technical specifications FireWire can connect up to 63 in a tree or daisy-chain (as opposed to Parallel SCSI's topology). It allows device communication — such as communication between a scanner and a printer — to take place without using system memory or the.

FireWire also supports multiple per bus. It is designed to support and. The copper cable it uses in its most common implementation can be up to 4.5 metres (15 ft) long and is more flexible than most cables. In its six-conductor or nine-conductor variations, it can supply up to 45 watts of power per port at up to 30 voltsallowing moderate-consumption devices to operate without a separate power supply.

FireWire devices implement the 'configuration ROM' model for device configuration and identification, to provide capability. All FireWire devices are identified by an IEEE unique identifier in addition to well-known codes indicating the type of device and the it supports. FireWire devices are organized at the bus in a tree topology. Each device has a unique self-ID. One of the nodes is elected root node and always has the highest ID. The self-IDs are assigned during the self-ID process, which happens after each bus resets.

The order in which the self-IDs are assigned is equivalent to traversing the tree, post-order. Is capable of safely operating critical systems due to the way multiple devices interact with the bus and how the bus allocates bandwidth to the devices. Is capable of both and transfer methods at once.

Data transfers are transfers for devices that require continuous, guaranteed bandwidth. In an aircraft, for instance, devices include control of the rudder, mouse operations and data from pressure sensors outside the aircraft. All these elements require constant, uninterrupted bandwidth. To support both elements, dedicates a certain percentage to data and the rest to data. In IEEE 1394, 80% of the bus is reserved for cycles, leaving data with a minimum of 20% of the bus.

Encoding scheme FireWire uses (D/S encoding). In D/S encoding, two (NRZ) signals are used to transmit the data with high reliability. The NRZ signal sent is fed with the clock signal through an, creating a strobe signal.

This strobe is then put through another XOR gate along with the data signal to reconstruct the clock. This in turn acts as the bus's for synchronization purposes.

Arbitration The process of the bus deciding which node gets to transmit data at what time is known as. Each arbitration round lasts about 125 microseconds. During the round, the root node (device nearest the processor) sends a cycle start packet. All nodes requiring data transfer respond, with the closest node winning.

After the node is finished, the remaining nodes take turns in order. This repeats until all the devices have used their portion of the 125 microseconds, with transfers having priority. Standards and versions The previous standards and its three published amendments are now incorporated into a superseding standard, IEEE 1394-2008. The features individually added give a good history on the development path. FireWire 400 (IEEE 1394-1995) The original release of IEEE 1394-1995 specified what is now known as FireWire 400. It can transfer data between devices at 100, 200, or 400 data rates (the actual transfer rates are 98.304, 196.608, and 393.216, i.e., 12.288, 24.576 and 49.152 per second respectively).

These different transfer modes are commonly referred to as S100, S200, and S400. Cable length is limited to 4.5 metres (14.8 ft), although up to 16 cables can be using active repeaters; external hubs, or internal hubs are often present in FireWire equipment. The S400 standard limits any configuration's maximum cable length to 72 metres (236 ft). The 6-conductor connector is commonly found on desktop computers, and can supply the connected device with power.

The 6-conductor powered connector, now referred to as an alpha connector, adds power output to support external devices. Typically a device can pull about 7 to 8 watts from the port; however, the voltage varies significantly from different devices.

Voltage is specified as unregulated and should nominally be about 25 volts (range 24 to 30). Apple's implementation on laptops is typically related to battery power and can be as low as 9 V. Improvements (IEEE 1394a-2000) An amendment, IEEE 1394a, was released in 2000, which clarified and improved the original specification. It added support for, quicker bus reconfiguration, and a power-saving. IEEE 1394a offers a couple of advantages over the original IEEE 1394-1995. 1394a is capable of arbitration accelerations, allowing the bus to accelerate arbitration cycles to improve efficiency. It also allows for arbitrated short bus reset, in which a node can be added or dropped without causing a big drop in isochronous transmission.

1394a also standardized the 4-conductor alpha connector developed by Sony and trademarked as ' i.LINK', already widely in use on consumer devices such as camcorders, most PC laptops, a number of PC desktops, and other small FireWire devices. The 4-conductor connector is fully data-compatible with 6-conductor alpha interfaces but lacks power connectors. FireWire 800 (IEEE 1394b-2002). A 9-conductor bilingual connector IEEE 1394b-2002 introduced FireWire 800 (Apple's name for the 9-conductor 'S800 bilingual' version of the IEEE 1394b standard). This specification and corresponding products allow a transfer rate of 786.432 via a new encoding scheme termed beta mode. It is backwards compatible with the slower rates and 6-conductor alpha connectors of FireWire 400. However, while the IEEE 1394a and IEEE 1394b standards are compatible, FireWire 800's connector, referred to as a beta connector, is different from FireWire 400's alpha connectors, making legacy cables incompatible.

A bilingual cable allows the connection of older devices to the newer port. In 2003, Apple was the first to introduce commercial products with the new connector. The full IEEE 1394b specification supports data rates up to 3200 (i.e., 400 ) over beta-mode or optical connections up to 100 metres (330 ft) in length. Standard supports 100 metres (330 ft) at S100.

The original 1394 and 1394a standards used (renamed to alpha mode) with the cables, while 1394b added a data encoding scheme called referred to as beta mode. Beta mode is based on (from, also used for many other protocols). 8B/10B encoding involves expanding an 8 bit data word into 10 bits, with the extra bits after the 5th and 8th data bits. The partitioned data is sent through a calculator function. The Running Disparity calculator attempts to keep the number of 1s transmitted equal to 0s, thereby assuring a DC-balanced signal.

Then, the different partitions are sent through a 5B/6B encoder for the 5 bit partition and a 3B/4B encoder for the 3 bit partition. This gives the packet the ability to have at least two 1s, ensuring synchronization of the PLL at the receiving end to the correct bit boundaries for reliable transfer. An additional function of the coding scheme is to support the arbitration for bus access and general bus control. This is possible due to the 'surplus' symbols afforded by the 8B/10B expansion. (While 8-bit symbols can encode a maximum of 256 values, 10-bit symbols permit the encoding of up to 1024.) Symbols invalid for the current state of the receiving PHY indicate data errors. FireWire S800T (IEEE 1394c-2006) IEEE 1394c-2006 was published on June 8, 2007. It provided a major technical improvement, namely new port specification that provides 800 Mbit/s over the same (Ethernet) connectors with, which is specified in IEEE 802.3 clause 40 along with a corresponding automatic negotiation that allows the same port to connect to either IEEE Std 1394 or devices.

Though the potential for a combined Ethernet and FireWire 8P8C port is intriguing, as of November 2008, no products or chipsets include this capability. FireWire S1600 and S3200 In December 2007, the 1394 Trade Association announced that products would be available before the end of 2008 using the S1600 and S3200 modes that, for the most part, had already been defined in 1394b and were further clarified in IEEE Std. The 1.572864 Gbit/s and 3.145728 Gbit/s devices use the same 9-conductor beta connectors as the existing FireWire 800 and are fully compatible with existing S400 and S800 devices.

It competes with. S1600 (Symwave ) and S3200 (Dap Technology ) development units have been made, however because of FPGA technology DapTechnology targeted S1600 implementations first with S3200 not becoming commercially available until 2012. Declared FireWire dead in 2008. As of 2012, there were few S1600 devices released, with a Sony camera being the only notable user.

Future enhancements (including P1394d) A project named IEEE P1394d was formed by the IEEE on March 9, 2009 to add as an additional transport medium to FireWire. The project was withdrawn in 2013. Other future iterations of FireWire were expected to increase speed to 6.4 Gbit/s and additional connectors such as the small multimedia interface. Operating system support Full support for IEEE 1394a and 1394b is available for, Apple through, and. In Windows XP, a degradation in performance of 1394 devices may have occurred with installation of Service Pack 2. This was resolved in Hotfix 885222 and in.

Some FireWire hardware manufacturers also provide custom device drivers that replace the Microsoft OHCI host adapter driver stack, enabling S800-capable devices to run at full 800 Mbit/s transfer rates on older versions of Windows (XP SP2 w/o Hotfix 885222) and Windows Vista. At the time of its release, Microsoft supported only 1394a, with assurances that 1394b support would come in the next service pack. Service Pack 1 for Microsoft has since been released, however the addition of 1394b support is not mentioned anywhere in the release documentation. The 1394 bus driver was rewritten for Windows 7 to provide support for higher speeds and alternative media. No driver is supplied with Windows 8, 8.1 or 10 but can be downloaded and installed. In Linux, support was originally provided by libraw1394 making direct communication between user space and IEEE 1394 buses.

Subsequently a new kernel driver stack, nicknamed JuJu, has been implemented. Cable TV system support Under FCC Code 47 CFR 76.640 section 4, subsections 1 and 2, Cable TV providers (in the US, with digital systems) must, upon request of a customer, have provided a high-definition capable with a functional FireWire interface. This applied only to customers leasing high-definition capable from their cable provider after April 1, 2004.

The interface can be used to display or record Cable TV, including HDTV programming. In June 2010, the FCC issued an order that permitted set-top boxes to include IP-based interfaces in place of FireWire. Comparison with USB While both technologies provide similar end results, there are fundamental differences between and FireWire. USB requires the presence of a master, typically a PC, which connects point to point with the USB slave. This allows for simpler (and lower-cost) peripherals, at the cost of lowered functionality of the bus. Intelligent are required to connect multiple USB devices to a single USB bus master.

By contrast, FireWire is essentially a (where any device may serve as the host or client), allowing multiple devices to be connected on one bus. The FireWire host interface supports DMA and memory-mapped devices, allowing data transfers to happen without loading the host CPU with interrupts and buffer-copy operations. Additionally, FireWire features two data buses for each segment of the bus network whereas, until USB 3.0, USB featured only one. This means that FireWire can have communication in both directions at the same time (full-duplex), whereas USB communication prior to 3.0 can only occur in one direction at any one time (half-duplex). While USB 2.0 expanded into the fully backwards-compatible and (using the same main connector type), FireWire used a different connector between 400 and 800 implementations. Common applications Consumer automobiles IDB-1394 Customer Convenience Port (CCP) was the automotive version of the 1394 standard.

Consumer audio and video IEEE 1394 was the (HANA) standard connection interface for A/V (audio/visual) component communication and control. HANA was dissolved in September 2009 and the 1394 Trade Association assumed control of all HANA-generated intellectual property. Military and aerospace vehicles Aerospace standard originally released in 2004 and reaffirmed in 2013 establishes IEEE-1394 standards as a military and aerospace databus network in those vehicles. AS5643 is utilized by several large programs, including the, the aircraft, weapon and polar satellite for NOAA. AS5643 combines existing 1394-2008 features like looped topology with additional features like transformer isolation and time synchronization, to create deterministic double and triple fault-tolerant data bus networks. General networking FireWire can be used for ad-hoc (terminals only, no routers except where a FireWire hub is used). Specifically, specifies how to run over the FireWire interface, and specifies how to run.

Mac OS X, and include support for networking over FireWire., and include native support for IEEE 1394 networking. Does not have native support but may work with third party drivers. A network can be set up between two computers using a single standard FireWire cable, or by multiple computers through use of a hub. This is similar to networks with the major differences being transfer speed, conductor length, and the fact that standard FireWire cables can be used for communication. On December 4, 2004, Microsoft announced that it would discontinue support for networking over the FireWire interface in all future versions of.

Consequently, support for this feature is absent from and later Windows releases. Microsoft rewrote their 1394 driver in but networking support for FireWire is not present.

Unibrain offers free FireWire networking drivers for Windows called ubCore, which support Windows Vista and later versions. Some models of the console had an i.LINK-branded 1394 connector. This was used for networking until the release of an Ethernet adapter late in the console's lifespan, but very few software titles supported the feature.

IIDC IIDC (Instrumentation & Industrial Digital Camera) is the FireWire data format standard for live video, and is used by Apple's A/V camera. The system was designed for systems but is also used for other applications and for some webcams.

Although they are easily confused since they both run over FireWire, IIDC is different from, and incompatible with, the ubiquitous AV/C (Audio Video Control) used to control camcorders and other consumer video devices. DV Digital Video is a standard used by some digital. All DV cameras that recorded to tape media had a FireWire interface (usually a 4-conductor).

All DV ports on camcorders only operate at the slower 100 Mbit/s speed of FireWire. This presents operational issues if the camcorder is daisy chained from a faster S400 device or via a common hub because any segment of a FireWire network cannot support multiple speed communication. Labelling of the port varied by manufacturer, with Sony using either its i.LINK trademark or the letters 'DV'. Many have a 'DV-input' FireWire connector (usually an alpha connector) that can be used to record video directly from a DV camcorder ('computer-free'). The protocol also accommodates remote control (play, rewind, etc.) of connected devices, and can stream time code from a camera. USB is unsuitable for transfer of the video data from tape because tape by its very nature does not support variable data rates.

USB relies heavily on processor support and this was not guaranteed to service the USB port in time. The later move away from tape towards solid state memory or disc media (e.g., SD Cards, optical disks or hard drives) has facilitated moving to USB transfer because file based data can be moved in segments as required. Frame grabbers IEEE 1394 interface is commonly found in, devices that capture and digitize an analog video signal; however, IEEE 1394 is facing competition from the interface (citing speed and availability issues). IPod and iPhone synchronization and charging released prior to the used IEEE 1394a ports for syncing music and charging, but in 2003, the FireWire port in iPods was succeeded by Apple's and IEEE 1394 to 30-pin connector cables were made. Dropped support for FireWire cables starting with, and in favor of cables. Security issues Devices on a FireWire bus can communicate by (DMA), where a device can use hardware to map internal memory to FireWire's 'Physical Memory Space'. The SBP-2 used by FireWire disk drives uses this capability to minimize interrupts and buffer copies.

In SBP-2, the initiator (controlling device) sends a request by remotely writing a command into a specified area of the target's FireWire address space. This command usually includes buffer addresses in the initiator's FireWire Physical Address Space, which the target is supposed to use for moving I/O data to and from the initiator. On many implementations, particularly those like PCs and Macs using the popular, the mapping between the FireWire 'Physical Memory Space' and device physical memory is done in hardware, without operating system intervention. While this enables high-speed and low-latency communication between data sources and sinks without unnecessary copying (such as between a video camera and a software video recording application, or between a disk drive and the application buffers), this can also be a security or media rights-restriction risk if untrustworthy devices are attached to the bus and initiate a. One of the applications known to exploit this to gain unauthorized access to running Windows, Mac OS and Linux computers is the spyware. For this reason, high-security installations typically either use newer machines that map a space to the FireWire 'Physical Memory Space' (such as a, or any ), disable relevant drivers at operating system level, disable the hardware mapping between FireWire and device memory, physically disable the entire FireWire interface, or opt to not use FireWire or other hardware like, or, which expose DMA to external components.

An unsecured FireWire interface can be used to a machine whose operating system has crashed, and in some systems for remote-console operations. Windows natively supports this scenario of kernel debugging, although newer Preview builds no longer include the ability out of the box. On FreeBSD, the dcons driver provides both, using as debugger. Under Linux, firescope and fireproxy exist. See also. References.

Retrieved 2017-03-07. The 1394 digital link standard was conceived in 1986 by technologists at Apple Computer.

Yaghmour, Karim; Masters, Jon; Ben-Yossef, Gilad; Gerum, Philippe (2008-08-15). O'Reilly Media, Inc. Retrieved 2012-01-08.

1394 Trade Association. Archived from on 2014-04-04. Retrieved 2016-06-14. ^ Teener, Michael J. Retrieved 2008-07-14. Retrieved 2010-01-25. Retrieved 2010-01-25.

Archived from on 2012-04-15. Archived from on 2011-11-04. Archived from on 2011-09-27.

Archived from (PDF) on 2007-01-07. Retrieved 2012-09-01. Retrieved 2012-09-01.

IEEE p1394 Working Group (1996-08-30). Davis, Larry. Retrieved 2016-06-20. Retrieved 2010-01-25. IEEE p1394a Working Group (2000-06-30).

IEEE Std 1394a-2000 High Performance Serial Bus — Amendment 1. available. IEEE p1394b Working Group (2002-12-14). Retrieved 2012-09-01. ^ Haden, Rhys (2007-06-30).

Retrieved 2012-09-01. IEEE Std 1394c-2006.

1394 Trade Association. Retrieved 2008-08-03. Retrieved 2012-09-01. Arthur, Charles (2008-10-17). Retrieved 2016-06-14. Henehan, Burke (2012-01-06). Retrieved 2016-06-14.

IEEE Standards. Retrieved 8 October 2012. Retrieved 2016-06-14. Baxter, Les (2007-11-01). Retrieved 2007-12-19.

Retrieved 2010-01-25. Retrieved 2010-01-25. Retrieved 2012-08-12. Retrieved 2010-01-25.

Retrieved 2010-01-25. Retrieved 2010-01-25. Archived from on 2008-05-17. Retrieved 2010-01-25. Archived from on 2008-04-30.

Retrieved 2010-01-25. Archived from on 2008-05-11. Retrieved 2010-01-25. Retrieved 2010-01-25. Retrieved 2010-09-12. Retrieved 2012-10-10.

Archived from (PDF) on 2010-05-27. Retrieved 2010-01-25. Retrieved 2010-01-25. (PDF), 2010-06-18, retrieved 2016-06-14. Retrieved 2016-06-14. (PDF), retrieved 2016-06-14. Retrieved 2012-09-01.

Archived from the original on 2006-10-06. Retrieved 2016-06-14. CS1 maint: Unfit url. Archived from on 2010-01-29.

Driver Usb Serial Port Op Commands

Retrieved 2010-01-25. B.V., Richard Mourn, DAPTechnology.

Retrieved 2016-06-14. Retrieved 2016-06-14. Mourn, Richard (2011-09-07).

Retrieved 2016-06-14. Retrieved 2010-01-25. Retrieved 2012-09-01. Retrieved 2010-01-25. Retrieved 2010-01-25. Retrieved 2010-01-25.

Retrieved 2010-01-25. Retrieved 2012-09-01. Retrieved 2012-09-01. Retrieved 2010-01-25.

Microsoft Developer Network. IEEE 1394a specification. Retrieved 2012-09-01. Retrieved 2013-09-14. Retrieved 2010-01-25. (PDF) (PDF). Gamma International.

Retrieved 2014-04-28. Retrieved 2011-03-15. Retrieved 2017-09-02. Retrieved 2017-09-02. Retrieved 2010-01-25. Retrieved 2010-01-25. This article is based on material taken from the prior to 1 November 2008 and incorporated under the 'relicensing' terms of the, version 1.3 or later.

Further reading. INCITS T10 Project 1467D (2004). Information technology—Serial Bus Protocol 3 (SBP-3). ANSI INCITS 375-2004.

Anderson, Don (1999). FireWire System Architecture. MindShare, Inc.

External links Wikimedia Commons has media related to.