• Menu
  • Product
  • Email
  • PDF
  • Order now
  • CC1352P SimpleLink™ Wireless MCU Device Revision E

    • SWRZ076D July   2018  – December 2020 CC1352P

       

  • CONTENTS
  • SEARCH
  • CC1352P SimpleLink™ Wireless MCU Device Revision E
  1.   1
  2.   2
  3.   3
    1.     4
    2.     5
    3.     6
  4.   7
    1.     8
    2.     9
    3.     10
    4.     11
    5.     12
    6.     13
    7.     14
    8.     15
    9.     16
    10.     17
    11.     18
    12.     19
    13.     20
    14.     21
    15.     22
    16.     23
    17.     24
    18.     25
    19.     26
    20.     27
    21.     28
  5.   29
  6. IMPORTANT NOTICE
search No matches found.
  • Full reading width
    • Full reading width
    • Comfortable reading width
    • Expanded reading width
  • Card for each section
  • Card with all content

 

ERRATA

CC1352P SimpleLink™ Wireless MCU Device Revision E

Trademarks

SimpleLink and Texas Instruments are trademarks of Texas Instruments Incorporated.

Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries).

All trademarks are the property of their respective owners.

1 Advisories Matrix

Table 1-1 lists all advisories, modules affected, and the applicable silicon revisions.

Table 1-1 Advisories Matrix
MODULEDESCRIPTIONSILICON REVISIONS AFFECTED
E
RadioAdvisory Radio_01 — Proprietary radio modes: spurious emissions can affect regulatory complianceYes
RadioAdvisory Radio_02 — High-power PA operation at temperatures below -20°C may affect the 32-kHz crystal oscillatorYes
PowerAdvisory Power_03 — Increased voltage ripple at low supply voltages when DC/DC converter is enabledYes
PKAAdvisory PKA_01 — Public key accelerator (PKA) interrupt line is always high when module is enabled and PKA is idleYes
PKAAdvisory PKA_02 — Public key accelerator (PKA) RAM is not byte accessibleYes
I2CAdvisory I2C_01 — I2C module master status bit is set lateYes
I2SAdvisory I2S_01 — I2S bus faults are not reportedYes
CPUAdvisory CPU_01 — Arm® Errata #838869: Store immediate overlapping exception return operation might vector to incorrect interruptYes
CPUAdvisory CPU_02 — Arm® Errata #752770: Interrupted loads to SP can cause erroneous behaviorYes
CPUAdvisory CPU_03 — Arm® Errata #776924 VDIV or VSQRT instructions might not complete correctly when very short ISRs are usedYes
CPU, SystemAdvisory CPU_Sys_01 — The SysTick calibration value (register field CPU_SCS.STCR.TENMS) used to set up 10-ms periodic ticks is incorrect when the system CPU is running off divided down 48-MHz clockYes
SystemAdvisory Sys_01 — Device might boot into ROM serial bootloader when waking up from shutdownYes
System ControllerAdvisory SYSCTRL_01 — Resets occurring in a specific 2-MHz period during initial power up are incorrectly reportedYes
IO ControllerAdvisory IOC_01 — Limited number of DIOs available for the bootloader backdoorYes
SRAMAdvisory SRAM_01 — Reserved addresses within SRAM_MMR region alias into SRAM arrayYes
General-Purpose TimerAdvisory GPTM_01 — An incorrect value might be written to the general-purpose (GP) timers MMRs (memory mapped registers) when simultaneously accessing the PKA (public key accelerator) engine and/or the AES (advanced encryption standard) engine from a different masterYes
ADCAdvisory ADC_01 — Periodic ADC trigger at 200 kHz rate can be ignored when XOSC_HF is turned on or offYes
ADCAdvisory ADC_02 — ADC samples can be delayed by 2 or 14 clock cycles (24 MHz) when XOSC_HF is turned on or off, resulting in sample jitterYes
ADCAdvisory ADC_03 — Software can hang when reading the ADC FIFO if a single manual ADC trigger is generated immediately after the ADC is enabledYes
ADCAdvisory ADC_04 — Misbehaving ADC FIFO status flags in the AUX_ANAIF:ADCFIFOSTAT register (OVERFLOW, FULL, ALMOST_FULL, and EMPTY)Yes
ADCAdvisory ADC_05 — Writing any value to AUX_ANAIF:ADCTRIG.START will create an ADC triggerYes

