imx8qxp Android BSP change dts issue

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8qxp Android BSP change dts issue

230 Views
Contributor II

Dear Expert:

   I changed dtb file in Boardconfig.mk  as the below and rebuild android image 

modify code in line 213 :

# imx8qxp standard android; MIPI-HDMI display
#TARGET_BOARD_DTS_CONFIG += imx8qxp:fsl-imx8qxp-mek-ov5640.dtb
TARGET_BOARD_DTS_CONFIG += imx8qxp:fsl-imx8qxp-mek.dtb

 

But the system booting fail as the below terminal log. could you let us know how to solve the issue?


U-Boot SPL 2018.03-00033-g1f40c25-dirty (Jan 10 2020 - 12:57:33 +0800)
Trying to boot from MMC1
Load image from MMC/SD 0x45000

....

[ 4.906687] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.913349] [drm] No driver support for vblank timestamp query.
[ 4.919430] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 4.927942] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 4.935466] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 4.942819] imx-drm display-subsystem: failed to bind ldb@562210e0 (ops imx_ldb_ops): -517
[ 4.951371] imx-drm display-subsystem: master bind failed: -517
[ 4.964472] mxc_bt_rfkill: gpio not ready, need defer
[ 4.984787] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.991451] [drm] No driver support for vblank timestamp query.
[ 4.997525] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 5.006036] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 5.013565] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 5.020910] imx-drm display-subsystem: failed to bind ldb@562210e0 (ops imx_ldb_ops): -517
[ 5.029461] imx-drm display-subsystem: master bind failed: -517
[ 5.042580] mxc_bt_rfkill: gpio not ready, need defer
[ 5.063019] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 5.069694] [drm] No driver support for vblank timestamp query.
[ 5.075781] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 5.084290] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 5.091809] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 5.099152] imx-drm display-subsystem: failed to bind ldb@562210e0 (ops imx_ldb_ops): -517
[ 5.107701] imx-drm display-subsystem: master bind failed: -517
[ 5.120780] mxc_bt_rfkill: gpio not ready, need defer

Detail log message , please refer to attached file.

Thank you.

0 Kudos
2 Replies

4 Views
NXP TechSupport
NXP TechSupport

We are reviewing internally if the only DTB  functional at this moment, it is the imx8qxp:fsl-imx8qxp-mek-ov5640.dtb.

Since we have several preliminary REV of the MEK board, can you please clarify which version of the board do you have?

0 Kudos

4 Views
Contributor II

Hi Jamesbone:
    The board version is SCH-29683 ERV C1.

Thank your support.

0 Kudos