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.

CC2650 BLE, ZigBee and OAD

Other Parts Discussed in Thread: CC2650, Z-STACK, CC2538, BLE-STACK, CC2640

Hi,

I'm considering the CC2650 for a new product design and have a few questions which I haven't been able to find answers to.

I have purchased two SensorTag DevPacks with TI Debugger DevPacks two experiment with.

OAD

It is my understanding that this functionality resides in Image A (for on-chip OAD) or can be included in a single binary/hex file for external off-chip OAD (SensorTag).

  1. Is OAD on the SensorTag for BLE apps only?
  2. Can OAD be used to switch between apps written for different wireless protocols, I.E. switch from an app running BLE to an app running ZigBee and vice-versa. Or is it only possible to go one way - BLE to ZigBee via OAD, then jtag is required to return back to the BLE app, or can OAD over Bluetooth still be done/integrated for a ZigBee app (I.E. hold a button during power-up)?
  3. Can a BLE app and a ZigBee app be switched between after power-up, before or at run-time?

Wireless firmware upgrade over Bluetooth from a Smart Phone would be very useful.

ZigBee on CC2650

I'm aware of the IAR requirement for ZigBee Z-Stack development. Ideally the CC2650 would be used as a single chip solution (not as a ZNP).

  1. I've read on the forum that the CC2650 simply doesn't have enough memory to run the full ZigBee stack as well as a user application and due to this, it can only operate as a ZigBee End-device? Is this true?
  2. If so, Is it limited to the ZigBee HA profile? I would like to use the generic ZigBee mesh to port an exiting application.
  3. If I need full ZigBee funtionality (ZC, ZR and ZED), without using the CC2650 as a ZNP, can you recommend an alternative? CC2538?

A major design requirement is for the product to be upgradeable over-the-air, hence the single chip approach. 

Thanks

Raf

  • Hello,

    OAD on SensorTag pushes the entire 128kB image to off chip flash, then updates the entire 128kB internal memory of the CC2650. The image can be any supported protocol. Note that SensorTag doesn't use on chip OAD due to the size of the application.

    You can implement a BIM that can load any image based on the size of the external flash memory. Please refer to the CC2640 BLE OAD User Guide, which is included in the BLE-Stack 2.1 SDK. Also, the BIM & OAD code is included in source forum in the BLE 2.1 SDK.

    For ZigBee, please post your question in in the ZibBee forum. Our ZigBee experts an assist you in that forum.

    Best wishes
  • Hello JXS,

    Thank you for your response. I will read through the CC2640 BLE OAD User Guide as per your suggestion.

    Just to clarify one thing:

    So it is possible to use OAD to download a BLE image onto a SensorTag that is running a ZigBee image, and vice-versa? The image used can be any protocol, even ZigBee can use OAD via Bluetooth?
    If so, are there any examples available?

    Thanks,
    Raf

  • Hello Raf,

    Yes, you can. OAD transfers a complete binary image of the CC2650 firmware, so that image can be any supported protocol stack. For details on how OAD is implemented on the ZigBee side, please refer to the ZigBee documentation or post in the corresponding E2E forum.

    Note that the SensorTag (or CC2650) running a given protocol can only communicate with the same protocol device. So a BLE image executing on the SensorTag can only communicate with a BLE Central device (e..g, smart phone). You can't connect to a SensorTag running ZigBee with a BLE Central.

    Best wishes

  • Thanks JXS. That cleared things up for me.

    Raf