Miracast support on NXP AOSP running on iMX8QM MEK

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

Miracast support on NXP AOSP running on iMX8QM MEK

902 Views
danielsorem
Contributor I

Hi,

I'm trying to make Miracast work on the NXP AOSP, my setup is iMX8QM MEK running Android 10.0.0_2.6.0.

  • Hardware: MEK-MX8Q
  • OS: Android 10 running kernel 5.4.70
  • WI-FI chip: Realtek RTL8192CU
  • TV: webOS TV UN80000PSD

I've compiled Android image from source just enabling support for the RTL8192CU as below:

--- a/arch/arm64/configs/imx_v8_android_defconfig
+++ b/arch/arm64/configs/imx_v8_android_defconfig
@@ -270,6 +270,7 @@ CONFIG_CFG80211=y
CONFIG_NL80211_TESTMODE=y
CONFIG_CFG80211_WEXT=y
CONFIG_MAC80211=y
+CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_RFKILL=y
CONFIG_RFKILL_INPUT=y
@@ -426,6 +427,7 @@ CONFIG_PPP_MPPE=y
CONFIG_PPTP=y
CONFIG_PPPOL2TP=y
CONFIG_USB_PEGASUS=m
+CONFIG_RTL8192CU=y
CONFIG_USB_RTL8150=m
CONFIG_USB_RTL8152=y
CONFIG_USB_LAN78XX=m

I'm able to see the device coming up without any issues:

[ 1689.343554] usb 2-1.3: new full-speed USB device number 8 using cdns-usb3
[ 1689.448008] usb 2-1.3: not running at top speed; connect to a high speed hub
[ 1689.456673] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8176, bcdDevice= 2.00
[ 1689.464985] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a
[ 1689.465106] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1689.480816] usb 2-1.3: Product: 802.11n WLAN Adapter
[ 1689.486101] usb 2-1.3: Manufacturer: Realtek
[ 1689.490495] usb 2-1.3: SerialNumber: 00e04c000001
[ 1689.504784] rtl8192cu: Chip version 0x10
[ 1689.576929] rtl8192cu: Board Type 0
[ 1689.580625] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 1689.586608] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin

On the above log, the firmware rtl8192cufw_TMSC.bin is being used but I also did some tests with the rtl8192cufw.bin without any success too.

When I enable WiFi on the UI I got some errors as below, but the connection is accomplished:

[ 39.444710] xhci-cdns3: Ring expansion failed

[ 39.449360] xhci-cdns3: ERROR unknown event type 37

Please see the full dmesg log attached.

I'm able to connect to Wi-Fi without any problems, but when I open Screen Cast it can't find any nearby device to connect to. Should this work by default? Doing some tests with my cellphone I was able to see and connect to the TV.

Another thing that it's strange is that there is no menu on the Screen Cast page, normally there should be a three-dot menu where we can click on Enable Wireless Display but it is not visible to me, is there a way to confirm that the Wireless Display is enabled?

Thanks in advance,

2 Replies

739 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @danielsorem 

We don't support it in BSP, you can see this case for reference:

https://community.nxp.com/t5/i-MX-Processors/Miracast-Support-on-NXP-AOSP-Marvell-WIFI-W8997-M1216/t...

This feature is strongly dependent on wifi, please check your wifi compatibility.

Regards

Zhiming

0 Kudos

809 Views
rkiss_tx
Contributor I

Hi NXP Support Team, 

Based on this topic, is it possible to inform us if Miracast is supported in your Android BSP ? If it is supported, do you know in which version(s) and boards? 

We are trying in our own module, but we are not able to start it on iMX8QMMEK also. Do you have a test setup you used for this test? 

In case you do not support Miracast, do you have other Screen Mirror service supported on NXP Android BSP? 

In the community we found divergent information about Miracast, so we need to clarify it. 

 

Thanks a lot. 

Best Regards,

Renato Kiss

 

0 Kudos