JAJSH69B January   2018  – November 2019 TCAN4550-Q1

PRODUCTION DATA.  

  1. 特長
  2. アプリケーション
  3. 概要
    1.     Device Images
      1.      概略回路図、MUC から CLKIN
      2.      概略回路図、水晶振動子
  4. 改訂履歴
  5. 概要(続き)
  6. Pin Configuration and Functions
    1.     Pin Functions
  7. Specifications
    1. 7.1  Absolute Maximum Ratings
    2. 7.2  ESD Ratings
    3. 7.3  ESD Ratings, IEC ESD and ISO Transient Specification
    4. 7.4  Recommended Operating Conditions
    5. 7.5  Thermal Information
    6. 7.6  Supply Characteristics
    7. 7.7  Electrical Characteristics
    8. 7.8  Timing Requirements
    9. 7.9  Switching Characteristics
    10. 7.10 Typical Characteristics
  8. Parameter Measurement Information
  9. Detailed Description
    1. 9.1 Overview
    2. 9.2 Functional Block Diagram
    3. 9.3 Feature Description
      1. 9.3.1  VSUP Pin
      2. 9.3.2  VIO Pin
      3. 9.3.3  VCCOUT Pin
      4. 9.3.4  GND
      5. 9.3.5  INH Pin
      6. 9.3.6  WAKE Pin
      7. 9.3.7  FLTR Pin
      8. 9.3.8  RST Pin
      9. 9.3.9  OSC1 and OSC2 Pins
      10. 9.3.10 nWKRQ Pin
      11. 9.3.11 nINT Interrupt Pin
      12. 9.3.12 GPIO1 Pin
      13. 9.3.13 GPO2 Pin
      14. 9.3.14 CANH and CANL Bus Pins
    4. 9.4 Device Functional Modes
      1. 9.4.1 Normal Mode
      2. 9.4.2 Standby Mode
      3. 9.4.3 Sleep Mode
        1. 9.4.3.1 Bus Wake via RXD_INT Request (BWRR) in Sleep Mode
        2. 9.4.3.2 Local Wake Up (LWU) via WAKE Input Terminal
      4. 9.4.4 Test Mode
      5. 9.4.5 Failsafe Feature
      6. 9.4.6 Protection Features
        1. 9.4.6.1 Watchdog Function
        2. 9.4.6.2 Driver and Receiver Function
        3. 9.4.6.3 Floating Terminals
        4. 9.4.6.4 TXD_INT Dominant Timeout (DTO)
        5. 9.4.6.5 CAN Bus Short Circuit Current Limiting
        6. 9.4.6.6 Thermal Shutdown
        7. 9.4.6.7 Under Voltage Lockout (UVLO) and Unpowered Device
          1. 9.4.6.7.1 UVSUP and UVCCOUT
          2. 9.4.6.7.2 UVIO
          3. 9.4.6.7.3 Fault and M_CAN Core Behavior:
      7. 9.4.7 CAN FD
    5. 9.5 Programming
      1. 9.5.1 SPI Communication
        1. 9.5.1.1 Chip Select Not (nCS):
        2. 9.5.1.2 SPI Clock Input (SCLK):
        3. 9.5.1.3 SPI Data Input (SDI):
        4. 9.5.1.4 SPI Data Output (SDO):
      2. 9.5.2 Register Descriptions
    6. 9.6 Register Maps
      1. 9.6.1 Device ID and Interrupt/Diagnostic Flag Registers: 16'h0000 to 16'h002F
        1. 9.6.1.1 DEVICE_ID1[31:0] (address = h0000) [reset = h4E414354]
          1. Table 10. Device ID Field Descriptions
        2. 9.6.1.2 DEVICE_ID2[31:0] (address = h0004) [reset = h30353534]
          1. Table 11. Device ID Field Descriptions
        3. 9.6.1.3 Revision (address = h0008) [reset = h00110201]
          1. Table 12. Revision Field Descriptions
        4. 9.6.1.4 Status (address = h000C) [reset = h0000000U]
          1. Table 13. Status Field Descriptions
      2. 9.6.2 Device Configuration Registers: 16'h0800 to 16'h08FF
        1. 9.6.2.1 Modes of Operation and Pin Configuration Registers (address = h0800) [reset = hC8000468]
          1. Table 15. Modes of Operation and Pin Configuration Registers Field Descriptions
        2. 9.6.2.2 Timestamp Prescalar (address = h0804) [reset = h00000002]
          1. Table 16. EMC Enhancement and Timestamp Prescalar Field Descriptions
        3. 9.6.2.3 Test Register and Scratch Pad (address = h0808) [reset = h00000000]
          1. Table 17. Test and Scratch Pad Register Field Descriptions
        4. 9.6.2.4 Test Register (address = h080C) [reset = h00000000]
          1. Table 18. Test Register Field Descriptions
      3. 9.6.3 Interrupt/Diagnostic Flag and Enable Flag Registers: 16'h0820/0824 and 16'h0830
        1. 9.6.3.1 Interrupts (address = h0820) [reset = h00100000]
          1. Table 19. Interrupts Field Descriptions
        2. 9.6.3.2 MCAN Interrupts (address = h0824) [reset = h00000000]
          1. Table 20. MCAN Interrupts Field Descriptions
        3. 9.6.3.3 Interrupt Enables (address = h0830 ) [reset = hFFFFFFFF]
          1. Table 21. Interrupt Enables Field Descriptions
      4. 9.6.4 CAN FD Register Set: 16'h1000 to 16'h10FF
        1. 9.6.4.1  Core Release Register (address = h1000) [reset = hrrrddddd]
          1. Table 25. Core Release Register Field Descriptions
        2. 9.6.4.2  Endian Register (address = h1004) [reset = h87654321]
          1. Table 26. Endian Register Field Descriptions
        3. 9.6.4.3  Customer Register (address = h1008) [reset = h00000000]
          1. Table 27. Customer Register Field Descriptions
        4. 9.6.4.4  Data Bit Timing & Prescaler (address = h100C) [reset = h0000A33]
          1. Table 28. Data Bit Timing & Prescaler Field Descriptions
        5. 9.6.4.5  Test Register (address = h1010 ) [reset = h00000000]
          1. Table 29. Test Register Field Descriptions
        6. 9.6.4.6  RAM Watchdog (address = h1014) [reset = h00000000]
          1. Table 30. RAM Watchdog Field Descriptions
        7. 9.6.4.7  Control Register (address = h1018) [reset = 0000 0019]
          1. Table 31. Control Register Field Descriptions
        8. 9.6.4.8  Nominal Bit Timing & Prescaler Register (address = h101C) [reset = h06000A03]
          1. Table 32. Nominal Bit Timing & Prescaler Register Field Descriptions
        9. 9.6.4.9  Timestamp Counter Configuration (address = h1020) [reset = h00000000]
          1. Table 33. Timestamp Counter Configuration Descriptions
        10. 9.6.4.10 Timestamp Counter Value (address = h1024) [reset = h00000000]
          1. Table 34. Timestamp Counter Value Field Descriptions
        11. 9.6.4.11 Timeout Counter Configuration (address = h1028) [reset = hFFFF0000]
          1. Table 35. Timeout Counter Configuration Field Descriptions
        12. 9.6.4.12 Timeout Counter Value (address = h102C) [reset = h0000FFFF]
          1. Table 36. Timeout Counter Value Field Descriptions
        13. 9.6.4.13 Reserved (address = h1030 - h103C) [reset = h00000000]
          1. Table 37. Reserved Field Descriptions
        14. 9.6.4.14 Error Counter Register (address = h1040) [reset = h00000000]
          1. Table 38. Error Counter Register Field Descriptions
        15. 9.6.4.15 Protocol Status Register (address = h1044) [reset = h00000707]
          1. Table 39. Protocol Status Register Field Descriptions
        16. 9.6.4.16 Transmitter Delay Compensation Register (address = h1048) [reset = h00000000]
          1. Table 40. Transmitter Delay Compensation Register Field Descriptions
        17. 9.6.4.17 Reserved (address = h104C) [reset = h00000000]
          1. Table 41. Reserved Field Descriptions
        18. 9.6.4.18 Interrupt Register (address = h1050) [reset = h00000000]
          1. Table 42. Interrupt Register Field Descriptions
        19. 9.6.4.19 Interrupt Enable (address = h1054) [reset = h00000000]
          1. Table 43. Interrupt Enable Field Descriptions
        20. 9.6.4.20 Interrupt Line Select (address = h1058) [reset = h00000000]
          1. Table 44. Interrupt Line Select Field Descriptions
        21. 9.6.4.21 Interrupt Line Enable (address = h105C) [reset = h00000000]
          1. Table 45. Interrupt Line Enable Field Descriptions
        22. 9.6.4.22 Reserved (address = h1060 - h107C) [reset = h00000000]
          1. Table 46. Reserved Field Descriptions
        23. 9.6.4.23 Global Filter Configuration (address = h1080) [reset = h00000000]
          1. Table 47. Global Filter Configuration Field Descriptions
        24. 9.6.4.24 Standard ID Filter Configuration (address = h1084) [reset = h00000000]
          1. Table 48. Standard ID Filter Configuration Field Descriptions
        25. 9.6.4.25 Extended ID Filter Configuration (address = h1088) [reset = h00000000]
          1. Table 49. Extended ID Filter Configuration Field Descriptions
        26. 9.6.4.26 Reserved (address = h108C) [reset = h00000000]
          1. Table 50. Reserved Field Descriptions
        27. 9.6.4.27 Extended ID AND Mask (address = h1090) [reset = h1FFFFFFF]
          1. Table 51. Extended ID AND Mask Field Descriptions
        28. 9.6.4.28 High Priority Message Status (address = h1094) [reset = h00000000]
          1. Table 52. High Priority Message Status Field Descriptions
        29. 9.6.4.29 New Data 1 (address = h1098) [reset = h00000000]
          1. Table 53. New Data 1 Field Descriptions
        30. 9.6.4.30 New Data 2 (address = h109C) [reset = h00000000]
          1. Table 54. New Data 2 Field Descriptions
        31. 9.6.4.31 Rx FIFO 0 Configuration (address = h10A0) [reset = h00000000]
          1. Table 55. Rx FIFO 0 Configuration Field Descriptions
        32. 9.6.4.32 Rx FIFO 0 Status (address = h10A4) [reset = h00000000]
          1. Table 56. Rx FIFO 0 Status Field Descriptions
        33. 9.6.4.33 Rx FIFO 0 Acknowledge (address = h10A8) [reset = h00000000]
          1. Table 57. Rx FIFO 0 Acknowledge Field Descriptions
        34. 9.6.4.34 Rx Buffer Configuration (address = h10AC) [reset = h00000000]
          1. Table 58. Rx Buffer Configuration Field Descriptions
        35. 9.6.4.35 Rx FIFO 1 Configuration (address = h10B0) [reset = h00000000]
          1. Table 59. Rx FIFO 1 Configuration Field Descriptions
        36. 9.6.4.36 Rx FIFO 1 Status (address = h10B4) [reset = h00000000]
          1. Table 60. Rx FIFO 1 Status Field Descriptions
        37. 9.6.4.37 Rx FIFO 1 Acknowledge (address = h10B8) [reset = h00000000]
          1. Table 61. Rx FIFO 1 Acknowledge Field Descriptions
        38. 9.6.4.38 Rx Buffer/FIFO Element Size Configuration (address = h10BC) [reset = h00000000]
          1. Table 62. Rx Buffer/FIFO Element Size Configuration Field Descriptions
        39. 9.6.4.39 Tx Buffer Configuration (address = h10C0) [reset = h00000000]
          1. Table 63. Tx Buffer Configuration Field Descriptions
        40. 9.6.4.40 Tx FIFO/Queue Status (address = h10C4) [reset = h00000000]
          1. Table 64. Tx FIFO/Queue Status Field Descriptions
        41. 9.6.4.41 Tx Buffer Element Size Configuration (address = h10C8) [reset = h00000000]
          1. Table 65. Tx Buffer Element Size Configuration Field Descriptions
        42. 9.6.4.42 Tx Buffer Request Pending (address = h10CC) [reset = h00000000]
          1. Table 66. Tx Buffer Request Pending Field Descriptions
        43. 9.6.4.43 Tx Buffer Add Request (address = h10D0) [reset = h00000000]
          1. Table 67.   Tx Buffer Add Request Field Descriptions
          2. 9.6.4.43.1  Tx Buffer Cancellation Request (address = h10D4 [reset = h00000000]
            1. Table 68. Tx Buffer Cancellation Request Field Descriptions
          3. 9.6.4.43.2  Tx Buffer Add Request Transmission Occurred (address = h10D8) [reset = h00000000]
            1. Table 69. Tx Buffer Add Request Transmission Occurred Field Descriptions
          4. 9.6.4.43.3  Tx Buffer Cancellation Finished (address = h10DC) [reset = h00000000]
            1. Table 70. Tx Buffer Cancellation Finished Field Descriptions
          5. 9.6.4.43.4  Tx Buffer Transmission Interrupt Enable (address = h10E0) [reset = h00000000]
            1. Table 71. Tx Buffer Transmission Interrupt Enable Field Descriptions
          6. 9.6.4.43.5  Tx Buffer Cancellation Finished Interrupt Enable (address = h10E4) [reset = h00000000]
            1. Table 72. Tx Buffer Cancellation Finished Interrupt Enable Field Descriptions
          7. 9.6.4.43.6  Reserved (address = h10E8) [reset = h00000000]
            1. Table 73. Reserved Field Descriptions
          8. 9.6.4.43.7  Reserved (address = h10EC) [reset = h00000000]
            1. Table 74. Reserved Field Descriptions
          9. 9.6.4.43.8  Tx Event FIFO Configuration (address = h10F0) [reset = h00000000]
            1. Table 75. Tx Event FIFO Configuration Field Descriptions
          10. 9.6.4.43.9  Tx Event FIFO Status (address = h10F4) [reset = h00000000]
            1. Table 76. Tx Event FIFO Status Field Descriptions
          11. 9.6.4.43.10 Tx Event FIFO Acknowledge (address = h10F8) [reset = h00000000]
            1. Table 77. Tx Event FIFO Acknowledge Field Descriptions
          12. 9.6.4.43.11 Reserved (address = h10FC) [reset = h00000000]
            1. Table 78. Reserved Field Descriptions
  10. 10Application and Implementation
    1. 10.1 Application Design Consideration
      1. 10.1.1 Crystal and Clock Input Requirements
      2. 10.1.2 Bus Loading, Length and Number of Nodes
      3. 10.1.3 CAN Termination
        1. 10.1.3.1 Termination
        2. 10.1.3.2 CAN Bus Biasing
      4. 10.1.4 INH Brownout Behavior
    2. 10.2 Typical Application
      1. 10.2.1 Detailed Requirements
      2. 10.2.2 Detailed Design Procedures
      3. 10.2.3 Application Curves
  11. 11Power Supply Recommendations
  12. 12Layout
    1. 12.1 Layout Guidelines
    2. 12.2 Layout Example
  13. 13デバイスおよびドキュメントのサポート
    1. 13.1 ドキュメントのサポート
      1. 13.1.1 関連資料
        1. 13.1.1.1 CAN トランシーバの物理層の標準
        2. 13.1.1.2 EMC要件
        3. 13.1.1.3 準拠テストの要件
        4. 13.1.1.4 サポート・ドキュメント
    2. 13.2 ドキュメントの更新通知を受け取る方法
    3. 13.3 サポート・リソース
    4. 13.4 商標
    5. 13.5 静電気放電に関する注意事項
    6. 13.6 Glossary
  14. 14メカニカル、パッケージ、および注文情報

パッケージ・オプション

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

Bus Wake via RXD_INT Request (BWRR) in Sleep Mode

As the TCAN4550-Q1 supports low power sleep mode and uses a wake up from the CAN bus mechanism called bus wake via RXD_INT Request (BWRR). Once this pattern is received, the TCAN4550-Q1 automatically switches to standby mode and inserts an interrupt onto the nINT and nWKRQ pins to indicate to a host microprocessor that the bus is active, and it should wake up and service the TCAN4550-Q1. The low power receiver and bus monitor are enabled in sleep mode to allow for RXD_INT Wake Requests via the CAN bus. A wake up request is output to the internal RXD_INT (driven low) as shown in Figure 25. The wake logic monitors RXD_INT for transitions (high to low) and reactivate the device to standby mode based on the RXD_INT Wake Request. The CAN bus terminals are weakly pulled to GND during this mode, see Figure 4.

These devices use the wake up pattern (WUP) from ISO 11898-2:2016 to qualify bus traffic into a request to wake the host microprocessor. The bus wake request is signaled to the integrated CAN FD controller by a falling edge and low corresponding to a “filtered” bus dominant on the RXD_INT terminal (BWRR).

The wake up pattern (WUP) consists of

  • A filtered dominant bus of at least tWK_FILTER followed by
  • A filtered recessive bus time of at least tWK_FILTER followed by
  • A second filtered dominant bus time of at least tWK_FILTER

Once the WUP is detected, the device starts issuing wake up requests (BWRR) on the RXD_INT signal every time a filtered dominant time is received from the bus. The first filtered dominant initiates the WUP and the bus monitor is now waiting on a filtered recessive, other bus traffic does not reset the bus monitor. Once a filtered recessive is received, the bus monitor is now waiting on a filtered dominant and again, other bus traffic does not reset the bus monitor. Immediately upon receiving of the second filtered dominant the bus monitor recognizes the WUP and transition to BWRR output. Immediately upon verification receiving a WUP the device transitions the bus monitor into BWRR mode, and indicates all filtered dominant bus times on the RXD_INT internal signal by driving it low for the dominant bus time that is in excess of tWK_FILTER, thus the RXD_INT output during BWRR matches the classical 8 pin CAN devices that used the single filtered dominant on the bus as the wake up request mechanism from ISO 11898-2:2016.

For a dominant or recessive to be considered “filtered”, the bus must be in that state for more than tWK_FILTER time. Due to variability in the tWK_FILTER the following scenarios are applicable.

  • Bus state times less than tWK_FILTER(MIN) are never detected as part of a WUP, and thus no BWRR is generated.
  • Bus state times between tWK_FILTER(MIN) and tWK_FILTER(MAX) may be detected as part of a WUP and a BWRR may be generated.
  • Bus state times more than tWK_FILTER(MAX) is always detected as part of a WUP, and thus, a BWRR is always be generated.

See Figure 24 for the timing diagram of the WUP.

The pattern and tWK_FILTER time used for the WUP and BWRR prevents noise and bus stuck dominant faults from causing false wake requests while allowing any CAN or CAN FD message to initiate a BWRR. If the device is switched to normal mode or an under voltage event occurs on VCC the BWRR is lost. The WUP pattern must take place within the tWK_TIMEOUT time otherwise the device is in a state waiting for the next recessive and then a valid WUP pattern.

TCAN4550-Q1 sllsez5_wake_up_patter_WUP_and_bus_.gifFigure 24. Wake Up Pattern (WUP) and Bus Wake via RXD_INT Request (BWRR)
TCAN4550-Q1 sllsez5_example_timing_diagram_with.gifFigure 25. Example timing diagram with TXD_INT DTO