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

RE: [bluetooth-dev] i can't send data using CSR dev kit.



See below :

> -----Original Message-----
> From: Namsu Lee [mailto:nslee@xxxxxxx.kr]
> Sent: den 8 maj 2001 23:14
> To: bluetooth-dev@xxxxxxx.com
> Subject: [bluetooth-dev] i can't send data using CSR dev kit.
> 
> 
> I am trying to use CSR development kit with axis stack.
> The following is what i have done until now.
> 
> 1. Upgrade CSR module firmware to version 10.4
> 2. The following is set with PSTools
> - Host Interface ==> UART link running H4
> - Marketing fask(Flashing Lights) ==> Diagonostic and Effect
> - UART : Non-BCSP Enabled ==> Enable
> - UART : Parity Bits ==> No parity
> - UART : Stop Bits ==> One stop bit
> - UART : RTS Auto Enable ==> Disable
> - UART : RTS Enable ==> Enable
> - UART : Baud Rate ==> 115200 kbps
> - UART : Flow control Enabled ==> Enbled
> - UART configuration bitfields ==> 168
> 
> 3. Unzip the axis stack version 20010329 and modify as follow...
> - #define CONFIG_BLUETOOTH_CSR in the file, 
> openbt/apps/bluetooth/btd/btd.h
> - #define HW_CURRENT HW_CSR in the file,
> openbt/apps/bluetooth/experimental/bt_conf.h
> 
> 4. make
> make install
> make devs
> insmod bt.o
> 
> 5. btd -u /dev/ttyS0 -b /dev/ttyBT0 -m -e 0 -r server -s 115200 -R
> (client)
> 
> And, i entered command mode.
> 
> 6. > inq 5 5
> BT (driver) bt_ioctl : HCINQUIRY
> hci_inquiry (9)
> 0x01 0x01 0x04 0x05 0x33 0x8b 0x9e 0x05 0x05
> BD addr 1
> BD (6)
> 0x00 0x02 0x5b 0xff 0x08 0x2b
> BD 0: 00:02:5b:ff:08:2b
> >
> 
> 7. > rf_conn 00:02:5b:ff:08:2b 0 1

[...]
 
> BT SYS: ERROR : rfcomm_send_data : Not allowed to send data on DLCI 0
> BT SYS: ERROR : rfcomm_send_data : Not allowed to send data on DLCI 0

You cannot connect a data channel on the control channel (dlci 0) since this is only intended
for internal rfcomm messaging !! 

Do  : rf_conn <BD> [1-62] <line> and it should work fine. 

brgds
Mattias
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com