This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Flashing CC2650 with CC-DEVPACK-DEBUGGER - Red LED

Other Parts Discussed in Thread: BLE-STACK, CC2650

Hello,


I have setup my development environment in a Windows 8 VM. I am using a CC2650 Simplelink SensorTag in addition to the CC-DEVPACK-DEBUGGER. I am using Code Composer Studio v6.1. I have downloaded the BLE-STACK v2.1 and all of the drivers appear to be correctly installed. I am able to execute Debug sessions reasonably as expected, against the SensorTag project which comes with the BLE Stack. Having built the SensorTag project in CCS and running the debug session* I found the board to not have been flashed as far as I can tell. Using SmartRF Flash Programmer 2 with the generated .hex from CCS results in the board (when disconnected) simply displaying a RED led. Using SmartRF Flash Programmer 2 with the ...BLE_All_v1.2.hex supplied with the BLE Device Monitor results in the device (when disconnected) functioning as it shipped, including advertisements, etc.


This leads me to the following questions:

- Are the sources (when built) given with the BLE Stack equivalent to the stock firmware for CC2650 SensorTag?

- If so, am I following the incorrect procedure(s) by either running a debug session and/or using SmartRF Flash Programmer 2 to flash my .hex file built by CCS?


* It is not clear to me whether or not running a debug session would satisfy 'flashing' the program for when the board is disconnected.

Thank you.