JAJSQ90 september   2020 TSB41BA3F-EP

PRODUCTION DATA  

  1.   1
  2. 特長
  3. アプリケーション
  4. 概要
  5. Revision History
  6. Terminal Configuration and Functions
    1.     Terminal Functions
  7. Specifications
    1. 6.1 Absolute Maximum Ratings
    2. 6.2 ESD Ratings
    3. 6.3 Recommended Operating Conditions
    4. 6.4 Thermal Information
    5. 6.5 Electrical Characteristics - Driver
    6. 6.6 Electrical Characteristics - Receiver
    7. 6.7 Electrical Characteristics - Device
    8. 6.8 Switching Characteristics
  8. Operating Life Deration
  9. Parameter Measurement Information
  10. Overview
  11. 10Functional Block Diagram
  12. 11Principles Of Operation (1394b Interface)
    1. 11.1 LLC Service Request
    2. 11.2 Status Transfer
    3. 11.3 Receive
    4. 11.4 Transmit
  13. 12Principles Of Operation (1394a-2000 Interface)
    1. 12.1 LLC Service Request
    2. 12.2 Status Transfer
    3. 12.3 Receive
    4. 12.4 Transmit
    5. 12.5 Interface Reset and Disable
  14. 13Applications, Implementation, and Layout
    1. 13.1 Known exceptions to functional specification (errata).
      1. 13.1.1 Errata # 1:Restore from Leaf Node (Nephew)
        1. 13.1.1.1 Detailed Description
        2. 13.1.1.2 Background
        3. 13.1.1.3 Workaround Proposal
        4. 13.1.1.4 Corrective Action
    2. 13.2 Application Information
      1. 13.2.1 Interoperability with earlier revisions of TSB41BA3
      2. 13.2.2 Internal Register Configuration
      3. 13.2.3 Feature Enhancements to revision F
        1. 13.2.3.1 Detect Loss of Descrambler Synchronization
          1. 13.2.3.1.1 Detect Loss of Descrambler Synchronization Advantages and Uses
        2. 13.2.3.2 Fast Retrain
          1. 13.2.3.2.1 Fast-Retrain Advantages and Uses
          2. 13.2.3.2.2 Fast-Retrain Backward Compatibility
        3. 13.2.3.3 Fast Power-On Re-connect
          1. 13.2.3.3.1 Fast Power-On Re-Connect Advantages and Uses
          2. 13.2.3.3.2 Fast Power-On Re-Connect Backward Compatibility
        4. 13.2.3.4 Fast Connection Tone Debounce
        5. 13.2.3.5 Programmable invalidCount
      4. 13.2.4 Power-Class Programming
      5. 13.2.5 Using The TSB41BA3F-EP With A 1394-1995 Or 1394a-2000 Link Layer
      6. 13.2.6 Power-Up Reset
      7. 13.2.7 Crystal Selection
      8. 13.2.8 Bus Reset
      9. 13.2.9 Designing With Powerpad™ Devices
  15. 14Device and Documentation Support
    1. 14.1 Tools and Software
    2. 14.2 Device Nomenclature
    3. 14.3 Documentation Support
    4. 14.4 サポート・リソース
    5. 14.5 Trademarks
    6. 14.6 静電気放電に関する注意事項
    7. 14.7 用語集
  16. 15Mechanical, Packaging, and Orderable Information
    1. 15.1 Packaging Information
    2. 15.2 Mechanical Data

パッケージ・オプション

メカニカル・データ(パッケージ|ピン)
サーマルパッド・メカニカル・データ
発注情報

LLC Service Request

To request access to the bus, to read or write a PHY register, or to send a link notification to PHY, the LLC sends a serial bit stream on the LREQ terminal as shown in Figure 11-2.

GUID-6E25A30F-EB85-421F-A354-F8D640527146-low.gifFigure 11-2 LREQ Request Stream

The length of the stream varies depending on the type of request as shown in Table 11-3.

Table 11-3 Request Stream Bit Length
REQUEST TYPENUMBER OF BITS
Bus request11
Read register request10
Write register request18
Link notification request6
PHY-link interface reset request6

Regardless of the type of request, a start bit of 1 is required at the beginning of the stream and a stop bit of 0 is required at the end of the stream. The second through fifth bits of the request stream indicate the type of the request. In the following descriptions, bit LR1 is the most significant and is transmitted first in the request bit stream. The LREQ terminal is normally low.

Table 11-4 shows the encoding for the request type.

