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).
- Is OAD on the SensorTag for BLE apps only?
- 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)?
- 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).
- 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?
- If so, Is it limited to the ZigBee HA profile? I would like to use the generic ZigBee mesh to port an exiting application.
- 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