With u.FL antenna (Unictron AA222) connected to AUX connector on the AW-CM276NF module
TorizonCore 5.4.154-5.5.0+git.c65f1622951c
I am unable to maintain a Bluetooth LE connection (peripheral role / GATT server) for more than a few minutes. I have used a variety of central devices (iPhone, iPad, nRF52840 dongle).
The simplest steps to reproduce:
sudo systemctl start dbus
sudo systemctl start bluetooth
bluetoothctl
> power on
> discoverable on
> advertise.name Toradex
> advertise.discoverable on
> advertise on
Then connect using e.g. nRF52840 Dongle via nRF Connect v3.7.1 and wait a few seconds/minutes.
I inevitably get the HCI disconnect event (0x05) with reason āConnection Timeoutā (0x08). The time seems to vary between different centrals. On my iOS devices I get a few minutes, whereas the disconnect happens in a few seconds with the nRF52840 dongle.
What Iāve tried so far:
Iāve checked that the disconnect is not being initiated by the central in all cases.
Tested using a different BLE adapter (nRF52840 dongle running Zephyr HCI USB sample). The problem does not occur, I can maintain a connection indefinitely. This makes me pretty sure the issue is either with the module or the driver.
Tested in both Torizon and in Debian container ( torizon-samples/debian-container)
Tested both the version of bluez that ships with Torizon (5.55) as well as latest (5.63, via debian container)
Tested disabling Wi-Fi first (sudo nmcli radio wifi off); this did not solve it
Just to confirm you are on our TorizonCore software offering correct?
If this is the case, then there are known issues with Bluetooth on TorizonCore. This is due to the Bluetooth feature not being fully tested/complete yet on TorizonCore.
As a sanity check could you try the following. Try flashing our BSP reference images and see if you can reproduce the same results there with your setup. Iām asking this because the current driver for that Bluetooth chipset has some odd issues and quirks.
I want to see if the issue is due to the incomplete feature on TorizonCore, or if itās due to the underlying driver.
Yes, I was using TorizonCore. Today I tested using the Toradex minimal reference image (5.5.0+build.15) and observed the same behavior.
What is the difference between TorizonCore and the BSP reference image for the purposes of Bluetooth? Is there a different driver being used?
Is there any documentation available about the known issues with Bluetooth on TorizonCore?
TorizonCore and the BSP reference images should use the same set of drivers. The full difference between TorizonCore and the reference images are a bit unknown at the moment. It comes down to bluetooth not being fully tested yet with TorizonCore (due to lack of interest historically). But there have been previous known issues with TorizonCore and bluetooth that arenāt observed with the reference BSP. Which is why I said what I said.
However, since you observed the same behavior I doubt itās due to one of these differences. Let me check internally what we can provide you with here.
Sorry for the delay, but our team got around to looking into this issue of yours. Is this something youāre still having issues with and are interested in?
Ok so in short it seems the issue can be resolved by using an updated driver for the WiFi/Bluetooth chipset. This driver is proprietary and may require some legal red-tape. But, Iāll see all that is required on our side.
In case we need to continue this discussion over private email is the email on your account here the best email to contact you with?
Iām currently evaluating the Verdin IMX8M Mini for our application and am having similar issues with our sensors, which communicate over BLE. The longest Iāve seen one of our sensors be able to stay connected is a little over an hour, but usually it disconnects in a few minutes. Both the sensor and our application report a timeout as the reason for the disconnect. I have not seen these problems with other platforms.
Bluetooth is still not fully supported yet on TorizonCore. We have already released our LTS for 5.7. So this means a new feature like Bluetooth will only come on our current 6.X.Y releases which are in development right now. I unfortunately donāt have any timeline I can provide on this though.
Since this thread is quite old could you please make a new thread with your information and details. Please include the version of software you are using as well as what issue you are referring to here regarding that you would like to be āfixedā.