Yocto mickledore Bluetooth bringup

[PavanNittala]

I am not able to bring up bluetooth on imx8mm-c2 board ,  I am using AMPAK firmware BCM4362A2_001.003.006.1132.1255.hcd , this is my dts file change 

&uart3 { /* BT */
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart3>;
assigned-clocks = <&clk IMX8MMN(CLK_UART3)>;
assigned-clock-parents = <&clk IMX8MMN(SYS_PLL1_80M)>;
uart-has-rtscts;
status = "okay";

bluetooth {
compatible = "brcm,bcm43438-bt";
enable-gpios = GP_BT_ENABLE;
max-speed = <3000000>;
};
};

[ 186.437564] Bluetooth: HCI UART driver ver 2.3
[ 186.442064] Bluetooth: HCI UART protocol H4 registered
[ 186.447244] Bluetooth: HCI UART protocol BCSP registered
[ 186.452582] Bluetooth: HCI UART protocol ATH3K registered
[ 186.458350] Bluetooth: HCI UART protocol Broadcom registered
[ 186.458475] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
[ 186.464121] Bluetooth: HCI UART protocol QCA registered
[ 186.471653] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
[ 186.484319] hci_uart_bcm serial0-0: No reset resource, using default baud rate
[ 188.734730] Bluetooth: hci0: command 0x0c03 tx timeout
[ 196.830734] Bluetooth: hci0: BCM: Reset failed (-110)

root@nitrogen8mm:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:4 acl:0 sco:0 commands:1 errors:0

[PavanNittala · Accepted solution]

Thanks to grok3, the new AI tool, i was able to resolve this . Now i have to bring down rfkill and up it again to make bluetooth work

+#if 0
pinctrl_uart3: uart3grp {
fsl,pins = <
MX8MMN(IOMUXC_ECSPI1_SCLK_UART3_DCE_RX, 0x140)
@@ -320,6 +321,17 @@ MX8MMN(IOMUXC_ECSPI1_MISO_UART3_DCE_CTS_B, 0x140)
MX8MMN(IOMUXC_NAND_DQS_GPIO3_IO14, 0x119)
>;
};
+#else
+ pinctrl_uart3: uart3grp {
+ fsl,pins = <
+ MX8MM_IOMUXC_ECSPI1_SCLK_UART3_DCE_RX 0x49
+ MX8MM_IOMUXC_ECSPI1_MOSI_UART3_DCE_TX 0x49
+ MX8MM_IOMUXC_ECSPI1_SS0_UART3_DCE_RTS_B 0x49
+ MX8MM_IOMUXC_ECSPI1_MISO_UART3_DCE_CTS_B 0x49
+ MX8MM_IOMUXC_NAND_DQS_GPIO3_IO14 0x19 /* BT_REG_ON */
+ >;
+ };
+#endif

+#if 0
&uart3 { /* BT */
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart3>;
@@ -1259,15 +1272,29 @@ &uart3 { /* BT */
assigned-clock-parents = <&clk IMX8MMN(SYS_PLL1_80M)>;
uart-has-rtscts;
status = "okay";
-#if 1
- 1 {
+ bluetooth {
compatible = "brcm,bcm43438-bt";
brcm,bt-pcm-int-params = [01 02 00 01 01];
enable-gpios = GP_BT_ENABLE;
max-speed = <2000000>;
};
-#endif
};
+#else
+&uart3 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_uart3>;
+ assigned-clocks = <&clk IMX8MM_CLK_UART3>;
+ assigned-clock-parents = <&clk IMX8MM_SYS_PLL1_80M>;
+ uart-has-rtscts; /* Flow control for AP6275S */
+ status = "okay";
+
+ bluetooth {
+ compatible = "brcm,bcm43438-bt"; /* AP6275S */
+ max-speed = <3000000>;
+ shutdown-gpios = <&gpio3 14 GPIO_ACTIVE_HIGH>; /* BT_REG_ON */
+ };
+};
+#endif

[PavanNittala]

Hi @joanxie , Thanks for the reply ,  Vendor asked to check using Scope which i don't have at the moment.

Some more info below , i am not able to see /dev/ttymxc2 , I think that's the issue ??

root@nitrogen8mm:~# dmesg |grep -iE 'tty'
[ 0.000000] Kernel command line: console=ttymxc1,115200 consoleblank=0 rootwait fixrtc root=/dev/mmcblk0p2 snd.slots=,snd-soc-imx-hdmi
[ 0.090110] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 185, base_baud = 5000000) is a IMX
[ 0.090237] serial serial0: tty port ttymxc2 registered
[ 0.090740] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 186, base_baud = 1500000) is a IMX
[ 0.821277] printk: console [ttymxc1] enabled

[joanxie]

you can use ls /dev/ttymxc* to check, and to confirm if you load the module correctly or not, pls refer to the link as below as reference

Bluetooth NXP UART Driver Linux BSP 6.1.22 btnxpuart - NXP Community

[joanxie]

refer to the log, maybe this issue is related to your module, did you contact the BT vendor to double confirm this?