Forums - BT Initialization Problem

1 post / 0 new
BT Initialization Problem
nathan.goslee
Join Date: 16 Jul 19
Posts: 1
Posted: Mon, 2019-12-02 09:32

Hello,

We are using a third party QCA9377 based module and it is not initializing reliably.

The systems are detecting the module correctly when cold. When warm, the initial data packet from the 9377 is four bytes shorter (0x0a instead of 0x0e) and causes the driver to error out.

Is this behavior due to a QCA9377 mode selection pin? If not, what can we do to mitigate this issue (modify driver to assume the current SOC version)? 

Thank you,

Nathan

 

Normal:

bt_vendor: wait_for_data: HCI-VS-EVENT available in TTY Serial buffer

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, buf[0] - 0x4

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, buf[1] - 0xff

bt_vendor: get_vs_hci_event: Received HCI-Vendor Specific event

bt_vendor: get_vs_hci_event: Parameter Length: 0xe

bt_vendor: get_vs_hci_event: Command response: 0x0

bt_vendor: get_vs_hci_event: Response type   : 0x2

bt_vendor: get_vs_hci_event: Command Request Response

bt_vendor:      Current Product ID             : 0x00000008

bt_vendor:      Current Patch Version          : 0x0111

bt_vendor:      Current ROM Build Version      : 0x0302

bt_vendor:      Current SOC Version            : 0x00000023

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, count - 0x11

bt_vendor: hci_send_vs_cmd: Received HCI-Vendor Specific Event from SOC

bt_vendor: read_hci_event: Wait for Command Complete Event from SOC

bt_vendor: rome_soc_init: Rome Version (0x03020023)

bt_vendor: File Open (/vendor/firmware/qca/tfbtfw11.tlv)

 

Failed:

bt_vendor: wait_for_data: HCI-VS-EVENT available in TTY Serial buffer

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, buf[0] - 0x4

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, buf[1] - 0xff

bt_vendor: get_vs_hci_event: Received HCI-Vendor Specific event

bt_vendor: get_vs_hci_event: Parameter Length: 0xa

bt_vendor: get_vs_hci_event: Command response: 0x0

bt_vendor: get_vs_hci_event: Response type   : 0x2

bt_vendor: get_vs_hci_event: Command Request Response

bt_vendor:      Current Product ID             : 0x00000008

bt_vendor:      Current Patch Version          : 0x0111

bt_vendor:      Current ROM Build Version      : 0x0302

bt_vendor: read_vs_hci_event: Wait for HCI-Vendor Specfic Event from SOC, count - 0xd

bt_vendor: hci_send_vs_cmd: Received HCI-Vendor Specific Event from SOC

bt_vendor: read_hci_event: Wait for Command Complete Event from SOC

bt_hci  : startup_timer_expired

bt_core_module: module_start_up Failed to start up module "hci_module"

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.