Sabresd bluetooth on Android 8.0 and murata 1DX

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sabresd bluetooth on Android 8.0 and murata 1DX

1,211 Views
matteo_pegoraro
Contributor I

Hi to all,

I'm working on Sabre-sd board with 1DX module from Murata(based on broadcom/cypress 4343 chip) running Andorid 8.0.

Wi-Fi is working fine, I'm able to connect to an AP and browse internet but I'm still having problem on bringing up bluetooth.

The board has all the modifications required by the Murata guide.

 

When I try to enable bluetooth from settings the start-up procedure fails during inizialization of of "controller_module" when issuing HCI opcodes:

the firmware seems to be correctly uploaded to the controller (as you can see in the logcat below) and the serial communication with the chip is started (the host receives response to the firsts HCI opcodes) but the communication stops at the same point (opcode= 0xc6d) . I've tried to increase timeout but without succes.

Could you please provide support to solve the issue?

 

01-17 09:31:23.911  1499  1515 I bt_core_module: module_start_up Starting module "hci_module"

01-17 09:31:23.911  1499  1515 I bt_hci  : hci_module_start_up

01-17 09:31:23.912  1499  1529 I bt_osi_thread: run_thread: thread id 1529, thread name hci_thread started

01-17 09:31:23.912  1499  1515 D bt_hci  : hci_module_start_up starting async portion

01-17 09:31:23.912  1499  1529 I bt_hci  : hci_initialize

01-17 09:31:23.914  1499  1529 I bt_hci  : hci_initialize: IBluetoothHci::getService() returned 0xa6530420 (remote)

01-17 09:31:23.915   278  1477 I android.hardware.bluetooth@1.0-impl: BluetoothHci::initialize()

01-17 09:31:23.916   278  1477 I bt_vendor: init

01-17 09:31:23.916   278  1477 I bt_vnd_conf: Attempt to load conf from /etc/bluetooth/bt_vendor.conf

01-17 09:31:23.916   278  1477 D android.hardware.bluetooth@1.0-impl: Open vendor library loaded

01-17 09:31:23.922   278  1477 W bt_vendor: NOTE: BT_VND_PWR_ON now forces power-off first

01-17 09:31:24.445   278  1477 I bt_userial_vendor: userial vendor open: opening /dev/ttymxc4

01-17 09:31:24.450   278  1477 I bt_userial_vendor: device fd = 6 open

01-17 09:31:24.490   278  1531 I bt_hwcfg: bt vendor lib: set UART baud 3000000

01-17 09:31:24.491   278  1531 D bt_hwcfg: Chipset BCM43430A1

01-17 09:31:24.491   278  1531 D bt_hwcfg: Target name = [BCM43430A1]

01-17 09:31:24.491   278  1531 I bt_hwcfg: FW patchfile: /vendor/firmware/bcm/Type_ZP.hcd

01-17 09:31:24.612   278  1531 I bt_hwcfg: bt vendor lib: set UART baud 115200

01-17 09:31:24.613   278  1531 D bt_hwcfg: Settlement delay -- 900 ms

01-17 09:31:24.613   278  1531 I bt_hwcfg: Setting fw settlement delay to 900

01-17 09:31:25.525   278  1531 I bt_hwcfg: bt vendor lib: set UART baud 3000000

01-17 09:31:25.525   278  1531 I bt_hwcfg: Setting local bd addr to 22:22:67:C6:69:73

01-17 09:31:25.526   278  1531 I bt_hwcfg: vendor lib fwcfg completed

01-17 09:31:25.526   278  1531 D android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured result: 0

01-17 09:31:25.526   278  1531 I android.hardware.bluetooth@1.0-impl: Firmware configured in 1.076s

01-17 09:31:25.526  1499  1529 I bt_hci  : event_finish_startup

01-17 09:31:25.526   278  1531 I android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured: lpm_timeout_ms 1500

01-17 09:31:25.527   278  1531 D android.hardware.bluetooth@1.0-impl: OnFirmwareConfigured Calling StartLowPowerWatchdog()

01-17 09:31:25.527  1499  1515 I bt_core_module: module_start_up Started module "hci_module"

01-17 09:31:25.527  1499  1532 I bt_osi_thread: run_thread: thread id 1532, thread name bt_workqueue started

01-17 09:31:25.527  1499  1532 I         : [0117/093125:INFO:btu_task.cc(108)] Bluetooth chip preload is complete

01-17 09:31:25.528   278  1531 D android.hardware.bluetooth@1.0-impl: low_power_mode_cb result: 0

01-17 09:31:25.528  1499  1532 E bt_att  : gatt_profile_db_init:  gatt_if=1

01-17 09:31:25.529  1499  1533 I bt_osi_thread: run_thread: thread id 1533, thread name btu message loop started

