Start your design with the fully programmable FCC, IC/ISED, ETSI/CE, MIC, and SRRC certified wireless
microcontroller (MCU) module with built-in dual-band Wi-Fi connectivity. The modules integrate the 40-MHz
crystal, 32.768-kHz RTC clock, 32Mb SPI serial flash, RF filters, diplexer, and passive components.
The SimpleLink™ CC3235MODx module is available in two variants:
•CC3235MODS includes 256KB of RAM, IoT networking security, device identity and keys, and MCU-level
security features such as file system encryption, user IP (MCU image) encryption, secure boot, and debug
security.
•CC3235MODSF builds on the CC3235MODS and integrates a user-dedicated 1MB of executable flash in
addition to the 256KB of RAM.
The SimpleLink™ CC3235MODAx module is available in two variants:
•CC3235MODAS includes 256KB of RAM, IoT networking security, device identity and keys, and MCU-level
security features such as file system encryption, user IP (MCU image) encryption, secure boot, and debug
security.
•CC3235MODASF builds on the CC3235MODAS and integrates a user-dedicated 1MB of executable flash in
addition to the 256KB of RAM.
Created for IoT, the SimpleLink™ Wi-Fi® CC3235MODx and CC3235MODAx module family from Texas
Instruments is a wireless module that integrates two physically separated on-chip MCUs.
•Application processor— Arm® Cortex®-M4 MCU with a user-dedicated 256KB of RAM and an optional 1MB
of executable flash.
•Network processor to run all Wi-Fi and Internet logical layers. This ROM-based subsystem completely
offloads the host MCU and includes an 802.11 a/b/g/n dual-band 2.4-GHz and 5-GHz radio, baseband, and
MAC with a powerful hardware cryptography engine.
This generation introduces new capabilities that further simplify the connectivity of things to the Internet. The
main new features include:
•802.11a/b/g/n: 2.4-GHz and 5-GHz support
•2.4-GHz coexistence with Bluetooth ® low energy radio
•Antenna diversity
•Enhanced security with FIPS 140-2 Level 1 validated IC inside: certification.
•Wi-Fi Alliance® certified for IoT applications with low-power capabilities and more
•Hostless mode for offloading template packet transmissions
•Improved fast scan
The CC3235MODx and CC3235MODAx device family is part of the SimpleLink MCU platform—a common,
easy-to-use development environment based on a single-core software development kit (SDK) with a rich tool
set and reference designs. The E2E™ support forums support Wi-Fi, Bluetooth low energy, Sub-1 GHz, and host
MCUs. For more information, visit www.ti.com/simplelink or www.ti.com/simplelinkwifi.
For information about other devices in this family of products or related products see the links below.
www.ti.com
The SimpleLink™ MCU
Portfolio
SimpleLink™ Wi-Fi
®
Family
BoosterPack™ Plug-In
Modules
Reference Designs for
CC3200, CC3220, and
CC3235 Modules
SimpleLink™ Wi-Fi
®
CC3235 SDK
offers a single development environment that delivers flexible hardware, software
and tool options for customers developing wired and wireless applications. With 100
percent code reuse across host MCUs, Wi-Fi®, Bluetooth® low energy, Sub-1GHz
devices and more, choose the MCU or connectivity standard that fits your design. A
one-time investment with the SimpleLink software development kit (SDK) allows you
to reuse often, opening the door to create unlimited applications.
The SimpleLink Wi-Fi Family offers several Internet-on-a chip solutions, which
address the need of battery operated, security enabled products. Texas instruments
offers a single chip wireless microcontroller and a wireless network processor which
can be paired with any MCU, to allow developers to design new wi-fi products, or
upgrade existing products with wi-fi capabilities.
BoosterPack™ Plug-In Modules extend the functionality of TI LaunchPad Kit.
Application specific BoosterPack Plug in modules allow you to explore a broad
range of applications, including capacitive touch, wireless sensing, LED Lighting
control, and more. Stack multiple BoosterPack modules onto a single LaunchPad kit
to further enhance the functionality of your design.
TI Designs Reference Design Library is a robust reference design library spanning
analog, embedded processor and connectivity. Created by TI experts to help you
jump start your system design, all TI Designs include schematic or block diagrams,
BOMs and design files to speed your time to market.
The SDK contains drivers for the CC3235 programmable MCU, sample applications,
and documentation required to start development with CC3235x solutions.
12JTAG_TDII/O16JTAG TDI input. Leave unconnected if not used on product
13FLASH_SPI_MISOI–External serial flash programming: SPI data in
14FLASH_SPI_nCS_INI–External serial flash programming: SPI chip select (active low)
15FLASH_SPI_CLKI–External serial flash programming: SPI clock
16GND––Ground
17FLASH_SPI_MOSIO–External serial flash programming: SPI data out
18JTAG_TDOI/O17JTAG TDO output. Leave unconnected if not used on product
(2)
19GPIO28I/O18GPIO
20NC––No Connect
21JTAG_TCKI/O19
JTAG TCK input. Leave unconnected if not used on product.
pulldown resistor is tied to this pin.
22JTAG_TMSI/O20JTAG TMS input. Leave unconnected if not used on product.
23SOP2–21
24SOP1–34
An internal 100-kΩ pulldown resistor is tied to this SOP pin. An external 10-kΩ resistor is
required to pull this pin high. See Section 9.11.1 for SOP[2:0] configuration modes.
An internal 100-kΩ pulldown resistor is tied to this SOP pin. An external 10-kΩ resistor is
required to pull this pin high. See Section 9.11.1 for SOP[2:0] configuration modes.
An internal 100-kΩ pulldown resistor is tied to this SOP pin. An external 10-kΩ resistor is
required to pull this pin high. See Section 9.11.1 for SOP[2:0] configuration modes.
35nRESETI32There is an internal, 100-kΩ pullup resistor option from the nRESET pin to
VBAT_RESET. Note: VBAT_RESET is not connected to VBAT1 or VBAT2 within the
module. The following connection schemes are recommended:
•Connect nRESET to a switch, external controller, or host, only if nRESET will be in a
defined state under all operating conditions. Leave VBAT_RESET unconnected to
36VBAT_RESET–37
save power.
•If nRESET cannot be in a defined state under all operating conditions, connect
VBAT_RESET to the main module power supply (VBAT1 and VBAT2). Due to the
internal pullup resistor a leakage current of 3.3 V / 100 kΩ is expected.
37VBAT1Power39Power supply for the module, must be connected to battery (2.3 V to 3.6 V)
38GND––Ground
39NC–47No Connect
40VBAT2Power10, 44, 54Power supply for the module, must be connected to battery (2.3 V to 3.6 V)
(1)I = input; O = output; I/O = bidirectional
(2)For pin multiplexing details, see Table 7-1.
TYPE
(1)
CC3235 DEVICE PIN
NO.
MODULE PIN DESCRIPTION
The module makes extensive use of pin multiplexing to accommodate the large number of peripheral functions in the smallest possible package. To
achieve this configuration, pin multiplexing is controlled using a combination of hardware configuration (at module reset) and register control.
The board and software designers are responsible for the proper pin multiplexing configuration. Hardware does not ensure that the proper pin
multiplexing options are selected for the peripherals or interface mode used. Table 7-1 describes the general pin attributes and presents an overview of
pin multiplexing. All pin multiplexing options are configurable using the pin MUX registers. The following special considerations apply:
•All I/Os support drive strengths of 2, 4, and 6 mA. Drive strength is individually configurable for each pin.
•All I/Os support 10-µA pullup and pulldown resistors.
•By default, all I/Os float in the Hibernate state. However, the default state can be changed by SW.
If an external device drives a positive voltage to the signal pads and the CC3235MODx or CC3235MODAx module is not powered, DC is
drawn from the other device. If the drive strength of the external device is adequate, an unintentional wakeup and boot of the CC3235MODx or
CC3235MODAx module can occur. To prevent current draw, TI recommends any one of the following conditions:
•All devices interfaced to the CC3235MODx and CC3235MODAx module must be powered from the same power rail as the chip.
•Use level shifters between the device and any external devices fed from other independent rails.
•The nRESET pin of the CC3235MODx and CC3235MODAx module must be held low until the VBAT supply to the module is driven and
stable.
•All GPIO pins default to high impedance unless programmed by the MCU. The bootloader sets the TDI, TDO, TCK, TMS, and Flash_SPI
pins to mode 1. All the other pins are left in the Hi-Z state.
The ADC inputs are tolerant up to 1.8 V (see Table 8-24 for more details about the usable range of the ADC). On the other hand, the digital
pads can tolerate up to 3.6 V. Hence, take care to prevent accidental damage to the ADC inputs. TI recommends first disabling the output
buffers of the digital I/Os corresponding to the desired ADC channel (that is, converted to Hi-Z state), and thereafter disabling the respective
pass switches (S7 [Pin 47], S8 [Pin 48], S9 [Pin 49], and S10 [Pin 50]). For more information, see Table 7-3.
(1)LPDS retention unavailable.
(2)The CC3235MODx or CC3235MODAx modules are compatible with TI BLE modules using an external RF switch.
(3)Future support.
(4)This pins is not accessible on the CC3235MODAx devices as it is directly tied to the integrated antenna.
(5)This pin has dual functions: as a SOP[2] (device operation mode), and as an external TCXO enable. As a TXCO enable, the pin is an
output on power up and driven logic high. During hibernate low-power mode, the pin is in a Hi-Z state but is pulled down for SOP mode
to disable TCXO. Because of the SOP functionality, the pin must be used as an output only.
7.4 Drive Strength and Reset States for Analog-Digital Multiplexed Pins
Table 7-3 describes the use, drive strength, and default state of analog- and digital-multiplexed pins at first-time
power up and reset (nRESET pulled low).
Table 7-3. Drive Strength and Reset States for Analog-Digital Multiplexed Pins
MAXIMUM
EFFECTIVE
DRIVE
STRENGTH
(mA)
4
4
4
4
4
4
PIN
42Generic I/O
44Generic I/O
47
48
49
50
BOARD LEVEL
CONFIGURATION AND USE
Analog signal (1.8-V absolute,
1.46-V full scale)
Analog signal (1.8-V absolute,
1.46-V full scale)
Analog signal (1.8-V absolute,
1.46-V full scale)
Analog signal (1.8-V absolute,
1.46-V full scale)
DEFAULT STATE AT FIRST POWER
UP OR FORCED RESET
Analog is isolated. The digital I/O cell
is also isolated.
Analog is isolated. The digital I/O cell
is also isolated.
ADC is isolated. The digital I/O cell is
also isolated.
ADC is isolated. The digital I/O cell is
also isolated.
ADC is isolated. The digital I/O cell is
also isolated.
ADC is isolated. The digital I/O cell is
also isolated.
STATE AFTER CONFIGURATION
OF ANALOG SWITCHES (ACTIVE,
LPDS, and HIB POWER MODES)
Determined by the I/O state, as are
other digital I/Os.
Determined by the I/O state, as are
other digital I/Os.
Determined by the I/O state, as are
other digital I/Os.
Determined by the I/O state, as are
other digital I/Os.
Determined by the I/O state, as are
other digital I/Os.
Determined by the I/O state, as are
other digital I/Os.
7.5 Pad State After Application of Power to Chip, but Before Reset Release
When a stable power is applied to the CC3235MODx or CC3235MODAx module for the first time or when supply
voltage is restored to the proper value following a prior period with supply voltage below 1.5 V, the level of the
digital pads are undefined in the period starting from the release of nRESET and until the DIG_DCDC of the
CC3235x chip powers up. This period is less than approximately 10 ms. During this period, pads can be
internally pulled weakly in either direction. If a certain set of pins are required to have a definite value during this
pre-reset period, an appropriate pullup or pulldown must be used at the board level. The recommended value of
these external pullup or pulldown resistors is 2.7 kΩ.
7.6 Connections for Unused Pins
All unused pin should be configured as stated in Table 7-4.
Table 7-4. Connections for Unused Pins
FUNCTIONSIGNAL DESCRIPTIONPIN NUMBERACCEPTABLE PRACTICE
Wake up I/O source should not be floating during
hibernate.
GPIOGeneral-purpose input or output
(1)
20, 31
No ConnectNC
SOPConfiguration sense-on-power23, 24, 34
ResetRESET input for the deviceNever leave the reset pin floating
JTAGJTAG interfaceLeave as NC if unused
, 33, 39,
41, 45
All the I/O pins will float while in Hibernate and Reset
states. Ensure pullup and pulldown resistors are available
on board to maintain the state of the I/O.
Leave unused GPIOs as NC
Unused pin, leave as NC.
Leave as NC (Modules contain internal 100-kΩ pulldown
resistors on the SOP lines). An external 10-kΩ pullup
resistor is required to pull these pins high. See Section
9.11.1 for SOP[2:0] configuration modes.
(1)The CC3235MODAx's RF_ABG pin is a NC as it is directly tied to the integrated PCB antenna.
process and voltage unless otherwise indicated.
Over operating free-air temperature range (unless otherwise noted)
V
BAT
Digital I/O–0.5V
RF pin–0.52.1V
Analog pins–0.52.1V
Operating temperature (TA)–4085°C
Storage temperature (T
Junction temperature (Tj)
(1)Stresses beyond those listed under Absolute Maximum Ratings may cause permanent damage to the device. These are stress ratings
only, and functional operation of the device at these or any other conditions beyond those indicated under Recommended Operating
Conditions is not implied. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.
(2)All voltage values are with respect to VSS, unless otherwise noted.
(3)Junction temperature is for the CC3235x device that is contained within the module.
)–4085°C
stg
(3)
(1) (2)
MINMAXUNIT
–0.53.8V
+ 0.5V
BAT
120°C
8.2 ESD Ratings
Human body model (HBM), per ANSI/ESDA/JEDEC JS001
V
ESD
(1)JEDEC document JEP155 states that 500-V HBM allows safe manufacturing with a standard ESD control process.
(2)JEDEC document JEP157 states that 250-V CDM allows safe manufacturing with a standard ESD control process.
Electrostatic discharge
Charged device model (CDM),
per JESD22-C101
(2)
All pins±500
(1)
VALUE
±2000
UNIT
V
8.3 Recommended Operating Conditions
Over operating free-air temperature range (unless otherwise noted)
V
BAT
Operating temperature–402585°C
Ambient thermal slew–2020°C/minute
(1)When operating at an ambient temperature of over 75°C, the transmit duty cycle must remain below 50% to avoid the auto-protect
feature of the power amplifier. If the auto-protect feature triggers, the device takes a maximum of 60 seconds to restart the
transmission.
(2)To ensure WLAN performance, the ripple on the power supply must be less than ±300 mV. The ripple should not cause the supply to
fall below the brownout voltage.
(3)The minimum voltage specified includes the ripple on the supply voltage and all other transient dips. The brownout condition is also 2.1
V, and care must be taken when operating at the minimum specified voltage.
8.4 Current Consumption (CC3235MODS and CC3235MODAS)
Table 8-1. Current Consumption Summary (CC3235MODS and CC3235MODAS) 2.4 GHz RF Band
TA = 25°C, V
MCU ACTIVE
MCU SLEEP
MCU LPDS
MCU SHUTDOWNMCU shutdown1µA
MCU HIBERNATEMCU hibernate5.5µA
Peak calibration current
= 3.6 V
BAT
PARAMETERTEST CONDITIONS
TX power level = 0272
TX power level = 4190
TX power level = 0248
TX power level = 4182
TX power level = 0223
TX power level = 4160
TX power level = 0269
TX power level = 4187
TX power level = 0245
TX power level = 4179
TX power level = 0220
TX power level = 4157
TX power level = 0266
TX power level = 4184
TX power level = 0242
TX power level = 4176
TX power level = 0217
TX power level = 4154
NWP ACTIVE
NWP idle connected
NWP ACTIVE
NWP idle connected
NWP ACTIVE
NWP LPDS
(2)
NWP idle connected
(4)
1 DSSS
TX
6 OFDM
54 OFDM
RX
(3)
1 DSSS59
54 OFDM59
1 DSSS
TX
6 OFDM
54 OFDM
RX
(3)
1 DSSS56
54 OFDM56
1 DSSS
TX
6 OFDM
54 OFDM
RX
SRAM Retention
(3)
V
= 3.6 V420
BAT
V
= 3.3 V450
BAT
V
= 2.3 V610
BAT
1 DSSS53
54 OFDM53
64 KB120
256 KB135
(1) (5)
MINTYP
15.3
12.2
710
(6)
MAX UNIT
mA
mA
mA
µA
mA
(1)TX power level = 0 implies maximum power (see Figure 8-1, Figure 8-2, and Figure 8-3). TX power level = 4 implies output power
backed off approximately 4 dB.
(2)LPDS current does not include the external serial flash. The CC3235MODS and CC3235MODAS device can be configured to retain
0 KB, 64 KB, 128 KB, 192 KB, or 256 KB of SRAM in LPDS. Each 64-KB block of MCU retained SRAM increases LPDS current by 4
µA.
(3)DTIM = 1
(4)The complete calibration can take up to 17 mJ of energy from the battery over a time of 24 ms. In default mode, calibration is
performed sparingly, and typically occurs when re-enabling the NWP and when the temperature has changed by more than 20°C.
There are two additional calibration modes that may be used to reduced or completely eliminate the calibration event. For further
details, see CC31xx, CC32xx SimpleLink™ Wi-Fi® and IoT Network Processor Programmer's Guide.
(1)Measurements taken at maximum TX power
(2)LPDS current does not include the external serial flash. The CC3235MODx and CC3235MODAx can be configured to retain 0 KB,
64 KB, 128 KB, 192 KB, or 256 KB of SRAM in LPDS. Each 64-KB block of MCU retained SRAM increases LPDS current by 4 µA.
(3)DTIM = 1
(4)The CC3235MODx and CC3235MODAx system is a constant power-source system. The active current numbers scale based on the
V
voltage supplied.
BAT
(5)Typical numbers assume a VSWR of 1.5:1.
(6)The complete calibration can take up to 17 mJ of energy from the battery over a time of 24 ms. In default mode, calibration is
performed sparingly, and typically occurs when re-enabling the NWP and when the temperature has changed by more than 20°C.
There are two additional calibration modes that may be used to reduced or completely eliminate the calibration event. For further
details, see CC31xx, CC32xx SimpleLink™ Wi-Fi® and IoT Network Processor Programmer's Guide.
8.5 Current Consumption (CC3235MODSF and CC3235MODASF)
Table 8-3. Current Consumption Summary (CC3235MODSF and CC3235MODASF) 2.4 GHz RF Band
TA = 25°C, V
MCU ACTIVE
MCU SLEEP
MCU LPDS
MCU
SHUTDOWN
MCU
HIBERNATE
Peak calibration current
= 3.6 V
BAT
PARAMETERTEST CONDITIONS
1 DSSS
TX
6 OFDM
NWP ACTIVE
54 OFDM
1 DSSS74
54 OFDM74
NWP idle connected
RX
(3)
1 DSSS
TX
6 OFDM
NWP ACTIVE
54 OFDM
1 DSSS70
54 OFDM70
NWP idle connected
RX
(3)
1 DSSS
TX
6 OFDM
NWP active
54 OFDM
1 DSSS53
54 OFDM53
64 KB120
256 KB135
NWP LPDS
(2)
NWP idle connected
RX
SRAM
Retention
(3)
(1) (5)
MINTYP
TX power level = 0286
TX power level = 4202
TX power level = 0255
TX power level = 4192
TX power level = 0232
TX power level = 4174
25.2
TX power level = 0282
TX power level = 4198
TX power level = 0251
TX power level = 4188
TX power level = 0228
TX power level = 4170
21.2
TX power level = 0266
TX power level = 4184
TX power level = 0242
TX power level = 4176
TX power level = 0217
TX power level = 4154
710
(5)
MCU shutdown1µA
MCU hibernate5.5µA
V
= 3.6 V420
(4)
BAT
V
= 3.3 V450
BAT
V
= 2.3 V610
BAT
www.ti.com
MAX UNIT
mA
mA
mA
µA
mA
(1)TX power level = 0 implies maximum power (see Figure 8-2, Figure 8-2, and Figure 8-3). TX power level = 4 implies output power
backed off approximately 4 dB.
(2)LPDS current does not include the external serial flash. The CC3235MODx and CC3235MODAx can be configured to retain 0 KB,
64 KB, 128 KB, 192 KB, or 256 KB of SRAM in LPDS. Each 64-KB block of MCU retained SRAM increases LPDS current by 4 µA.
(3)DTIM = 1
(4)The complete calibration can take up to 17 mJ of energy from the battery over a period of 24 ms. Calibration is performed sparingly,
typically when coming out of HIBERNATE and only if temperature has changed by more than 20°C. The calibration event can be
controlled by a configuration file in the serial flash.
(5)Typical numbers assume a VSWR of 1.5:1.
(1)Measurements taken at maximum TX power
(2)LPDS current does not include the external serial flash. The CC3235MODS and CC3235MODAS can be configured to retain 0 KB,
64 KB, 128 KB, 192 KB, or 256 KB of SRAM in LPDS. Each 64-KB block of MCU retained SRAM increases LPDS current by 4 µA.
(3)DTIM = 1
(4)Typical numbers assume a VSWR of 1.5:1.
(5)The complete calibration can take up to 17 mJ of energy from the battery over a period of 24 ms. Calibration is performed sparingly,
typically when coming out of HIBERNATE and only if temperature has changed by more than 20°C. The calibration event can be
controlled by a configuration file in the serial flash.
The CC3235MODS and CC3235MODAS has several options for modifying the output power of the device when
required. For the 2.4 GHz band it is possible to lower the overall output power at a global level using the global
TX power level setting. In addition, the 2.4 GHz band allows the user to enter additional back-offs 2, per channel,
region 3and modulation rates 4 5, through Image creator (see the Uniflash with Image Creator User Guide for
more details).
Figure 8-1, Figure 8-2, and Figure 8-3 show TX power and IBAT versus TX power level settings for the
CC3235MODS module at modulations of 1 DSSS, 6 OFDM, and 54 OFDM, respectively. For the
CC3235MODSF module, the IBAT current has an increase of approximately 10 mA to 15 mA depending on the
transmitted rate. The TX power level remains the same.
In Figure 8-1, the area enclosed in the circle represents a significant reduction in current during transition from
TX power level 3 to level 4. In the case of lower range requirements (14-dBm output power), TI recommends
using TX power level 4 to reduce the current.
5
Figure 8-1. TX Power and IBAT vs TX Power Level Settings (1 DSSS)
2
The back-off range is between –6 dB to +6 dB in 0.25-dB increments.
3
FCC, IC/ISED, ETSI/CE, MIC, and SRRC are supported.
4
Back-off rates are grouped into 11b rates, high modulation rates (MCS7, 54 OFDM and 48 OFDM), and
lower modulation rates (all other rates).
5
There will be a difference between the CC3135MOD and CC3135 IC TX power levels.
5-GHz power control is done via Image Creator where the maximum transmit power is provided 6. Within Image
Creator, power control is possible per channel, region 7, and modulation rate 8. In addition, it is possible to enter
an additional back-off 9factor per channel and modulation rate for further margin to regulatory requirements.
It is also possible to set the TX and RX trace losses to the antenna per band 10. The peak antenna gain 11can
also be provided, thus allowing further control. For a full description of options and capabilities see Uniflash with
Image Creator User Guide.
8.8 Brownout and Blackout Conditions
The module enters a brownout condition whenever the input voltage dips below V
BROWNOUT
(see Figure 8-4 and
Figure 8-5). This condition must be considered during design of the power supply routing, especially if operating
from a battery. High-current operations, such as a TX packet or any external activity (not necessarily related
directly to networking) can cause a drop in the supply voltage, potentially triggering a brownout. The resistance
includes the internal resistance of the battery, contact resistance of the battery holder (four contacts for a 2× AA
battery), and the wiring and PCB routing resistance.
Note
When the module is in HIBERNATE state, brownout is not detected. Only blackout is in effect during
HIBERNATE state.
6
The maximum transmit power range is 18 dBm to 0.125 dBm in 0.125-dBm decrements.
7
FCC, IC/ISED, ETSI/CE, MIC, and SRRC are supported.
8
Rates are grouped into high modulation rates (MCS7, 54 OFDM and 48 OFDM) and lower modulation rates
(all other rates).
9
The back-off range is 0 dBm to 18 dBm in 0.125-dBm increments, with the maximum back-off not exceed
that of the maximum transmit power.
10
The range of losses if from 0 dBm to 7.75 dBm in 0.125-dBm increments.
11
The antenna gain has a range of -2 dBi to 5.75 dBi in 0.125-dBi increments.
In the brownout condition, all sections of the device shut down within the module except for the Hibernate block
(including the 32-kHz RTC clock), which remains on. The current in this state can reach approximately 400 µA.
The blackout condition is equivalent to a hardware reset event in which all states within the module are lost.
V
brownout
= 2.1 V and V
blackout
= 1.67 V
Table 8-5 lists the brownout and blackout voltage levels.
Maximum RMS output power measured at 1
dB from IEEE spectral mask or EVM
Transmit center frequency accuracy–2525ppm
= 2.3 V to 3.6 V.
BAT
PARAMETERTEST CONDITIONSMINTYPMAXUNIT
(4) (5)
(1)
Parameters measured at SoC pin on channel 6 (2437 MHz).
24122472MHz
1 DSSS16
2 DSSS16
11 CCK16.3
6 OFDM15.3
9 OFDM15.3
18 OFDM15
36 OFDM14
54 OFDM12.5
MCS711
(2) (3)
dBm
(1)Transmit power will be reduced by 1.5dB for V
(2)The 11g/n low rates on edge channels (2412 and 2462 MHz) have reduced TX power to meet FCC emission limits.
(3)Power of 802.11b rates are reduced to meet ETSI requirements in Europe.
(4)Channels 1 (2142 MHz) through 11 (2462 MHz) are supported for FCC.
(5)Channels 1 (2142 MHz) through 13 (2472MHz) are supported for Europe and Japan. Note that channel 14 is not supported for Japan.
BAT
< 2.8V
Table 8-11. WLAN Transmitter Characteristics: 5 GHz Band
TA = 25°C, V
and 157 .
Operating frequency range
Maximum RMS output power measured at 1
dB from IEEE spectral mask or EVM
Transmit center frequency accuracy-2020ppm
(1)Transmit power will be reduced by 1.5dB for V
(2)FCC band covers U-NII-1, U-NII-2A, U-NII-2C, and U-NII-3 20-MHz BW modulations.
(3)Europe bands 1, 2 and 3, 20-MHz BW modulations are supported.
(4)For Japan, W52, W53 and W56, 20-MHz BW modulations are supported.
(5)FCC channels 36, 60, 64, 100, and 140, where harmonics/sub-harmonics of fall in the FCC restricted band, have reduced output
power to meet the FCC RSE requirement.
(6)The edge channels (100 and 140) have reduced TX power to meet FCC emissions limits.
= 2.3 V to 3.6 V.
BAT
(5) (6)
PARAMETERTEST CONDITIONSMINTYPMAXUNIT
(2) (3) (4)
(1)
Parameters measured at SoC pin are the average of channels 40, 56, 120,
For proper BLE and WLAN 2.4 GHz radio coexistence, the following requirements must be met:
Table 8-12. BLE/WLAN Coex
PARAMETERBandMINTYPMAXUNIT
Port-to-port isolationDual antenna configuration
(1)The CC3235MODS and CC3235MODAS modules are compatible with TI BLE modules using an external RF switch.
(2)A single antenna configuration is possible using the CC3x35 devices.
(3)For dual antenna configuration, the antenna placement must be such that isolation between the BLE and WLAN ports is at least 20 dB.
(1)
Isolation Requirement
(2)
20
(3)
dB
8.14 Reset Requirement
PARAMETERMINTYPMAXUNIT
V
IH
V
IL
Tr and T
(1)The nRESET pin must be held below 0.6 V for the module to register a reset.
Operation mode level0.65 × V
Shutdown mode level
(1)
00.6V
BAT
Minimum time for nReset low for resetting the module5ms
Rise and fall times20µs
f
V
8.15 Thermal Resistance Characteristics for MOB and MON Packages
NO.
PARAMETERDESCRIPTION°C/W
T1RΘ
T2RΘ
JC
JB
T3
T4
T513.42
RΘ
JA
Junction-to-case11.4N/A
Junction-to-board8.0N/A
Junction-to-free air19.10
Junction-to-moving air
T612.53
T7
T8
T96.12
Ψ
JT
Junction-to-free air5.40
Junction-to-package top
T106.53
T11
T12
T136.62
Ψ
JB
Junction-to-free air6.80
Junction-to-board
T146.53
(1)°C/W = degrees Celsius per watt.
(2)These values are based on a JEDEC-defined 2S2P system (with the exception of the Theta JC [RΘJC] value, which is based on a
JEDEC-defined 1S0P system) and will change based on environment as well as application. For more information, see these EIA/
JEDEC standards:
2. Hold the nRESET pin low while the supplies are ramping up.
Figure 8-6 shows the reset timing diagram for the first-time power-up and reset removal.
Figure 8-6. First-Time Power-Up and Reset Removal Timing Diagram
Table 8-13 lists the timing requirements for the first-time power-up and reset removal.
Table 8-13. First-Time Power-Up and Reset Removal Timing Requirements
ITEMNAMEDESCRIPTIONMINTYPMAX UNIT
T1nReset timenReset timing after VBAT supplies are stable1ms
T2Hardware wake-up time25ms
Time taken by ROM
T3
firmware to initialize
hardware
App code load time for
CC3235MODS and
CC3235MODAS
T4
App code load time for
CC3235MODSF and
CC3235MODASF
Includes internal 32-kHz XOSC settling time1.1s
CC3235MODS and CC3235MODASImage size (KB) × 1.7 ms
CC3235MODSF and CC3235MODASFImage size (KB) × 0.06 ms
8.16.2 Power-Down Sequencing
For proper power down of the CC3235MODx and CC3235MODAx module, ensure that the nRESET (pin 35) and
nHIB (pin 4) pins have remained in a known state for a minimum of 200 ms before removing power from the
module.
8.16.3 Device Reset
When a device restart is required, issue a negative pulse to the nRESET pin. Ensure the reset is properly
applied: A negative reset pulse (on pin 35) of at least 200-mS duration.
The CC3235MODx and CC3235MODAx MCU includes one SPI module, which can be configured as a master or
slave device. The SPI includes a serial clock with programmable frequency, polarity, and phase; a programmable
timing control between chip select and external clock generation; and a programmable delay before the first SPI
word is transmitted. Slave mode does not include a dead cycle between two successive words.
Figure 8-8 shows the timing diagram for the SPI master.
Figure 8-8. SPI Master Timing Diagram
Table 8-15 lists the timing parameters for the SPI master.
Table 8-15. SPI Master Timing Parameters
ITEMNAMEDESCRIPTIONMINMAXUNIT
(1)
F
T2T
T6tIS
T7tIH
T8tOD
T9tOH
clk
D
(1)
(1)
(1)
(1)
(1)
(1)
Clock frequency20MHz
Clock period50ns
Duty cycle45%55%
RX data setup time1ns
RX data hold time2ns
TX data output delay8.5ns
TX data hold time8ns
(1)Timing parameter assumes a maximum load of 20 pF.
The McASP interface functions as a general-purpose audio serial port optimized for multichannel audio
applications and supports transfer of two stereo channels over two data pins. The McASP consists of transmit
and receive sections that operate synchronously and have programmable clock and frame-sync polarity. A
fractional divider is available for bit-clock generation.
All digital pins of the module can be used as general-purpose input/output (GPIO) pins. The GPIO module
consists of four GPIO blocks, each of which provides eight GPIOs. The GPIO module supports 24
programmable GPIO pins, depending on the peripheral used. Each GPIO has configurable pullup and pulldown
strength (weak 10 µA), configurable drive strength (2, 4, and 6 mA), and open-drain enable.
Figure 8-12 shows the GPIO timing diagram.
Figure 8-12. GPIO Timing Diagram
Table 8-19 lists the GPIO output transition times for V
Table 8-19. GPIO Output Transition Times (V
DRIVE
STRENGTH (mA)
2
4
6
(1)V
(2)The transition data applies to the pins other than the multiplexed analog-digital pins 25, 26, 42, and 44.
= 2.3 V, T = 25°C, total pin load = 30 pF
BAT
DRIVE STRENGTH
CONTROL BITS
2MA_EN=1
4MA_EN=0
2MA_EN=0
4MA_EN=1
2MA_EN=1
4MA_EN=1
MINNOMMAXMINNOMMAX
11.713.916.311.513.916.7ns
13.715.618.09.911.613.6ns
5.56.47.43.84.75.8ns
BAT
T
r
= 2.3 V.
= 2.3 V)
BAT
(1) (2)
Table 8-20 lists the GPIO output transition times for V
Table 8-20. GPIO Output Transition Times (V
DRIVE
STRENGTH (mA)
2
4
6
DRIVE STRENGTH
CONTROL BITS
2MA_EN=1
4MA_EN=0
2MA_EN=0
4MA_EN=1
2MA_EN=1
4MA_EN=1
MINNOMMAXMINNOMMAX
8.09.310.78.29.511.0ns
6.67.17.64.75.25.8ns
3.23.53.72.32.62.9ns
BAT
T
r
= 3.3 V.
= 3.3 V)
BAT
(1) (2)
T
f
T
f
UNIT
UNIT
(1)V
(2)The transition data applies to the pins except the multiplexed analog-digital pins 29, 30, 45, 50, 52 and 53.
The Joint Test Action Group (JTAG) port is an IEEE standard that defines a test access port (TAP) and boundary
scan architecture for digital integrated circuits and provides a standardized serial interface to control the
associated test logic. For detailed information on the operation of the JTAG port and TAP controller, see the
IEEE Standard 1149.1,Test Access Port and Boundary-Scan Architecture.
The fast camera parallel port interfaces with a variety of external image sensors, stores the image data in a
FIFO, and generates DMA requests. The camera parallel port supports 8 bits.
Figure 8-16 shows the timing diagram for the camera parallel port.
Figure 8-16. Camera Parallel Port Timing Diagram
Table 8-25 lists the timing parameters for the camera parallel port.
Table 8-25. Camera Parallel Port Timing Parameters
The CC3235MODx and CC3235MODAx MCU includes the Macronix™ 32-Mbit serial flash. The serial flash can
be programmed directly using the external flash interface (pins 13, 14, 15, and 17). During normal operation, the
external flash interface should remain unconnected.
For timing details, see the MX25R3235F data sheet.
8.16.5.10 SD Host
The CC3235MODx and CC3235MODAx MCU provides an interface between a local host (LH), such as an MCU
and an SD memory card, and handles SD transactions with minimal LH intervention.
The SD host does the following:
•Provides SD card access in 1-bit mode
•Deals with SD protocol at the transmission level
•Handles data packing
•Adds cyclic redundancy checks (CRC)
•Start and end bit
•Checks for syntactical correctness
The application interface sends every SD command and either polls for the status of the adapter or waits for an
interrupt request. The result is then sent back to the application interface in case of exceptions or to warn of endof-operation. The controller can be configured to generate DMA requests and work with minimum CPU
intervention. Given the nature of integration of this peripheral on the CC3235x platform, TI recommends that
developers use peripheral library APIs to control and operate the block. This section emphasizes understanding
the SD host APIs provided in the peripheral library of the CC3235x Software Development Kit (SDK).
The SD host features are as follows:
•Full compliance with SD command and response sets, as defined in the SD memory card
– Specifications, v2.0
– Includes high-capacity (size >2 GB) cards HC SD
•Flexible architecture, allowing support for new command structure.
•1-bit transfer mode specifications for SD cards
•Built-in 1024-byte buffer for read or write
– 512-byte buffer for both transmit and receive
– Each buffer is 32-bits wide by 128-words deep
•32-bit-wide access bus to maximize bus throughput
•Single interrupt line for multiple interrupt source events
•Two slave DMA channels (1 for TX, 1 for RX)
•Programmable clock generation
•Integrates an internal transceiver that allows a direct connection to the SD card without external transceiver
•Supports configurable busy and response timeout
•Support for a wide range of card clock frequency with odd and even clock ratio
Programmable timers can be used to count or time external events that drive the timer input pins. The generalpurpose timer module (GPTM) of the CC3235MODx and CC3235MODAx MCU contains 16- or 32-bit GPTM
blocks. Each 16- or 32-bit GPTM block provides two 16-bit timers or counters (referred to as Timer A and Timer
B) that can be configured to operate independently as timers or event counters, or they can be concatenated to
operate as one 32-bit timer. Timers can also be used to trigger µDMA transfers.
The GPTM contains four 16- or 32-bit GPTM blocks with the following functional options:
•Operating modes:
– 16- or 32-bit programmable one-shot timer
– 16- or 32-bit programmable periodic timer
– 16-bit general-purpose timer with an 8-bit prescaler
– 16-bit input-edge count- or time-capture modes with an 8-bit prescaler
– 16-bit PWM mode with an 8-bit prescaler and software-programmable output inversion of the PWM signal
•Counts up or counts down
•Sixteen 16- or 32-bit capture compare pins (CCP)
•User-enabled stalling when the microcontroller asserts CPU Halt flag during debug
•Ability to determine the elapsed time between the assertion of the timer interrupt and entry into the interrupt
service routine
•Efficient transfers using micro direct memory access controller (µDMA):
– Dedicated channel for each timer
– Burst request generated on timer interrupt
The CC3235MODx and CC3235MODAx MCU is a Dual-Band Wi-Fi internet-on-a chip module that consists of an
Arm Cortex-M4 processor with a rich set of peripherals for diverse application requirements, a Wi-Fi network
processor, and power-management subsystems.
9.2 Functional Block Diagram
Figure 9-1 shows the functional block diagram of the CC3235MODx and CC3235MODAx SimpleLink™ Wi-Fi
The high-performance Arm Cortex-M4 processor provides a low-cost platform that meets the needs of minimal
memory implementation, reduced pin count, and low power consumption, while delivering outstanding
computational performance and exceptional system response to interrupts.
•The Cortex-M4 core has low-latency interrupt processing with the following features:
– A 32-bit Arm Thumb® instruction set optimized for embedded applications
– Handler and thread modes
– Low-latency interrupt handling by automatic processor state saving and restoration during entry and exit
– Support for ARMv6 unaligned accesses
•Nested vectored interrupt controller (NVIC) closely integrated with the processor core to achieve low-latency
interrupt processing. The NVIC includes the following features:
– Bits of priority configurable from 3 to 8
– Dynamic reprioritization of interrupts
– Priority grouping that enables selection of preempting interrupt levels and nonpreempting interrupt levels
– Support for tail-chaining and late arrival of interrupts, which enables back-to-back interrupt processing
without the overhead of state saving and restoration between interrupts
– Processor state automatically saved on interrupt entry and restored on interrupt exit with no instruction
overhead
– Wake-up interrupt controller (WIC) providing ultra-low-power sleep mode support
•Bus interfaces:
– Advanced high-performance bus (AHB-Lite) interfaces: system bus interfaces
– Bit-band support for memory and select peripheral that includes atomic bit-band write and read operations
•Low-cost debug solution featuring:
– Debug access to all memory and registers in the system, including access to memory-mapped devices,
access to internal core registers when the core is halted, and access to debug control registers even while
SYSRESETn is asserted
– Serial wire debug port (SW-DP) or serial wire JTAG debug port (SWJ-DP) debug access
– Flash patch and breakpoint (FPB) unit to implement breakpoints and code patches
The Wi-Fi network processor subsystem includes a dedicated Arm MCU to completely offload the host MCU
along with an 802.11 a/b/g/n radio, baseband, and MAC with a powerful crypto engine for a fast, secure WLAN
and Internet connections with 256-bit encryption. The CC3235MODx and CC3235MODAx MCU supports station,
AP, and Wi-Fi Direct modes. The module also supports WPA2 personal and enterprise security, WPS 2.0, and
WPA3 personal 12. The Wi-Fi network processor includes an embedded IPv6, IPv4 TCP/IP stack, TLS stack, and
network applications such as HTTPS server.
9.4.1 WLAN
The WLAN features are as follows:
•802.11 a/b/g/n integrated radio, modem, and MAC supporting WLAN communication as a BSS station, AP,
Wi-Fi Direct client and group owner with CCK and OFDM rates in the 2.4 GHz ISM band, channels 1 to 13,
and 5 GHz U-NII band.
Note
802.11n is supported only in Wi-Fi station, Wi-Fi Direct, and P2P client modes.
•Autocalibrated radio with a single-ended 50-Ω interface enables easy connection to the antenna without
requiring expertise in radio circuit design.
•Advanced connection manager with multiple user-configurable profiles stored in serial-flash allows automatic
fast connection to an access point without user or host intervention.
•Supports all common Wi-Fi security modes for personal and enterprise networks with on-chip security
accelerators, including: WEP, WPA/WPA2 PSK, WPA2 Enterprise (802.1x), WPA3 Personal .
•Smart provisioning options deeply integrated within the module providing a comprehensive end-to-end
solution. With elaborate events notification to the host, enabling the application to control the provisioning
decision flow. The wide variety of Wi-Fi provisioning methods include:
– Access Point using HTTPS
– SmartConfig Technology: a 1-step, 1-time process to connect a CC3235MODx or CC3235MODAx-
enabled module to the home wireless network, removing dependency on the I/O capabilities of the host
MCU; thus, it is usable by deeply embedded applications
•802.11 transceiver mode allows transmitting and receiving of proprietary data through a socket without
adding MAC or PHY headers. The 802.11 transceiver mode provides the option to select the working
channel, rate, and transmitted power. The receiver mode works with the filtering options.
9.4.2 Network Stack
The Network Stack features are as follows:
•Integrated IPv4, IPv6 TCP/IP stack with BSD socket APIs for simple Internet connectivity with any MCU,
microprocessor, or ASIC
Note
Not all APIs are 100% BSD compliant. Not all BSD APIs are supported.
•Support of 16 simultaneous TCP, UDP, RAW, SSL\TLS sockets
•Built-in network protocols:
– Static IP, LLA, DHCPv4, DHCPv6 with DAD and stateless autoconfiguration
– ARP, ICMPv4, IGMP, ICMPv6, MLD, ND
– DNS client for easy connection to the local network and the Internet
•Built-in network application and utilities:
– HTTP/HTTPS
•Web page content stored on serial flash
12
See CC3x35 SDK v3.40 or newer for details. Limited to STA mode only.
Power managementEnhanced power policy management uses 802.11 power save and deep-sleep power modes
Transceiver
Other
(1)See CC3x35 SDK v3.40 or newer for details. Limited to STA mode only.
Programmable RX filters with event-trigger mechanism
Rx Metrics for tracking the surrounding RF environment
9.5 Security
The SimpleLink Wi-Fi CC3235MODx and CC3235MODAx internet-on-a chip module enhances the security
capabilities available for development of IoT devices, while completely offloading these activities from the MCU
to the networking subsystem. The security capabilities include the following key features:
Wi-Fi and Internet Security:
•Personal and enterprise Wi-Fi security
– Personal standards
•AES (WPA2-PSK)
•TKIP (WPA-PSK)
•WEP
– Enterprise standards
•EAP Fast
•EAP PEAPv0/1
•EAP PEAPv0 TLS
•EAP PEAPv1 TLS EAP LS
•EAP TLS
•EAP TTLS TLS
•EAP TTLS MSCHAPv2
•Secure sockets
– Protocol versions: SSL v3, TLS 1.0, TLS 1.1, TLS 1.2
– Powerful crypto engine for fast, secure Wi-Fi and internet connections with 256-bit AES encryption for TLS
•SL_SEC_MASK_TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
– Server authentication
– Client authentication
– Domain name verification
– Runtime socket upgrade to secure socket – STARTTLS
•Secure HTTP server (HTTPS)
•Trusted root-certificate catalog – Verifies that the CA used by the application is trusted and known secure
content delivery
•TI root-of-trust public key – Hardware-based mechanism that allows authenticating TI as the genuine origin of
a given content using asymmetric keys
•Secure content delivery – Allows encrypted file transfer to the system using asymmetric keys created by the
device
Code and Data Security:
•Network passwords and certificates are encrypted and signed
•Cloning protection – Application and data files are encrypted by a unique key per device
•Access control – Access to application and data files only by using a token provided in file creation time. If an
unauthorized access is detected, a tamper protection lockdown mechanism takes effect
•Encrypted and authenticated file system
•Secured boot – Authentication of the application image on every boot
•Code and data encryption – User application and data files are encrypted in sFlash
•Code and data authentication – User Application and data files are authenticated with a public key certificate
•Offloaded crypto library for asymmetric keys, including the ability to create key-pair, sign and verify data
buffer
•Recovery mechanism
Device Security:
•Separate execution environments – Application processor and network processor run on separate Arm cores
•Initial secure programming – Allows for keeping the content confidential on the production line
•Debug security
– JTAG lock
– Debug ports lock
•True random number generator
Figure 9-2 shows the high-level structure of the CC3235S and CC3235SF devices that are contained within the
CC3235MODS and CC3235MODSF modules, respectively. The application image, user data, and network
information files (passwords, certificates) are encrypted using a device-specific key.
Figure 9-2. CC3235S and CC3235SF High-Level Structure
9.6 FIPS 140-2 Level 1 Certification
The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. government computer security
standard. It is commonly referred to as FIPS 140-2, and is used to accredit the design and implementation of
cryptographic functions, for example within a chip. A cryptographic function within a chip security system is
necessary to maintain the confidentiality and integrity of the information that is being processed.
The security functions of the CC3235x chip that is inside the CC3235MODx or CC3235MODAx module, are
FIPS certified to FIPS 140-2 level 1. This certification covers topics such as: cryptographic specifications, ports
and interfaces, a finite state model for the cryptographic functions, the operational environment of the function,
and how cryptographic keys are managed. The certification provides the assurance that the implementation
meets FIPS 140-2 level 1 standards.
9.7 Power-Management Subsystem
The CC3235MODx and CC3235MODAx power-management subsystems contain DC/DC converters to
accommodate the differing voltage or current requirements of the system.
The CC3235MODx and CC3235MODAx MCU is a fully integrated module-based WLAN radio solution used on
an embedded system with a wide-voltage supply range. The internal power management, including DC/DC
converters and LDOs, generates all of the voltages required for the module to operate from a wide variety of
input sources. For maximum flexibility, the module can operate in the modes described in the following sections.
9.7.1 VBAT Wide-Voltage Connection
In the wide-voltage battery connection, the module can be directly connected to two AA alkaline batteries. All
other voltages required to operate the module are generated internally by the DC/DC converters. This scheme is
the most common mode for the module because it supports wide-voltage operation from 2.3 to 3.6 V.
9.8 Low-Power Operating Mode
From a power-management perspective, the CC3235MODx and CC3235MODAx MCU comprises the following
two independent subsystems:
•Arm Cortex-M4 application processor subsystem
•Networking subsystem
Each subsystem operates in one of several power states.
The Arm Cortex-M4 application processor runs the user application loaded from an internal serial flash, or onmodule XIP flash (in CC3235MODSF). The networking subsystem runs preprogrammed TCP/IP and Wi-Fi data
link layer functions.
The user program controls the power state of the application processor subsystem and can be in one of the five
modes described in Table 9-2.
MCU active modeMCU executing code at 80-MHz state rate.
MCU sleep mode
MCU LPDS mode
MCU hibernate mode
MCU shutdown mode
(1)
The MCU clocks are gated off in sleep mode and the entire state of the device is retained. Sleep mode
offers instant wakeup. The MCU can be configured to wake up by an internal fast timer or by activity
from any GPIO line or peripheral.
State information is lost and only certain MCU-specific register configurations are retained. The MCU
can wake up from external events or by using an internal timer. (The wake-up time is less than 3 ms.)
Certain parts of memory can be retained while the MCU is in LPDS mode. The amount of memory
retained is configurable. Users can choose to preserve code and the MCU-specific setting. The MCU
can be configured to wake up using the RTC timer or by an external event on specific GPIOs as the
wake-up source.
The lowest power mode in which all digital logic is power-gated. Only a small section of the logic directly
powered by the input supply is retained. The RTC keeps running and the MCU supports wakeup from an
external event or from an RTC timer expiry. Wake-up time is longer than LPDS mode at about 15 ms
plus the time to load the application from serial flash, which varies according to code size. In this mode,
the MCU can be configured to wake up using the RTC timer or external event on a GPIO.
The lowest power mode system-wise. All device logics are off, including the RTC. The wake-up time in
this mode is longer than hibernate at about 1.1 s. To enter or exit the shutdown mode, the state of the
nRESET line is changed (low to shut down, high to turn on).
DESCRIPTION
(1)Modes are listed in order of power consumption, with highest power modes listed first.
The NWP can be active or in LPDS mode and takes care of its own mode transitions. When there is no network
activity, the NWP sleeps most of the time and wakes up only for beacon reception (see
Table 9-3).
Table 9-3. Networking Subsystem Modes
NETWORK PROCESSOR
Network active mode
(processing layer 3, 2, and 1)
Network active mode
(processing layer 2 and 1)
Network active listen modeSpecial power optimized active mode for receiving beacon frames (no other frames supported)
Network connected Idle
Network LPDS mode
Network disabledThe network is disabled
MODE
Transmitting or receiving IP protocol packets
Transmitting or receiving MAC management frames; IP processing not required.
A composite mode that implements 802.11 infrastructure power save operation. The CC3235MODx and
CC3235MODAx NWPs automatically go into LPDS mode between beacons and then wakes to active
listen mode to receive a beacon and determine if there is pending traffic at the AP. If not, the NWP
returns to LPDS mode and the cycle repeats.
Low-power state between beacons in which the state is retained by the NWP, allowing for a rapid wake
up.
DESCRIPTION
The operation of the application and network processor ensures that the module remains in the lowest power
mode most of the time to preserve battery life.
The following examples show the use of the power modes in applications:
•A product that is continuously connected to the network in the 802.11 infrastructure power-save mode but
sends and receives little data spends most of the time in connected idle, which is a composite of receiving a
beacon frame and waiting for the next beacon.
•A product that is not continuously connected to the network but instead wakes up periodically (for example,
every 10 minutes) to send data, spends most of the time in hibernate mode, jumping briefly to active mode to
transmit data.
The CC3235x device within the CC3235MODx and CC3235MODAx modules includes on-chip SRAM to which
application programs are downloaded and executed. The application developer must share the SRAM for code
and data. The micro direct memory access (µDMA) controller can transfer data to and from SRAM and various
peripherals. The CC3235x device ROM holds the rich set of peripheral drivers, which saves SRAM space. For
more information on drivers, see the CC3235x API list.
9.9.1.1 SRAM
The CC3235MODx and CC3235MODAx MCU family provides 256KB of on-chip SRAM. Internal RAM is capable
of selective retention during LPDS mode. This internal SRAM is at offset 0x2000 0000 of the device memory
map.
Use the µDMA controller to transfer data to and from the SRAM.
When the device enters low-power mode, the application developer can choose to retain a section of memory
based on need. Retaining the memory during low-power mode provides a faster wakeup. The application
developer can choose the amount of memory to retain in multiples of 64KB. For more information, see the API
guide.
9.9.1.2 ROM
The internal zero-wait-state ROM of the CC3235MODx and CC3235MODAx module is at address 0x0000 0000
of the device memory and is programmed with the following components:
•Bootloader
•Peripheral driver library (DriverLib) release for product-specific peripherals and interfaces
The bootloader is used as an initial program loader (when the serial flash memory is empty). The DriverLib
software library of the CC3235MODx and CC3235MODAx MCU controls on-chip peripherals with a bootloader
capability. The library performs peripheral initialization and control functions, with a choice of polled or interruptdriven peripheral support. The DriverLib APIs in ROM can be called by applications to reduce flash memory
requirements and free the flash memory to be used for other purposes.
9.9.1.3 Flash Memory
The CC3235SF device within the CC3235MODSF and CC3235MODASF modules comes with an on-chip flash
memory of 1MB that allows application code to execute in place while freeing SRAM exclusively for read-write
data. The flash memory is used for code and constant data sections and is directly attached to the ICODE/
DCODE bus of the Arm Cortex-M4 core. A 128-bit-wide instruction prefetch buffer allows maintenance of
maximum performance for linear code or loops that fit inside the buffer.
The flash memory is organized as 2-KB sectors that can be independently erased. Reads and writes can be
performed at word (32-bit) level.
9.9.1.4 Memory Map
Table 9-4 describes the various MCU peripherals and how they are mapped to the processor memory. For more
The module has an internal recovery mechanism that rolls back the file system to its predefined factory image or
restoring the factory default parameters of the device. The factory image is kept in a separate sector on the
sFLASH in a secure manner and cannot be accessed from the host processor. The following restore modes are
supported:
•None—no factory restore settings
•Enable restore of factory default parameters
•Enable restore of factory image and factory default parameters
The restore process is performed by calling software APIs, or by pulling or forcing SOP[2:0] = 011 pins and
toggling the nRESET pin from low to high.
The process is fail-safe and resumes operation if a power failure occurs before the restore is finished. The
restore process typically takes about 8 seconds, depending on the attributes of the serial flash vendor.
9.11 Boot Modes
9.11.1 Boot Mode List
The CC3235MODx and CC3235MODAx MCU implements a sense-on-power (SoP) scheme to determine the
device operation mode.
SoP values are sensed from the module pin during power up. This encoding determines the boot flow. Before
the device is taken out of reset, the SoP values are copied to a register and used to determine the device
operation mode while powering up. These values determine the boot flow as well as the default mapping for
some of the pins (JTAG, SWD, UART0). Table 9-5 lists the pull configurations.
All CC3235MODx and CC3235MODAx MCUs contain internal pulldown resistors on the SOP[2:0] lines. The
application can use SOP2 for other functions after chip has powered up. However, to avoid spurious SOP values
from being sensed at power up, TI strongly recommends using the SOP2 pin only for output signals. The SOP0
and SOP1 pins are multiplexed with the WLAN analog test pins and are not available for other functions.
Table 9-5. CC3235MODx and CC3235MODAx Functional Configurations
NAMESOP[2]SOP[1]SOP[0]SoP MODECOMMENT
Factory, lab flash, and SRAM loads
through the UART. The device waits
indefinitely for the UART to load code.
The SOP bits then must be toggled to
configure the device in functional mode.
Also puts JTAG in 4-wire mode.
Functional development mode. In this
mode, 2-pin SWD is available to the
developer. TMS and TCK are available for
debugger connection.
Functional development mode. In this
mode, 4-pin JTAG is available to the
developer. TDI, TMS, TCK, and TDO are
available for debugger connection. The
default configuration for CC3235MODx
and CC3235MODAx MCUs.
Supports flash and SRAM load through
UART and functional mode. The MCU
bootloader tries to detect a UART break
on UART receive line. If the break signal
is present, the device enters the
UARTLOAD mode, otherwise, the device
enters the functional mode. TDI, TMS,
TCK, and TDO are available for debugger
connection.
Table 9-5. CC3235MODx and CC3235MODAx Functional Configurations (continued)
NAMESOP[2]SOP[1]SOP[0]SoP MODECOMMENT
RET_FACTORY_IMAGEPulldownPullupPullupRetFactDef
When module reset is toggled, the MCU
bootloader kickstarts the procedure to
restore factory default images.
9.12 Hostless Mode
The SimpleLink™ Wi-Fi® CC3235MODx or CC3235MODAx devices incorporate a scripting ability that enables
offloading of simple tasks from the host processor. Using simple and conditional scripts, repetitive tasks can be
handled internally, which allows the host processor to remain in a low-power state. In some cases where the
scripter is being used to send packets, it reduces code footprint and memory consumption. The if-this-then-that
style conditioning can include anything from GPIO toggling to transmitting packets.
The conditional scripting abilities can be divided into conditions and actions. The conditions define when to
trigger actions. Only one action can be defined per condition, but multiple instances of the same condition may
be used, so in effect multiple actions can be defined for a single condition. In total, 16 condition and action pairs
can be defined. The conditions can be simple, or complex using sub-conditions (using a combinatorial AND
condition between them). The actions are divided into two types, those that can occur during runtime and those
that can occur only during the initialization phase.
The following actions can only be performed when triggered by the pre-initialization condition:
•Set roles AP, station, P2P, and Tag modes
•Delete all stored profiles
•Set connection policy
•Hardware GPIO indication allows an I/O to be driven directly from the WLAN core hardware to indicate
internal signaling
The following actions may be activated during runtime:
•Send transceiver packet
•Send UDP packet
•Send TCP packet
•Increment counter increments one of the user counters by 1
•Set counter allows setting a specific value to a counter
•Timer control
•Set GPIO allows GPIO output from the device using the internal networking core
•Enter Hibernate state
Note
Consider the following limitations:
•Timing cannot be ensured when using the network scripter because some variable latency will
apply depending on the utilization of the networking core.
•The scripter is limited to 16 pairs of conditions and reactions.
•Both timers and counters are limited to 8 instances each. Timers are limited to a resolution of 1
second. Counters are 32 bits wide.
•Packet length is limited to the size of one packet and the number of possible packet tokens is
limited to 8.
The CC3235MODx and CC3235MODAx MCU from TI is certified for FCC, IC/ISED, ETSI/CE, Japan MIC, and
SRRC. Moreover, the module is also Wi-Fi CERTIFIED™ with the ability to request a certificate transfer for Wi-Fi
Alliance® members. TI customers that build products based on the CC3235MODx or CC3235MODAx MCU from
TI can save in testing cost and time per product family.
Table 9-6. CC3235MODx and CC3235MODAx List of Certifications
IC/ISED (Canada)RSS-102 (MPE) and RSS-247 (Wi-Fi)451I-CC3235MOD
EN300328 v2.2.1 (2.4GHz Wi-Fi)—
EN301893 v2.1.1 (5GHz Wi-Fi)—
EN62311:2008 (MPE)—
ETSI/CE (Europe)
MIC (Japan)Article 49-20 of ORRE201-190033
SRRC (China)—
EN301489-1 v2.2.1 (General EMC)—
EN301489-17 v3.2.0 (EMC)—
EN60950-1:2006/A11:2009/A1:2010/
A12:2011/A2:2013
—
Please contact TI for more information on
using SRRC ID Certification: www.ti.com/tool/
SIMPLELINK-CC3XXX-CERTIFICATION
9.13.1 FCC Certification and Statement
CAUTION
FCC RF Radiation Exposure Statement:
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled
environment. End users must follow the specific operating instructions for satisfying RF exposure
limits. This transmitter must not be co-located or operating with any other antenna or transmitter.
The CC3235MODx and CC3235MODAx modules from TI are certified for the FCC as a single-modular
transmitter. The modules are FCC-certified radio modules that carries a modular grant.
You are cautioned that changes or modifications not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
•This device may not cause harmful interference.
•This device must accept any interference received, including interference that may cause undesired
operation of the device.
9.13.2 IC/ISED Certification and Statement
CAUTION
IC RF Radiation Exposure Statement:
To comply with IC RF exposure requirements, this device and its antenna must not be co-located or
operating in conjunction with any other antenna or transmitter.
Pour se conformer aux exigences de conformité RF canadienne l'exposition, cet appareil et son
antenne ne doivent pas étre co-localisés ou fonctionnant en conjonction avec une autre antenne ou
transmetteur.
The CC3235MODx and CC3235MODAx modules from TI are certified for IC as a single-modular transmitter. The
CC3235MODx and CC3235MODAx modules from TI meet IC modular approval and labeling requirements. The
IC follows the same testing and rules as the FCC regarding certified modules in authorized equipment.
This device complies with Industry Canada licence-exempt RSS standards.
Operation is subject to the following two conditions:
•This device may not cause interference.
•This device must accept any interference, including interference that may cause undesired operation of the
device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de
licence.
L'exploitation est autorisée aux deux conditions suivantes:
•L'appareil ne doit pas produire de brouillage
•L'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est
susceptible d'en compromettre le fonctionnement.
9.13.3 ETSI/CE Certification
The CC3235MODx and CC3235MODAx modules from TI are CE certified with certifications to the appropriate
EU radio and EMC directives summarized in the Declaration of Conformity and evidenced by the CE mark. The
modules are tested against the new Radio Equipment Directive (RE-D). See the full text of the EU Declaration of
Conformity for the CC3235MODSM2MOB and CC3235MODSF12MOB devices.
9.13.4 MIC Certification
The CC3235MODx and CC3235MODAx modules from TI are MIC certified against article 49-20 and the relevant
articles of the Ordinance Regulating Radio Equipment.
Operation is subject to the following condition:
•The host system does not contain a wireless wide area network (WWAN) device.
This device operates in the W52 and W53 bands and is for indoor use only (except communication to high power
radio).
Table 9-7 lists the CC3235MODx and CC3235MODAx module markings.
Table 9-7. Module Descriptions
MARKINGDESCRIPTION
CC3235MODSM2MOB
CC3235MODSF12MOB
CC3235MODASM2MON
CC3235MODASF12MON
YMWLLLC
Z64-CC3235MODFCC ID: single modular FCC grant ID
451I-CC3235MODIC: single modular IC grant ID
CECE compliance mark
Model
Model
LTC (Lot Trace Code):
•Y = Year
•M = Month
•WLLLC = Reserved for internal use
MIC compliance mark
MIC ID: modular MIC grant ID
www.ti.com
9.15 End Product Labeling
These modules are designed to comply with the FCC single modular FCC grant, FCC ID: Z64-CC3235MOD.
The host system using this module must display a visible label indicating the following text:
Contains FCC ID: Z64-CC3235MOD
These modules are designed to comply with the IC single modular FCC grant, IC: 451I-CC3235MOD. The host
system using this module must display a visible label indicating the following text:
Contains IC: 451I-CC3235MOD
This module is designed to comply with the JP statement, 201-190033. The host system using this module must
display a visible label indicating the following text:
Contains transmitter module with certificate number: 201-190033
9.16 Manual Information to the End User
The OEM integrator must be aware not to provide information to the end user regarding how to install or remove
this RF module in the user’s manual of the end product which integrates this module.
The end user manual must include all required regulatory information and warnings as shown in this manual.
Information in the following applications sections is not part of the TI component specification, and TI
does not warrant its accuracy or completeness. TI’s customers are responsible for determining
suitability of components for their purposes. Customers should validate and test their design
implementation to confirm system functionality.
10.1 Typical Application
10.1.1 BLE/2.4 GHz Radio Coexistence
The CC3235MODx and CC3235MODAx devices are designed to support BLE/2.4 GHz radio coexistence.
Because WLAN is inherently more tolerant to time-domain disturbances, the coexistence mechanism gives
priority to the Bluetooth® low energy entity over the WLAN. Bluetooth® low energy operates in the 2.4 GHz band,
therefore the coexistence mechanism does not affect the 5 GHz band. The CC3235MODx and CC3235MODAx
device can operate normally on the 5 GHz band, while the Bluetooth® low energy works on the 2.4 GHz band
without mutual interference.
The following coexistence modes can be configured by the user:
•Off mode or intrinsic mode
– No BLE/2.4 GHz radio coexistence, or no synchronization between WLAN and Bluetooth® low energy—in
case Bluetooth® low energy exists in this mode, collisions can randomly occur.
In this mode, the WLAN can operate on either a 2.4 or 5 GHz band and Bluetooth® low energy operates
on the 2.4 GHz band.
Figure 10-1 shows the dual antenna implementation of a complete Bluetooth® low energy and WLAN
coexistence network with the WLAN operating on either a 2.4- or a 5 GHz band. Note in this implementation a
Coex switch is not required and only a single GPIO from the BLE device to the CC3235MOD device is needed.
In addition, the CC3235MODx's antenna is external while the CC3235MODAx's antenna is integrated.
The CC3235MODx device is designed to also support antenna selection and is controlled from Image Creator.
When enabled, there are 3 options possible options:
•ANT 1: When selected, the GPIOs that are defined for antenna selection with set the RF path for antenna 1.
•ANT 2: When selected, the GPIOs that are defined for antenna selection will set the RF path for antenna 2.
•Autoselect: When selected, during a scan and prior to connecting to an AP, CC3235MODx device will
determine the best RF path and select the appropriate antenna 13 14. The result is the saved as port of the
profile.
Figure 10-2 shows the antenna selection implementation for Wi-Fi, with BLE operating on it's own antenna. Note
in this implementation, only a single GPIO from the BLE device to the CC3235MODx device is required. The
Antenna switch 15is controlled by 2 GPIO lines from the CC3235MODx device. Section 7.3 lists which GPIOs
can be used for Antenna Selection.
Figure 10-2. Coexistence Solution with Wi-Fi Antenna Selection and Dedicated BLE Antenna
13
When selecting Autoselect via the API, a reset is required in order for the CC3235MODx device to
determine the best antenna for use.
14
Refer to the Uniflash with Image Creator User Guidefor more information.
15
The recommended Antenna switch is the Richwave RTC6608OSP.
Figure 10-3 shows the typical application schematic using the CC3235MODx module. See the full reference schematic for CC3235MODx.
Note that the CC3235MODx and CC3235MODAx modules share the same reference schematic. The difference between the two references is the
antenna and its matching circuitry. The CC3235MODAx's pin 31 is not accessible to the designer because it is directly tied to the integrated antenna.
Note
The following guidelines are recommended for implementation of the RF design:
•Ensure an RF path is designed with an impedance of 50 Ω
•Tuning of the antenna impedance π matching network is recommended after manufacturing of the PCB to account for PCB parasitics
•π or L matching and tuning may be required between cascaded passive components on the RF path
10.2.1 Power Supply Decoupling and Bulk Capacitors
Depending upon routing resistors and battery type, TI recommends adding two 100-µF ceramic capacitors to
help provide the peak current drawn by the CC3235MODx and CC3235MODAx modules.
Note
The module enters a brown-out condition whenever the input voltage dips below V
BROWN
(see Figure
8-4 and Figure 8-5). This condition must be considered during design of the power supply routing
specifically if operating from a battery. For more details on brown-out consideration, see Section 8.8.
10.2.2 Reset
The module features an internal RC circuit to reset the device during power ON. The nRESET pin must be held
below 0.6 V for at least 5 ms for the device to successfully reset.
10.2.3 Unused Pins
All unused pins can be left unconnected without the concern of having leakage current.
10.3 PCB Layout Guidelines
This section details the PCB guidelines to speed up the PCB design using the CC3235MODx and
CC3235MODAx. The integrator of theCC3235MODx and CC3235MODAx modules must comply with the PCB
layout recommendations described in the following subsections to minimize the risk with regulatory certifications
for the FCC, IC/ISED, ETSI/CE, MIC, and SRRC. Moreover, TI recommends customers follow the guidelines
described in this section to achieve similar performance to that obtained with the TI reference design.
10.3.1 General Layout Recommendations
Ensure that the following general layout recommendations are followed:
•Have a solid ground plane and ground vias under the module for stable system and thermal dissipation.
•Do not run signal traces underneath the module on a layer where the module is mounted.
10.3.2 CC3235MODx RF Layout Recommendations
The RF section of this wireless module gets top priority in terms of layout. It is very important for the RF section
to be laid out correctly to ensure optimum performance from the module. A poor layout can cause low-output
power, EVM degradation, sensitivity degradation, and mask violations.
Figure 10-5 shows the RF placement and routing of the CC3235MODx module with external antenna.
Follow these RF layout recommendations for the CC3235MODx device:
•RF traces must have 50-Ω impedance.
•RF trace bends must be made with gradual curves, and 90° bends must be avoided.
•RF traces must not have sharp corners.
•There must be no traces or ground under the antenna section.
•RF traces must have via stitching on the ground plane beside the RF trace on both sides.
•RF traces must be as short as possible. The antenna, RF traces, and the module must be on the edge of the
PCB product in consideration of the product enclosure material and proximity.
The antenna is the element used to convert the guided waves on the PCB traces to the free space
electromagnetic radiation. The placement and layout of the antenna are the keys to increased range and data
rates. Table 10-3 provides a summary of the recommended antennas to use with the CC3235MODx module.
Table 10-3. Antenna Guidelines
SR NO.GUIDELINES
1Place the antenna on an edge or corner of the PCB.
7Ensure that the antenna has a near omnidirectional pattern.
8
Ensure that no signals are routed across the antenna elements on all the layers of the
PCB.
Most antennas, including the chip antenna used on the LaunchPad™, require ground
clearance on all the layers of the PCB. Ensure that the ground is cleared on inner layers
as well.
Ensure that there is provision to place matching components for the antenna. These must
be tuned for best return loss when the complete board is assembled. Any plastics or
casing must also be mounted while tuning the antenna because this can impact the
impedance.
Ensure that the antenna impedance is 50 Ω because the module is rated to work only with
a 50-Ω system.
In case of printed antenna, ensure that the simulation is performed with the solder mask in
consideration.
The feed point of the antenna is required to be grounded. This is only for the antenna type
used on the CC3235MODx Launchpad. See the specific antenna data sheets for the
recommendations.
Table 10-4 lists the recommended antennas to use with the CC3235MODx module. Other antennas may be
available for use with the CC3235MODx modules.
Table 10-4. Recommended Components
CHOICEPART NUMBERMANUFACTURERNOTES
1M830520Ethertronics
Can be placed on edge of the PCB and uses much less PCB
space
The RF signal from the module is routed to the antenna using a Coplanar Waveguide with ground (CPW-G)
structure. CPW-G structure offers the maximum amount of isolation and the best possible shielding to the RF
lines. In addition to the ground on the L1 layer, placing GND vias along the line also provides additional
shielding.
Figure 10-7 shows a cross section of the coplanar waveguide with the critical dimensions.
Figure 10-8 shows the top view of the coplanar waveguide with GND and via stitching.
Figure 10-7. Coplanar Waveguide (Cross Section)
Figure 10-8. CPW With GND and Via Stitching (Top View)
11 Environmental Requirements and SMT Specifications
11.1 PCB Bending
The PCB follows IPC-A-600J for PCB twist and warpage < 0.75% or 7.5 mil per inch.
11.2 Handling Environment
11.2.1 Terminals
The product is mounted with motherboard through land-grid array (LGA). To prevent poor soldering, do not make
skin contact with the LGA portion.
11.2.2 Falling
The mounted components will be damaged if the product falls or is dropped. Such damage may cause the
product to malfunction.
11.3 Storage Condition
11.3.1 Moisture Barrier Bag Before Opened
A moisture barrier bag must be stored in a temperature of less than 30°C with humidity under 85% RH. The
calculated shelf life for the dry-packed product will be 24 months from the date the bag is sealed.
11.3.2 Moisture Barrier Bag Open
Humidity indicator cards must be blue, < 30%.
11.4 PCB Assembly Guide
The wireless MCU modules are packaged in a substrate base Leadless Quad Flatpack (QFM) package.
Components were mounted onto the substrate with standard SMT process with the additional of a metal lid
covering the top of the module. The module are designed with pull back leads for easy PCB layout and board
mounting.
11.4.1 PCB Land Pattern & Thermal Vias
We recommended a solder mask defined land pattern to provide a consistent soldering pad dimension in order
to obtain better solder balancing and solder joint reliability. PCB land pattern are 1:1 to module soldering pad
dimension. Thermal vias on PCB connected to other metal plane are for thermal dissipation purpose. It is critical
to have sufficient thermal vias to avoid device thermal shutdown. Recommended vias size are 0.2mm and
position not directly under solder paste to avoid solder dripping into the vias.
11.4.2 SMT Assembly Recommendations
The module surface mount assembly operations include:
•Screen printing the solder paste on the PCB
•Monitor the solder paste volume (uniformity)
•Package placement using standard SMT placement equipment
•X-ray pre-reflow check - paste bridging
•Reflow
•X-ray post-reflow check - solder bridging and voids
A uniform PCB plating thickness is key for high assembly yield. For an electroless nickel immersion gold finish,
the gold thickness should range from 0.05 µm to 0.20 µm to avoid solder joint embrittlement. Using a PCB with
Organic Solderability Preservative (OSP) coating finish is also recommended as an alternative to Ni-Au.
11.4.4 Solder Stencil
Solder paste deposition using a stencil-printing process involves the transfer of the solder paste through predefined apertures with the application of pressure. Stencil parameters such as aperture area ratio and the
fabrication process have a significant impact on paste deposition. Inspection of the stencil prior to placement of
package is highly recommended to improve board assembly yields.
11.4.5 Package Placement
Packages can be placed using standard pick and place equipment with an accuracy of ±0.05 mm. Component
pick and place systems are composed of a vision system that recognizes and positions the component and a
mechanical system that physically performs the pick and place operation. Two commonly used types of vision
systems are:
•A vision system that locates a package silhouette
•A vision system that locates individual pads on the interconnect pattern
The second type renders more accurate placements but tends to be more expensive and time consuming. Both
methods are acceptable since the parts align due to a self-centering features fo the solder joint during solder
reflow. It is recommended to release the package to 1 to 2 mils into the solder paste or with minimum force to
avoid causing any possible damage to the thinner packages.
11.4.6 Solder Joint Inspection
After surface mount assembly, transmission X-ray should be used for sample monitoring of the solder
attachment process. This identifies defects such as solder bridging, shorts, opens, and voids. It is also
recommended to use side view inspection in addition to X-rays to determine if there are "Hour Glass" shaped
solder and package tilting existing. The "Hour Glass" solder shape is not a reliable joint. 90° mirror projection can
be used for side view inspection.
11.4.7 Rework and Replacement
TI recommends removal of modules by rework station applying a profile similar to the mounting process. Using a
heat gun can sometimes cause damage to the module by overheating.
11.4.8 Solder Joint Voiding
TI recommends to control solder joint voiding to be less than 30% (per IPC-7093). Solder joint voids could be
reduced by baking of components and PCB, minimized solder paste exposure duration, and reflow profile
optimization.
•Heating method: Conventional convection or IR convection
•Temperature measurement: Thermocouple d = 0.1 mm to 0.2 mm CA (K) or CC (T) at soldering portion or
equivalent method
•Solder paste composition: SAC305
•Allowable reflow soldering times: 2 times based on the reflow soldering profile (see Figure 11-1)
•Temperature profile: Reflow soldering will be done according to the temperature profile (see
Figure 11-1)
•Peak temperature: 260°C
Figure 11-1. Temperature Profile for Evaluation of Solder Heat Resistance of a Component (at Solder
Joint)
Table 11-1. Temperature Profile
Profile ElementsConvection or IR
Peak temperature range235 to 240°C typical (260°C maximum)
Pre-heat / soaking (150 to 200°C)60 to 120 seconds
Time above melting point60 to 90 seconds
Time with 5°C to peak30 seconds maximum
Ramp up< 3°C / second
Ramp down< -6°C / second
(1)For details, refer to the solder paste manufacturer's recommendation.
(1)
Note
TI does not recommend the use of conformal coating or similar material on the SimpleLink™ module.
This coating can lead to localized stress on the solder connections inside the module and impact the
module reliability. Use caution during the module assembly process to the final PCB to avoid the
presence of foreign material inside the module.
TI offers and extensive line of development tools. Tools and software to evaluate the performance of the device,
generate code, and develop solutions are listed in this section.
12.1 Development Tools and Software
For the most up to date list of Development Tools and Software, visit the CC3235MOD tools and software page.
Or, click on the Alert me button in the top-right corner of the page, to stay informed of updates related to the
CC3235MOD.
Pin Mux Tool
SimpleLink™ Wi-Fi
®
Starter Pro
SimpleLink™ CC32XX
Software Development
Kit (SDK)
The supported devices are: CC3200, CC3220x, and CC3235x.
The Pin Mux Tool is a software tool that provides a graphical user interface (GUI) for
configuring pin multiplexing settings, resolving conflicts and specifying I/O cell
characteristics for MPUs from TI. Results are output as C header/code files that can
be imported into software development kits (SDKs) or used to configure customers'
custom software. Version 3 of the Pin Mux Tool adds the capability of automatically
selecting a mux configuration that satisfies the entered requirements.
The supported devices are: CC3100, CC3200, CC3120R, CC3220x, CC3135, and
CC3235x.
The SimpleLink™ Wi-Fi® Starter Pro mobile App is a new mobile application for
SimpleLink™ provisioning. The app goes along with the embedded provisioning
library and example that runs on the device side (see SimpleLink™ Wi-Fi® SDK
plugin and TI SimpleLink™ CC32XX Software Development Kit (SDK)). The new
provisioning release is a TI recommendation for Wi-Fi® provisioning using
SimpleLink™ Wi-Fi® products. The provisioning release implements advanced AP
mode and SmartConfig™ technology provisioning with feedback and fallback options
to ensure successful process has been accomplished. Customers can use both
embedded library and the mobile library for integration to their end products.
The CC3235x devices are supported.
The SimpleLink™ CC32XX SDK contains drivers for the CC3235 programmable
MCU, more than 30 sample applications, and documentation needed to use the
solution. It also contains the flash programmer, a command line tool for flashing
software, configuring network and software parameters (SSID, access point channel,
network profile, BS NIEW), system files, and user files (certificates, web pages, and
more). This SDK can be used with TI’s SimpleLink™ Wi-Fi® CC3235 LaunchPad™
development kits.
Uniflash Standalone
Flash Tool for TI
Microcontrollers (MCU),
Sitara Processors &
SimpleLink Devices
The supported devices are: CC3120R, CC3220x, CC3135, and CC3235x.
CCS Uniflash is a standalone tool used to program on-chip flash memory on TI
MCUs and on-board flash memory for Sitara™ processors. Uniflash has a GUI,
command line, and scripting interface. CCS Uniflash is available free of charge.
The supported devices are: CC3100, CC3200, CC3120R, CC3220, CC3135, and
CC3235x.
The SimpleLink™ Wi-Fi® Radio Testing Tool is a Windows-based software tool for
RF evaluation and testing of SimpleLink™ Wi-Fi® CC3x20 and CC3x35 designs
during development and certification. The tool enables low-level radio testing
capabilities by manually setting the radio into transmit or receive modes. Using the
tool requires familiarity and knowledge of radio circuit theory and radio test methods.
Created for the internet-of-things (IoT), the SimpleLink™ Wi-Fi® CC31xx and
CC32xx family of devices include on-chip Wi-Fi®, Internet, and robust security
protocols with no prior Wi-Fi® experience needed for faster development. For more
information on these devices, visit SimpleLink™ Wi-Fi® family, Internet-on-a chip™
solutions.
UniFlash Standalone
Flash Tool for TI
Microcontrollers (MCU),
CCS UniFlash is a standalone tool used to program on-chip flash memory on TI
MCUs and on-board flash memory for Sitara™ processors. UniFlash has a GUI,
command line, and scripting interface. CCS UniFlash is available free of charge.
Sitara™ Processors
and SimpleLink™
Devices
12.2 Firmware Updates
TI updates features in the service pack for this module with no published schedule. Due to the ongoing changes,
TI recommends users have the latest service pack in their module for production.
To stay informed, sign up for updates using the SDK Alert me button in the top-right corner of the product page,
or visit http://www.ti.com/tool/download/SIMPLELINK-CC32XX-SDK.
12.3 Device Nomenclature
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of the
CC3235MODx and CC3235MODAx and support tools (see Figure 12-1).
To designate the stages in the product development cycle, TI assigns prefixes to the part numbers of all
microprocessors (MPUs) and support tools. Each device has one of three prefixes: X, P, or null (no prefix) (for
example, CC3235MODxandCC3235MODAx). 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 (TMDX) through fully qualified production devices and tools (TMDS).
Device development evolutionary flow:
XExperimental device that is not necessarily representative of the final device's electrical specifications and
PPrototype device that is not necessarily the final silicon die and may not necessarily meet final electrical
null Production version of the silicon die that is fully qualified.
Support tool development evolutionary flow:
TMDX Development-support product that has not yet completed Texas Instruments internal qualification testing.
Transfer of TI's Wi-Fi® Alliance
Certifications to Products Based
on SimpleLink™
Using Serial Flash on SimpleLink™
CC3135 and CC3235 Wi-Fi® and
Internet-of-Things Devices
CC3135 and CC3235 SimpleLink Wi-Fi Embedded Programming User
Guide
This application report describes the best practices for power
management and extended battery life for embedded low-power Wi-Fi
devices such as the SimpleLink Wi-Fi Internet-on-a chip solution from
Texas Instruments.
The SimpleLink Wi-Fi CC31xx and CC32xx Internet-on-a chip family of
devices from Texas Instruments offer a wide range of built-in security
features to help developers address a variety of security needs, which is
achieved without any processing burden on the main microcontroller
(MCU). This document describes these security-related features and
provides recommendations for leveraging each in the context of
practical system implementation.
This document describes the OTA library for the SimpleLink Wi-Fi
CC3x35 family of devices from Texas Instruments and explains how to
prepare a new cloud-ready update to be downloaded by the OTA library.
This guide describes the provisioning process, which provides the
SimpleLink Wi-Fi device with the information (network name, password,
and so forth) needed to connect to a wireless network.
This document explains how to employ the Wi-Fi® Alliance (WFA)
derivative certification transfer policy to transfer a WFA certification,
already obtained by Texas Instruments, to a system you have
developed.
This application note is divided into two parts. The first part provides
important guidelines and best- practice design techniques to consider
when choosing and embedding a serial Flash paired with the CC3135
and CC3235 (CC3x35) devices. The second part describes the file
system, along with guidelines and considerations for system designers
working with the CC3x35 devices.
More Literature
CC3235MODx SimpleLink™ Wi-Fi® and Internet-of-Things Hardware Design Files
CC3220MODAx SimpleLink™ Wi-Fi® and Internet-of-Things Hardware Design Files
CC3x35x SimpleLink™ Wi-Fi® and Internet-of-Things Design Checklist