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.

Getting started with CC2650

Hi everyone

I'm having problems getting my CC2650EM to work with my SmartRF06 EB. First of all, I intend to do it through the CC26xxware library, so no RTOS. I'm fairly new to CCS (v6.1), so something might be wrong in the default configuration of my project. I'm just trying to get a basic "hello world" to work. The problem I get is shown in the following picture:

It might be a very stupid error, but I've been stucked for 2 days with this.

The main() is apparently never reached, and the in the debug session I can only stop the program. I have worked with an MSP430 EB before, and it paused at the begining of the main() in a breakpoint. Does anyone have any idea of what is happening?

Thanks.

  • Hi Alexandre,

    Which example project are you using? Did you verify your CC26xx device support is up to date in CCS? To test your dev environment, can you try building one of the example projects from the BLE SDK, such as simpleBLEPripheral? This should work and can be a reference to getting other CCS projects working.

    Best wishes
  • First of all, thanks for your answer. Here's what I did:

    1 - I re-checked my device support and it's up to date.
    2 - I built and execute the simpleBLEPeripheral. The building worked, but in the linking phase, the error persisted (Timed out waiting for target to halt).
    3 - I tried to launch the simpleBLEPeripheral project in my second out-of-the-box Evaluation Board and it worked!
    4 - I tried to launch my other test project and the error was reproduced.
    5 - Now I cannot launch any project in any of my two Evaluation Boards.

    This seems pretty strange. Is there anything I'm missing? Do I have to do anything special to flash the device?

    Thanks.
  • I was suspecting something very stupid and it was. After several tests with different projects, I realized that any printf() at any point causes the debug session not to enter the main(). I have deleted all my printf().

    I can finally start debugging and doing something productive.

    Nevertheless, how is it possible that a printf() causes the debug session to beahave like this?

    Thanks.

  • Hi,

    Glad to hear that you are able to debug now. I will check if there is a procedure to use printf, this is not part of our standard debug environment.

    Best wishes