Subject: Bluetooth: Unknown BR/EDR signaling command 0x16 / Wrong link type (-22) on meson-gx / Banana Pi M2 Pro

Description: When connecting modern Android (POCO F7) and Windows/Linux devices (Lenovo Legion) via Bluetooth to Banana Pi M2 Pro, the dmesg log gets flooded with BR/EDR signaling errors during connection/disconnection phases.

Steps taken: - Forced 'ControllerMode = bredr' in /etc/bluetooth/main.conf - Disabled USB autosuspend for the BT controller (set to -1)

Logs: [ 345.122975] Bluetooth: Unknown BR/EDR signaling command 0x16 [ 345.123005] Bluetooth: Wrong link type (-22)

Environment: - Board: Banana Pi M2 Pro (Amlogic S905X3) - Kernel version: 6.18.34-current-meson64

nano armbianEnv.txt

extraargs=usbcore.autosuspend=-1

The problem with Bluetooth on bananapim2pro is that I constantly have trouble connecting. My tweaks to the settings fixed it somewhat, but not 100%... Finally, if all else fails, I use this method:

sudo rmmod btusb
sudo modprobe btusb
sudo systemctl restart bluetooth
sudo systemctl restart bluealsa

But I have a question: are there any kernel/driver fixes or updates for this Bluetooth model?

I was trying to use SPI communication with Banana Pi M2 Pro.

I am currently using Armbian 26.5.1 and I realized that I cannot find spidev from /boot/dev/ .

I tried loading all dtbo files from armbian-config but still I can't get SPI.

Is there something that I haven't check yet?

........................
verbosity=1
console=both
overlay_prefix=meson
fdtfile=amlogic/meson-sm1-bananapi-m2-pro.dtb
rootdev=UUID=a4fb8074-c453-45da-ab31-4d61dca46cfa
rootfstype=ext4
overlays=i2cA i2cB
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

..................

There are other options, but they probably don't apply to bananapim2pro.  :

sm1-odroid-c4-i2c0

g12b-bananapi-cm4-i2c2

g12a-radxa-zero-i2c-ao.... 

For coreelec, I erased the emmc using the Image burning tool and a usb cable. Android boots up normally and I execute reboot update and the SD with coreelec boots up correctly.

For armbian, I insert the SD card formated with Armbian_24.11.1_Bananapim2pro_bookworm_current_6.6.61_minimal.img and Android boots up, next, I execute "reboot update" and Android shows a error page.

Attached there is a serial log, the one from coreelec is from cold boot to coreelec using a SD card, without needing to type "reboot update". The second, is from armbian using an armbian SD, I typed reboot update on android and next error image.

My whole intention is to install armbian directly on emmc, and boot up without SD card. Hope somebody can helpme.

coreelec_good_boot.txt armbian_bad_boot.txt

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d6:e3:db:f5:f2:24 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.124/24 metric 100 brd 192.168.100.255 scope global dynamic end0
       valid_lft 259179sec preferred_lft 259179sec
    inet6 fe80::d4e3:dbff:fef5:f224/64 scope link 
       valid_lft forever preferred_lft forever
4: wlx60fb005126f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 60:fb:00:51:26:f0 brd ff:ff:ff:ff:ff:ff

This is what the network status looks like after a reboot:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d6:e3:db:f5:f2:24 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.124/24 metric 100 brd 192.168.100.255 scope global dynamic end0
       valid_lft 258362sec preferred_lft 258362sec
    inet6 fe80::d4e3:dbff:fef5:f224/64 scope link 
       valid_lft forever preferred_lft forever

Nothing helps other than unplugging the power cable and plugging it back in.

Tried the following images:

Armbian_24.8.1_Bananapim2pro_bookworm_current_6.6.47_minimal.img.xz
Armbian_24.5.3_Bananapim2pro_bookworm_current_6.6.36_minimal.img.xz
Armbian_24.2.1_Bananapim2pro_bookworm_current_6.6.16.img.xz

Outputs of armbianmonitor -U are in attachment.

wifi_ok.txt wifi_no.txt

What happened? I connected a new harddrive via usb3 but the machine wouldn't boot because of some "Unexpected XHCI event". 

I had to add a usbstoragequirks to u-boot env. (via armbian-config) to solve that, but now the usb otg port is no longer working.

Googled a lot and found one possible solution but it did not work for me ( https://forum.banana-pi.org/t/topic/5485/13 ).

https://paste.armbian.com/aqowuxukev

root@bananapi-m2p:~# lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

Do I have a defective device, or is the WiFi not actually a USB module?  Is there something else I need to try to enable WiFi?

Thanks,

Ray