• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 336 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.

LMX9838 release SCO (double confirmation)

Vladimir Aparin
Expert 2610 points

Sometime when I sending packet into module I don't get answer.
But when I resending same command after delay (2-20 sec) I get confirmation for both commands.
Log in attachment

4667.lmx9838_error.txt 
[12/09/2014 14:42:43:024]   [D] BT: Indication received [opcode: 0x10, len: 7]
[12/09/2014 14:42:43:036]   [D] BT: 2 <- ATA
[12/09/2014 14:42:43:040]   [D] BT: 2 -> 
[12/09/2014 14:42:43:048]   OK
[12/09/2014 14:42:43:055]   +CIEV: 2,1
[12/09/2014 14:42:43:062]   +CIEV: 3,0
[12/09/2014 14:42:43:069]   [D] BT: [VOICE] Open SCO
[12/09/2014 14:42:43:073]   [D] BT: Send cmd [opcode: 0x5d]
[12/09/2014 14:42:43:077]   [D] BT: Confirm received [opcode: 0x5d, len: 7]
[12/09/2014 14:42:43:087]   [D] BT: Confirmed
[12/09/2014 14:42:43:094]   [D] BT: SCO opening...
[12/09/2014 14:42:43:098]   [D] BT: Confirm received [opcode: 0x0f, len: 2]
[12/09/2014 14:42:43:105]   [D] BT: Confirmed
[12/09/2014 14:42:43:112]   [D] BT: Indication received [opcode: 0x5d, len: 7]
[12/09/2014 14:42:43:221]   [D] BT: SCO opened
[12/09/2014 14:42:44:868]   [D] BT: [VOICE] Close SCO
[12/09/2014 14:42:44:972]   [D] BT: Send cmd [opcode: 0x5e]
[12/09/2014 14:43:04:681]   [D] BT: Command timeout
[12/09/2014 14:43:04:686]   [D] BT: [VOICE] Close SCO
[12/09/2014 14:43:04:692]   [D] BT: Send cmd [opcode: 0x5e]
[12/09/2014 14:43:04:797]   [D] BT: Confirm received [opcode: 0x5e, len: 1]
[12/09/2014 14:43:04:805]   [D] BT: Confirmed
[12/09/2014 14:43:04:813]   [D] BT: Confirm received [opcode: 0x5e, len: 1]
[12/09/2014 14:43:04:824]   [D] BT: Confirmed
[12/09/2014 14:43:04:831]   [D] BT: Indication received [opcode: 0x5e, len: 2]
[12/09/2014 14:43:04:840]   [D] BT: SCO closed
[12/09/2014 14:43:04:844]   [D] BT: 2 -> 
[12/09/2014 14:43:04:852]   +CIEV: 2,0
[12/09/2014 14:43:25:677]   [D] BT: sleep
[12/09/2014 14:43:25:782]   [D] BT: Send cmd [opcode: 0x52]
[12/09/2014 14:43:25:787]   [D] BT: Confirm received [opcode: 0x52, len: 1]
[12/09/2014 14:43:25:796]   [D] BT: Confirmed
[12/09/2014 14:43:25:905]   [D] BT: TL disabled
[12/09/2014 14:43:25:911]   [D] BT: TL wakeup request
[12/09/2014 14:43:25:916]   [D] BT: Indication received [opcode: 0x53, len: 1]
[12/09/2014 14:43:26:025]   [D] BT: TL enabled
[12/09/2014 14:43:26:030]   [D] BT: Confirm received [opcode: 0x0f, len: 2]
[12/09/2014 14:43:26:154]   [D] BT: Confirmed
[12/09/2014 14:43:46:675]   [D] BT: sleep
[12/09/2014 14:43:46:782]   [D] BT: Send cmd [opcode: 0x52]
[12/09/2014 14:44:27:676]   [D] BT: force sleep [timeout]
[12/09/2014 14:44:27:780]   [D] BT: TL wakeup request
[12/09/2014 14:44:48:674]   [D] BT: sleep
[12/09/2014 14:44:48:680]   [D] BT: Send cmd [opcode: 0x52]
[12/09/2014 14:44:48:683]   [D] BT: Confirm received [opcode: 0x52, len: 1]
[12/09/2014 14:44:48:688]   [D] BT: Confirmed
[12/09/2014 14:44:48:691]   [D] BT: TL disabled
[12/09/2014 14:44:48:694]   [D] BT: Confirm received [opcode: 0x52, len: 1]
[12/09/2014 14:44:48:697]   [D] BT: Confirmed
.
How I can fix it?

  • 0
    TI__Prodigy 725 points

    Hi Vladimir,

    I've replied to you on a seperate email.

     

    The sequence marked red looks strange:

     

    [12/09/2014 14:42:43:094]   [D] BT: SCO opening...

    [12/09/2014 14:42:43:098]   [D] BT: Confirm received [opcode: 0x0f, len: 2]

    [12/09/2014 14:42:43:105]   [D] BT: Confirmed

    [12/09/2014 14:42:43:112]   [D] BT: Indication received [opcode: 0x5d, len: 7]

    [12/09/2014 14:42:43:221]   [D] BT: SCO opened

    [12/09/2014 14:42:44:868]   [D] BT: [VOICE] Close SCO

    [12/09/2014 14:42:44:972]   [D] BT: Send cmd [opcode: 0x5e]

    [12/09/2014 14:43:04:681]   [D] BT: Command timeout

    [12/09/2014 14:43:04:686]   [D] BT: [VOICE] Close SCO

    [12/09/2014 14:43:04:692]   [D] BT: Send cmd [opcode: 0x5e]

    [12/09/2014 14:43:04:797]   [D] BT: Confirm received [opcode: 0x5e, len: 1]

    [12/09/2014 14:43:04:805]   [D] BT: Confirmed

    [12/09/2014 14:43:04:813]   [D] BT: Confirm received [opcode: 0x5e, len: 1]

    [12/09/2014 14:43:04:824]   [D] BT: Confirmed

    [12/09/2014 14:43:04:831]   [D] BT: Indication received [opcode: 0x5e, len: 2]

    [12/09/2014 14:43:04:840]   [D] BT: SCO closed

     

    Normal sequence looks as follows:

    Rx: Event: Establish SCO Link, Status: 00, BdAddr: 555555555555

    Rx: Event: SCO Link Established, Status: 00, BdAddr: 555555555555

    Tx: Cmd: Release SCO Link                                                                         [Tx(RAW):  02,52,5E,00,00,B0,03]

    Rx: Event: Release SCO Link, Status: 00                                               [Rx(RAW):  02,43,5E,01,00,A2,00,03]

    Rx: Event: SCO Link Released, Status: 00, HCI Reason: 16             [Rx(RAW):  02,69,5E,02,00,C9,00,16,03]

     

    The reaction to Release SCO Link command is normally immediate. In their case LMX9838 does not even confirm it received a command. It does it after the command is resent and then it makes it twice so it receives both Close SCO commands.

     

    May the customer check if the [12/09/2014 14:42:44:972]   [D] BT: Send cmd [opcode: 0x5e]

    is really sent to LMX9838 UART? The best would be to check it with a scope or UART transmission analyzer. Do they handle UART handshake lines correctly? Do they not block transmission from LMX9838 UART by setting its CTS incorrectly when the timeout occurs? Having CTS in blocking state would result in LMX9838 not being able to say anything on UART.

     

    What is the meaning of

    “[12/09/2014 14:43:04:805]   [D] BT: Confirmed”?