-
Notifications
You must be signed in to change notification settings - Fork 1
Board: CC2650STK
The CC2650STK is an 'IoT kit' with 10 sensors, a fancy case, and a radio unit that is capable of irradiating IEEE802.15.4 and BLE (or SMART or whatever they call it now).
- Official homepage
- Another official homepage
- Platform <- CPU data sheet here
Use BOARD=cc2650stk
for building RIOT for this platform.
MCU | CC2650f128 |
---|---|
Family | ARM Cortex-M3 |
Vendor | Texas Instruments |
RAM | 20KB |
Flash | 128KB |
Frequency - Standby | 31.26kHz, 32kHz or 32.768kHz |
Frequency - Active / Idle | 48MHz |
RF core | ARM Cortex-M0 CPU, 4KB RAM |
Timers | 4x 32-bit |
ADCs | 1x 12-bit (8 channels) |
UARTs | 2 |
SPIs | 2 |
I2C | 1 |
I2S | 1 |
Datasheet | Datasheet |
Reference Manual | Reference Manual |
It's an ongoing process...
Module | Status | |
---|---|---|
Cortex-M3 | Partial support | Missing: energy saving features |
UART | OK | |
LEDS | OK | |
Hardware buttons | OK | |
Timers | Unstable | See #5631 |
RF core | Work in progress | See here. |
The arm-none-eabi toolchain works fine. You can get it here.
You'll need debugging hardware.
So far, the XDS110 debug probe has been tested. That bugger requires you to load a firmware onto it each time it powers up. The tool is contained in the Uniflash utility or the CodeComposer Studio
from TI. Look for a folder called uscif
in the installation directory, go to the folder xds110
therein, and follow the instructions in the ReadMe.txt
.
The process is relying on proprietary TI softsoftware. If you're on Windows you can use the stuff linked to on the product websites.
On Linux, there's an application called Uniflash. Sadly, you'll have to install the whole IDE just to get the scripting interface :-[
No idea about MacOSX.
In order to flash the CC2650STK you need to plug the XDS110 probe through the JTAG and so-called "DevPack" connectors. Note that the back of the SensorTag case has a removable plastic cut-out: as a result the XDS110 can be used while the CC2650STK is still protected in its case. For the flashing process to be successful, the CC2650STK needs to be powered by a working battery.
Once your application code has compiled, you need to indicate the path to your UniFlash tool. You can do it in two ways:
-
Add
export UNIFLASH_PATH = your_path
toboards/cc2650stk/Makefile.include
and then runmake BOARD=cc2650stk flash
-
Use the command
make BOARD=cc2650stk UNIFLASH_PATH=your_path flash
to flash the board. If you're lazy you can create an alias to do it with the following command:alias cc2650stkmake='make BOARD=cc2650stk UNIFLASH_PATH=your_path flash'
In both cases you can add term
at the end of the make
command to enter the pyterm console directly. After the board has been flashed, it needs to be manually reset using the reset button on the XDS110 probe.
RIOT - The friendly Operating System for the Internet of Things
Homepage | [GitHub] (https://github.com/RIOT-OS/) | Developers Mailing List | Users Mailing List | Twitter @RIOT_OS
- Family: ARM
- Board: Airfy Beacon
- Board: Arduino Due
- Board: CC2538DK
- Board: CC2650STK
- Board: HikoB Fox
- Board: IoT LAB M3
- Board: LimiFrog-v1
- Board: mbed_lpc1768
- Board: MSB-IoT
- Board: MSBA2
- Board: Nucleo-L1
- Board: Nucleo-F334
- Board: Nucleo-F303
- Board: Nucleo-F091
- Board: Mulle
- Board: OpenMote
- Board: PCA1000x (nRF51822 Development Kit)
- Board: Phytec phyWAVE-KW22
- Board: RFduino
- Board: SAMR21-xpro
- Board: SAML21-xpro
- Board: Spark Core
- Board: STM32F0discovery
- Board: STM32F3discovery
- Board: STM32F4discovery
- Board: UDOO
- Board: yunjia-nrf51822
- Board: Zolertia remote
- Family: ATmega
- Board: Arduino Mega2560
- Family: MSP430
- Board: MSB-430H
- Board: TelosB
- Board: WSN430
- Board: Zolertia Z1
- Board: eZ430-Chronos
- Family: native
- Board: native
- Family: x86
- Board: Intel Galileo