• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 53 subscribers
  • Views 9348 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

how to get started with CC2640 & CC2650?

pixbroker
Genius 5820 points

Other Parts Discussed in Thread: CC-DEBUGGER, CC2640, CC2650, BLE-STACK

Hi, 

we are experienced using CC1xxx 8051 based MCU's via CC-Debugger & IAR as well as CC430 based MCU's via Chronos debugger and IAR. These are great platforms and we have a lot of code for them. 

The new CC2640/CC2650 chips look awesome and we have been craving to move to an ARM based CPU for a while, but did not take the plunge and move away from the Ti ecosystem that has been so good to us. So these chips come just at the right time. 

We are looking for a simple overview or transition guide that will help us understand what would be involved in moving from the 8051/MSP430 based CC systems to the CC ARM environment. 

Some questions we have include:

* IAR can still be used (ARM), but CCS is the better choice?

* what debuggers does Ti offer/recommend for the CC2640/50? we are typically not interested in DK's, so we are looking for bare bones debugger, as was CC-Debugger or chronos watch tool debugger

* the CC1xxx and CC430 had a pretty complete set of example code that made it easy to get started. is this available for the ARM versions as well?

We understand that these chips are new and not all supporting materials are on the Ti website just yet, but it would be great to get a general idea of how existing customers would tradition. 

Thanks.

PS: we see the CC2640 on the Ti website and the CC2650DK. Why is there no CC2640DK or CC2650 standalone chip? just curious.

  • 0
    TI__Mastermind 29650 points

    Hi pixbroker,

    IAR is currently the best supported platform with CCS very close behind. With CCS v6.1 being released this week I think they should both be equal. It comes down to a question of taste and tool cost vs code size (CCS compiles with slightly larger code size). The stack library is pre-built with IAR and included as a binary in CCS. This is due to avoiding needing a BLE certification for two different compilers.

    We have the following debuggers available:

    • SmartRF06EB using XDS100v3
    • XDS100v3 standalone (from 3rd party manufacturers)
    • XDS200 (from 3rd part manufacturers)
    • CC DevPack for the new SensorTag (new XDS debugger)


    These all use cJTAG for communication (TMS/TCK only), freeing up two pins on the device. In addition the 4-pin JTAG Segger J-Link and IAR I-jet should work.

    The BLE developers user guide included with the BLE stack v2 might be a good starting point, explaining a bit both how to use the stack but also the new concepts with TI RTOS.

    The BLE stack comes with a number of examples out of the box and the driver software is on a much better level compared to our old offerings.
    Currently there are no standalone peripheral examples included with TI RTOS but as documentation is quite thorough it should be very fast to get started.

    I would suggest downloading v2 of the BLE stack (ti.com/blestack) and start out with the documents pointed to by the included release notes.

    The CC2650 is a superset of the CC2640 and other futurue devices supporting other protocols. It is 100% code compatible with the CC2640.


    .:svend

  • 0 in reply to svendbt
    Genius 5820 points
    Thanks, that helps a lot.

    * What is the price of the CC DevPack?
    * does (or will) CCS offer better support for Ti-RTOS over IAR or are they on par?
  • 0 in reply to pixbroker
    Genius 5820 points
    I am not sure if this (BLE Forum) is the right place to ask general questions about the CC2640, please let me know if not.

    The CC2640 data sheet states:

    "Timer 0 is a general-purpose timer module (GPTM), which provides two 16-bit timers. The GPTM can be configured to operate as a single 32-bit timer, dual 16-bit timers or as a PWM module.
    Timer 1, Timer 2, and Timer 3 are also GPTMs. Each of these timers is functionally equivalent to Timer 0."

    are all 4 timers available to the user if the TIRTOS is used? or is the OS using some of them already to do it's scheduling? We ask because our application needs 5 simultaneous PWM outputs (to drive servos).
  • 0 in reply to pixbroker
    TI__Guru** 105180 points

    pixbroker said:
    Thanks, that helps a lot.

    * What is the price of the CC DevPack?
    * does (or will) CCS offer better support for Ti-RTOS over IAR or are they on par?

    The CC DevPack will be orderable, along with pricing information, on TI.com soon.

    CCS offers better debug integration with the TI-RTOS. More details can be found in the CC2640 BLE SW Developer's Guide included the the BLE-Stack V2 SDK installer.

    Best wishes

  • 0 in reply to pixbroker
    TI__Mastermind 29650 points

    You can have up to 8 16 bit timers enabled doing PWM outputs. The radio has its own timers.

    .:svend

  • 0 in reply to svendbt
    Genius 5820 points
    That sounds great. However, the following statement from the technical reference manual is a bit misleading then:

    "Up to four PWM pins (one PWM pin per 32-bit timer)"

    Can you clarify that one could indeed output 8 PWM signals to 8 GPIO's simultaneously?
  • 0 in reply to pixbroker
    TI__Mastermind 29650 points
    I -think- you should be able to have 8 outputs but will need to double check this.

    Regards,
    Svend
  • 0 in reply to svendbt
    Genius 5820 points

    Any suggests who i could check this with? Thanks.

  • 0 in reply to pixbroker
    TI__Mastermind 29650 points
    I am checking it with our digital R&D team right now.

    Regards,
    Svend
  • 0 in reply to pixbroker
    TI__Mastermind 29650 points
    Pixbroker,

    According to the design team there is support for 8x 16-bit timers doing PWM in parallel.

    Regards,
    Svend
  • 0 in reply to svendbt
    Genius 5820 points

    Thats great news! Thanks for checking.