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

RE: [bluetooth-dev] BCSP synchronisation



We get the 0x1C after initialization too. We just ignore it,
which does not seem to cause any harm.

However, we sometimes get the error 0xFE after having had a
number of connections running for a while, which causes the
module to stop working until it is reset (which is what
we do now if we receive that error). Unfortunately, we do
not know what causes this. :(

//Peter

> -----Original Message-----
> From: Alain Paschoud [mailto:alain.paschoud@xxxxxxx.ch]
> Sent: 04 February 2002 17:23
> To: Bluetooth-dev
> Subject: Re: [bluetooth-dev] BCSP synchronisation
> 
> 
> Hello,
> 
> I know that I'm talking to myself (because I respond to my 
> own e-mails). I've resolved previous problem by rebooting the 
> PC... But I've now a question that I can't certainly find a 
> response by myself :
> 
> When I initiate the BCSP module, the module send back an 
> hardware error. But I can't find an appropriate documentation 
> on this error. I look on CSR web site, but I haven't access 
> to "secure area". I'm looking for what means the hardware error 0x1C.
> 
> Does someone have a documentation that explain such hardware error ?
> 
> Did someone already had this error and have found the way to 
> correct it ?
> 
> Any proposition is appreciated.
> 
> ---- Logs ----
> 
> Feb  4 17:13:10 danube bti: bt_set_baudrate: 57600 baud
> Feb  4 17:13:10 danube kernel: BT (driver) __bt_ioctl: 
> Setting baudrate in host controller to 57600 
> Feb  4 17:13:10 danube kernel: HCI: hci_set_baudrate [CSR] 
> (57600 baud) 
> Feb  4 17:13:10 danube kernel: BT DATA <--|X|     25 
> Feb  4 17:13:10 danube kernel: BT (driver) bt_open: Line 7 
> Feb  4 17:13:10 danube kernel: BT (driver) Registering tty on 
> line 7 (bti) 
> Feb  4 17:13:10 danube kernel: BT (driver) Now 2 open fd:s 
> for ttyBTC [bti] 
> Feb  4 17:13:10 danube kernel: BT (driver) BTSETBCSPMODE: -1 
> Feb  4 17:13:10 danube kernel: BT (driver) bt_close: Line 7 
> Feb  4 17:13:10 danube kernel: BT (driver) Unregistering tty 
> on line 7 
> Feb  4 17:13:10 danube kernel: BT DATA -->|X|      9 
> Feb  4 17:13:10 danube kernel: BT DATA -->|X|     22 
> Feb  4 17:13:10 danube kernel: BT DATA <--|X|      6 
> Feb  4 17:13:10 danube kernel: HCI: release_cmd_timer 
> Feb  4 17:13:11 danube kernel: BT DATA -->|X|     39 
> Feb  4 17:13:11 danube kernel: BT DATA <--|X|      6 
> Feb  4 17:13:11 danube kernel: HCI: release_cmd_timer 
> Feb  4 17:13:11 danube kernel: BT SYS: hci_receive_hq: 
> Received a SETREQ, sending back GETRESP 
> Feb  4 17:13:11 danube kernel:  
> Feb  4 17:13:11 danube kernel: hci_receive_hq (24): 
> Feb  4 17:13:11 danube kernel: 0x02 0x00 0x0c 0x00 0x8d 0x1e 
> 0x00 0x10 0x00 0x00 0x1c 0x00 0x5c 0x00 0x91 0x57  
> Feb  4 17:13:11 danube kernel: 0x01 0x00 0x3d 0x97 0x24 0xb3 
> 0x24 0xb7  
> Feb  4 17:13:11 danube kernel:  
> Feb  4 17:13:11 danube kernel: csr_send_general_hq (29): 
> Feb  4 17:13:11 danube kernel: 0x01 0x00 0xfc 0x19 0xc3 0x01 
> 0x00 0x0c 0x00 0x8d 0x1e 0x00 0x10 0x00 0x00 0x1c  
> Feb  4 17:13:11 danube kernel: 0x00 0x5c 0x00 0x91 0x57 0x01 
> 0x00 0x3d 0x97 0x24 0xb3 0x24 0xb7  
> Feb  4 17:13:11 danube kernel: BT DATA <--|X|     30 
> Feb  4 17:13:11 danube kernel: BT DATA <--|X|      6 
> Feb  4 17:13:11 danube kernel: BT SYS: ERROR: process_event: 
> A hardware error with error code 0x1C occurred. 
> Feb  4 17:13:11 danube kernel: BT SYS: ERROR: process_event: 
> Please refer to your Bluetooth module's manual. 
> Feb  4 17:13:11 danube kernel: BT DATA -->|X|      6 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
> 
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com