Start your design with the industry's first programmable FCC, IC/ISED, ETSI/CE, and MIC Certified
SimpleLinkTMWi-Fi® CC3235MOD Dual-Band Wireless Microcontroller Module with built-in DualBand (2.4 GHz and 5 GHz) Wi-Fi®connectivity. Created for the Internet-of-Things (IoT), the SimpleLink™
CC3235MODx family of devices from Texas Instruments™ are wireless modules that integrate two
physically separated, on-chip MCUs:
•An application processor – Arm®Cortex®-M4 MCU with a user-dedicated 256KB of RAM and an
optional 1MB of Serial Flash.
•A network processor MCU to run all Wi-Fi and Internet logic layers. This ROM based subsystem
includes an 802.11 a/b/g/n radio, baseband, and MAC with a powerful crypto engine for fast, secure
internet connections with 256-bit encryption.
The CC3235MODx comes in 2 variants:
•CC3235MODSM2MOB
– Requires an external antenna
•CC3235MODSF12MOB
– Requires an external antenna
– Contains 1MB of Serial Flash
The LAUNCHCC3235MOD is a low-cost evaluation platform for MCUs based on Arm®Cortex®-M4
devices. The LaunchPad™ design highlights the CC3235MODSF fully-integrated industrial module
solution and Dual-Band Wi-Fi capabilities. The LAUNCHCC3235MOD also features temperature and
accelerometer sensors, programmable user buttons, an RBG LED for custom applications, and onboard
emulation for debugging. The stackable headers interface demonstrates how easy it is to expand the
functionality of the LaunchPad when interfacing with other peripherals on existing BoosterPack™ add-on
boards, such as graphical displays, audio codec, antenna selection, environmental sensing, and more.
Figure 1 shows the CC3235MODSF LaunchPad development kit.
4
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
Created for the Internet of Things (IoT), the SimpleLink CC3235MODx is a wireless module with built-in
Dual-Band Wi-Fi connectivity for the LaunchPad ecosystem, which integrates a high-performance Arm
Cortex®-M4 MCU and lets customers develop an entire application with one device. With on-chip Wi-Fi,
Internet, and robust security protocols, no prior Wi-Fi experience is required for fast development.
The CC3235MODSF LaunchPad, referred to by its part number LAUNCHCC3235MOD, is a low-cost
evaluation platform for Arm®Cortex®-M4-based MCUs. The LaunchPad design highlights the
CC3235MODSF Internet-on-a chip solution and Dual-Band Wi-Fi capabilities. The CC3235MODSF
LaunchPad also features temperature and accelerometer sensors, programmable user buttons, an RGB
LED for custom applications, and onboard emulation for debugging. The stackable headers of the
CC3235MODSF LaunchPad XL interface demonstrate how easy it is to expand the functionality of the
LaunchPad when interfacing with other peripherals on many existing BoosterPack add-on boards, such as
graphical displays, audio codecs, antenna selection, environmental sensing, and more. Figure 1 shows
the CC3235MOD LaunchPad.
Multiple development environment tools are also available, including TI’s Eclipse-based Code Composer
Studio™ (CCS) integrated development environment (IDE) and IAR Embedded Workbench®. More
information about the LaunchPad, the supported BoosterPack modules, and the available resources can
be found at TI’s LaunchPad portal.
NOTE: The maximum RF power transmitted in each WLAN 2.4 GHz band is 19 dBm (EIRP power).
The maximum RF power transmitted in each WLAN 5 GHz band is 18.8 dBm (EIRP power).
www.ti.com
®
NOTE: The antennas used for this transmitter must be installed to provide a separation distance of
at least 20 cm from all persons, and must not be colocated or operating in conjunction with
any other antenna or transmitter.
6
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The LAUNCHCC3235MOD SimpleLink LaunchPad includes the following features:
•CC3235MODSF, SimpleLinkTMDual-Band Wi-Fi®module solution
– Integrated MCU
– 40.0-MHz Crystal
– 32.768-kHz Crystal (RTC)
– 32-Mbit SPI Serial Flash
– RF and Full Power-Management Components
•40-pin LaunchPad standard that leverages the BoosterPack ecosystem
•TI standard, XDS110-based JTAG emulation with serial port for flash programming
•Supports 4-wire JTAG and 2-wire SWD
•Two buttons and one RGB LED for user interaction
•Back-channel universal asynchronous receiver/transmitter (UART) through USB to PC
•Onboard chip antenna with U.FL for conducted testing selectable using 0-Ω resistors
•Onboard accelerometer and temperature sensor for out-of-box demo with option to isolate the sensors
from the inter-integrated circuit (I2C) bus
•Micro-USB connector for power and debug connections
•Headers for current measurement and external JTAG connection (option to use the onboard XDS110
to debug customer platforms)
•Bus-powered device with no external power required for Wi-Fi
•Long-range transmission with highly optimized antenna (200 m typical in open air using an access
point with 6-dBi antenna AP)
•Can be powered externally, with two AA or two AAA alkaline batteries working down to 2.3-V typical
•Dimensions: 106.1 mm (L) × 58.42 mm (W)
Introduction
1.3What's Included
1.3.1Kit Contents
•CC3235MODSF LaunchPad development tool (LAUNCHCC3235MOD)
•Micro USB cable
•Quick start guide
1.3.2Software Examples
•Out-of-Box Experience (OOBE) Software
1.4REACH Compliance
In compliance with the Article 33 provision of the EU REACH regulation we are notifying you that this
EVM includes component(s) containing at least one Substance of Very High Concern (SVHC) above
0.1%. These uses from Texas Instruments do not exceed 1 ton per year. The SVHC’s are:
Certifications in Process
Indoor Usage Restrictions:
The device is restricted to indoor use only when operating in the 5150 to 5350 MHz frequency range.
An easy way to get started with the EVM is by using its preprogrammed out-of-box experience code. It
demonstrates some key features of the EVM.
1.6.1Connecting to the Computer
Connect the LaunchPad development kit by connecting the included USB cable to a computer. A red
power LED should illuminate. For proper operation, the SimpleLink drivers and Service Pack from the
CC3235 Software Development Kit (SDK) are needed. The SDK is available at
http://www.ti.com/tool/simplelink-cc32xx-sdk.
www.ti.com
1.6.2Running the Out-of-Box Experience
The CC3235MODSF LaunchPad development kit's Out-of-Box Experience (OOBE) demonstrates and
highlights the following features:
•Easy connection to the CC3235MODSF LaunchPad:
– Using the SimpleLinkTMWi-Fi® Starter Pro application (available on iOS and Android™), users can
use Access Point (AP) provisioning or SmartConfig™ provisioning for a fast CC3235MOD
connection.
– Configuring the device in AP mode gives users a direct connection to the CC3235MODSF
LaunchPad.
Once the device is provisioned and connected to an AP in station mode, the profile is stored on the
local file system so that any reset to the CC3235MODSF automatically connects it to the AP.
•Easy access to the CC3235MODSF through its internal web server, using either:
– The SimpleLinkTMWi-Fi® Starter Pro application
– Any browser; web pages stored on the serial flash are loaded on the browser, to provide ease of
use.
This feature demonstrates configuring and reading onboard sensors.
•Over-The-Air (OTA) updates that demonstrate an update of a full image. OTA service enables insystem updates of the MCU application, CC3235 firmware releases (Service Pack) made available by
TI, and other vendor files. An update procedure executed in a full-system integrity fashion, such as
failure to upgrade any image components, results in rolling back to the previous valid version.
Visit the CC3235 LaunchPad Out-of-Box Experience Guide on SimpleLink Academy (see Section 6.3) for
more details.
1.7Next Steps: Looking into the Provided Code
After the EVM features have been explored, the user can open an integrated development environment
and start editing the code examples from the SDK. See Section 6.2 for available IDEs and where to
download them. The Out-of-Box source code and more code examples are provided in the CC3235 SDK.
Code is licensed under BSD, and TI encourages reuse and modifications to fit specific needs.
8
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
With the onboard XDS110 debug probe, debugging and downloading new code is simple. A USB
connection between the EVM and a PC through the provided USB cable is all that is needed.
1.8Trademarks
SimpleLink, Texas Instruments, LaunchPad, BoosterPack, Code Composer Studio are trademarks of
Texas Instruments.
Arm, Cortex are registered trademarks of Arm Limited.
IAR Embedded Workbench is a registered trademark of IAR Systems AB.
WPA, WPA2 are trademarks of Wi-Fi Alliance.
Wi-Fi, Wi-Fi Direct are registered trademarks of Wi-Fi Alliance.
All other trademarks are the property of their respective owners.
Introduction
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
To keep development easy and cost effective, TI's LaunchPad development kits integrate an onboard
debug probe, which eliminates the need for expensive programmers. The CC3235MODSF LaunchPad
has the XDS-110-based debug probe (see Figure 5), which is a simple and low-cost debugger that
supports nearly all TI Arm device derivatives.
Figure 5. XDS-110 Debug Probe
www.ti.com
16
The dotted line through J101 shown in Figure 5 divides the XDS110 debug probe from the target area.
The signals that cross this line can be disconnected by jumpers on J101, the isolation jumper block. More
details on the isolation jumper block are in Section 2.2.3.
The XDS110 debug probe also provides a "backchannel" UART-over-USB connection with the host, which
can be very useful during debugging and for easy communication with a PC. More details can be found in
Section 2.2.4.
The XDS110 debug probe hardware can be found in the schematics in Section 7.2 and in the
CC3235MOD LaunchPad hardware design files.
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The isolation jumper block at jumper J101 allows the user to connect or disconnect signals that cross from
the XDS110 domain into the CC3235MOD target domain. This includes JTAG signals, application UART
signals, and 3.3-V and 5-V power.
Reasons to open these connections:
•To remove any and all influence from the XDS110 debug probe for high accuracy target power
measurements
•To control 3-V and 5-V power flow between the XDS110 and target domains
•To expose the target MCU pins for other use than onboard debugging and application UART
communication
•To expose the programming and UART interface of the XDS110 so that it can be used for devices
other than the onboard MCU.
Table 1. Isolation Block Connections
JumperDescription
BRDBoard Power. Supplies the board power from the onboard DC-DC converter. The board power
includes the sensors, LED, and the OPAMP used to drive the ADC input.
GNDGround reference
5V5-V VBUS from USB
VBAT3.3-V rail, derived from VBUS in the XDS110 domain. Can also be used to measure the current
flowing into the CC3235MOD.
RXBackchannel UART: The target CC3235MODSF receives data through this signal.
TXBackchannel UART: The target CC3235MODSF sends data through this signal.
RSTThis pin functions as the RST signal (active low).
TMSSerial wire data input (SWDIO) / JTAG test mode select (TMS)
TCKSerial wire clock input (SWCLK) / JTAG clock input (TCK)
TDOJTAG test data out
TDIJTAG test data in
VBUFFERUsed to power the level shifters located on the emulator side of the board. The level shifters can
be powered by shorting this pin with a jumper. Removing the jumper enables low current
measurement.
Hardware
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The board supports a USB-based virtual COM port, using the Tiva™ Arm®MCU. The LaunchPad is
shipped with the UART lines from the CC3235MODSF connected to the UART on the Tiva MCU. The
CC3235MODSF's UART can also be routed to the 20-pin connector for use as a GPIO or external UART.
The selection is performed using jumpers on the board.
Figure 6 shows the UART routed to USB COM port. Ensure that a jumper is also placed on the VBUFFER
header to power the level shifters located on the emulator side of the board. Figure 7 shows the UART
routed to 20-pin header connector.
Figure 6. UART Routed to USB COM Port
www.ti.com
Figure 7. UART Routed to 20-Pin Header Connector
18
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The headers are provided on the board to isolate the CC3235MOD from the onboard XDS110-based
JTAG emulator. These jumpers are shorted by default when the board is shipped from TI. Figure 5 and
Table 1 are for default configurations, and Figure 8 shows the external emulator connection. To connect
an external emulator, remove the isolation block JTAG jumpers and place the external emulator on the
JTAG IN connector.
Hardware
Figure 8. JTAG IN Connector (J6)
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
2.2.6Using the XDS110 Debug Probe with a Different Target
The XDS110 debug probe on the LaunchPad development kit can interface to most Arm®Cortex®-M
devices, not just the onboard target CC3235MODSF device. This functionality is enabled by the J2 10-pin
Cortex-M JTAG connector (see Figure 9) and a 10-pin cable, such as the FFSD-05-D-06.00-01-N (sold
separately from the LaunchPad development kit).
Figure 9. XDS110 OUT Connector (J2)
www.ti.com
20
Header J2 follows the Arm®Cortex®-M standard; however, pin 1 is not a voltage sense pin. The XDS110
outputs only 3.3-V JTAG signals. If another voltage level is needed, the user must provide level shifters to
translate the JTAG signal voltages.
1. Remove jumpers on the JTAG signals on the isolation block, including RST, TMS, TCK, TDO, and TDI.
2. Plug the 10-pin cable into J2, and connect to an external target.
a. J2 follows the Arm®Cortex®Debug Connector standard outlined in Cortex-M Debug Connectors.
3. Plug USB power into the LaunchPad development kit, or power it externally
a. JTAG levels are 3.3-V ONLY
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The board accommodates various power methods, including through the onboard XDS110 as well as
external or BoosterPack plug-in module power (see Figure 10).
Figure 10. LAUNCHCC3235MOD Power Block Diagram
Hardware
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The most common power-supply scenario is from USB through the XDS110 debugger. This provides 5-V
power from the USB and also regulates this power rail to 3.3 V for XDS110 operation and 3.3-V to the
target side of the LaunchPad development kit. Power from the XDS110 is controlled by jumper J101.
When the board is powered from the USB connector, ensure that the jumpers are placed on the following
headers, shown in Figure 11.
Figure 11. Powering the CC3235MODSF LP from USB
www.ti.com
22
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
2.2.7.2BoosterPack Plug-in Module and External Power Supply
Headers J19 and J20 are present on the board to supply external power directly when USB power is not
available. Use the following precautions before using the board with an external power supply.
1. Remove the USB cable.
2. Ensure that jumpers are only placed on the headers shown in Figure 12.
3. Use a jumper wire to connect VBAT and BRD.
4. Plug in the external power supply on J20 with the correct polarity.
Figure 12. Powering the CC3235MODSF LP from an External Power Supply
Hardware
The OPAMP EN and LED EN jumpers are also available to remove any current draw from the onboard
OpAmp and LEDs being driven by the GPIOs, see Table 2.
ReferenceUseComments
J195-V power inputUsed to power the board from an external 5-V supply
J203.3-V power inputUsed to power the board from an external 3.3-V supply.
J21OPAMP ENIf uninstalled, the power supply to the operational amplifier is cut off. This can
SWRU548A–February 2019
Submit Documentation Feedback
Table 2. External Supply Connections and Enable Jumpers
be used to enable low-power measurements.
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The board features an accelerometer and a temperature sensor for the out-of-box demo. These are
connected to the I2C bus, and can be isolated using the jumpers provided (shown as yellow jumpers J23
and J24 in Figure 13).
Hardware
Figure 13. I2C Connections
By removing J23 and J24, the accelerometer and the temperature sensors are isolated from the I2C bus.
This measure also removes the I2C pullup resistors from the sensor side of the circuit, and therefore any
connection to the circuit requires the user to install external pullup resistors.
Table 4 lists the I2C jumper definitions.
ReferenceUseComments
J23I2C SCLPopulated: CC3235MOD SCL connected to onboard sensors with pullup
J24I2C SDAPopulated: CC3235MOD SDA connected to onboard sensors with pullup
2.2.10.1Default I2C Addresses
Table 5 lists the default I2C addresses of the onboard sensors.
The CC3235MODx device can be set to operate in four different modes based on the state of the sense
on power (SOP) lines. The SOP lines are pins 23, 24, and 34 on the CC3235MODx module. Table 6
shows the state of the device and Figure 14 shows the SOP jumpers.
SW1RESETThis is used to reset the CC3235MOD device. This signal is also output on the
SW2GPIO_13When pushed, GPIO_13 is pulled to VCC.
SW3GPIO_22When pushed, GPIO_22 is pulled to VCC.
SW4Factory defaultPressing this button and toggling RESET restores the factory default image on
Table 8 lists the LED indicators.
ReferenceColorUseComments
D1,D2Green and RedDebugIndicates the state of the JTAG
D3YellownRESETIndicates the state of the NRESET
D4RedPowerIndicates when the 3.3-V power is
D7RGBGPIO_09Glows when the GPIO is logic-1.
RGBGPIO_10
RGBGPIO_11
D8RedFactory ResetIndicates that the push-button for
(1)
GPIO_10 and GPIO_11 are also used as I2C. Whenever the pullups are enabled, the LEDs glow by default without configuring
the GPIOs.
Hardware
20-pin connector to reset any external BoosterPack which may be stacked. The
reset can be isolated using the RST jumper at the isolation block.
the serial flash. This can be used to recover a corrupted serial flash, provided
the s-flash was programmed with a recovery image.
Table 8. LED Indicators
emulator. For TI use only.
pin. If this LED is on, the device is
functional.
supplied to the board.
(1)
(1)
Glows when the GPIO is logic-1.
Glows when the GPIO is logic-1.
the factory reset is pressed.
2.3Electrical Characteristics
For electrical characteristics of the CC3235MODx modules, see CC3235MODx SimpleLink™ Wi-Fi
CERTIFIED®Dual-Band Wireless MCU Module data sheet.
2.4Antenna Characteristics
The CC3235MODSM2MOB and the CC3235MODSF12MOB reference design detail the use of an onboard antenna. For more information on the antenna VSWR, efficiency, and electrical characteristics, see
M830520.
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The BoosterPack header pinout specification is at Build Your Own BoosterPack. Also see the BoosterPack Pinout Standard.
The CC3235MODSF LaunchPad follows this standard, with the exception of naming. (P1:P4 is used instead of J1:J4.). See Figure 15 for the
CC3235MODSF LaunchPad pin-mapping assignments and functions.
NOTE: RESET output is an open-drain-type output and can only drive the pin low. The pullup ensures that the line is pulled back high when the
button is released. No external BoosterPack can drive this pin low.
All the signals are referred to by the pin number in the SDK; Figure 15 shows the default mappings. Some of the pins are repeated across the
connector. For instance, pin 62 is available on P1 and P4, but only P1 is connected by default. The signal on P4 is marked with an asterisk (*) to
signify that it is not connected by default. The signal can be routed to the pin by using a 0-Ω resistor in the path. For the exact resistor placement,
see the CC3235MODSF SimpleLinkTMWi-Fi®Wireless MCU LaunchPad Board Design Files.
28
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
The integrator of the CC3235MODx modules must comply with the PCB layout recommendations
described in the following subsections to preserve and minimize the risk with regulatory certifications for
FCC, ISED/IC, ETSI/CE, and MIC. Also, TI recommends that customers follow the guidelines described in
this section to achieve similar performance.
3.1LAUNCHCC3235MOD Board Layout
The reference layout consists of a four-layer design. Figure 16 shows the LAUNCHCC3235MOD top layer.
Figure 16. LAUNCHCC3235MOD Top Layer
Layout Guidelines
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
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.
3.3RF 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 20 shows the RF placement and routing of the CC3235MODSF module.
Figure 20. RF Section Layout
Layout Guidelines
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
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 9 provides a summary of the recommended antennas to use with the CC3235MODx
module.
SR NO.GUIDELINES
1Place the antenna on an edge or corner of the PCB.
2Ensure that no signals are routed across the antenna elements on all the layers of the PCB.
3
4
5Ensure that the antenna impedance is 50 Ω because the module is rated to work only with a 50-Ω system.
6In case of printed antenna, ensure that the simulation is performed with the solder mask in consideration.
7Ensure that the antenna has a near omnidirectional pattern.
8
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.
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.
Layout Guidelines
Table 9. Antenna Guidelines
3.5Transmission Line Considerations
The RF signal from the module is routed to the antenna using a Coplanar Waveguide with ground (CPWG) 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 22 shows a cross section of the coplanar waveguide with the critical
dimensions.
Figure 22. Coplanar Waveguide (Cross Section)
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
A compatible BoosterPack can be stacked on top of the LaunchPad using the two, 20-pin connectors. The
connectors do not have a key to prevent the misalignment of the pins or reverse connection. Ensure that
the VCC and 5-V pins are aligned with the BoosterPack header pins. On the CC3235MODSF LaunchPad,
a small white symbol is provided near pin 1 (see Figure 24) to orient all BoosterPacks.
Figure 24. Pin 1 Marking on LaunchPad (3V3 Mark)
Operational Setup and Testing
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
To measure the current draw of the CC3235MOD device using a multimeter, use the VBAT jumper on the
J101 isolation block. The current draw measured in this mode includes only the CC3235MOD device,
Serial Flash, any current drawn through the BoosterPack plug-in module headers. However, if a GPIO of
the CC3235MOD is driving a high current load like the LED, then that is also included in this
measurement.
4.1.1Low-Current Measurement with USB Power (<1 mA)
See the following instructions to measure ultra-low power when powering with a USB cable (see ).
1. Remove the VBAT jumper in the J101 isolation block, and attach an ammeter across this jumper.
2. Consider the effect that the backchannel UART and any circuitry attached to the CC3235MOD may
have on current draw. Consider disconnecting these at the siolation jumper block, or at least consider
their current sinking and sourcing capability in the final measurement.
3. Begin target execution and set the device to low-power modes (LPDS or hibernate).
4. Measure the current. Remember that if the current levels are fluctuating, it may be difficult to get a
stable measurement. It is easier to measure quiescent states.
4.1.2Active Current Measurements
See the following instructions to measure active power.
1. Remove the VBAT jumper (J18).
2. Solder a 0.1-Ω resistor on a wire which can be connected to a voltmeter/oscilloscope. Or, attach a
jumper across J18 so that it can be used with a current probe.
3. Measure the voltage across the resistor using an oscilloscope with a differential probe. For the current
probe, coil the wire around the sensor several times for good sensitivity.
•An ammeter can also be used for this measurement, but the results may be erroneous due to the
switching nature of the current
www.ti.com
38
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
By default, the board ships with the 2.4 GHz and 5 GHz RF signals routed to the onboard chip antenna,
as shown in Figure 25.
Figure 25. Using Onboard Antenna (Default Condition)
Operational Setup and Testing
A U.FL connector J17 provides a way to test in the lab using a compatible cable. Alternatively, trackpads
for an SMA connector J15 are provided onboard to replace the J17 U.FL connector for testing conducted
measurements. A rework must be performed before these connectors can be used; this involves swapping
the position of a resistor. Figure 26 shows the modified board.
Figure 26. Board Modified for External Antenna Connections (Measure 2.4 GHz or 5 GHz)
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
Schematics can be found in Section 7.2.All design files, including schematics, layout, Bill of Materials
(BOM), Gerber files, and documentation are available for download from LAUNCHCC3235MOD.
4.4Software
All design files, including firmware patches, software example projects, and documentation are available
from the CC3235 Software Development Kit. Inside of the SDK, a set of very simple CC3235 code
examples can be found that demonstrates how to use the entire set of CC3235 peripherals. When starting
a new project or adding a new peripheral, these examples serve as a great starting point.
5Development Environment Requirements
The following software examples with the LaunchPad require an integrated development environment
(IDE) that supports the CC3235MOD.
The CC313x and CC323x SimpleLink™ Wi-Fi®Embedded Programming User's Guide has detailed
information about software environment setup with examples. See this document for further details on the
software sample examples.
5.1CCS
CCS 6.0 or higher is required. When CCS is launched, and a workspace directory is chosen, use
Project → Import Existing CCS Eclipse Project. Direct it to the desired demo project directory containing
main.c.
www.ti.com
5.2IAR
IAR 6.70 or higher is required. To open the demo in IAR, choose File → Open → Workspace…, and direct
it to the *.eww workspace file inside the \IAR subdirectory of the desired demo. All workspace information
is within this file.
The subdirectory also has an *.ewp project file; this file can be opened into an existing workspace, using
Project → Add-Existing-Project….
40
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
For more information on the CC3235MOD device, visit the CC3235MOD product page, which includes the
CC3235MODx SimpleLink™ Wi-Fi®Wireless and Internet-of-Things Solution, a Single-Chip Wireless MCU
data sheet and key documents such as the CC32xx SimpleLink™ Wi-Fi® and Internet-of-Things Technical
Reference Manual.
6.2Download CCS, IAR
Although the files can be viewed with any text editor, more can be done with the projects if they are
opened with a development environment such as Code Composer Studio (CCS), IAR, or Energia. CCS
and IAR are each available in a full version, or a free, code-size-limited version. The full out-of-box demo
cannot be built with the free version of CCS or IAR (IAR Kickstart), due to the code-size limit. To bypass
this limitation, a code-size-limited CCS version is provided that has most functionality integrated into a
library. The code built into the library is able to be viewed by the user, but it cannot be edited. For full
functionality, download the full version of either CCS or IAR.
6.3SimpleLink™ Academy for CC3235 SDK
The SimpleLink™ Academy is a collection of curated training modules developed by TI subject matter
experts to help developers get up and running as quickly as possible with a SimpleLink MCU device and
its SDK. The training is delivered using TI Resource Explorer, which offers a powerful cloud-enabled
environment that includes background information, interactive exercises, code snippets, quizzes, and
more.
Experience the SimpleLink™ Academy now using the TI Resource Explorer at dev.ti.com.
Additional Resources
Figure 27. CC32xx SimpleLink™ Academy
6.4TI E2E Community
Search the forums at e2e.ti.com. If you cannot find your answer, post your question to the community!
SWRU548A–February 2019
Submit Documentation Feedback
CC3235MODSF LaunchPad™ Development Kit (LAUNCHCC3235MOD)
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
Changes from Original (February 2019) to A Revision .................................................................................................. Page
•Added last paragraph to Section 1.6.2 ................................................................................................. 8
1The 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.
2RF Function and Frequency Range
The CC3235MODSM2MOB and CC3235MODSF12MOB devices are designed to operate in the WLAN
2.4-GHz and 5-GHz band. The CC3235MODSM2MOB and CC3235MODSF12MOB devices support
the following channels dependent on the region of operation:
•FCC and IC: Ch 1 to 11 (2142 MHz to 2462 MHz) and 36 to 161 (5180 MHz to 5805 MHz)
•EU: Channels 1 through 13 (2142 MHz to 2472 MHz) and 36 to 136 (5180 MHz to 5680 MHz)
•JP: Channels 1 through 13 (2142 MHz to 2472 MHz) and 36 to 136 (5180 MHz to 5680 MHz)
Note that the CC3235MODx devices do not support determination of its region through any external
mechanism. The region is set by the application SW, or at the time of programming of the device. The
end user is unable to change the region of operation at any time.
NOTE: The maximum RF power transmitted in each WLAN 2.4 GHz band is 19 dBm (EIRP power).
The maximum RF power transmitted in each WLAN 5 GHz band is 18.8 dBm (EIRP power).
3FCC and IC Certification and Statement
This device is intended for OEM integrators under the following conditions:
•The antenna must be installed so 20 cm of space is maintained between the antenna and the users.
•The transmitter module may not be colocated with any other transmitter of antenna.
•To comply with FCC and IC regulations limiting maximum RF output power and human exposure to RF
radiation, the maximum antenna gain including cable loss in a mobile exposure condition must not
exceed:
– +2.5 dBi in WLAN 2.4 GHz
– +4.5 dBi in WLAN 5 GHz
In the event that these conditions cannot be met (for example, certain laptop configurations or
colocation with another transmitter), then the FCC and IC authorization is no longer considered valid
and the FCC and IC ID cannot be used on the final product. In these circumstances, the OEM
integrator will be responsible for re-evaluating the end product (including the transmitter) and obtaining
a separate FCC and IC authorization.
3.1FCC
The TI CC3235MODx modules are certified for FCC as a single-modular transmitter. The module is an
FCC-certified radio module 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 must accept any interference received, including interference that may cause undesired
operation of the device.
FCC RF Radiation Exposure Statement:
This equipment complies with FCC radiation exposure limits set forth for an
uncontrolled environment. This equipment should be installed and operated
with a minimum distance of 20 cm between the radiator and your body.
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant
to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. this equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference
to radio communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception, which can
be determined by turning the equipment off and on, the user is encouraged to try to correct the
interference by one or more of the following measures:
•Reorient or relocate the receiving antenna.
•Increase the separation between the equipment and receiver.
•Connect the equipment into an outlet on a circuit different from the one the receiver is connected to.
•Consult the dealer or an experienced radio or TV technician for help.
The antennas listed in Table 12 of this document were verified in the compliance testing. Use only the
antennas listed in Table 12 . A separate approval is required for all other operating configurations,
including different antenna configurations
www.ti.com
CAUTION
3.2CAN ICES-3(B) and NMB-3(B) Certification and Statement
The TI CC3235MODx modules are certified for IC as a single-modular transmitter. The TI CC3235MODx
modules 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 license-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 deus 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 ests
susceptible d'en compromettre lu fonctionnement.
This equipment complies with IC radiation exposure limits set forth for an
uncontrolled environment. This equipment should be installed and operated
with a minimum distance of 20 cm between the radiator and your body.
Déclaration d'exposition aux radiations:
Cut équipement est conforme aux limites d'exposition aux rayonnements IC
établies pour un environnement non contrôlé. Cet équipement doit être installé
et utilisé avec un minimum de 20 cm de distance entre la source de
rayonnement et votre corps.
This radio transmitter (451I-CC3235MOD) has been approved by Industry Canada to operated with the
antenna types listed in Table 12 of this document with the maximum permissible gain indicated. Antenna
types not included in this list, having a gain greater than the maximum gain indicated for that type, are
strictly prohibited for use with this device.
The antennas listed in Table 12 of this document were verified in the compliance testing. Use only the
antennas listed in Table 12 . A separate approval is required for all other operating configurations,
including different antenna configurations.
3.3End Product Labeling
This module is designed to comply with the FCC statement, FCC ID: Z64-CC3220MOD. The host
system using this module must display a visible label indicating the following text:
•Contains FCC ID: Z64-CC3235MOD
This module is designed to comply with the IC statement, IC: 451I-CC3220MOD. 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 JP statement 201-190033. The host system using this module
must display a visible label indicating the following text:
•Contains transmitter module with certificate module 201-190033
FCC and IC Certification and Statement
CAUTION
3.4Device Classifications
Because host devices vary widely with design features and configurations, module integrators shall
reference the following guidelines regarding device classification and simultaneous transmission, and
seek guidance from their preferred regulatory test lab to determine how regulatory guidelines will
impact the device compliance. Proactive management of the regulatory process will minimize
unexpected schedule delays and costs due to unplanned testing activities.
The module integrator must determine the minimum distance required between their host device and
the body of the user. The FCC provides device classification definitions to assist in making the correct
determination. Note that these classifications are guidelines only; strict adherence to a device
classification may not satisfy the regulatory requirement as near-body device design details may vary
widely. The user-preferred test lab will be able to assist in determining the appropriate device category
for the host product and if a KDB or PBA must be submitted to the FCC.
Note, the module that the user is using has been granted modular approval for mobile applications.
Portable applications may require further RF exposure (SAR) evaluations. It is also likely that the host
and module combination will need to undergo testing for FCC Part 15, regardless of the device
classification. The preferred test lab of the user will be able to assist in determining the exact tests
which are required on the host and module combination.
3.5FCC Definitions
Portable: (§2.1093)— A portable device is defined as a transmitting device designed to be used so that
the radiating structures of the device is or are within 20 centimeters of the body of the user.
Mobile: (§2.1091) (b)— A mobile device is defined as a transmitting device designed to be used in other
than fixed locations and to generally be used in such a way that a separation distance of at least 20
centimeters is normally maintained between the transmitter’s radiating structures and the body of
the user or nearby persons. Per §2.1091d(d)(4) In some cases (for example, modular or desktop
transmitters), the potential conditions of use of a device may not allow easy classification of that
device as either Mobile or Portable. In these cases, applicants are responsible for determining
minimum distances for compliance for the intended use and installation of the device based on
evaluation of either specific absorption rate (SAR), field strength, or power density, whichever is
most appropriate.
3.6Simultaneous Transmission Evaluation
This module has not been evaluated or approved for simultaneous transmission as it is impossible to
determine the exact multi-transmission scenario that a host manufacturer may choose. Any
simultaneous transmission condition established through module integration into a host product must
be evaluated per the requirements in KDB447498D01(8) and KDB616217D01,D03 (for laptop,
notebook, netbook, and tablet applications).
These requirements include, but are not limited to:
•Transmitters and modules certified for mobile or portable exposure conditions can be incorporated in
mobile host devices without further testing or certification when:
– The closest separation among all simultaneous transmitting antennas is > 20 cm
or
– Antenna separation distance and MPE compliance requirements for ALL simultaneous transmitting
antennas have been specified in the application filing of at least one of the certified transmitters
within the host device. In addition, when transmitters certified for portable use are incorporated in a
mobile host device, the antennas must be > 5 cm from all other simultaneous transmitting antennas
•All antennas in the final product must be at least 20 cm from users and nearby persons.
www.ti.com
4EU Certification and Statement
4.1RF Exposure Information (MPE)
This device has been tested and meets applicable limits for Radio Frequency (RF) exposure. To comply
with the RF exposure requirements, this module must be installed in a host platform that is intended to be
operated in a minimum of 20-cm separation distance to the user.
4.2Simplified DoC Statement
4.2.1CC3235MODx
Hereby, Texas Instruments declares that the radio equipment type CC3235MODSM2MOB and
CC3235MODSF12MOB are in compliance with Directive 2014/53/EU.
The full text of the EU declarations of conformity are available at:
•CC3220MODSM2MOB EC Declaration of Conformity (DoC)
•CC3220MODSF12MOB EC Declaration of Conformity (DoC)
•CC3220MODASM2MON EC Declaration of Conformity (DoC)
•CC3220MODASF12MON EC Declaration of Conformity (DoC)
4.2.2LAUNCHCC3235MOD
Hereby, Texas Instruments declares that the radio equipment type LAUNCHCC3235MOD is in compliance
with Directive 2014/53/EU.
The full text of the EU declaration of conformity are available at LAUNCHCC3220MODASF EC
This symbol means that according to local laws and regulations your
product and/or battery shall be disposed of separately from household
waste. When this product reaches its end of life, take it to a collection point
designated by local authorities. Proper recycling of your product will protect
human health and the environment.
www.ti.com
4.3Waste Electrical and Electronic Equipment (WEEE)
4.4OEM and Host Manufacturer Responsibilities
OEM and host manufacturers are ultimately responsible for the compliance of the host and module. The
final product must be reassessed against all of the essential requirements of the RED before it can be
placed on the EU market. This includes reassessing the transmitter module for compliance with the radio
and EMF essential requirements of the RED. This module must not be incorporated into any other device
or system without retesting for compliance as multi-radio and combined equipment.
4.5Antenna Specifications
In all cases, assessment of the final product must be met against the Essential requirements of RE
Directive Article 3.1(a) and (b), safety and EMC respectively, as well as any relevant Article 3.3
requirements.
1. The antennas listed in Table 12 were verified in the conformity testing, and for compliance the antenna
shall not be modified. A separate approval is required for all other operating configurations, including
different antenna configurations.
2. If any other simultaneous transmission radio is installed in the host platform together with this module,
or above restrictions cannot be kept, a separate RF exposure assessment and CE equipment
certification is required.
TI PROVIDES TECHNICAL AND RELIABILITY DATA (INCLUDING DATASHEETS), DESIGN RESOURCES (INCLUDING REFERENCE
DESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND OTHER RESOURCES “AS IS”
AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION ANY
IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRD
PARTY INTELLECTUAL PROPERTY RIGHTS.
These resources are intended for skilled developers designing with TI products. You are solely responsible for (1) selecting the appropriate
TI products for your application, (2) designing, validating and testing your application, and (3) ensuring your application meets applicable
standards, and any other safety, security, or other requirements. These resources are subject to change without notice. TI grants you
permission to use these resources only for development of an application that uses the TI products described in the resource. Other
reproduction and display of these resources is prohibited. No license is granted to any other TI intellectual property right or to any third
party intellectual property right. TI disclaims responsibility for, and you will fully indemnify TI and its representatives against, any claims,
damages, costs, losses, and liabilities arising out of your use of these resources.
TI’s products are provided subject to TI’s Terms of Sale (www.ti.com/legal/termsofsale.html) or other applicable terms available either on
ti.com or provided in conjunction with such TI products. TI’s provision of these resources does not expand or otherwise alter TI’s applicable
warranties or warranty disclaimers for TI products.