Hardware Secrets
Home | Camera | Case | CE | Cooling | CPU | Input | Memory | Mobile | Motherboard | Networking | Power | Storage | Video | Other
First Look
Gabriel’s Blog
Main Menu
About Us
Awarded Products
Manufacturer Finder
RSS Feed
Test Your Skills
Subscribe today!
FireWire System Architecture: IEEE 1394A (2nd Edition)
FireWire System Architecture: IEEE 1394A (2nd Edition), by Don Anderson (Addison-Wesley Professional), starting at $0.26
Home » Motherboard » Bus
Firewire Bus (IEEE 1394)
Author: Ricardo Zelenovsky and Alexandre Mendonça 70,855 views
Type: Articles Last Updated: October 26, 2004
Page: 2 of 6

With the new FireWire revisions working to make it a serial bus with better performance each day, the communication rate implemented by a bridge is flexibly programmable to be between S100 (100 Mb/s) and S3200 (3200 Mb/s), with accessible cost either to connect computer peripherals or appliances. According to the 1394 committee, other devices, such as digital video transmission, are still limited by an architecture and a definition of protocol to bridges that are incomplete nowadays. In fact, the bus physical specification was very simple. The most complex is to define the bridge patterns, what is being done by IEEE 1394-1 proposition.

To start a description of 1394-1 proposition, some definitions will be shown.

  • Bridge: it is the circuit capable of allowing the communication between two or more serial buses with independent operations.
  • Bus_ID: it is a number of 10 bits that identifies, in a single way, one of the serial buses in a network topology made up of many buses.
  • Portal: it is the circuit that physically connects a FireWire bridge to a bus. Each bridge should implement at least 2 portals, that is, allow the communication between 2 buses. In a generic network, a bridge can implement various portals, identified by 0, 1, ..., N-1.
  • Network: it is a group of interconnected buses and nodes, capable of being mutually addressed by transactions involving data packets.
  • Local Node: Two nodes are said to be local if they are connected to the same bus, that is, with the same Bus_ID.
  • Local Node ID: it is a number of 16 bits that will represent an address to the node (peripheral) connected to the bus.
  • Network Cycle Master: it is a circuit elected to be the responsible for giving the clock that will synchronize the network. This way, many network events could happen synchronized by a single clock (isochronal way). But, the pattern IEEE 1394-1 also mentions an asynchronous communication.
  • Physical ID: it is a number of 6 bits associated to each node, through auto-identification process that comes after the bus initialization.
  • Remote Node: A node said to be remote in relation to another if they are connected to buses with different IDs.
  • Virtual Node: A generic node.
  • Virtual ID: it is a number of 6 bits that represents an address of a connected local node. The association of those Ids is made through the portal that generated the local bus.
  • Virtual Node ID: it is a number of 16 bits that represents an address to a generic node that, to transaction packets with a determined portal, should go over at least one bridge.
Print Version | Send to Friend | Bookmark Article « Previous |  Page 2 of 6  | Next »

Related Content
  • Everything You Need to Know About Serial ATA
  • Computer Port Extension
  • Why Serial?
  • Installing Frontal USB Ports
  • Basic Security in Wireless Networks

  • RSSLatest Content
    ASRock FM2A88X-ITX+ Motherboard
    April 27, 2015 - 2:40 AM
    GeForce GTX TITAN X Video Card Review
    April 22, 2015 - 4:00 AM
    A10-7800 CPU Review
    April 6, 2015 - 2:50 AM
    Samsung Galaxy A5 Smartphone Review
    March 31, 2015 - 2:47 AM
    A10-6800K vs. Core i3-4150 CPU Review
    March 25, 2015 - 3:15 AM
    Core i7-5960X CPU Review
    February 24, 2015 - 3:00 AM

    © 2004-15 Clube do Hardware, all rights reserved.
    Advertising | Legal Information | Privacy Policy
    All times are Pacific Standard Time (PST, GMT -08:00)