[IMX8QM-MEK] UI is not coming up in custom AOSP build.

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

[IMX8QM-MEK] UI is not coming up in custom AOSP build.

Jump to solution
5,362 Views
Jose1985
Contributor IV

Hi nxf65025,

I am trying to flash Android-11 Android Automotive flavor in iMX8QM. 

Let me make an update. When I tried the below command to flash, I am able to flash the custom android image.

However, when booting up, I am getting below error in dmesg and there is no UI.

//Adb log

[ 1082.571915] init: Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 268 (/system/bin/servicemanager)

//Dmesg

[ 32.346527] android_work: sent uevent USB_STATE=CONFIGURED
[ 33.903990] vref_1v8: disabling
[ 33.907141] epdev_on: disabling
[ 33.910313] SD1_SPWR: disabling
[ 36.534616] init: Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid:239 (/system/bin/servicemanager)

Could you help me with this? Log is attached

0 Kudos
Reply
1 Solution
5,358 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

@Jose1985 

 

What changes between your custom board and evk?

 

This error shows that android power HAL hang.

View solution in original post

0 Kudos
Reply
12 Replies
5,293 Views
msopiha
Contributor II

hey @Jose1985 ,

I am working on this board with Android Automotive 11 either, and have issues with booting up the device. 

08-31 16:20:42.241 367 367 I display : try dev:/dev/dri/card0
08-31 16:20:42.241 367 367 E display : Failed to set universal plane cap -1

Have you ever faced something like this?

0 Kudos
Reply
5,290 Views
Jose1985
Contributor IV

Hello @msopiha ,

I believe your source code is not synced properly. 

Could you retry downloading the source code freshly, as per my previous post. It should work seamlesly until and unless your source code is not proper.

0 Kudos
Reply
5,285 Views
msopiha
Contributor II

The point is that I can't boot that up even using a prebuilt image. 

But thanks, I got your point.

0 Kudos
Reply
5,282 Views
Jose1985
Contributor IV

Are you downloading the image from https://www.nxp.com/design/software/embedded-software/i-mx-software/android-automotive-os-for-i-mx-a...

11.0.0_1.1.0_AUTO_DEMO_8Q

I assume that you are using the LVDS-HDMI adapter brought from NXP. Right?

If you this image and if still facing the problem, then the issue is with your display device probably. 

Could you try to boot without connecting monitor? If still not, pls share you kernel and adb logs

0 Kudos
Reply
5,279 Views
msopiha
Contributor II

So, yea, the long story short - first I have verified the device + LVDS connector with a display using an image on SD card (a linux image). That worked correctly.

After that I have downloaded the images - using automotive-11.0.0_1.1.0_image_8qmek2 with LVDS-HDMI adapter from the box.

I am observing an infinite boot animation with colored balls flying over the display.

I have also set bootargs from user guide to enable LVDS-HDMI adapter:

U-Boot > setenv bootargs console=ttyLP0,115200 earlycon androidboot.console=ttyLP0
androidboot.xen_boot=default init=/init androidboot.hardware=nxp androidboot.fbTileSupport=enable
cma=800M@0x960M-0xe00M galcore.contiguousSize=33554432 androidboot.primary_display=imx-drm
firmware_class.path=/vendor/firmware loop.max_part=7 androidboot.vendor.sysrq=1
transparent_hugepage=never video=HDMI-A-2:d androidboot.wificountrycode=CN androidboot.lcd_density=240

And enable permissive SELinux:

U-Boot > setenv append_bootargs androidboot.selinux=permissive

Attaching logs.

0 Kudos
Reply
5,274 Views
Jose1985
Contributor IV

I see, but I havent tried automotive-11.0.0_1.1.0_image_8qmek2 yet.

Could you try with automotive-11.0.0_1.1.0_image_8qmek image instead of 11.0.0_1.1.0_image_8qmek2?

And yes, I checked you adb logs. There is nothing suspicious.

0 Kudos
Reply
5,243 Views
msopiha
Contributor II

Thanks for help!

I have downloaded repo once more - an the board has booted.

0 Kudos
Reply
5,272 Views
msopiha
Contributor II

Well, I have booted up the image. IT took about 45 minutes to get it up and running. Looks like it was a long initial boot.

Now I am syncing source tree one more time to build the image ant test it again.

Appreciate your help, will post here what I have in a while!

0 Kudos
Reply
5,339 Views
Jose1985
Contributor IV

Source code & prebuilt: https://www.nxp.com/webapp/sps/download/license.jsp?colCode=11.0.0_1.1.0_AUTO_SOURCE&appType=file1&D...
You need to register with NXP to access artifacts from above link.

  1. Install build tools, GIT & repo as per the attached documents
    2. Download imx-automotive-11.0.0_1.1.0.tar.gz 
  1. mkdir ~/iMX8QM-MEK
  2. cd ~/iMX8QM-MEK
  3. mv ~/Downloads/imx-automotive-11.0.0_1.1.0.tar.gz .
  4. tar -xzvf imx-automotive-11.0.0_1.1.0.tar.gz
  5. ./imx-automotive-11.0.0_1.1.0/imx_android_setup.sh ==> This will download the source code in ~/iMX8QM-MEK.android_build

After download will take over (5-10 hours) based on your internet speed. After download is over

  1. cd ~/iMX8QM-MEK
  2. cd android_build
  3. source build/envsetup.sh
  4. lunch 10 = => aosp_car_x86_64
  5. make -j4/j8 based on your RAM size

OR

  1. lunch 68 = => For iMX8QM-MEK
  2. ./imx-make.sh -j4/-j8 based on your RAM size
0 Kudos
Reply
4,844 Views
geekdarcy
Contributor III

hi  Jose ,

     Have you solved this problem, I have a similar problem with you.

     I  used  prebuilt automotive-11.0.0_2.3.0_image_8qmek_car.tar images, UI stuck on boot screen after flashing the device.

     Could you help me with this?

     Kind regards!

0 Kudos
Reply
5,355 Views
Jose1985
Contributor IV

There is not change in EVK. I just tried the Android image build out of IMXQM android source.

Yes. Android power HAL seems to be not running. I am looking for a solution for the same.

0 Kudos
Reply
5,359 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

@Jose1985 

 

What changes between your custom board and evk?

 

This error shows that android power HAL hang.

0 Kudos
Reply