** Merge proposal linked:
https://code.launchpad.net/~kzapalowicz/snappy-hwe-snaps/+git/bluez/+merge/341516
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth
** Merge proposal linked:
https://code.launchpad.net/~kzapalowicz/snappy-hwe-snaps/+git/bluez/+merge/331039
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth
** Changed in: snappy
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifi
well, the btattach tool would still have to be shipped and executed by
bluez.
how would the additional info added in the interface data get handed over to
the btattach tool ?
how would we execute it ? i admit it looks a lot better and bluez wouldn't have
to define each and every board implement
I like @morphis idea
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifications about this bug go to:
https:
Btw. you guys should see if the more modern btattach utility does the
job instead of hciattach too. See
http://manpages.ubuntu.com/manpages/xenial/man1/btattach.1.html for a
few details. Sooner or later btattach will replace hciattach as the way
to attach serial lines to the kernel bluetooth stack.
@ogra
A few questions to make sure that I understand:
I have seen that you have added /dev/ttyAMA to the serial interface of
snapd. Any other changes on this side such as discussed previously
modifications to gadget snap?
Now you are also suggesting a unit that would hciattach to the desired
ser
here is a proof of concept script+systemd unit ...
http://paste.ubuntu.com/24537569/
using this setup i have properly working BT after boot *if* the bluez snap is
in --devmode
my proposal forward would be to:
- ship a similar script inside the bluez package
- make it a daemon so we get a syst
with todays edge image the interface is available on the pi3 ... we now
need a device specific hciattach systemd unit in the bluez snap (since
that ships the hciattach binary, we cant ship this in the image)
ogra@pi3:~$ snap interfaces|grep blue
:bluetooth-control-
pi3:pi-bluetooth
@ogra going back to this after a while, what is the status - is it being
included in the gadget snap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on
Jamie's suggestion seems spot on for the time being. This is really
something for the gadget to expose, and it should be made in an explicit
way. It can be a regular expression as suggested because then you cannot
assign a particular snap plug to a particular serial port anymore.
The upcoming hot-
Sorry, it CANNOT be a regular expression. I wish Launchpad allowed
edits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
also ... keep in mind that we will additionally need to ship a systemd
unit caring for the hciattach call that will be equally specific and
will likely live where the hciattach tool lives (in the bluez package),
we can not ship this in the gadget without having the tool available. i
think we need t
@korad, well, i would assume that 90% of the IoT boards we will support
will have such a UART based setup, so i would lean towards having
generic serial tty support in the BT rules without having to define it
for each single board in the gadget... i.e. simply by adding rw support
for /dev/tty[A-Z]*
@jdstrand @ogra
This depends on how the Bluetooth chip is wired on hardware level. If it
is using UART like in this case it all further depends on how the UARTs
are wired. It might be /dev/ttyAMA0 however it might also be /dev/ttyS0
or even /dev/bluetooth - whoever writes the driver has the luxury
For the slot Permanent policy I think it is fine to allow the bluez
interface access to /dev/ttyAMA0. ofono, ppp, et al are in similar
situations.
That said, if I understand this bug correctly, the most correct solution
would seem to be for the pi gadget snap to declare the serial-port
interface,
** Tags added: snapd-interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifications about this bug go
@konrad: 5.44-1-dev from the edge channel works fine now as long as i
use --devmode ... not using devmode gets me a denial:
[ 48.909501] audit: type=1400 audit(1491387062.644:27):
apparmor="DENIED" operation="open" profile="snap.bluez.hciattach"
name="/dev/ttyAMA0" pid=1501 comm="hciattach" requ
@ogra, yes, sure, I created report here -
https://bugs.launchpad.net/snappy/+bug/1679747
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running
@ogra, changes pushed to snappy-hwe-snaps/+git/bluez
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notificati
@ogra, yes I will include
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifications about this bug go to:
h
@Nikolay: this bug is about generally making BT work on the pi images by
default, your problem is very specific, would you file a new bug for it
instead (so we can close this one once the driver works at all)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And I experiences quite similar issue, that I fill here -
https://bugs.launchpad.net/snappy/+bug/1679432
RPi establish SCO connection with my headset and I can send SCO packets
to it (with dragonboard I can not even send them), and actually here
sound from headset. But I cannot read SCO packets fr
oops, I forget the attachment that I promised. It's
here.?field.comment=oops, I forget the attachment that I promised. It's
here.
** Attachment added: "bluez.tar.xz"
https://bugs.launchpad.net/snappy/+bug/1674509/+attachment/4854099/+files/bluez.tar.xz
--
You received this bug notification b
I did the same patch - modify firmware patch and speed initialization patch...
and I got bluetooth working on RPi!
I used my own app to test it - https://github.com/Nikolay-Kha/BluetoothAudio
hcitool scan
also works fine. bluetoothctl starts, but I cannot type anything there, don't
know why.
Pat
note: this is without any overlay dtb loaded, using the standard Ubuntu
Core config.txt
so we need the patched hciattach and a systemd unit that calls it like
above to initialize the controller.
@konrad: can you include:
https://github.com/OpenELEC/OpenELEC.tv/blob/6b9e7aaba7b3f1e7b69c8deb1558ef
WHEEE !
ogra@pi3:~$ sudo mount --bind /home/ogra/hciattach
/snap/bluez/current/usr/bin/hciattach
ogra@pi3:~$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -
bcm43xx_init
Flash firmware /lib/firmware/BCM43430A1.hcd
Set Controller UART speed to 921600 bit/s
Device setup complete
ogra@pi3:~$ sud
@ogra
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]#
Try 'power on' before you 'scan on'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable
Can you try with hcitool?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifications about this bug go to:
h
using a patched hciattch (with the speed setting patch from above as
well as a fixed FIRMWARE_DIR pointing to /lib/firmware):
ogra@pi3:~$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -
bcm43xx_init
Flash firmware /lib/firmware/BCM43430A1.hcd
Set Controller UART speed to 921600 bit/s
Device se
the respective lines from dmesg:
[ 32.367423] Bluetooth: Core ver 2.21
[ 32.367486] NET: Registered protocol family 31
[ 32.367491] Bluetooth: HCI device and connection manager initialized
[ 32.367509] Bluetooth: HCI socket layer initialized
[ 32.367521] Bluetooth: L2CAP socket layer ini
seems the /etc/firmware dir is actually hardcoded in
https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-
snaps/+git/bluez/tree/tools/hciattach_bcm43xx.c?h=bluez/5.37
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
ok, i got a little further, seems the bluez snap doesnt really have
access to ttyAMA0 so i had to re-install it in --devmode ... now i get
(still without the dtoverlay though, since this does not boot at all):
ogra@pi3:~$ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -
bcm43xx_init
Cannot open
now i see bluetooth in lsmod right after boot when not changing anything in
config.txt ...
but still no working BT:
ogra@pi3:~$ sudo bluez.bluetoothctl
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
No default controller
@ogra: done, and i kicked a new build of the rpi2 kernel snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage
@paolo:
bluez--firmware is in the PPA now, can you add it to the:
PACKAGE :=
line for pi2 in the Makefile ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth d
Makes sense to include the bluetooth firmware files in the kernel snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
T
@paolo: this is all ancient bluez 4 stuff i fear ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notificati
could we just ship the fw files in the pi2-kernel snap ?
i'll happily push the deb to the image PPA where the kernel snap Makefile could
pull it from ...
iirc there is already some special casing for pi2 in the Makefile code that
installs the raspberrypi-wireless-firmware deb from the PPA.
--
Here is the bluez package i tested:
https://archive.raspberrypi.org/debian/pool/main/b/bluez/bluez_5.23-2+rpi2_armhf.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find
The kernel is fine, i've tested it on a xenial image:
-add to config.txt:
dtoverlay=pi3-miniuart-bt
core_freq=250
-grab raspberry's bluez and bluez-firmware packages:
https://archive.raspberrypi.org/debian/pool/main/b/bluez-firmware/bluez-
firmware_1.2-3+rpi1_all.deb
and install both
-reboot
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 runni
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
** Changed in: snappy
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to fin
@ogra thanks for following up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674509
Title:
Unable to find bluetooth device on RPi3 running Ubuntu Core 16
To manage notifications about this bug go t
so digging deeper there are dtoverlay=pi3-miniuart-bt and dtoverlay=pi3
-disable-bt overlays but no matter which combo of enable_uart, core_freq
and either overlay i use, as soon as i enable them no boot is possible
at all anymore. (note that we use other overlays successfully in teh
default setup)
46 matches
Mail list logo
