Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

RemoTI-2.0.0-CC2650RC

From Texas Instruments Wiki
Jump to: navigation, search

The CC2650RC remote control contains a multi-standard 2.4GHz CC2650 wireless MCU. Out of the box, the CC2650RC is loaded with a dual-image Bluetooth Low Engery demo as described in the CC2650RC User's Guide. The following sections are intended to get you started with RF4CE using RemoTI 2.0 on the CC2650RC remote control.

Included with the CC2650RC development kit is an RF enabled remote control using a CC2650 and a DevPack emulator used for flashing and debugging. In RF4CE terminology, the remote control is the controller. To get started quickly, the RF4CE target used in this guide is a CC2531EMK USB dongle as it's quickly flashed and debugged easily using a CC Debugger. For more information on RF4CE development, please see the RemoTI Developer's Guide.

Software Prerequisites

  1. Install the development toolchain of your choice. The following IDEs are supported:
  2. Install RemoTI 2.0.1
    • The RemoTI 2.0.1 installer includes all product dependencies (such as TI-RTOS).
    • RemoTI 2.0.1 follows the general high level software overview as described in the CC26xx Family SW Quickstart guide.
    • While not required, it's recommended to use the default installation directory paths:
    For RemoTI 2.0.1: C:\ti\simplelink
    For TI-RTOS 2.x: C:\ti
  3. Install SmartRF Flash Programmer
    • Flash Programmer is used to program pre-built .hex files onto the CC2531 USB dongle

Starting the CC2650RC remote control example

Using CCS

1. Open CCS and select/create a workspace. A "workspace" in context of CCS is a root directory in which one can store one or more CCS projects. In this example, we'll call it myworkspace.

Myworkspace.png

2. Every time CCS starts up it performs a product discovery in the default installation directory. For Windows users, the default installation directory is C:/ti. In this step, it is important that the newly installed TI-RTOS and XDCTools products (which were included with the RemoTI 2.0.1 installer) are discovered by CCS. After the discovery process, CCS will prompt for a restart.

Product discovery.png

3. After restarting CCS, the next step is to Import the example projects included with Remo TI 2.0.1. Select both cc2650rc_app and the cc2650rc_stack CCS projects. In order for the remote control application to work, both application and stack projects need to be flashed to the device.

Import ccs project.png
Select cc2650rc projects.png

4. The next step is to build the imported projects. Select the cc2650rc_stack project and click on Hammer.png. Observe that the project builds without any errors in the Console window. Repeat these steps with the cc2650rc_app project.

Building each project.png

5. With both projects built, the next step is to load each image (.out) file onto the target. Select the cc2650rc_stack project and click on Bug.png. This project does not have a main(), so CCS (and IAR) will complain that it can't run to the main symbol. This is OK. After loading the stack, terminate the debug session CCS Stop.png and repeat the debug steps for the cc2650rc_app project.

At main.png

Using IAR

1. Open IAR 7.70.2 and open an IAR workspace.

Open workspace iar remoti.png

2. Navigate and open the IAR remote_control workspace included with RemoTI 2.0.1

Remote control workspace iar.png

3. Build both projects in the workspace. Select the cc2650rc_stack - controller_rom project and click on Make IAR RemoTI.png. Observe that the project builds without any errors in the Build output window. Repeat these steps with the cc2650rc_app - controller project.

Building each project iar.png

4. With both projects built, the next step is to load each image (.out) file onto the target. Select the cc2650rc_stack - controller_rom project and click on Debug iar.png. This project doesn't not have a main(), so IAR (and CCS) will complain that it can't run to the main symbol. That is OK. After loading the stack, terminate the debug session Stop iar.png and repeat the debug steps for the cc2650rc_app - controller project.

At main iar.png

Programming CC2531 USB Dongle as a RF4CE target

To quickly emulate a RF4CE target, RemoTI 2.0.1 includes pre-built .hex files that can be easily flashed onto a CC2531 USB dongle. To support voice over RF4CE, load C:\ti\simplelink\rti_sdk_2_00_01_15\examples\hex\zrc_audio_cc2531_dongle_sbl.hex using SmartRF Flash Programmer. Note! We want to program a CC25xx device so we need to use the original SmartRF Flash Programmer, not SmartRF Flash Programmer 2.

Instructions on how to program the CC2531 USB dongle can be found here.

Using the example

This section requires the CC2650RC and the CC2531 to have been programmed as described in the previous two sections Starting the CC2650RC remote control example and Programming CC2531 USB Dongle as a RF4CE target.

Buttons and LEDs on the CC2531USB Dongle

Button S1: Press Button S1 to allow bind requests
Button S2: Press Button S2 to perform a cold start

During voice streaming either LED1 or LED2 blinks.

LED2 (Green): Blinking indicates voice data is successfully being transferred from the dongle to the operating system. LED2 on indicates dongle is bonded with a controller.
LED1 (Red): Blinking indicates voice data is not being transferred from the dongle to the operating system. LED1 blinking indicates it has enabled bond requests. LED1 will also blink whenever a ZRC report is sent.

CC2540USB Dongle Buttons.jpg

Bind/Pair the CC2650RC

Start the bonding process by pushing button S1 on the target and the "Pair" button on the controller.

Sending ZRC reports

After the bonding process, LED2 (Green) on the CC2531 dongle will turn on. Pushing various keys on the remote will briefly toggle the dongle's LED1 (Red) indicating a ZRC report was sent.

Sending voice

To send voice over RF4CE (Vendor specific ZRC protocol), press and hold the "Mic" button on the controller. The dongle's LED2 (Green) will blink while voice data is being transferred.

If the LED1 (Red) is blinking instead, you may be running into a permissions issue on the window's workstation. A work-around for this is to open "Recording devices" in the windows Sound Mixer.

  1. Right-click on the speaker icon
  2. Select Recording devices

This opens up the Recording tab in the Sound window. You should have "USB CC2531 ZRC AUD" microphone listed. If LED2 (red) still blinks, you may have to disconnect and reconnect the USB dongle.

Speaker recorder.pngZrc dongle.png