SWRZ072B May   2017  – December 2020 AWR1642

 

  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#10
    2.     MSS#11
    3.     MSS#12
    4.     MSS#14
    5.     MSS#16
    6.     MSS#17
    7.     MSS#18
    8.     MSS#19
    9.     MSS#20
    10.     MSS#22
    11.     MSS#37B
    12.     MSS#38A
    13.     MSS#39
    14.     MSS#40
    15.     MSS#42
    16.     MSS#43
    17.     MSS#44
    18.     MSS#45
    19.     ANA#06
    20.     ANA#08A
    21.     ANA#09A
    22.     ANA#10A
    23.     ANA#11A
    24.     ANA#12A
    25.     ANA#15
    26.     ANA#16
    27.     ANA#17A
    28.     ANA#18B
    29.     ANA#20
    30.     ANA#21A
    31.     ANA#22A
    32.     ANA#24A
    33.     ANA#27
    34.     DSS#01
    35.     DSS#02
    36.     DSS#03
    37.     DSS#04
    38.     DSS#05
    39.     DSS#06
    40.     DSS#07
  7. 7Trademarks
  8. 8Revision History

MSS#39

The state of the MSS DMA is left pending and uncleared on any DMA MPU fault

Revision(s) Affected:

AWR1642 ES1.0 and AWR1642 ES2.0

Description:

The state of the MSS DMA is left pending and uncleared on any DMA MPU fault. The transfer that caused this MPU fault is left pending inside the DMA IP.

Any trigger on DMA REQ lines (could be caused by any module/IP that is hooked up to DMA in h/w) can re-trigger DMA to start executing the above pending transfer irrespective of whether that trigger is actually valid/enabled in DMA or that module/IP

Workaround(s):

For devices where the Boot ROM is executing the MSS DMA MPU Self tests. As part of application initialization, if the MSS DMA will be used, the following register field should be used to reset the MSS DMA IP so that the uncleared transfer is reset

  1. Write MSS_RCM:SOFTRST1[31:24] 0xAD
  2. Write MSS_RCM:SOFTRST1[31:24] 0x0

It is not recommended to use this configuration at any another instance other than that recommended here in this Errata.

On an actual Real time MPU Error, this error should be treated as a non-recoverable error and a warm reset should be issued to recover.