SWRZ092B April   2021  – March 2022 IWR6843AOP

 

  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#03
    2.     MSS#10
    3.     MSS#11
    4.     MSS#12
    5.     MSS#13
    6.     MSS#14
    7.     MSS#16
    8.     MSS#17
    9.     MSS#18
    10.     MSS#19
    11.     MSS#20
    12.     MSS#21
    13.     MSS#22
    14.     MSS#23
    15.     MSS#24
    16.     MSS#25
    17.     MSS#26
    18.     MSS#27
    19.     MSS#28
    20.     MSS#29
    21.     MSS#30
    22.     MSS#31
    23.     MSS#32
    24.     MSS#33
    25.     MSS#34
    26.     MSS#35
    27.     MSS#36
    28.     MSS#37B
    29.     MSS#38A
    30.     MSS#39
    31.     MSS#40
    32.     MSS#41
    33.     MSS#42A
    34.     MSS#43A
    35.     MSS#44A
    36.     MSS#45
    37. 6.1 MSS#50
    38. 6.2 MSS#51
    39.     ANA#11B
    40.     ANA#12A
    41.     ANA#13B
    42.     ANA#14
    43.     ANA#16
    44.     ANA#17A
    45.     ANA#18B
    46.     ANA#19
    47.     ANA#20
    48.     ANA#22A
    49. 6.3 ANA#27A
    50.     ANA#30
    51.     ANA#31
    52.     DSS#01
    53.     DSS#02
    54.     DSS#03
    55.     DSS#05
    56.     DSS#07
    57.     PACKAGE#01
    58.     PACKAGE#02
  7. 7Trademarks
  8. 8Revision History

MSS#32

DMMGLBCTRL BUSY Flag Not Set When DMM Starts Receiving A Packet

Revision(s) Affected:

IWR6843AOP ES1.0 and IWR6843AOP ES2.0

Description:

The BUSY flag in the DMMGLBCTRL register should be set when the DMM starts receiving a packet or has data in its internal buffers. However, the BUSY flag (DMMGLBCTRL.24) may not get set when the DMM starts receiving a packet under the following condition:

  • The BUSY bit is set only after the packet has been received, de-serialized, and written to the internal buffers. It stays active while data is still in the DMM internal buffers. If the internal buffers are empty (meaning that no data needs to be written to the destination memory) then, the BUSY bit will be cleared.

Workaround(s):

Wait for a number of DMMCLK cycles (for example, 95 DMMCLK cycles) beyond the longest reception and deserialization time needed for a given packet size and DMM port configuration, before checking the status of the BUSY flag, and after the DMM ON/OFF bit field (DMMGLBCTRL.[3:0]) has been programmed to OFF.