Setting up an External USB to MTPCIE Bluetooth Serial Interface
To set up an external USB to the serial Bluetooth interface on the MTPCIE-DK1 developer board when a MTPCIE
radio is installed:
Note: The external USB connection terminates to a quad UART on the MTPCIE-DK1 board with one UART channel connected to the Bluetooth device.
- On the MTPCIE-DK1 developer board, position jumpers next to Bluetooth DB9 connector J14 to the 2,3
Word count: 510 Last edited by kgroening on February 14, 2014 at 12:17 pm
- Position jumpers next to USB Serial connector J24 to the 1,2 position.
- Position jumpers next to USB 3G connector J4 to the 1,2 position.
- Power up the MTPCIE-DK1 developer board with the MTPCIE Bluetooth/Wi-Fi capable radio installed.
- Connect computer USB port to the USB Serial J24 USB connector on DK1 board.
- Use commands such as dmesg, lsusb -v, etc to find the ports Linux assigned to the quad uart on DK1.Record the port designation assigned to the second port. For example:
- Copy the file TIInit_7.6.15.bts to the /lib/firmware folder of the computer.
- Install jumper JP86(labeled “BT_EN”), then remove it again to toggle the Bluetooth Enable signal for the MTPCIE.
- Enter the following string, substituting the computer’s tty port that corresponds to uart port B on MTPCIE-DK1:
- On the Linux computer, enter:
- Verify the remote serial Bluetooth device is configured to wait for a connection.
- Verify the remote Bluetooth device’s MAC address is in the list of detected Bluetooth devices. Enter:
- Enter the following, where xx represents MAC address of the remote Bluetooth device you set up
- Open another Linux terminal session and run a terminal program such as minicom at 3000000 bps attached to /dev/rfcomm0 port. Use minicom to communicate with your remote device.
[ 126.376017] usb 7-1: new full speed USB device using uhci_hcd and address 3 [ 126.532263] usb 7-1: configuration #1 chosen from 1 choice [ 126.582980] cdc_acm 7-1:1.0: This device cannot do calls on its own. It is not a modem. [ 126.583024] cdc_acm 7-1:1.0: ttyACM0: USB ACM device [ 126.590282] cdc_acm 7-1:1.2: This device cannot do calls on its own. It is not a modem. [ 126.590322] cdc_acm 7-1:1.2: ttyACM1: USB ACM device [ 126.592170] cdc_acm 7-1:1.4: This device cannot do calls on its own. It is not a modem. [ 126.592215] cdc_acm 7-1:1.4: ttyACM2: USB ACM device [ 126.595064] cdc_acm 7-1:1.6: This device cannot do calls on its own. It is not a modem. [ 126.595115] cdc_acm 7-1:1.6: ttyACM3: USB ACM device
hciattach -s 115200 /dev/ttyACM1 texas 3000000
hciconfig -a name Example Response ptg@ptg-desktop:~$ hciconfig -a name hci0: Type: UART BD Address: 1C:E2:CC:04:5C:C2 ACL MTU: 1021:4 SCO MTU: 180:4 UP RUNNING PSCAN RX bytes:1013 acl:0 sco:0 events:30 errors:0 TX bytes:883 acl:0 sco:0 commands:30 errors:0 Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: '' Class: 0x4a0104 Service Classes: Networking, Capturing, Telephony Device Class: Computer, Desktop workstation HCI Ver: (0x6) HCI Rev: 0x0 LMP Ver: (0x6) LMP Subver: 0x1f29 Manufacturer: Texas Instruments Inc. (13)
hcitool scan Example Response ptg@ptg-desktop:~$ hcitool scan Scanning ... CC:55:AD:2B:53:FA BB 9330 00:18:E7:36:CF:91 DTMVW7JREI01 00:A0:96:0F:B8:2A SocketWireless
rfcomm -S connect 0 xx:xx:xx:xx:xx:xx To run rfcomm in the background add "&" to the end of the string as follows: rfcomm -D connect 0 00:A0:96:0F:B8:2A &