• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 635 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.

CC2564: SPPDemo Bluetooth only connects for a few seconds (Windows 10)

Brian Smith20
Intellectual 410 points
Part Number: CC2564

STMF3 Eval board with CC2564MODAEM and SPPdemo, and trying either as client or server.  SPPDemo comes up on Windows10 as ready to pair, and pairing initiated either from host or target gives the same result - at the target end pairing seems to be successful, but at the host end the connection status only lasts for about 5 seconds, and is then disconnected at the host end with silence at the target, e.g.

Target dialogue

Server>inquiry

Server>
Inquiry Entry: 0x001583E59271.

Server>
Inquiry Entry: 0x001A7DDA7114.

Server>
Result: 1,0x001583E59271.
Result: 2,0x001A7DDA7114.

Server>open 1 0
Server Opened: 1.

Server>
atPINCodeRequest: 0x001583E59271
Respond with: PINCodeResponse

Server>PINCodeResponse 1234
GAP_Authentication_Response(), Pin Code Response Success.

Server>
atLinkKeyCreation: 0x001583E59271
Link Key Stored.

Server>

Using released STM32F4 port with __SUPPORT_CC256XB_PATCH__

Any pointers greatly appreciated!

Brian

  • 0
    TI__Mastermind 27080 points
    What is Windows10 in your setup? Did, you try with a Blueterm or similar Bluetooth SPP app on phone? You, may have already read the SPP demo instructions at : processors.wiki.ti.com/.../CC256x_TI_Bluetooth_Stack_SPPDemo_App

    Thanks
  • 0 in reply to Hari Nagalla
    Intellectual 410 points
    Yes, have read the SPP demo instructions.

    Windows10 Pro 64bit with current updates. Same result also from different machine with Win10 Home 64bit. Have tried setting CC2564MODAEM (target) as client with this result:

    Client>inquiry

    Client>
    Inquiry Entry: 0x001583E59271.

    Client>
    Inquiry Entry: 0x001A7DDA7114.

    Client>
    Result: 1,0x001583E59271.
    Result: 2,0x001A7DDA7114.

    Client>open 1 10

    SPP_Open_Remote_Port success.

    Client>
    SPP Open Confirmation, ID: 0x0004, Status 0x0002.

    Client>write
    Function Error.

    The status (0x0002) is generated by the SPP_EventCallback and any non-zero result indicates that the port isn't really open, and this is why the write fails, since the serial port ID has been set back to zero by the callback. Phone (Android HTC One_M8) pairs ok, and is visible with Inquiry. Seeking to open from target gives identical response to Win10 machines with Status 0x0002. Attempting to connect from phone to target (client) gives 'Unable to connect device' with Blueterm. Same result if not previously paired. Yet, Blueterm on phone connects correctly with WIn10 PC and transmits data fine in both directions.

    Setting the target as a server and attempting to pair from Win10 PC we get an apparent good pairing, but the 'connected' blue progress bar comes up for a few seconds and then disappears and the final status as changes from Connected to Paired after about 5 seconds.

    Server>setdiscoverabilitymode 2
    Discoverability: General.

    Server>setconnectabilitymode 1
    Connectability Mode: Connectable.

    Server>setpairabilitymode 2
    Pairability Mode Changed to pmPairableMode_EnableSecureSimplePairing.
    I/O Capabilities: Display Yes/No, MITM: TRUE.

    Server>changesimplepairingparameters 2 2
    I/O Capabilities: Keyboard Only, MITM: TRUE.

    Server>inquiry

    Server>
    Inquiry Entry: 0x001583E59271.

    Server>
    Inquiry Entry: 0x001A7DDA7114.

    Server>
    Result: 1,0x001583E59271.
    Result: 2,0x001A7DDA7114.

    Server>
    atIOCapabilityResponse: 0x001583E59271
    Capabilities: Display Yes/No, MITM

    Server>
    atIOCapabilityRequest: 0x001583E59271

    Auth success.

    Server>
    atPasskeyRequest: 0x001583E59271
    Respond with: PassKeyResponse

    Server>passkeyresponse 064752

    Passkey Response Success success.

    Server>Un-handled Auth. Event: 11

    Server>
    atLinkKeyCreation: 0x001583E59271
    Link Key Stored.

    Server>write
    Function Error.

    I guess 'Un-handled Auth. Event: 11' is telling us that the connection has been dropped for some reason (I added the reporting of the event number). Currently totally stuck, and needing to get past first base urgently!!

    Thank you for any pointers...

    Brian