Table 11-4 Request Type Encoding
LR1–LR4NAMEDESCRIPTION
0000ReservedReserved
0001Immed_ReqImmediate request. On detection of idle, the PHY arbitrates for the bus.
0010Next_EvenNext even request. The PHY arbitrates for the bus to send an asynchronous packet in the even fairness interval phase.
0011Next_OddNext odd request. The PHY arbitrates for the bus to send an asynchronous packet in the odd fairness interval phase.
0100CurrentCurrent request. The PHY arbitrates for the bus to send an asynchronous packet in the current fairness interval.
0101ReservedReserved
0110Isoch_Req_EvenIsochronous even request. The PHY arbitrates for the bus to send an isochronous packet in the even isochronous period.
0111Isoch_Req_OddIsochronous odd request. The PHY arbitrates for the bus to send an isochronous packet in the odd isochronous period.
1000Cyc_Start_ReqCycle start request. The PHY arbitrates for the bus to send a cycle start packet.
1001ReservedReserved
1010Reg_ReadRegister read request. The PHY returns the specified register contents through a status transfer.
1011Reg_WriteRegister write request. Write to the specified register in the PHY.
1100Isoch_Phase_EvenIsochronous phase even notification. The link reports to the PHY that:
1) A cycle start packet has been received.
2) The link has set the isochronous phase to even.
1101Isoch_Phase_OddIsochronous phase odd notification. The link reports to the PHY that:
1) A cycle start packet has been received.
2) The link has set the isochronous phase to odd.
1110Cycle_Start_DueCycle start due notification. The link reports to the PHY that a cycle start packet is due for reception.
1111ReservedReserved

For a bus request, the length of the LREQ bit stream is 11 bits as shown in Table 11-5.

Table 11-5 Bus Request
BIT(s)NAMEDESCRIPTION
0Start bitIndicates the beginning of the transfer (always 1)
1–4Request typeIndicates the type of bus request. See Table 11-4.
5Request formatIndicates the packet format to be used for packet transmission. See Table 11-6.
6–9Request speedIndicates the speed at which the link sends the data to the PHY. See Table 11-7 for the encoding of this field.
10Stop bitIndicates the end of the transfer (always 0). If bit 6 is 0, then this bit can be omitted.

Table 11-6 shows the 1-bit request format field used in bus requests.

Table 11-6 Bus Request Format Encoding
LR5DATA RATE
0Link does not request either Beta or legacy packet format for bus transmission
1Link requests Beta packet format for bus transmission

Table 11-7 shows the 4-bit request speed field used in bus requests.

Table 11-7 Bus Request Speed Encoding
LR6–LR9DATA RATE
0000S100
0001Reserved
0010S200
0011Reserved
0100S400
0101Reserved
0110S800
All OthersInvalid
Note:

The TSB41BA3F-EP accepts a bus request with an invalid speed code and processes the bus request normally. However, during packet transmission for such a request, the TSB41BA3F-EP ignores any data presented by the LLC and transmits a null packet.

For a read register request, the length of the LREQ bit stream is 10 bits as shown in Table 11-8.

Table 11-8 Read Register Request
BIT(s)NAMEDESCRIPTION
0Start bitIndicates the beginning of the transfer (always 1)
1–4Request typeA 1010 indicates this is a read register request.
5–8AddressIdentifies the address of the PHY register to be read
9Stop bitIndicates the end of the transfer (always 0)

For a write register request, the length of the LREQ bit stream is 18 bits as shown in Table 11-9.

Table 11-9 Write Register Request
BIT(s)NAMEDESCRIPTION
0Start bitIndicates the beginning of the transfer (always 1)
1–4Request typeA 1011 indicates this is a write register request.
5–8AddressIdentifies the address of the PHY register to be written
9–16DataGives the data that is to be written to the specified register address
17Stop bitIndicates the end of the transfer (always 0)

For a link notification request, the length of the LREQ bit stream is 6 bits as shown in Table 11-10.

Table 11-10 Link Notification Request
BIT(s)NAMEDESCRIPTION
0Start bitIndicates the beginning of the transfer (always 1)
1–4Request typeA 1100, 1101, or 1110 indicates this is a link notification request
5Stop bitIndicates the end of the transfer (always 0)

For fair or priority access, the LLC sends a bus request at least one clock after the PHY-LLC interface becomes idle. The PHY queues all bus requests and can queue one request of each type. If the LLC issues a different request of the same type, then the new request overwrites any nonserviced request of that type. On the receipt (CTL terminals are asserted to the receive state, 10b) of a packet, queued requests are not cleared by the PHY.

The cycle master node uses a cycle start request (Cyc_Start_Req) to send a cycle start message. After receiving or transmitting a cycle start message, the LLC can issue an isochronous bus request (IsoReq). The PHY clears an isochronous request only when the serial bus has been won.

To send an acknowledge packet, the LLC must issue an immediate bus request (Immed_Req) during the reception of the packet addressed to it. This is required in order to minimize the idle gap between the end of the received packet and the start of the transmitted acknowledge packet. As soon as the received packet ends, the PHY immediately grants control of the bus to the LLC. The LLC sends an acknowledgment to the sender unless the header CRC of the received packet is corrupted. In this case, the LLC does not transmit an acknowledge, but instead cancels the transmit operation and releases the interface immediately; the LLC must not use this grant to send another type of packet. After the interface is released the LLC can proceed with another request.

For write register requests, the PHY loads the specified data into the addressed register as soon as the request transfer is complete. For read register requests, the PHY returns the contents of the addressed register to the LLC at the next opportunity through a PHY status transfer. A write or read register request can be made at any time, including while a bus request is pending. Once a read register request is made, the PHY ignores further read register requests until the register contents are successfully transferred to the LLC. A bus reset does not clear a pending read register request.