After boot, we need to execute some commands to get the BT controller alive:  

user@bananapim7:~$ hcitool dev
Devices:


user@bananapim7:~$ sudo modprobe bluetooth

user@bananapim7:~$ sudo modprobe hci_uart


user@bananapim7:~$ sudo btattach -B /dev/ttyS6 -P bcm -S 115200 &
[1] 3405
Attaching Primary controller to /dev/ttyS6
Switched line discipline from 0 to 15
Device index 0 attached


user@bananapim7:~$ hcitool dev
Devices:
    hci0    F0:23:AE:09:82:E3

Thanks for your help!

PS: 

Some data that may help:

user@bananapim7:~$ uname -a
Linux bananapim7 6.1.115-vendor-rk35xx #1 SMP Thu Oct 16 07:30:53 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
user@bananapim7:~$ 
user@bananapim7:~$ lsmod
Module                  Size  Used by
bnep                   24576  2
squashfs               53248  0
pwm_fan                20480  0
rk805_pwrkey           16384  0
bcmdhd               1495040  0
panfrost               61440  0
drm_shmem_helper       20480  1 panfrost
gpu_sched              40960  1 panfrost
joydev                 24576  0
input_leds             16384  0
zram                   28672  3
zsmalloc               20480  1 zram
binfmt_misc            20480  1
sch_fq_codel           20480  4
fuse                  114688  1
dm_mod                110592  0
nfnetlink              20480  1
ip_tables              28672  0
ipv6                  458752  48
r8169                  77824  0
nvmem_rockchip_otp     20480  0
rockchip_cpuinfo       16384  1 nvmem_rockchip_otp
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
user@bananapim7:~$ 
user@bananapim7:~$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-10-27 23:00:19 -03; 1 day 9h ago
       Docs: man:bluetoothd(8)
   Main PID: 1794 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37795)
     Memory: 2.5M (peak: 3.0M)
        CPU: 48ms
     CGroup: /system.slice/bluetooth.service
             └─1794 /usr/libexec/bluetooth/bluetoothd

oct 27 23:00:19 bananapim7 systemd[1]: Started bluetooth.service - Bluetooth service.
oct 27 23:00:19 bananapim7 bluetoothd[1794]: Starting SDP server
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support csip plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support micp plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support vcp plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support mcp plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support bass plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: src/plugin.c:plugin_init() System does not support bap plugin
oct 27 23:00:19 bananapim7 bluetoothd[1794]: Bluetooth management interface 1.22 initialized    

I have Armbian Ubuntu install that may have been messed around with and is not showing /dev/mmcblk1, where as a fresh uSCDCard install is.

I am wondering if this is possibly affecting a large number targets or whether its just BananaPi-M7 / rockchip64 ?

I have tried on another monitor also and am getting a black screen.

On doing an `apt-get upgrade` on ssh terminal I happened to loose by HDMI display.

AFAICT It looks like Ubuntu 'backgraded' gnome v46 (in Nobel release, and also in my older unofficial image) to v44.

https://armbian.atlassian.net/jira/software/c/projects/AR/issues/AR-2702?jql=project %3D "AR" ORDER BY created DESC

It also fails to resync when turned off and on again or another source is selected on and the BPi-M7 is reselected, resulting in a flickering white backgound.

Armbian_25.2.1_Bananapim7_bookworm_vendor_6.1.99_xfce_desktop.img

with apt-get update & apt-get upgrade

Armbian 25.2.3 bookworm 12

Linux bananapim7 6.1.99-vendor-rk35xx

Ubuntu works fine and supports the Viewsonic VX3276-2K-MHD WQHD on 2560x1440 for this but has a display area issue when changing the scaling where 3/4 of the screen is black on x2. I will file this separately.

Armbian_25.2.1_Bananapim7_noble_current_6.12.13_xfce_desktop.img

with apt-get update & apt-get upgrade

Armbian 25.2.3 noble 24.04

https://armbian.atlassian.net/jira/software/c/projects/AR/issues/AR-2641?jql=project %3D "AR" ORDER BY created DESC

I had a failed install as the uSDCard image was 256GB larger than the eMMC, so it balked. I tried a 128GB uSDCard, followed by a 64GB uSDCard, but got the same error each time even on the 64GB one. I seem to have two partitions on the eMMC, mmcblk0boot0, and mmcblk0boot2 now,.

I am not sure if they were on the boards eMMC originally or what the boot sequence for the board is If the Masked ROM tries to boot the uSDCard if present and if that fails it boots the eMMC ?

