M2-CC3351: bluetoothctl shows "No default controller available"

user6241824

Part Number: M2-CC3351

Tool/software:

Hi,
bluetoothctl shows "No default controller available".
because AM62B-P1 doesn't have cc33xx-nvs.bin or another reason?

[ 3.141483] cc33xx_sdio mmc2:0001:2: Using GPIO as IRQ
[ 3.174552] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 3.218211] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 3.224573] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 3.321699] cc33xx_driver cc33xx.5.auto: Direct firmware load for ti-connectivity/cc33xx-nvs.bin failed with error -2
done
Starting system message bus: done
Starting iptables: OK
Starting bluetoothd: OK
Starting network: [ 3.513364] Bluetooth: Core ver 2.22
ifup: don't have all variables for eth0/inet
[ 3.517148] NET: Registered PF_BLUETOOTH protocol family
[ 3.526315] Bluetooth: HCI device and connection manager initialized
[ 3.536674] Bluetooth: HCI socket layer initialized
[ 3.541919] Bluetooth: L2CAP socket layer initialized
Starting telnetd: OK

Welcome to Buildroot
(none) login: root
# calibrator dev wlan0 cc33xx_plt set_manual_calib -rx 1 -tx 1
set_manual_calib has been called with: 4 Parameters
Calibrator:: Setting Calibration Parameters
# ls -l
total 0
# bluetoothctl show
No default controller available
#

5 months ago

0 Dean Ramsier 5 months ago

Expert 1431 points

This device requires you to send a command via the Wi-Fi host interface to start Bluetooth. See the ble_enable.sh script that was included in the rootfs portion of the SDK.

0 Sabeeh Khan1 5 months ago

TI__Mastermind 32850 points

Hello,

Are you using the buildroot image from TI Processor SDK? If so, which version?

The TI Processor SDK for AM62x currently do not include the BLE driver for CC33xx devices, so you should not expect to see the bluetooth available.

You will need to patch the kernel with one of the "ti-linux" patches from the GitHub repo linked below, depending on which SDK version you are using, and then overwrite the firmware from the respective CC33xx SDK, also linked below.

https://github.com/TexasInstruments-Sandbox/cc33xx-linux-mpu-ports/

https://www.ti.com/tool/download/CC33XX-LINUX-MPU

0 user6241824 5 months ago in reply to Sabeeh Khan1

Prodigy 135 points

Hi Sabeeh,

buildroot image comes from buildroot-2024.05.3 and buildroot-external-TI 10.01.10.04, and two patches: cc33xx_linux_package_1_0_0_8 and cc33xx-linux-mpu-ports/ti-linux-6.6.y/drivers-cc33xx-update-to-1.0.0.8.patch

already did all what you said.

0 user6241824 5 months ago in reply to Dean Ramsier

Prodigy 135 points

Hi Dean,

thanks for your answer. the issue still exist after added these configurations:

CONFIG_DEBUG_FS=y
CONFIG_CFG80211_DEBUGFS=y
CONFIG_BT_DEBUGFS=y
CONFIG_MAC80211_DEBUGFS=y

# mount -t debugfs none /sys/kernel/debug
# ./ble_enable.sh

# bluetoothctl show
No default controller available

# ls -la /sys/kernel/debug/ieee80211/phy0/cc33xx/
total 0
drwxr-xr-x 3 root root 0 Jan 1 00:00 .
drwxr-xr-x 3 root root 0 Jan 1 00:00 ..
-r-------- 1 root root 0 Jan 1 00:00 antenna_diversity_enable
-r-------- 1 root root 0 Jan 1 00:00 antenna_diversity_select_default_antenna
-r-------- 1 root root 0 Jan 1 00:00 antenna_diversity_set_rssi_threshold
-r-------- 1 root root 0 Jan 1 00:00 antenna_select
-r-------- 1 root root 0 Jan 1 00:00 beacon_filtering
-r-------- 1 root root 0 Jan 1 00:00 beacon_interval
-r-------- 1 root root 0 Jan 1 00:01 ble_enable

0 user6241824 5 months ago in reply to user6241824

Prodigy 135 points

k3-am62x-sk-common.dtsi
/ {
aliases {
serial2 = &main_uart0;
serial3 = &main_uart1; <-- add this line

# dmesg

.....

[ 1.349919] omap8250 2810000.serial: PM domain pd:152 will not be powered off
[ 1.357761] 2810000.serial: ttyS3 at MMIO 0x2810000 (irq = 240, base_baud = 3000000) is a 8250
[ 1.366636] serial serial0: tty port ttyS3 registered
...

[ 2.773952] Bluetooth: Core ver 2.22
[ 2.780386] k3-m4-rproc 5000000.m4fss: local reset is deasserted for device
[ 2.792149] remoteproc remoteproc0: 5000000.m4fss is available
[ 2.794767] rtc-ti-k3 2b1f0000.rtc: registered as rtc0
[ 2.800102] NET: Registered PF_BLUETOOTH protocol family
[ 2.804644] rtc-ti-k3 2b1f0000.rtc: setting system clock to 1970-01-01T00:00:08 UTC (8)
[ 2.808942] remoteproc remoteproc0: powering up 5000000.m4fss
[ 2.809995] Bluetooth: HCI device and connection manager initialized
[ 2.810016] Bluetooth: HCI socket layer initialized
[ 2.810025] Bluetooth: L2CAP socket layer initialized

Wi-Fi

Wi-Fi forum

M2-CC3351: bluetoothctl shows "No default controller available"