IMX8MMD4 android wifi/bt issue

[AndyHo]

Hi,

We have purchased imx8mmd4 evk + MX8_DSI_OLDE1 and ready to design follow the schematic.

But we found the wifi and bluetooth are not working, because the wifi/bt is broadcom(cypress) 1MW , not qca,

There is no document to guide how to modify android 9 bsp to make wifi/bt working for imx8mmd4, so after some study and modification (dts/boardconfig), wifi is working now, but bluetooth is still not working, and I got following error message when every time turn on the bluetooth under android (module found, firmware loaded).

Finally I saw the there is a service wcnss_filter for qca module in init.rc, but can't find service for 1mw module, maybe it's the root cause. So I have 2 questions:

1.Are there any document to guide how to enable 1mw wifi/bluetooth and its service/HAL/library? (document from Murata/Cyress are only for linux, no hcitool in android bsp)

2.There is 2 pins used for BT, BT_WAKE_DEV,BT_WAKE_HOST but can't find any definition in dts, I am afraid it's possible BT is sleeping because no driver handle those pin, how to use those pin?

Hope I can get support here.

thank you

--------------------------------------------------------------------------------------------

06-18 03:56:49.128 3117 13962 I bt_hwcfg: bt vendor lib: set UART baud 3000000
06-18 03:56:49.129 3117 13962 D bt_hwcfg: Chipset BCM4345C0
06-18 03:56:49.129 3117 13962 D bt_hwcfg: Target name = [BCM4345C0]
06-18 03:56:49.130 3117 13962 I bt_hwcfg: FW patchfile: /vendor/firmware/brcm/CYW4345C0.1MW.hcd
06-18 03:56:49.464 3117 13962 I bt_hwcfg: bt vendor lib: set UART baud 115200
06-18 03:56:49.464 3117 13962 D bt_hwcfg: Settlement delay -- 100 ms
06-18 03:56:49.464 3117 13962 I bt_hwcfg: Setting fw settlement delay to 100
06-18 03:56:49.601 3117 13962 I bt_hwcfg: bt vendor lib: set UART baud 3000000
06-18 03:56:49.601 3117 13962 I bt_hwcfg: Setting local bd addr to 19:21:0A:09:DA:B4
06-18 03:56:49.602 3117 13962 I bt_hwcfg: vendor lib fwcfg completed
06-18 03:56:49.602 3117 13962 D android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured result: 0
06-18 03:56:49.602 3117 13962 I android.hardware.bluetooth@1.0-impl: Firmware configured in 0.526s
06-18 03:56:49.602 3117 13962 I android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured: lpm_timeout_ms 1500
06-18 03:56:49.602 3117 13962 D android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured Calling StartLowPowerWatchdog()
06-18 03:56:49.602 13926 13959 I bt_hci : event_finish_startup
06-18 03:56:49.602 13926 13942 I bt_core_module: module_start_up Started module "hci_module"
06-18 03:56:49.603 13926 13963 I bt_osi_thread: run_thread: thread id 13963, thread name bt_workqueue started 

.......

