SPRZ536C September   2022  – June 2026 AM69 , AM69A , TDA4AH-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VH-Q1 , TDA4VP-Q1 , TDA4VPE-Q1

 

  1.   1
  2. 1Modules Affected
  3. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development-Support Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  4. 3Silicon Revision 1.0 Usage Notes and Advisories
    1. 3.1 Silicon Revision 1.0 Usage Notes
      1.      i2134
    2. 3.2 Silicon Revision 1.0 Advisories
      1.      i2049
      2.      i2062
      3.      i2063
      4.      i2064
      5.      i2065
      6.      i2079
      7.      i2087
      8.      i2097
      9.      i2102
      10.      i2103
      11.      i2120
      12.      i2134
      13.      i2137
      14.      i2146
      15.      i2157
      16.      i2159
      17.      i2160
      18.      i2161
      19.      i2163
      20.      i2166
      21.      i2177
      22.      i2189
      23.      i2190
      24.      i2196
      25.      i2197
      26.      i2205
      27.      i2215
      28.      i2216
      29.      i2219
      30.      i2232
      31.      i2234
      32.      i2242
      33.      i2244
      34.      i2249
      35.      i2253
      36.      i2271
      37.      i2272
      38.      i2278
      39.      i2279
      40.      i2310
      41.      i2311
      42.      i2312
      43.      i2320
      44.      i2326
      45.      i2330
      46.      i2351
      47.      i2362
      48.      i2366
      49.      i2371
      50.      i2372
      51.      i2378
      52.      i2381
      53.      i2383
      54.      i2399
      55.      i2401
      56.      i2409
      57.      i2413
      58.      i2414
      59.      i2415
      60.      i2419
      61.      i2422
      62.      i2424
      63.      i2431
      64.      i2435
      65.      i2436
      66.      i2437
      67.      i2449
      68.      i2459
      69.      i2482
  5.   Trademarks
  6.   Revision History

i2279

MCAN: Specification Update for dedicated Tx Buffers and Tx Queues configured with same Message ID

Details

The erratum updates the descriptions in Section 3.5.2 Dedicated Tx Buffers and 3.5.4 Tx Queue of the M_CAN User’s Manual related to message transmission from multiple dedicated Tx Buffers configured with the same Message ID.

Workaround

Workaround #1:

After writing the Tx messages with same Message ID to the Message RAM, request transmission of all these message concurrently by single write access to TXBAR. Make sure none of these messages have a pending Tx request before making the concurrent request.

Workaround #2:

Use the Tx FIFO instead of dedicated Tx Buffers (set bit MCAN_TXBC[30] TFQM = 0 to use Tx FIFO) for the transmission of several messages with the same Message ID in a specific order.