Beaglebone Black Wifi (and others) Serial port notes

Some info from another site on the serial ports.

The BeagleBone Black 1 has 6 on-board serial ports 3.3V TTL.

On the BeagleBone Black, it’s only the /dev/ttyO0 that is enabled by default, and it is coupled to the serial console. The other serial ports must be enabled before they can be used.

There is useful information about the serial ports of the BeagleBone in this link 2.


The BeagleBone Black Wireless is Bluetooth 4.1 compatible which is normally compatible with Bluetooth 4.0. Therefore, you should be able to use this 4.0 Bluetooth BLE Link Bee 1 with the SSC32.

some sources:

video with some app, maybe for below link

https://www.robotshop.com/en/easydriver-stepper-motor-controller.html

https://github.com/derekmolloy/beaglebone



--30--

raspberry pi bluetooth audio

as of 10/2017 versions of raspbian, it appears that bluetooth raspberry pi bluetooth adio doesn't work.

A lot of the thread below is for any bluetooth (probably adding a USB adapter for the RPI).

My attempt is for Raspberry Pi Model 3 B which has bluetooth  on the board.

Select audio device by right clicking the gui symbol and selecting audio device.

https://www.raspberrypi.org/forums/viewtopic.php?t=192859

https://raspberrypi.stackexchange.com/questions/53408/automatically-connect-trusted-bluetooth-speaker

https://www.raspberrypi.org/magpi/bluetooth-audio-raspberry-pi-3/

note after all the audio crap, VLC playback of video produces a black box, no video on the 7" raspberry pi screen frame buffer.  Not so useful.

bluetoothctl
scan on
<search for device>
copy device address
pair <device>
connect <device>

should show connected on gui bluetooth gui.

right click the gui audio, and bluetooth device should be available as a device for audio.

-30-

Bluetooth serial Raspberry Pi 3

set up raspberry pi 3 bluetooth to allow serial connection once paired.

https://hacks.mozilla.org/2017/02/headless-raspberry-pi-configuration-over-bluetooth/

Basic part of above which covers setting up bluetooth connection.  No pass code, all parings accepted.

rfcomm connects and presents a shell session on connection w/o password, so more can be done to secure this.

You’ll create this file in the /home/pi directory, like so:

$ sudo nano /home/pi/btserial.sh

Add the following lines to the script:

#!/bin/bash -e

#Edit the display name of the RaspberryPi so you can distinguish
#your unit from others in the Bluetooth console
#(very useful in a class setting)

echo PRETTY_HOSTNAME=raspberrypi > /etc/machine-info

# Edit /lib/systemd/system/bluetooth.service to enable BT services
sudo sed -i: 's|^Exec.*toothd$| \
ExecStart=/usr/lib/bluetooth/bluetoothd -C \
ExecStartPost=/usr/bin/sdptool add SP \
ExecStartPost=/bin/hciconfig hci0 piscan \
|g' /lib/systemd/system/bluetooth.service

# create /etc/systemd/system/rfcomm.service to enable 
# the Bluetooth serial port from systemctl
sudo cat <<EOF | sudo tee /etc/systemd/system/rfcomm.service > /dev/null
[Unit]
Description=RFCOMM service
After=bluetooth.service
Requires=bluetooth.service

[Service]
ExecStart=/usr/bin/rfcomm watch hci0 1 getty rfcomm0 115200 vt100 -a pi

[Install]
WantedBy=multi-user.target
EOF

# enable the new rfcomm service
sudo systemctl enable rfcomm

# start the rfcomm service
sudo systemctl restart rfcomm

Save the file, and then make it executable by updating its permissions like so:

$ chmod 755 /home/pi/btserial.sh

Now you have the basics of the script required to turn on the Bluetooth service and configure it.  But to do this 100% headless, you’ll need to run this new script on startup. Let’s edit /etc/rc.local to launch this script automatically.

$ sudo nano /etc/rc.local

Add the following lines after the initial comments:

#Launch bluetooth service startup script /home/pi/btserial.sh
sudo /home/pi/btserial.sh &

Save the rc.local script, unmount the image, and write it to an SD Card using your favorite tool (mine is ApplePiBaker).
Now you are ready to go.  Plug in power to the Rpi and give it 30 seconds or so to startup. Then unplug it, and plug it in again and let it boot up a second time.  Restarting the Bluetooth service doesn’t work correctly, so we need to reboot.
-30-

Raspberry pi 3 Bluetooth

https://www.cnet.com/how-to/how-to-setup-bluetooth-on-a-raspberry-pi-3/

• From the Raspberry Pi desktop, open a new Terminal window.
• Type sudo bluetoothctl then press enter and input the administrator password (the default password is raspberry).
• Next, enter agent on and press enter. Then type default-agent and press enter.
• Type scan on and press enter one more time. The unique addresses of all the Bluetooth devices around the Raspberry Pi will appear and look something like an alphanumericXX:XX:XX:XX:XX:XX. If you make the device you want to pair discoverable (or put it into pairing mode), the device nickname may appear to the right of the address. If not, you will have to do a little trial and error or waiting to find the correct device.
• To pair the device, type pair [device Bluetooth address]. The command will look something likepair XX:XX:XX:XX:XX:XX.

If you're pairing a keyboard, you will need to enter a six-digit string of numbers. You will see that the device has been paired, but it may not have connected. To connect the device, type connect XX:XX:XX:XX:XX:XX

Example from local pi:

pi@raspberrypi:~ $ sudo bluetoothctl
[NEW] Controller B8:27:EB:2B:C8:3A raspberrypi [default]
[NEW] Device C6:0A:5E:74:80:9E Flex
[NEW] Device 00:18:AC:38:76:BE Bluetooth Keyboard
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:2B:C8:3A Discovering: yes
[NEW] Device FC:58:FA:F7:08:36 AUVIO4000449
[bluetooth]# pair FC:58:FA:F7:08:36
Attempting to pair with FC:58:FA:F7:08:36
[CHG] Device FC:58:FA:F7:08:36 Connected: yes
[CHG] Device FC:58:FA:F7:08:36 Modalias: bluetooth:v0039p13A4d0501
[CHG] Device FC:58:FA:F7:08:36 UUIDs:
        00001108-0000-1000-8000-00805f9b34fb
        0000110b-0000-1000-8000-00805f9b34fb
        0000110c-0000-1000-8000-00805f9b34fb
        0000110e-0000-1000-8000-00805f9b34fb
        0000111e-0000-1000-8000-00805f9b34fb
        0000112e-0000-1000-8000-00805f9b34fb
        00001200-0000-1000-8000-00805f9b34fb
[CHG] Device FC:58:FA:F7:08:36 Paired: yes
Pairing successful
[CHG] Device FC:58:FA:F7:08:36 Trusted: yes
[CHG] Device FC:58:FA:F7:08:36 Connected: no