kris777
Members
-
Joined
-
Last visited
-
-
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?
-
Gemini info 😞 ..... In the official, pure Armbian for Banana Pi M2 Pro, enabling SPI is currently extremely difficult (and even impossible for the average user) If you absolutely need the SPI bus for your project: Operating system change: SPI works without any problems on official system images provided directly by the board manufacturer (BPI-M2 Pro Debian/Ubuntu with kernel 4.9 from Amlogic). The manufacturer uses an older but fully modified kernel (Kernel BSP), where all pins are rigidly and correctly assigned. Or... Staying with Armbian: If you must stick with Armbian, it's safer to abandon SPI attempts and—if possible—connect the target device to a free I2C bus or UART serial communication (which work flawlessly in Armbian on this board). But ultimately, the Armbian system developer will have to decide. (Maybe there is some method to enable SPI on the latest Armbian images/firmware?) 🙂 Check https://docs.banana-pi.org/en/BPI-M2_Pro/BananaPi_BPI-M2_Pro Armbian older firmware (bananapi manufacturer's firmware) (bookworm): https://drive.google.com/drive/folders/1DPkc7AHEZVS7PT_yzhNH1Dfuiz99mE0p
-
-
-
-
Thanks for the info to try other options 🙂 Thanks for the tip, I'll try other options 🙂 It worked for: odroid-c4 ... basically, the settings are the same as for the OrangePI3LTS, I'm talking about connecting cables to a 40x2 / 20x2 LCD. The diagram for the BananapiM2pro is as follows: My Winstar 40x2 OLED LCD compatible with drivers: hd44780 / driver: WS0010 is detected in the system as: 3f .................................. sudo i2cdetect -y 0 [sudo] kris: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 3f 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- .................................. You can also enter the appropriate values yourself in the file: sudo nano /boot/armbianEnv.txt 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=sm1-odroid-c4-i2c0 sm1-odroid-c4-i2c1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u regards
-
What should the correctly enabled I2C service (for a 40x2 LCD) look like on Bananapim2pro? Should I edit the armbianEnv.txt file and add, for example, the following entry: overlays=i2c0 i2c1? The armbian-config service is a bit confusing, and after editing it, I get this: ........................ 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....
-
After the update/upgrade, all CPUs are now installed nproc 4 This didn't fix my Bluetooth (maybe it's some individual bug in my system?) but since Bluetooth works correctly in the new images for OrangePi 3 LTS, I'm marking this thread as resolved... I'll probably install the latest image soon, although it will be time-consuming. ........................... orangepi3-lts:~# dmesg | grep "CPU" [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.005157] smp: Bringing up secondary CPUs ... [ 0.007070] Detected VIPT I-cache on CPU1 [ 0.007260] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.009368] Detected VIPT I-cache on CPU2 [ 0.009541] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.011117] Detected VIPT I-cache on CPU3 [ 0.011261] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.011373] smp: Brought up 1 node, 4 CPUs [ 0.011398] CPU: All CPU(s) started at EL2 [ 0.011443] CPU features: detected: 32-bit EL0 Support [ 0.011449] CPU features: detected: 32-bit EL1 Support [ 0.011458] CPU features: detected: CRC32 instructions [ 0.011470] CPU features: detected: PMUv3 [ 0.260754] ledtrig-cpu: registered to indicate activity on CPUs [ 0.414642] sun50i_cpufreq_nvmem: Using CPU speed bin speed0 [ 0.457342] WARNING: CPU: 3 PID: 71 at drivers/iommu/iommu.c:612 __iommu_probe_device+0x1a8/0x4a0 [ 0.457375] CPU: 3 UID: 0 PID: 71 Comm: kworker/u16:4 Not tainted 6.18.19-current-sunxi64 #2 PREEMPT Ps. I don't know if I announced the CPU solution too early? Maybe there's a problem with the processor clock speed? .............. cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# cpu Temperature: 40 °C CPU-0 Frequency: 1608 Mhz CPU-1 Frequency: 1608 Mhz CPU-2 Frequency: 1608 Mhz CPU-3 Frequency: 1608 Mhz root@orangepi3-lts:~# cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq 1608000 root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance ............... shouldn't it be : 1810000 ... ?
-
I tested the new version (Armbian_26.2.0-trunk.591_Orangepi3-lts_forky_current_6.18.18_minimal) in terms of bloototh and it's OK... but there are errors that rule out this image. Namely, the system lacks 4 working processor cores 🙂 ... only one. Something is wrong at startup because the green LED is on and the red LED is constantly flashing/pulsing. Bringing up secondary CPUs ... [ 5.092655] CPU1: failed to come online [ 5.092666] CPU1: failed in unknown state : 0x0 [ 10.217311] CPU2: failed to come online [ 10.217324] CPU2: failed in unknown state : 0x0 [ 15.341948] CPU3: failed to come online [ 15.341961] CPU3: failed in unknown state : 0x0 [ 15.342047] smp: Brought up 1 node, 1 CPU [ 15.342057] SMP: Total of 1 processors activated. [ 15.342063] CPU: All CPU(s) started at EL2 [ 15.342112] CPU features: detected: 32-bit EL0 Support [ 15.342119] CPU features: detected: 32-bit EL1 Support [ 15.342129] CPU features: detected: CRC32 instructions [ 15.342146] CPU features: detected: PMUv3 [ 15.342193] alternatives: applying system-wide alternatives It's some kind of incompatibility: U-Boot / TF-A / kernel .... Similar errors are found in the version uploaded by: armbian imager (minimal / cli / debian - trixie) more information: https://paste.armbian.com/afokonucej command "poweroff" not working ! ? On version: Ubuntu / minimal (cli) there are the same errors regarding CPU...etc ..................................... dmesg | grep "CPU" [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.006129] smp: Bringing up secondary CPUs ... [ 5.092344] CPU1: failed to come online [ 5.092356] CPU1: failed in unknown state : 0x0 [ 10.216761] CPU2: failed to come online [ 10.216771] CPU2: failed in unknown state : 0x0 [ 15.341165] CPU3: failed to come online [ 15.341176] CPU3: failed in unknown state : 0x0 [ 15.341242] smp: Brought up 1 node, 1 CPU [ 15.341258] CPU: All CPU(s) started at EL2 [ 15.341291] CPU features: detected: 32-bit EL0 Support [ 15.341297] CPU features: detected: 32-bit EL1 Support [ 15.341309] CPU features: detected: CRC32 instructions [ 16.273971] ledtrig-cpu: registered to indicate activity on CPUs [ 17.351303] sun50i_cpufreq_nvmem: Using CPU speed bin speed0 .........................
-
That's strange 🙂 ...we have the same kernel. Maybe something's broken in the system? But I haven't messed with Bluetooth in the system. I've only updated the system: apt update /apt upgrade /reboot 🙂 root@orangepi3-lts:~# rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bluetooth unblocked unblocked 1 wlan phy0 unblocked unblocked .............................. bluetoothctl Waiting to connect to bluetoothd... it keeps reading but shows nothing? ................... bt-device -l ** ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Aborted ............. Something must have broken in the system, but what and where? Can you give me the exact: Armbian image + version ... Contents of ..../lib/firmware/uwe5622/ also: armbianEnv.txt Output dmesg | grep -i uart i dmesg | grep -i bluetooth Maybe that will help me figure out where the errors are in my system? Or maybe I have Debian and you have Ubuntu? Ps. or, more simply, information from the file: diagnostics.txt command in terminal: ................. ( uname -a cat /etc/os-release ls -lh /lib/firmware/uwe5622/ lsmod | grep -iE "bt|sprd|uwe" dmesg | grep -i uart ls /dev/tty* | grep -i "ttyS\|ttyAMA\|ttyBT" cat /boot/armbianEnv.txt rfkill list hciconfig -a bluetoothctl list hcitool dev bt-device -l dmesg | grep -iE "bluetooth|uwe|sprd|hci" ) > diagnostics.txt .....................
-
-
-
-
