• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 50 subscribers
  • Views 2908 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SimpleBLECentral Disconnected Reason 62

Brian Leonard
Prodigy 145 points
Other Parts Discussed in Thread: CC2541, CC2540

Hi all,

I am running SimpleBLECentral on a CC2540 connected to a SmartRF05 Board and SimpleBLEPeripheral on a custom board with a CC2541 connected to another SmartRF05 Board.  The Central can detect the Peripheral, but once I press the joystick to connect, it momentarily says connected, and then says Disconnected Reason 62, which I understand is a Connection Failure.  Is there any way I can debug this error and figure out whether this is a hardware issue or a connection parameter(which I doubt since this is the sample code)?

Thanks,

Brian

  • 0
    TI__Genius 17975 points

    The error code 0x3E means "failed to establish". The BT core spec states that if a master does not receive a packet from the slave within the first 6 connection events after sending a connection requests then the master considers the connection lost.

    You most likely are getting this because your slave device is not receiving the connection request, and therefore is just continuing to advertise. The master then tries 6 connection events and never gets a packet. I suspect this is an RF issue on your board.

    Another case where this 0x3E error code occurs (though I don't think this applies in your case) is if the slave has the advertising filter policy set such that it does not accept connection requests from non-whitelisted devices. The slave would then ignore the connection request and continue advertising, causing the master to get this error.

  • 0 in reply to Willis1
    Prodigy 145 points
    Thanks! It turned out the peripheral needed to be right next to the central in order to connect. I assume this means it is an antenna problem on the Bluetooth of the custom peripheral board. Thanks again!