Hey, I am working with IMX8QM-MEK (imx-automotive-11.0.0_1.1.0).
I have tried to use both prebuilt 11.0.0_1.1.0 images, and built by myself - UI does not come up after flashing the device.
To make a first flash I have used UUU, after that I am working with emmc boot and fastboot flashing script.
I am observing, basically, 2 issues:
1) At some random boot cycles there is a delay between commands were entered and executed (about 45 seconds between the moment I have taped 'logcat' in minicom/adb shell and the moment I can actually see the log). I was not able yet to catch what causes such a behavior, and I can't see any dependency so far - but sometimes board works with this 45 seconds delay, and sometimes - without.
2) I am using LVDS-to-HDMI card + hdmi display to verify the UI. And HDMI display does not have any reaction during the boot, plugging and unplugging does not have any effect either. UI simply does not show up. I have tried to use that both with clean bootargs, and using bootargs from user guide:
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
I have attached minicom output and logcat output text files. I have noticed these lines:
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
08-31 16:20:42.241 367 367 I display : drm driver may not ready or bootargs is not correct
08-31 16:20:42.241 367 367 W display : xres = 1920 px
08-31 16:20:42.241 367 367 W display : yres = 1080 px
08-31 16:20:42.241 367 367 W display : format = 1
08-31 16:20:42.241 367 367 W display : xdpi = 160.00 ppi
08-31 16:20:42.241 367 367 W display : ydpi = 160.00 ppi
08-31 16:20:42.241 367 367 W display : fps = 60.00 Hz
08-31 16:20:42.241 367 367 E dpug2d : g2d_open: Init Dpu Handle fail !
08-31 16:20:42.241 367 367 I display : no need to alloc memory
Could you help me to verify the reasons of this behavior of the board?
Solved! Go to Solution.
I have synced repo from scratch, seems that has solved the issue.
Yes, I have followed the guide to verify if the HW works properly. I was able to boot to UI through LVDS-to-HDMI without any issues.
But what I need is Android automotive OS, that was a target SW for this board (the board has been chosen because the Android Automotive OS image is supported). And I can not boot to UI with that. LVDS-to-HDMI board does not show green LED, HDMI TX connector does not work either.
Are you follow this guide?
https://www.nxp.com/document/guide/get-started-with-the-i-mx-8quadmax-mek:GS-iMX-8QM-MEK