2 Nomenclature, Package Symbolization, and Revision Identification

2.1 Device and Development Support-Tool Nomenclature

To designate the stages in the product development cycle, Texas Instruments™ assigns prefixes to the part numbers of all devices and support tools. Each device has one of three prefixes: X, P, or null (for example, XCC1352P). Texas Instruments recommends two of three possible prefix designators for its support tools: TMDX and TMDS. These prefixes represent evolutionary stages of product development from engineering prototypes (X/TMDX) through fully qualified production devices/tools (null/TMDS).

Device development evolutionary flow:

    XExperimental device that is not necessarily representative of the final device's electrical specifications and may not use production assembly flow.
    PPrototype device that is not necessarily the final silicon die and may not necessarily meet final electrical specifications.
    nullProduction version of the silicon die that is fully qualified.

Support tool development evolutionary flow:

    TMDXDevelopment-support product that has not yet completed Texas Instruments internal qualification testing.
    TMDSFully-qualified development-support product.

X and P devices and TMDX development-support tools are shipped against the following disclaimer:

"Developmental product is intended for internal evaluation purposes."

Production devices and TMDS development-support tools have been characterized fully, and the quality and reliability of the device have been demonstrated fully. TI's standard warranty applies.

Predictions show that prototype devices (X or P) have a greater failure rate than the standard production devices. Texas Instruments recommends that these devices not be used in any production system because their expected end-use failure rate still is undefined. Only qualified production devices are to be used.

2.2 Devices Supported

This document supports the following device:

  • CC1352P

2.3 Package Symbolization and Revision Identification

Figure 2-1 and Table 2-1 describe package symbolization and the device revision code.

GUID-7C75D375-6EA9-4369-9998-0B38D340B5E2-low.gif Figure 2-1 Package Symbolization for Silicon Revision E
Table 2-1 Revision Identification
DEVICE REVISION CODESILICON REVISION
EPG2.1

3 Advisories

Radio_01

Proprietary radio modes: spurious emissions can affect regulatory compliance

Revisions Affected:

Revision E and earlier

Details:

When device internal load capacitors are used with the external 48-MHz crystal, energy couples from the crystal oscillator circuit to the RF output. This coupling causes spurious emissions at N × 48 MHz from carrier frequency. This includes, but is not limited to, the frequency bands supported by the device covered by the following regulations:

When using the +14-dBm RF power amplifier

  • ARIB T-108 (Japan)

When using the +20-dBm RF power amplifier

  • 470- to 510-MHz (China) Band
  • FCC CFR47 Part 15 (US)
  • ETSI EN 300 220 (Europe)
  • ETSI EN 300 328 (Europe)
  • ETSI EN 300 440 (Europe)

Workaround:

For compliance with affected standards, external load capacitors might be needed for the 48-MHz crystal to reduce spurious emissions. Internal capacitors (default 7-pF connected capacitance) must then be disconnected internally.

This workaround is implemented by defining the following symbols in the included customer configuration file (ccfg.c) available in all Software Development Kit (SDK) examples:
#define SET_CCFG_MODE_CONF_XOSC_CAPARRAY_DELTA -128
#define SET_CCFG_MODE_CONF_XOSC_CAP_MOD 0

 

Texas Instruments

© Copyright 1995-2025 Texas Instruments Incorporated. All rights reserved.
Submit documentation feedback | IMPORTANT NOTICE | Trademarks | Privacy policy | Cookie policy | Terms of use | Terms of sale