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.

CC2640R2F: What are the best and easiest of SW/HW tools needed for HW/SW development?

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640, , LAUNCHXL-CC2640R2, LAUNCHXL-CC2650

Hi:

I'm fairly new to MCU development let alone software development(let alone BLE development). I am a HW EE, but software is somewhat a mystery to me, but I have to tackle it, so I need to know the following (and please excuse my naive questions):

1. What are the basic differences between the CC2640 and CC2640R2F MCU's, apart from the latter supporting BLE v5.0? I also know the latter comes in a smaller 2.7mm package.

2. What are the necessary HW development tools needed for either processor(development boards, RF test kits etc)?

3. What are the recommended (and easiest or most straightforward to use) SW development tools for these processors?

4.  Do all tools have or require and/or support a RTOS?

Please advise... Thank you!

-David

  • Hi David,

    No worries, all good questions!

    1. The difference is ROM content. The CC2640R2F has more up to date and optimized BLE Stack SW in ROM. This means that more flash is available for your application, as well as supporting BT5 features.

    2. LAUNCHXL-CC2640R2 is the HW development kit for CC2640R2F. It has all you need to get started, including built-in debugger.

    3. The IDE to use is Code Composer Studio which can be downloaded for free from ti.com. You should start off by looking at the CC2640R2 SDK in Resource Explorer (dev.ti.com/tirex). In documentation you will find the BLE Stack User´s Guide, and the SimpleLink Academy trainings are designed to get you going as smoothly as possible.

    4. All TI RF protocol stacks require TI-RTOS so this is included in all the example projects.

    Cheers,
    Fredrik
  • Thank you so much Fredrik...very helpful answers!

    1. I'm interfacing the cc2640xxx to a mechanical on/off switch that produces a digital pulse signal with a maximum pulse rate of 200 pulses per second. I need to decide whether to debounce this switch externally or whether the Sensor Controller or the schmitt triggered digital inputs perform that task. I'd rather not have a software debounce routine, unless I have to.

    2. My task mostly is to count pulses and keep track of the counts accurately. Most of the time, the MCU will be asleep to save power, so:

    a) What is the minimum clock frequency I could run the MCU to save power and still be able to function as expected.
    b) Once asleep, can I use a forthcoming pulse to not only 'wake-up' the processor but count that pulse as part of my ongoing pulse
    counting routine?

    3. Once I've proven out my code on the LaunchXL-CC2650 dev-kit and am ready too move it to my target PCB, can I plug the Jtag
    connections from my target PCB into the Launch XL devkit Jtag interface for live debugginh and program my target board from the dev
    kit?

    4. Does the dev-kit have an onboard 2.4GHz antenna that I could use during testing or is their an addon board for that purpose?

    5. Is it safe to assume that the TX/RX, RFP/RPN pins need 50 ohm traces all the way from the MCU through the RLC passives in between and
    finally to the onboard 50 ohm antenna?


    Thanks again for the helpful answers!

    - David