This application demonstrates the out-of-box (OOB) experience with the CC3220 LaunchPad™ Development Kit from Texas Instruments™.
The CC3220 device is part of the SimpleLink™ microcontroller (MCU) platform which consists of Wi-Fi®, Bluetooth® low energy, Sub-1 GHz and host MCUs, which all share a common, easy-to-use development environment with a single core software development kit (SDK) and rich tool set. A one-time integration of the SimpleLink platform enables you to add any combination of the portfolio’s devices into your design, allowing 100 percent code reuse when your design requirements change. For more information, visit www.ti.com/simplelink.
LaunchPad, Texas Instruments, SimpleLink, SmartConfig, Code Composer Studio are trademarks of Texas Instruments.
Bluetooth is a registered trademark of Bluetooth SIG, Inc.
iOS is a trademark of Cisco.
Android is a trademark of Google, Inc.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
All other trademarks are the property of their respective owners.
The CC3220 device is part of the SimpleLink™ microcontroller (MCU) platform which consists of Wi-Fi®, Bluetooth® low energy, Sub-1 GHz and host MCUs, which all share a common, easy-to-use development environment with a single core software development kit (SDK) and rich tool set. A one-time integration of the SimpleLink platform enables you to add any combination of the portfolio’s devices into your design, allowing 100 percent code reuse when your design requirements change. For more information, visit www.ti.com/simplelink.
This application demonstrates the out-of-box (OOB) experience with the CC3220 LaunchPad Development Kit from Texas Instruments. The following features are highlighted.
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 CC3220 automatically connects it to the AP.
This feature demonstrates configuring and reading onboard sensors.
This guide is intended for two types of audiences:
This guide is structured chronologically starting with required downloads and installations, then building the setup, flashing the OOB image, and finally experiencing the demo.