Hi all,
我很雄厚cing the following behavior: My application sends the GAPM_START_ADVERTISE_CMD command to TASK_GAPM. In terms of functionality, all works fine: The DA1458x starts advertising and I can establish a connection. The weird thing is that I only get the GAPM_CMP_EVT message (which is the confirm response to the GAPM_START_ADVERTISE_CMD command) AFTER a connection has been established! The communication sequence is as follows:
TASK_APP: GAPM_START_ADVERTISE_CMD
<>
<>
TASK_GAPC: GAPC_CONNECTION_REQ_IND
TASK_GAPM: GAPM_CMP_EVT (param->operation: 0x0E, "Start undirected connectable advertising")
I believe I should receive the GAPM_CMP_EVT right after sending the GAPM_START_ADVERTISE_CMD. Any ideas what might be causing this behavior?
I'm working with the external uC configuration (GTL SPI), in case that's important.
Thanks for any help,
mabraun
Hi mabraun,
The GAPM_CMP_EVENT for the advertising command is issued by the stack after the completetion of the command ( only for the directed advertising which last for about 10 seconds) or when cancelling the command in the undirected advertising, you dont get this indication right after issuing the command. You get this event after the connection is established because when you connect you send a cancellation of the air operation. You dont get the GAPM_CMP_EVT right after you send the command.
Thanks MT_dialog
Hi MT_dialog,
that makes sense, thanks for your explanation. Now I can stop worrying about it.
Topic may be closed.
Thanks
mabraun