[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] BCSP synchronisation



Hello,

I just respond to my e-mail to give new information. I've finnaly managed to make a good synchronization by adding the option -i 57600. But now the stack stop at next step : HCI: csr_waitcmdnum.

As I can see in the stack, it means that HCI layer is waiting a command status from the chip. Does someone know why it doesn't get out by a timeout or by a response ?

Thank you for any help.

---- Logs ------

Feb  4 16:21:38 danube kernel: BT (driver) bt_open: Line 7 
Feb  4 16:21:38 danube kernel: BT (driver) Registering tty on line 7 (bti) 
Feb  4 16:21:38 danube kernel: BT (driver) Now 1 open fd:s for ttyBTC [bti] 
Feb  4 16:21:38 danube kernel: BT (driver) BTSETBCSPMODE: -1 
Feb  4 16:21:38 danube kernel: BT (driver) bt_close: Line 7 
Feb  4 16:21:38 danube kernel: BT (driver) Unregistering tty on line 7 
Feb  4 16:21:38 danube kernel: BT SYS: Setting BT driver to use serial tty 
Feb  4 16:21:38 danube bti: Registered bluetooth line discipline on /dev/ttyS0
Feb  4 16:21:38 danube kernel: BT (driver) bt_open: Line 7 
Feb  4 16:21:38 danube kernel: BT (driver) Registering tty on line 7 (bti) 
Feb  4 16:21:38 danube kernel: BT (driver) Now 1 open fd:s for ttyBTC [bti] 
Feb  4 16:21:38 danube bti: Init stack
Feb  4 16:21:38 danube kernel: BT SYS: Initialising Bluetooth Stack 
Feb  4 16:21:38 danube kernel: BT SYS: Current HW: CSR 
Feb  4 16:21:38 danube kernel: BT SYS: Initialising BTMEM [2500 bytes] 
Feb  4 16:21:38 danube kernel: BT SYS: Initializing BCSP 
Feb  4 16:21:38 danube kernel: BT DATA <--|X|     10 
Feb  4 16:21:38 danube kernel: BT DATA -->|X|     10 
Feb  4 16:21:38 danube kernel: BT SYS: BCSP initialized and syncronized 
Feb  4 16:21:38 danube kernel: HCI: csr_waitcmdnum 


---- First e-mail -----

On Mon, 4 Feb 2002 15:15:53 +0100
Alain Paschoud <alain.paschoud@xxxxxxx.ch> wrote:

> Hello,
> 
> I just try one CSR module since last week. I've compiled the stack with both options activated (Support BCSP and Use BCSP). I've verified that the module is continualy sending the 10 bytes to synchronise the BCSP.
> 
> But when I start bti, the can't synchronize. Does someone know why ?
> 
> And one detail more : why do I have the message BT (driver) BTSETBCSPMODE: -1 ? Does it means that BCSP mode is desactivated ?
> 
> I decoded what the CSR module send continualy through the serial line. I recieve next 10 bytes (in hexa) :
> 
> 00c0 0041 dabe eddc c0ed
> 
> ---- Log during initialisation ----
> 
> Feb  4 15:01:56 danube bti: Init stack
> Feb  4 15:01:56 danube kernel: BT (driver) bt_open: Line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) Registering tty on line 7 (bti) 
> Feb  4 15:01:56 danube kernel: BT (driver) Now 1 open fd:s for ttyBTC [bti] 
> Feb  4 15:01:56 danube kernel: BT (driver) bt_close: Line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) Unregistering tty on line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) bt_open: Line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) Registering tty on line 7 (bti) 
> Feb  4 15:01:56 danube kernel: BT (driver) Now 1 open fd:s for ttyBTC [bti] 
> Feb  4 15:01:56 danube kernel: BT (driver) BTSETBCSPMODE: -1 
> Feb  4 15:01:56 danube kernel: BT (driver) bt_close: Line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) Unregistering tty on line 7 
> Feb  4 15:01:56 danube kernel: BT SYS: Setting BT driver to use serial tty 
> Feb  4 15:01:56 danube kernel: BT (driver) bt_open: Line 7 
> Feb  4 15:01:56 danube kernel: BT (driver) Registering tty on line 7 (bti) 
> Feb  4 15:01:56 danube kernel: BT (driver) Now 1 open fd:s for ttyBTC [bti] 
> Feb  4 15:01:56 danube kernel: BT SYS: Initialising Bluetooth Stack 
> Feb  4 15:01:56 danube kernel: BT SYS: Current HW: CSR 
> Feb  4 15:01:56 danube kernel: BT SYS: Initialising BTMEM [2500 bytes] 
> Feb  4 15:01:56 danube kernel: BT SYS: Initializing BCSP 
> Feb  4 15:01:56 danube kernel: BT DATA <--|X|     10 
> Feb  4 15:01:56 danube kernel: BT DATA -->|X|     14 
> Feb  4 15:01:58 danube last message repeated 7 times
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|     13 
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|      1 
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|     13 
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|      1 
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|      4 
> Feb  4 15:01:58 danube kernel: BT DATA -->|X|     10 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|      4 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|     10 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|      4 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|     10 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|      1 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|     13 
> Feb  4 15:01:59 danube kernel: BT DATA -->|X|     14 
> Feb  4 15:02:01 danube last message repeated 5 times
> Feb  4 15:02:01 danube kernel: BT SYS: ERROR: bcsp_sync_timeout: sync failed 
> 
> -- 
> Alain Paschoud                      SMARTDATA SA
> alain.paschoud@xxxxxxx.ch         PSE-A
> http://www.smartdata.ch             1015 Lausanne
> Phone +41-21-693'84'98              
> Fax   +41-27-693'84'91              
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
> 


-- 
Alain Paschoud                      SMARTDATA SA
alain.paschoud@xxxxxxx.ch         PSE-A
http://www.smartdata.ch             1015 Lausanne
Phone +41-21-693'84'98              
Fax   +41-27-693'84'91              
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com