alarmdecoder.com

Hi

I had some issues getting ser2sock talking to my ad2pi on the Pi 3 running the latest RASPBIAN JESSIE LITE. I appears that they have changed the way serial pins map in the PI3 with the bluetooth config

I threw together this post and I have screwed with a lot of other files that may have interacted but this is what fixed ser2sock for me. If I get time I will clean up the post and post more details on making this work

The details are here and was nicely documented by Brian Dorey. All I did is figure out that it allowed my Pi 3 to work with ser2sock and ad2pi:

Tim

http://www.briandorey.com/post/Raspberr ... Workaround

Basically:

Download http://www.briandorey.com/docs/Raspberr ... verlay.zip
Unzip the overlay and copy it to the root / on the Pi3
sudo vim /boot/config.txt
You need to add the following lines:

dtoverlay=pi3-miniuart-bt-overlay
force_turbo=1

save changes and exit

sudo vim /boot/cmdline.txt
Change the file to the following:

dwc_otg.lpm_enable=0 console=serial1,115200 console=tty1 root=/dev/mmcblk0p2 kgdboc=serial1,115200 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Exit and save your changes

I also did the following:

sudo systemctl disable hciuart
Now edit /lib/systemd/system/hciuart.server and replace ttyAMA0 with ttyS0.

sudo nano /lib/systemd/system/hciuart.service
Replace ttyAMA0 with ttyS0

Exit and save your changes

You need to update the operating system with the latest patches with:

sudo apt-get update
sudo apt-get upgrade
sudo reboot

Cool, this thread https://www.raspberrypi.org/forums/view ... 7&t=138223 describes and provides an overlay that maps the bluetooth to the mini uart and maps ama0 back to the hardware uart which we utilize on all previous pi's. Looks like that was maybe the source of the blog post? We will probably do this in our official image when we get our pi 3. Should allow bluetooth to still be used.