2397859_en-US

はい

IW612 Bluetooth UART not responding on i.MX95 after combo firmware download

Hello,

we are bringing up Bluetooth on a Verdin i.MX95 WB running the NXP Android 15 BSP (Linux 6.6.58). The onboard wireless module is a u-blox MAYA-W260 based on NXP IW612.

Wi-Fi works correctly over SDIO, and the combo firmware is successfully loaded:

Request firmware: sduart_nw61x_v1.bin.se
Wlan: FW download over
WLAN FW is active

,Bluetooth instead does not appear to work. Whenever we enable it on Android settings, the UI switch is frozen and no BT device is found.

Bluetooth is connected to LPUART6 (/dev/ttyLP5). The NXP vendor HAL opens the UART successfully.

We initially found that hardware flow control blocked transmission; after temporarily disabling CRTSCTS, the HAL sends the four-byte HCI Reset command:

01 03 0c 00

The UART counters then show:

tx:4 rx:0

No response is received from the IW612. The same result occurs with a direct manual UART test at 115200 baud, 8N1, without hardware flow control.

Our current configuration is:

mchar_port = /dev/ttyLP5
baudrate_fw_init = 115200

enable_download_fw is left disabled because the combo firmware is already downloaded by the Wi-Fi driver.

Could you please clarify:

After loading sduart_nw61x_v1.bin.se through SDIO, should the IW612 Bluetooth UART respond directly to an HCI Reset at 115200 baud?
Is a boot-sleep trigger, wake command, vendor command, or another initialization sequence required first?
Is hardware flow control mandatory for IW612, and what should the expected CTS state be after firmware initialization?
Should we use the UART firmware-download path with uartspi_n61x_v1.bin.se instead of relying on the combo firmware loaded by Wi-Fi?
Is there a recommended bt_vendor.conf for IW612 on i.MX95?

Any reference configuration or expected UART trace would be very helpful.

Best regards.

Android

Linux