WICED Smart Bluetooth

[Anonymous]

Hi hardy.chen and boont

Per the details in this thread: Disconnected happened right after connection

We are running into the same issue on 20737. Could I get some info on how you were able to resolve this issue,

Thanks

[BoonT_56]

Can you provide some logs? Your issue could be unique in its own way...

[Anonymous]

I am programing on MAC, not using the IDE. So i dont have any standard logs. But I can describe my situation.

After many successful connections with the peripheral device, 20737(central) receives a disconnect with reason 0x08.

And every successive connection attempt after that also disconnects with reason 0x08. The only way to establish a good connection with the peripheral is to hard reset the 20737.

Below are the list of things that I tried to fix this problem:

Changed the connection parameters ----

   blecen_cen_cfg.high_conn_max_interval   = 40;       // frames

  blecen_cen_cfg.low_conn_max_interval    = 48;      // frames

  blecen_cen_cfg.low_supervision_timeout    = 700;      // N * 10ms

  blecen_cen_cfg.high_supervision_timeout   = 400;

Update connection parameter in connection up handler ----

lel2cap_sendConnParamUpdateReq();  Re: DiscReason 08

Fake a timeout so the indication queue is cleared and freed, in the connection down handler -----

leatt_timeoutCallback(0);  Re: Problem when client disconnection during Indication/confirmation phase.

Retry connection in connection down handler -----

blecli_ClientHandleReset();

blecen_connDown();

None of these have helped fix this problem.

[BoonT_56]

Pardon me.. What do you mean when you said you are not using the IDE? Did you download our SDK and build your app in it?

[Anonymous]

Yes I am using the WICED Smart Software Development Kit 2.2.1. However I am not using the wiced smart IDE.

I compile and download from the command line.

[BoonT_56]

Can you furnish some air trace? That may help us to understand some of the issues.