Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
interfaces:bt0417c [2023/12/05 12:11] darron |
interfaces:bt0417c [2023/12/15 07:35] darron [Windows] |
||
---|---|---|---|
Line 5: | Line 5: | ||
\\ \\ | \\ \\ | ||
{{: | {{: | ||
+ | \\ \\ | ||
+ | {{: | ||
</ | </ | ||
This is a low cost bluetooth module that may or may not come on a base board. There are a number of variations and here we have the one known as the HC-05. This can be configured as a bluetooth master or slave and appears to be the most popular and versatile. | This is a low cost bluetooth module that may or may not come on a base board. There are a number of variations and here we have the one known as the HC-05. This can be configured as a bluetooth master or slave and appears to be the most popular and versatile. | ||
- | The module is comprised of a CSR BC417 radio and an MX29LV800 flash chip. | + | The module is comprised of a CSR BC417 radio which supports BT 2.0+EDR |
+ | |||
+ | This module has been verified to work with the RPi 400 and its internal BT 5.0 BLE interface using the legacy mode rfcomm interface. | ||
=== Pinout === | === Pinout === | ||
My module came on a board with the following layout. There are at least two other board variations which don't apply here. | My module came on a board with the following layout. There are at least two other board variations which don't apply here. | ||
Line 98: | Line 102: | ||
__btattach__ | __btattach__ | ||
- | For built-in BT on Pi3/4, you may also need to attach the device, however, | + | For built-in BT on Pi3/4, you may also need to attach the device. |
- | since these are BLE and this guide was originally written in 2015 the | + | |
- | Pi3/4 BLE connection is untested with the HC-05 at the time of writing this. | + | |
< | < | ||
Line 108: | Line 110: | ||
__btkrn__ | __btkrn__ | ||
- | For Pi4, BT can be enabled in / | + | Alternatively to the above, BT can be enabled in / |
< | < | ||
Line 119: | Line 121: | ||
== Bluez 4 == | == Bluez 4 == | ||
+ | |||
+ | __hciconfig__ | ||
+ | |||
< | < | ||
hciconfig hci0 up | hciconfig hci0 up | ||
Line 132: | Line 137: | ||
== Bluez 5 == | == Bluez 5 == | ||
+ | |||
+ | __bluetoothctl__ | ||
+ | |||
< | < | ||
- | bluetoothctl -a | ||
[NEW] Controller 00: | [NEW] Controller 00: | ||
[bluetooth]# | [bluetooth]# | ||
Line 156: | Line 163: | ||
[DEL] Controller 00: | [DEL] Controller 00: | ||
</ | </ | ||
+ | |||
+ | == RFCOMM == | ||
Talk to module via virtual serial port. | Talk to module via virtual serial port. | ||
Line 162: | Line 171: | ||
sdptool add --channel=666 SP | sdptool add --channel=666 SP | ||
rfcomm bind rfcomm0 98: | rfcomm bind rfcomm0 98: | ||
- | screen | + | picocom |
</ | </ | ||
+ | |||
+ | ===Windows==== | ||
+ | |||
+ | <wrap right> | ||
+ | {{: | ||
+ | </ | ||
+ | |||
+ | Under windows 10 scan for the device, click connect and enter the pass code. | ||
+ | |||
+ | A COM port will be added for the module which acts just like a regular hardware | ||
+ | com port. | ||
=== Resources === | === Resources === | ||