Do I  clear mmcblk0 and try again with the 64GB uSDcard ? Or is mmcblk0 required to boot mmcblk1 ?

I have done an

Quote

armbianmonitor -u

  :-

https://paste.armbian.com/ehanixecoh

Also

```
aaronngray@bananapim7:~$ lsblk -a
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
ram0           1:0    0     4M  0 disk
loop0          7:0    0     0B  0 loop
loop1          7:1    0     0B  0 loop
loop2          7:2    0     0B  0 loop
loop3          7:3    0     0B  0 loop
loop4          7:4    0     0B  0 loop
loop5          7:5    0     0B  0 loop
loop6          7:6    0     0B  0 loop
loop7          7:7    0     0B  0 loop
mmcblk1      179:0    0  59.7G  0 disk
└─mmcblk1p1  179:1    0  59.1G  0 part /var/log.hdd
                                       /
mmcblk0      179:32   0 115.3G  0 disk
mmcblk0boot0 179:64   0     4M  1 disk
mmcblk0boot1 179:96   0     4M  1 disk
zram0        252:0    0  15.5G  0 disk [SWAP]
zram1        252:1    0    50M  0 disk /var/log
zram2        252:2    0     0B  0 disk
nvme0n1      259:0    0   1.8T  0 disk
```

First of all thanks for this awesome product, BananaPi M7 is really great in many ways!

Only one last thing appears to be broken on our project, I'm having connection troubles from IoT in 2.4Ghz against BananaPi setup as an AP.I'm using the latest up to date armbian server image
 

$ uname -a
Linux bananapim7 6.1.75-vendor-rk35xx #1 SMP Tue Nov 12 08:48:32 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