06-18 03:56:50.056 3116 3217 D audio_hw_primary: adev_set_parameters: exit with code(0)
06-18 03:56:50.080 3711 3711 D HeadsetProfile: Bluetooth service connected
06-18 03:56:51.481 3116 3217 W audio_hw_primary: do_out_standby... 0xe8050000
06-18 03:56:51.808 13926 13945 E bt_hci : command_timed_out
06-18 03:56:51.808 13926 13945 E bt_hci : command_timed_out_log_info: 1 commands pending response
06-18 03:56:51.808 13926 13945 E bt_hci : command_timed_out_log_info: Waited 2000 ms for a response to opcode: 0xc26 *matches timer
*
06-18 03:56:51.808 13926 13945 E bt_hci : command_timed_out_log_info: Size 5 Hex 26 0c 02 60
06-18 03:56:51.808 13926 13945 E bt_hci : command_timed_out: requesting a firmware dump.
06-18 03:56:51.809 13926 13945 E bt_hci : command_timed_out: Setting a timer to restart.
06-18 03:56:56.811 13926 13945 E bt_hci : hci_timeout_abort restarting the Bluetooth process.
--------- beginning of crash
06-18 03:56:56.811 13926 13945 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 13945 (alarm_default_c), pid 13926 (d
roid.bluetooth)
06-18 03:56:56.886 13998 13998 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
06-18 03:56:56.888 3171 3171 I /system/bin/tombstoned: received crash request for pid 13945
06-18 03:56:56.889 13998 13998 I crash_dump64: performing dump of process 13926 (target tid = 13945)
06-18 03:56:56.902 13998 13998 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-18 03:56:56.902 13998 13998 F DEBUG : Build fingerprint: 'MILDEF/df9a_8mm/df9a_8mm:9/2.3.0-ga-rc2/software04210221:userdebug/de
v-keys'
06-18 03:56:56.902 13998 13998 F DEBUG : Revision: '0'
06-18 03:56:56.902 13998 13998 F DEBUG : ABI: 'arm64'
06-18 03:56:56.902 13998 13998 F DEBUG : pid: 13926, tid: 13945, name: alarm_default_c >>> com.android.bluetooth <<<
06-18 03:56:56.902 13998 13998 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
06-18 03:56:56.902 13998 13998 F DEBUG : x0 0000000000000000 x1 0000000000003679 x2 0000000000000006 x3 000000000000000
8
06-18 03:56:56.902 13998 13998 F DEBUG : x4 000f25befeff6862 x5 000f25befeff6862 x6 000f25befeff6862 x7 7f7f7fff7f7f7f7
f
06-18 03:56:56.902 13998 13998 F DEBUG : x8 0000000000000083 x9 0000ff750113a9a0 x10 fffffff87ffffbdf x11 000000000000000
1
06-18 03:56:56.902 13998 13998 F DEBUG : x12 0000ff74e87e8608 x13 ffffffffffffffff x14 ffffffffff000000 x15 fffffffffffffff
f
06-18 03:56:56.902 13998 13998 F DEBUG : x16 0000ff75011732c8 x17 0000ff75010b12d8 x18 0000ff74e87e7dca x19 000000000000366
6
06-18 03:56:56.902 13998 13998 F DEBUG : x20 0000000000003679 x21 0000000000000083 x22 0000ff74e87e8a90 x23 0000ff74e8d31f4
0
06-18 03:56:56.902 13998 13998 F DEBUG : x24 0000000000135754 x25 0000ff74e87e9588 x26 0000ff74e87e8d68 x27 000000000000000
1
06-18 03:56:56.902 13998 13998 F DEBUG : x28 0000000000000000 x29 0000ff74e87e8a30
06-18 03:56:56.902 13998 13998 F DEBUG : sp 0000ff74e87e89f0 lr 0000ff75010a5a90 pc 0000ff75010a5abc
06-18 03:56:56.926 13998 13998 F DEBUG :
06-18 03:56:56.926 13998 13998 F DEBUG : backtrace:
06-18 03:56:56.926 13998 13998 F DEBUG : #00 pc 0000000000021abc /system/lib64/libc.so (abort+124)
06-18 03:56:56.926 13998 13998 F DEBUG : #01 pc 000000000015ef74 /system/lib64/libbluetooth.so (hci_timeout_abort(void*)+52)
06-18 03:56:56.926 13998 13998 F DEBUG : #02 pc 00000000002296b8 /system/lib64/libbluetooth.so (alarm_ready_generic(alarm_t*,
std::__1::unique_lock<std::__1::mutex>&)+216)
06-18 03:56:56.926 13998 13998 F DEBUG : #03 pc 00000000002295a0 /system/lib64/libbluetooth.so (alarm_queue_ready(fixed_queue
_t*, void*)+112)
06-18 03:56:56.926 13998 13998 F DEBUG : #04 pc 000000000022d454 /system/lib64/libbluetooth.so (internal_dequeue_ready(void*)
+84)
06-18 03:56:56.926 13998 13998 F DEBUG : #05 pc 0000000000232ee8 /system/lib64/libbluetooth.so (run_reactor(reactor_t*, int)+
320)
06-18 03:56:56.926 13998 13998 F DEBUG : #06 pc 0000000000232d7c /system/lib64/libbluetooth.so (reactor_start(reactor_t*)+84)

06-18 03:56:56.926 13998 13998 F DEBUG : #07 pc 0000000000234750 /system/lib64/libbluetooth.so (run_thread(void*)+184)
06-18 03:56:56.926 13998 13998 F DEBUG : #08 pc 0000000000083114 /system/lib64/libc.so (__pthread_start(void*)+36)
06-18 03:56:56.926 13998 13998 F DEBUG : #09 pc 00000000000233bc /system/lib64/libc.so (__start_thread+68)
06-18 03:56:57.678 3171 3171 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_14
06-18 03:56:50.052 3269 3269 I Telecom : Bluetoot[ 1268.572639] init: Untracked pid 13998 exited with status 0
hPhoneService: updateHeadsetWithCallState numActive 0, numHeld 0, callState 6, ringing number ***[ 1268.585364] init: Untracked pid
14000 exited with status 0
, ringing type 128

[Mithun1]

Is this BT crash issue is fixed?

As I am facing same issues with BT and IMX8MM