SWRZ102B November   2021  – October 2023 AWR2944

PRODUCTION DATA  

  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#46
    9. 5.2  MSS#48
    10. 5.3  MSS#49
    11. 5.4  MSS#52
    12. 5.5  MSS#53
    13. 5.6  MSS#54
    14. 5.7  MSS#55
    15. 5.8  MSS#56
    16. 5.9  MSS#57
    17. 5.10 MSS#58
    18. 5.11 MSS#59
    19. 5.12 MSS#60
    20. 5.13 MSS#61
    21. 5.14 MSS#62
    22. 5.15 ANA#12A
    23.     ANA#32A
    24.     ANA#33A
    25.     ANA#34A
    26.     ANA#35A
    27.     ANA#36
    28.     ANA#37A
    29.     ANA#38A
    30.     ANA#39
    31.     ANA#43
    32.     ANA#44
    33.     ANA#45
    34.     ANA#46
    35.     ANA#47
  7.   Trademarks
  8.   Revision History

5.5 MSS#53

Incorrect behavior seen when context switch happens in the last parameter-set in the Hardware Accelerator (HWA 2.1)

Revision(s) Affected:

AWR294x ES2.0 Only

Description:

At the end of the last parameter-set of the last loop in low-priority context, if a context-switch happens to high priority, then an incorrect behavior is observed when returning back to low-priority. This incorrect behavior can manifest itself as a fresh (unintended) re-start of the low-priority loop once completed. Following are the erroneous conditions:

  • CONTEXT_SW_EN or FORCED_CONTEXT_SW_EN set in the last paramset of the low priority thread.
Similarly, forced context switch (FORCED_CONTEXT_SW_EN) shouldn’t be enabled in last paramset of high priority thread .

Workaround(s):

It is recommended to not enable context switch in the last parameter-set of the above mentioned conditions. In case, the last parameter-set has to have context switch enabled, user could add a dummy parameter-set with context switch disabled as the last parameter-set.