Pocket Chip updated with Bluez 5.46 first try worked great!

I got my pocket chip in the mail this past week. And I’ve been curious if I had to do anything to my bluez 5.46-1 build working on chip

Pocket Chip comes with the original CHIP (not the pro). It has some spaces and breathing room to do a lot in 3.3GB (2.6G free) of space.

On to trying out bluez 5.46;  I just installed it and it worked out of the box.   https://github.com/eSpecialized/bluez-5.46-rpi3

Pocket Chip once updated is at version Debian 8.9.

Preliminary tests;
bluetoothctl
scan on = success
scan off = success

after reboot; still running
when I removed the bluetooth from within my paired iPhone and tried to start up bluetoothctl, bluetoothd was dead.

I power cycled the device, to ensure it is still running.
bluetoothd is back online.  And it all works great. This means the firmware is loading at boot time properly.
remove (iPhone Mac address) = success.
trust 64:A5:C3:B8:9A:2B:D6 = worked
pair 64:A5:C3:B8:9A:2B:D6 = worked

I’m all paired up with my iPhone again.

What benefits does this have?
I’ll get back to this. Today is looking like a beach day for my family.  Least to say BLE works really great in Bluez 5.46, plus numerous other bug fixes since 5.23.

My true plans are really to work with the BLE and see how well it works. Also to work with some A2DP with stereo headsets and play some mp3’s.

Trying PAN with Bluez 5.46

chip@chip:~$ cat bnepconnect
dbus-send --system --print-reply --type=method_call --dest=org.bluez /org/bluez/hci0/dev_64_A5_C3_DC_F7_1C org.bluez.Network1.Connect string:nap


chip@chip:~$ bash ./bnepconnect
method return sender=:1.18 -> dest=:1.17 reply_serial=2
string "bnep0"

chip@chip:~$ sudo vi /etc/network/interfaces

#add these two lines
auto bnep0
iface bnep0 inet dhcp

chip@chip:~$
chip@chip:~$ sudo /sbin/ifup bnep0
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/bnep0/a0:2c:36:63:d3:7f
Sending on LPF/bnep0/a0:2c:36:63:d3:7f
Sending on Socket/fallback
DHCPDISCOVER on bnep0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on bnep0 to 255.255.255.255 port 67 interval 9
DHCPREQUEST on bnep0 to 255.255.255.255 port 67
DHCPOFFER from 172.20.10.1
DHCPACK from 172.20.10.1
bound to 172.20.10.2 — renewal in 33235 seconds.
chip@chip:~$

chip@chip:~$ ip addr show
6: bnep0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether a0:2c:36:63:d3:7f brd ff:ff:ff:ff:ff:ff
inet 172.20.10.2/28 brd 172.20.10.15 scope global bnep0
valid_lft forever preferred_lft forever
inet6 2607:fb90:8232:e7f4:a22c:36ff:fe63:d37f/64 scope global mngtmpaddr dynamic
valid_lft forever preferred_lft forever
inet6 fe80::a22c:36ff:fe63:d37f/64 scope link
valid_lft forever preferred_lft forever

Contact me here;
https://www.facebook.com/especialized

 

todo: finish this post later.

todo: power draw requirements for bluetooth PAN over WIFI.

Leave a Reply

Your email address will not be published. Required fields are marked *