Other Parts Discussed in Thread: CC2640, CC2650
We had a requirement where the TI bt chip CC2640 needed to be controlled from the host CPU and the TI bt chip CC2640 needed to act both as a peripheral and central, based on the need. When we looked at the docs we figured out the best way to handle this is to use the SNP architecture (The SNP is a dual-device solution that requires an external MCU application processor (AP) to control the CC2650 simple network processor (SNP). However we have the following queries :
1 ) SNP architecture is the best and will suit our solution if we have only the peripheral role. However if we dig deep into the doc it says " The SNP will be configured by default to act only as a peripheral and/or broadcaster device. This can not be modified. This implies that the device can only advertise and accept/reject connection. It can not discover devices or initiate a connection. Also, the SNP will only be configured as a GATT server; it can not be a GATT client. The standard use case is for the SNP (peripheral GATT client) to connect to a central GATT server such as a smartphone". Given this can we enhance the firmware to play the role of central also ? How easy is it to modify the firmware to switch from peripheral to central role ? Will TI suggest to follow the SNP way given our requirement ?
2 ) Is there a sample AP application that will use the SNP architecture and configure the CC2640 (in SNP mode) to act as a simple peripheral i.e add a simple service which will provide simple read , write and notify options etc. Looking at the doc i see "The simple_ap project demonstrates an application (host) MCU using the SAP lib to communicate with the CC2640, running the SNP network processor application. See CC2640 Simple Network Processor API Guide in the Documents folder for APIs available for the SNP implementation.". But we are not able to find the code for the same.
