using CYSPP in "retained command mode"

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
AlSp_2628001
Level 1
Level 1
First reply posted First question asked Welcome!

Hi,

I'm trying to use a CYBLE-013025 in "retained command mode", that is keeping the CYSPP pin driven high and the CYSPP "enable" value to "enabled", so that no transparent mode is used.

In this condition, API commands, replies and events are visible and I can succesfully receive data from the central remote on the "Acknowledged Data Characteristic" (gatts_data_written event). Instead, I can't find a way to indicate data to the remote using the same characteristic.

When I try to indicate (/IH,C=0,H=0E,D=AB), I get a 0x108 error (operation not permitted). Of course, the remote central has subscribed to indications. Indeed, if I assert CYSPP low and try to indicate with the same command, I can see the indication packet that gets indicated on the remote.

So, my question is: how can I retain the command mode and indicate to a remote? Is this possible? If not, should I write my own custom GATT?

Thank you very much.

Alberto

0 Likes
1 Solution

Hi Alberto,

   As soon as we subscribe the client device either for Notifications or Indications ,the CYSPP Command Mode will no longer work if the CYSPP is enabled in platform configuration ( CYSPPSP, E=1) and that is mandatory condition for command retained mode.  ( page # 14 " Starting CYSPP Operation")

Now, if you want to send indication packets based on an ACK from central device ,you need to create your own GATT database.

-Gyan

View solution in original post

5 Replies