HFP and A2DP IMPLEMENTATION WITH 88W8987 Based BT module

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

HFP and A2DP IMPLEMENTATION WITH 88W8987 Based BT module

1,731 Views
Wobaffet
Senior Contributor I

Hello,

We are trying to implement A2DP and HFP with i.MX8MP custom board. We can load the firmware and connect to any BT device, however when we try to 

root@imx8mp-lpddr4-evk:~# pactl list cards
Card #0
	Name: alsa_card.platform-sound-bt-sco
	Driver: module-alsa-card.c
	Owner Module: 6
	Properties:
		alsa.card = "1"
		alsa.card_name = "bt-sco-audio"
		alsa.long_card_name = "bt-sco-audio"
		device.bus_path = "platform-sound-bt-sco"
		sysfs.path = "/devices/platform/sound-bt-sco/sound/card1"
		device.form_factor = "internal"
		device.string = "1"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card"
	Profiles:
		input:mono-fallback: Mono Input (sinks: 0, sources: 1, priority: 1, available: yes)
		output:mono-fallback: Mono Output (sinks: 1, sources: 0, priority: 100, available: yes)
		output:mono-fallback+input:mono-fallback: Mono Output + Mono Input (sinks: 1, sources: 1, priority: 101, available: yes)
		off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
	Active Profile: output:mono-fallback+input:mono-fallback
	Ports:
		analog-input: Analog Input (type: Analog, priority: 10000, latency offset: 0 usec, availability unknown)
			Part of profile(s): input:mono-fallback, output:mono-fallback+input:mono-fallback
		analog-output: Analog Output (type: Analog, priority: 9900, latency offset: 0 usec, availability unknown)
			Part of profile(s): output:mono-fallback, output:mono-fallback+input:mono-fallback

Card #1
	Name: alsa_card.platform-sound-tlv320aic31xx
	Driver: module-alsa-card.c
	Owner Module: 7
	Properties:
		alsa.card = "0"
		alsa.card_name = "tlv320aic31xx-Codec"
		alsa.long_card_name = "tlv320aic31xx-Codec"
		device.bus_path = "platform-sound-tlv320aic31xx"
		sysfs.path = "/devices/platform/sound-tlv320aic31xx/sound/card0"
		device.form_factor = "internal"
		device.string = "0"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card"
	Profiles:
		input:stereo-fallback: Stereo Input (sinks: 0, sources: 1, priority: 51, available: yes)
		output:stereo-fallback: Stereo Output (sinks: 1, sources: 0, priority: 5100, available: yes)
		output:stereo-fallback+input:stereo-fallback: Stereo Output + Stereo Input (sinks: 1, sources: 1, priority: 5151, available: yes)
		off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
	Active Profile: output:stereo-fallback+input:stereo-fallback
	Ports:
		analog-input: Analog Input (type: Analog, priority: 10000, latency offset: 0 usec, availability unknown)
			Part of profile(s): input:stereo-fallback, output:stereo-fallback+input:stereo-fallback
		analog-output-speaker: Speakers (type: Speaker, priority: 10000, latency offset: 0 usec, availability unknown)
			Properties:
				device.icon_name = "audio-speakers"
			Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback

We can't detect a card for the connected devices as can be seen on this guide.  Even though we can detect Audio sink feature like this 

Device B8:D5:0B:FA:89:8E (public)
	Name: Busra JBL
	Alias: Busra JBL
	Class: 0x00240414
	Icon: audio-card
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: CSR                       (0000fe8f-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (65786365-6c70-6f69-6e74-2e636f6d0000)
	Modalias: bluetooth:v000ApFFFFdFFFF

We are on 5.15 kernel and our distro has these packages

IMAGE_INSTALL:append = "dbus packagegroup-tools-bluetooth pulseaudio pulseaudio-server pulseaudio-miscbluealsa alsa-lib bluez5 bluez5-noinst-tools bluez5-obex openobex obexftp"

When we try to load discover module we get

root@imx8mp-lpddr4-evk:~# pactl load-module module-bluez5-discover
Failure: Module initialization failed

 Also the list of pactl modules are attached.

What could be the issue here?

Thanks!

0 Kudos
Reply
2 Replies

1,664 Views
jimmychan
NXP TechSupport
NXP TechSupport

Hello,

 

Could you show me how you connect the module? 

What is the boot up log?

Please also send me the device tree file of your board for checking.

 

Thanks.

 

Best regards,

Jimmy

0 Kudos
Reply

1,698 Views
Wobaffet
Senior Contributor I

reminder.

0 Kudos
Reply