SWRZ075D May   2017  – December 2020 AWR1443

 

  1. 1Introduction
  2. 2Device Nomenclature
  3. 3Device Markings
  4. 4Usage Notes
    1. 4.1 MSS: SPI Speed in 3-Wire Mode Usage Note
  5. 5Advisory to Silicon Variant / Revision Map
  6. 6Known Design Exceptions to Functional Specifications
    1.     MSS#01
    2.     MSS#03A
    3.     MSS#04A
    4.     MSS#05A
    5.     MSS#06
    6.     MSS#07A
    7.     MSS#08
    8.     MSS#09
    9.     MSS#13
    10.     MSS#14
    11.     MSS#15
    12.     MSS#19
    13.     MSS#20
    14.     MSS#21A
    15.     MSS#22
    16.     MSS#23
    17.     MSS#24
    18.     MSS#25
    19.     MSS#26
    20.     MSS#27
    21.     MSS#28
    22.     MSS#29
    23.     MSS#30
    24.     MSS#31
    25.     MSS#33
    26.     MSS#35
    27.     MSS#37B
    28.     MSS#38A
    29.     MSS#39
    30.     MSS#40
    31.     MSS#43
    32.     MSS#44
    33.     MSS#45
    34.     ANA#01
    35.     ANA#02
    36.     ANA#03
    37.     ANA#04
    38.     ANA#06
    39.     ANA#08A
    40.     ANA#10A
    41.     ANA#11A
    42.     ANA#12A
    43.     ANA#13
    44.     ANA#15
    45.     ANA#16
    46.     ANA#17A
    47.     ANA#18B
    48.     ANA#20
    49.     ANA#21A
    50.     ANA#22A
    51.     ANA#24A
    52.     ANA#27
  7. 7Trademarks
  8. 8Revision History

MSS#40

Any EDMA Transfer That Spans ACCEL_MEM1 +ACCEL_MEM2 Memories of Hardware Accelerator May Result In Data Corruption Without Any Notification Of Error From The SoC

Revision(s) Affected:

AWR1443 ES1.0, AWR1443 ES2.0, and AWR1443 ES3.0

Description:

As per TPTC IP Spec, a Transfer request (TR) is supposed to access a single slave end point. ACCEL_MEM0/ACCEL_MEM1 memory banks of HWA are available via single slave point and ACCEL_MEM2/ ACCEL_MEM3 memory banks of HWA are available as another slave point (different from that of ACCEL_MEM0/ ACCEL_MEM1). Hence if a single TR is used to access a buffer spanning ACCEL_MEM1 and ACCEL_MEM2 memories of the HWA (i.e. a single buffer spanning 2 different slave points), the spec is not being adhered to. This errata is explicitly highlighting this spec requirement

Workaround(s):

Split the access into 2 TRs so that a single TR does not span ACCEL_MEM1 +ACCEL_MEM2. The 2 TRs can be chained.