$ cat /etc/*release
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapim7
BOARD_NAME="Banana Pi M7"
BOARDFAMILY=rockchip-rk3588
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=26d182157
LINUXFAMILY=rk35xx
ARCH=arm64
BOOT_SOC=rk3588
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
KERNEL_TARGET=edge,current,vendor
KERNEL_TEST_TARGET=vendor,current
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
OVERLAY_DIR="/boot/dtb/rockchip/overlay"
VENDOR="Armbian"
VENDORDOCS="https://docs.armbian.com"
VENDORURL="https://www.armbian.com"
VENDORSUPPORT="https://forum.armbian.com"
VENDORBUGS="https://www.armbian.com/bugs"
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
VERSION=24.11.1
REVISION=24.11.1
IMAGE_UUID=14f1a719-8726-4abf-a76a-d0c4da1658c6
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapim7
BOARD_NAME="Banana Pi M7"
BOARDFAMILY=rockchip-rk3588
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=26d182157
LINUXFAMILY=rk35xx
ARCH=arm64
BOOT_SOC=rk3588
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
KERNEL_TARGET=edge,current,vendor
KERNEL_TEST_TARGET=vendor,current
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
OVERLAY_DIR="/boot/dtb/rockchip/overlay"
VENDOR="Armbian"
VENDORDOCS="https://docs.armbian.com"
VENDORURL="https://www.armbian.com"
VENDORSUPPORT="https://forum.armbian.com"
VENDORBUGS="https://www.armbian.com/bugs"
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
VERSION=24.11.1
REVISION=24.11.1
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS"
PRETTY_NAME="Armbian 24.11.1 noble"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
PRIVACY_POLICY_URL="https://www.armbian.com"
UBUNTU_CODENAME=noble
LOGO="armbian-logo"
ARMBIAN_PRETTY_NAME="Armbian 24.11.1 noble"

The wireless config seems to be alright:

$ iwconfig                                                                                                                                                                             
...

wlan0     IEEE 802.11  ESSID:""  
          Mode:Master  Channel:34  Access Point: Not-Associated   
          Bit Rate:1.2005 Gb/s   Tx-Power:32 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Managementmode:All packets received
          Link Quality=5/5  Signal level=-2 dBm  Noise level=-99 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ iw wlan0 info
Interface wlan0
    ifindex 4
    wdev 0x1
    addr b8:2d:28:5a:56:f6
    type managed
    wiphy 0
    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
    txpower 31.00 dBm

$ iw ap0 info
Interface ap0
    ifindex 16
    wdev 0x4
    addr ba:2d:28:5a:56:f6
    ssid XXXXXXXX
    type AP
    wiphy 0
    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
    txpower 31.00 dBm

The interface is correctly setup:

$ ip a
...
16: ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ba:2d:28:5a:56:f6 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.1/8 brd 10.255.255.255 scope global noprefixroute ap0
       valid_lft forever preferred_lft forever
    inet6 fe80::be9a:7773:f8dc:f9fa/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

$ nmcli con show
NAME                 UUID                                  TYPE       DEVICE    
XXXXXXXX           7c89f803-bd17-42e1-8134-e2f6f33edc28  wifi       ap0
...

I'm able to connect to my AP using my laptop (the only differences I see is that I'm using a 5Ghz capable network card even if 2.4Ghz is setup in nmcli config...)
But the IoT equipement keep being deauthenticated with messages like:

$ sudo dmesg
...
[ 2279.531130] [dhd] __dhd_add_sta: Adding  STA 00:XX:XX:XX:70:90
[ 2279.535314] [dhd] [ap0] wl_ext_iapsta_link : [A] connected device 00:XX:XX:XX:70:90
[ 2279.536101] [dhd] dhd_update_sta_chanspec_info: updated chanspec:0x1001 for STA:00:XX:XX:XX:70:90
[ 2279.536133] [dhd] [ap0] wl_notify_connect_status_ap : new sta event for 00:XX:XX:XX:70:90
[ 2279.537036] [dhd] CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set

A quick google search led me to this line in wl_cfg80211.c driver -> https://android.googlesource.com/kernel/msm/+/9a5104b845c1558cc204abfe97c120d14677baa5/drivers/net/wireless/bcmdhd/wl_cfg80211.c#6928
It appear to be a question about params->sta_flags_mask not set, as NL80211_STA_FLAG_AUTHORIZED is set to 0 in include files

Question: Where are set the struct station_parameters ? How could it be modified ?

Reproduce steps script:
 

#!/bin/bash

HOTSPOT="XXXXXXXX"
AP_PASS="XXXXXXXX"
AP_IFACE="ap0"

# Setup iface
sudo iw dev wlan0 interface add $AP_IFACE type __ap

# Setup HotSpot
sudo nmcli con add type wifi con-name $HOTSPOT ssid $HOTSPOT
sudo nmcli con modify $HOTSPOT 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.channel 1 ipv4.method shared
sudo nmcli con modify $HOTSPOT wifi-sec.key-mgmt none
sudo nmcli con modify $HOTSPOT wifi-sec.wep-key-type 1
sudo nmcli con modify $HOTSPOT wifi-sec.wep-key0 $AP_PASS
sudo nmcli con modify $HOTSPOT ifname $AP_IFACE
sudo nmcli con modify $HOTSPOT ipv4.address 10.1.0.1/8
sudo nmcli con modify $HOTSPOT ipv4.gateway 10.1.0.1
sudo nmcli con up $HOTSPOT

Thanks for your help !

The three images are these:

• Armbian_24.8.1_Bananapim7_noble_vendor_6.1.75_gnome-kisak_desktop.img
• Armbian_24.8.1_Bananapim7_jammy_vendor_6.1.75_kde-neon-kisak_desktop.img
• Armbian_24.8.1_Bananapim7_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img

For each image, I booted and logged the board output. The board fails to successfully boot and instead gets stuck in a boot loop. I then mounted the armbi_root partition and edited the file armbi_root/boot/armbianEnv.txt to set verbosity=7, in the hope of getting more useful information from the kernel. I retried booting the board, and I observed the same boot loop, but this time with more kernel logs.

The serial outputs of the failed boots are here:

• Armbian 24.8.1 Noble GNOME: noble.log (see attached files)
• Armbian 24.8.1 Ubuntu 22.04 Jammy: jammy.log (see attached files)
• Armbian 24.8.1 Debian 12 Bookworm: bookworm.log (see attached files)

I’m not sure why the kernel decides to reboot everytime, but I’m sharing the information in case it is useful to someone.

(see original post)

noble.log jammy.log bookworm.log

And was wondering if someone whould be interested in giving me the output of a few tests for me please ?

```

ffmpeg -hide_banner -encoders

```

```

ffmpeg -hide_banner -decoders

```

```

ffmpeg -hide_banner -hwaccels

```

Many thanks in advance.

image：Armbian_24.5.5_Bananapim7_bookworm_vendor_6.1.75_cinnamon_desktop.img

sudo create_ap -m nat wlan0 enP2p33s0 armsom armsom-jack   --no-virt --freq-band 5

Failed to get phy interface
ERROR: Your adapter does not support AP (master) mode

We used joshua-Riek/ubuntu-rockchip's ubuntu system which supports ap and has been connected normally

Hardware interface:

online documents: https://docs.banana-pi.org/en/BPI-M7/BananaPi_BPI-M7