NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs

From Texas Instruments Wiki
Jump to: navigation, search

A 10-step guide

This is a step by step guide to designing a low power RF product based on the CC26xx/CC13xx family of SimpleLink wireless MCU devices. The goal is to present you with the resources that are relevant at the different stages of design. If you get stuck or have questions anywhere along the line, please post your questions to our e2e forum:

http://e2e.ti.com/support/wireless_connectivity/

Step 1 - Decide on which RF technology you want to use[edit]

  • Bluetooth low energy (BLE) – low power star network with ~100 m range and connectivity to most phones, tablets and computers. Previously known as Bluetooth Smart.
  • Contiki 6LoWPAN – 6LoWPAN is a low-power wireless mesh network where every node has its own IPv6 address, allowing it to connect directly to the Internet using open standards
  • ZigBee – A robust mesh network with sleeping end nodes and standards defined application profiles for vendor interoperability
  • Proprietary – Take advantage or long range (kilometers) or high throughput (up to 5 Mbps) physical layers by writing your own protocol on top of the CC2650 or CC1310/50 very flexible and powerful radio architecture. The TI-RTOS release contains the drivers you need to access hardware features easily and ensure efficient power management:



Step 2 - Buy the relevant development kit[edit]

Step 3 - Download an evaluation tool[edit]



Step 4 - Download a software development environment:[edit]

  • You have several choices for the platform:
  • Download the relevant SDK (software development kit) according to your choice of technology above (follow the associated link to download and install)
  • Read the Bluetooth Low Energy Software Developer’s Guide: SWRU393 Bluetooth Low Energy Software Developer's Guide
  • Read the CC26XX Family SW Quickstart guide for a better understanding of the SW architecture: CC26xx Family SW Quickstart Guide
  • Find the application example that most closely resembles your application
  • Open it in your chosen IDE. The rest of this guide will assume that it’s Code Composer Studio. More details on how to use the SDK, including supported IDE version, are provided in the respective SW Developer’s Guide.
  • Make your own project based on the example. For BLE, there is a tutorial in SimpleLink Academy using Project Zero
  • For BLE proprietary profiles, you should also make the corresponding iOS and Android App



Step 5 - Design the hardware[edit]

  • Consider using a module to reduce development time & cost. Links to module vendors can be found on the BLE Wiki.
  • Based on I/O requirements, RF front-end options and form-factor constraints, choose the right package for your CC26xx/CC13xx device
    • The available package options are found in each device data sheet
  • Order samples of your desired device from TI.com. Example for CC2640:
    • http://www.ti.com/product/CC2640/samplebuy
  • Based on form-factor, desired performance and cost targets, choose a relevant reference design to take as a starting point. The “EM” reference design is designed to be a good starting point for the most common applications. Example for CC2640:
  • Replicate the reference design into your PCB design tool.
  • Make changes and additions to the design based on your application requirements.
  • Think about how you will test and program your product, and make sure you have the required connectors available for that. Skip ahead to the “Production Test” section for details.
  • Send your design to production



Step 6 - Test the hardware[edit]

  • Check the following aspects as a minimum:
    • Power up/down sequence
    • Application functionality
    • Current consumption
    • RF performance
    • RF Standards compliance when relevant (Bluetooth Smart, ZigBee etc. )
    • RF regulations compliance (FCC, ETSI, ARIB) depending on the targeted market regions
    • Remember to test over the full voltage and temperature range of your application
  • Tuning and matching of the RF – compare to the TI reference design performance for a point of comparison
  • If you find bugs or performance below target, re-design and repeat – if in need of advice, please post on the relevant e2e forum

Step 7 – Test the software and application functionality[edit]

  • Test your software running on your hardware – you’re getting close

Step 8 – Certify your product[edit]

Step 9 – Production Test and Programming[edit]

  • Develop your production test solution
    • Test RF performance
    • Test peripheral functionality
    • Test current consumption
  • Program your device with the final program. This can be done by your distributor before mounting the devices on your board, before board production testing or after board production testing.
  • For BLE products, a lot can be tested with PTM mode controlled over UART:
  • More information:



Step 10 – Production[edit]

  • Send your product off to pilot production
  • Start production
  • Sell a lot of them and keep improving the production flow throughout the lifetime of the product.

Don’t hesitate contact us on the e2e forum if you have any questions along the way!

http://e2e.ti.com/support/wireless_connectivity/

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article Designing a Product with SimpleLink CC26xx or CC13xx Wireless MCUs here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity