SWRZ166 November   2024 AWR2944P

 

  1.   1
  2. 1Introduction
  3. 2Device Nomenclature
  4. 3Device Markings
  5. 4Advisory to Silicon Variant / Revision Map
  6. 5Known Design Exceptions to Functional Specifications
    1.     MSS#25
    2.     MSS#27
    3.     MSS#28
    4.     MSS#29
    5.     MSS#30
    6.     MSS#33
    7.     MSS#40
    8. 5.1  MSS#49
    9. 5.2  MSS#52
    10. 5.3  MSS#53
    11. 5.4  MSS#54
    12. 5.5  MSS#55
    13. 5.6  MSS#56
    14. 5.7  MSS#57
    15. 5.8  MSS#61
    16. 5.9  MSS#62
    17.     MSS#66
    18. 5.10 MSS#67
    19. 5.11 ANA#12A
    20.     ANA#37A
    21.     ANA#39
    22.     ANA#43
    23.     ANA#44
    24.     ANA#45
    25.     ANA#46
    26.     ANA#47
  7.   Trademarks
  8.   Revision History

MSS#57

Loss of data observed on Flush/Marker or completion of packet over MDO interface.

Revision(s) Affected:

AWR2944P, AWR2E44P

Description:

AWR2944P, AWR2E44P: Data frames sent over MDO discards the last 6 bytes at the end of the frame

It is observed that data transfer over the MDO having data_size = 6 get dropped. To ensure complete data gets transferred, the data size needs to adhere to 4byte and 8byte aligned data. If not done, a loss of the last 6 bytes of data on Flush/Marker trigger or completion of packet could be observed.

Data Flow: EDMA -> SNIFFER -> FIFO --> AGGREGATOR -> STM -> TPIU -> AURORA TX.

With Data transfer using MSS_TPCC to MDO_DSS_FIFO having data size of 6 bytes results in the 6 bytes getting dropped. STM module has cxstm500_axislvif_write block which samples data based on WSTRB. There is no case inside the STM which can handle 6 bytes of incoming data.

Design Limitation in STM module to handle 6 bytes of data.

1, 2, 4, 8 bytes of data get handled. But 6 bytes results in data getting dropped.

Workaround(s):

It is recommended to include 2 dummy bytes during transfer to make the WSTRB handle 8 bytes.