SWRZ062F September   2015  – December 2022 CC1310

 

  1.   CC1310 SimpleLink™ Ultra-Low-Power Sub-1 GHz Wireless MCU Silicon Revisions B, A
  2.   Trademarks
  3. 1Advisory Matrix
  4. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development Support-Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  5. 3Silicon Revision B Advisories
    1.     Advisory 02
    2.     Advisory 03
    3.     Advisory 04
    4.     Advisory 05
    5.     Advisory 06
    6.     Advisory 07
    7.     Advisory 08
    8.     Advisory 09
    9.     Advisory 10
    10.     Advisory 11
    11.     Advisory 12
    12.     Advisory 13
    13.     Advisory 14
    14.     Advisory 15
    15.     Advisory 16
    16.     Advisory 17
    17.     Advisory 18
    18.     Advisory 19
  6. 4Silicon Revision A Advisories
    1.     Advisory 01
  7. 5Revision History

Advisory 14

An Incorrect Value Might Be Written to the General-Purpose (GP) Timers MMRs (Memory Mapped Registers) When Simultaneously Accessing the AES (Advanced Encryption Standard) Engine from a Different Master

Revisions Affected:

A and B

Details:

When writing data to the GP Timer MMRs from one master while simultaneously accessing the AES modules from another master (read/write), an incorrect value might be captured in the GP Timer MMRs. In some cases, the incorrect value is replaced by the correct one after two clock cycles, but not always. No issue is seen when accessing the modules from the same master.

Workaround 1:

Avoid accesses to AES by other masters while writing to the GP Timer MMRs. This can be accomplished by acquiring the relevant semaphores (depending on drivers/stacks) before writing to the GP Timer.

Workaround 2:

Verify the value written to the GP Timer MMR by reading it back in software. Correct the value if necessary.