01-17 09:31:25.530  1499  1534 I bt_osi_thread: run_thread: thread id 1534, thread name module_wrapper started

01-17 09:31:25.530  1499  1534 I bt_core_module: module_start_up Starting module "controller_module"

01-17 09:31:25.530  1499  1534 I bt_controller: start_up ENTER

01-17 09:31:25.530  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0xc03

01-17 09:31:25.534  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x0c03

01-17 09:31:25.534  1499  1534 I bt_controller: start_up reset done

01-17 09:31:25.534  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0x1005

01-17 09:31:25.535  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x1005

01-17 09:31:25.535  1499  1534 I bt_controller: start_up buffer request done

01-17 09:31:25.535  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0xc33

01-17 09:31:25.536  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x0c33

01-17 09:31:25.536  1499  1534 I bt_controller: start_up buffer set done

01-17 09:31:25.536  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0x1001

01-17 09:31:25.537  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x1001

01-17 09:31:25.537  1499  1534 I bt_controller: start_up read local version done

01-17 09:31:25.537  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0x1009

01-17 09:31:25.539  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x1009

01-17 09:31:25.539  1499  1534 I bt_controller: start_up read bt address done

01-17 09:31:25.539  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0x1002

01-17 09:31:25.540  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x1002

01-17 09:31:25.540  1499  1534 I bt_controller: start_up supported commands request done

01-17 09:31:25.540  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0x1004

01-17 09:31:25.541  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x1004

01-17 09:31:25.541  1499  1534 I bt_controller: start_up read page 0 done

01-17 09:31:25.541  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0xc56

01-17 09:31:25.601  1499  1530 I bt_hci  : filter_incoming_event : (HCI_COMMAND_COMPLETE_EVT) got opcode = 0x0c56

01-17 09:31:25.602  1499  1534 I bt_controller: start_up simple pairing done

01-17 09:31:25.602  1499  1534 I bt_controller: start_up write host support START

01-17 09:31:25.602  1499  1529 D bt_hci  : event_command_ready sending command opcode= 0xc6d

01-17 09:31:25.688   404   420 D ViewRootImpl[bluetooth]: updatePointerIcon called with position out of bounds

01-17 09:31:26.916   281   389 I display : alloc cache buffer err:0

01-17 09:31:30.602  1499  1518 E bt_hci  : command_timed_out: 1 commands pending response

01-17 09:31:30.602  1499  1518 E bt_hci  : command_timed_out: Waited 5000 ms for a response to opcode: 0xc6d *matches timer*

01-17 09:31:30.602  1499  1518 E bt_hci  : command_timed_out: Size 5 Hex 6d 0c 02 01

01-17 09:31:30.602  1499  1518 E bt_hci  : command_timed_out: requesting a firmware dump.

01-17 09:31:30.603  1499  1518 E bt_hci  : command_timed_out restarting the Bluetooth process.

01-17 09:31:31.103  1499  1518 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 1518 (alarm_default_c), pid 1499 (droid.bluetooth)

Labels (1)
0 Kudos
2 Replies

828 Views
openclosed
Contributor I

Hi. Matteo

I have an i.mx6dq sabred board.
And I am testing Android 8.0.

The type zp wifi module was applied to i.mx6dp android source.
But I want to use type 1dx.


So I replaced the file.
In /vendor/firmware/bcm, the bin and hcd files were replaced with those in the 1DX_BCM4343W folder.
Then, I replaced the cal file in /etc/firmware/bcm with the file in the 1DX_BCM4343W folder.


However, WiFi does not work properly.
Bluetooth works, so you can scan.

I would be very grateful if you let me know how you applied it.

And the log below is the error log that appears when loading WiFi.
[44.096046] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x1 pkg:0x3
[44.103028] DHD: dongle ram size is set to 524288(orig 524288) at 0x0
[45.053770] dhdsdio_membytes: membytes transfer failed
[45.060785] dhdsdio_write_vars: error -1 on reading 552 nvram bytes at 0x0007fdd4
[45.068025] dhdsdio_write_vars: Downloaded NVRAM image is corrupted.

0 Kudos

828 Views
igorpadykov
NXP Employee
NXP Employee

Hi Matteo

one can try broadcom firmware package for i.MX Linux L4.9.11_1.0.0 BSP

(as android 8.0 is based on L4.9.11), BCMDHD-L4.9.11_1.0.0
https://www.nxp.com/webapp/Download?colCode=BCMDHD-L4.9.11_1.0.0&appType=license&location=null 

use it as described in Android Guide

wireless.murata.com/datasheet?/RFM/data/murata_quick_start_guide_android.pdf

In general support for murata modules is provided through murata support portal:

wireless.murata.com/eng/products/rf-modules-1/wi-fi-bluetooth-for-nxp-i-mx.html

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos