imx8 kernel boot fail --imx-image-core-imx8qxpmek-rootfs.wic.bz2 deadloop

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

imx8 kernel boot fail --imx-image-core-imx8qxpmek-rootfs.wic.bz2 deadloop

1,321件の閲覧回数
weichushun
Contributor I

Hi expert,

I meet the following problem, the meseage between two "imx-drm display-subsystem: master bind failed: -517"  repeats deadloop. How can I resolve it ?Maybe it was caused by dts?

Thank you !

 

----------------------------------------------------------------------------------------------------------

[ 3.258559] imx_rpmsg_i2c bus@5a000000:i2c-rpbus-15: add I2C adapter i2c-rpmsg-adapter successfully
[ 3.269402] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy
[ 3.269996] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.281648] [drm] No driver support for vblank timestamp query.
[ 3.287677] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 3.295987] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 3.303389] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 3.311066] imx-drm display-subsystem: failed to bind bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops): -517
[ 3.321054] imx-drm display-subsystem: master bind failed: -517
[ 3.334114] mx8-img-md: Registered mxc_isi.0.capture as /dev/video0
[ 3.340745] mx8-img-md: Registered mxc_isi.1.capture as /dev/video1
[ 3.347328] mx8-img-md: Registered mxc_isi.2.capture as /dev/video2
[ 3.353882] mx8-img-md: Registered mxc_isi.3.capture as /dev/video3
[ 3.360439] mx8-img-md: Registered mxc_isi.4.capture as /dev/video4
[ 3.367098] unregister ISI channel: mxc_isi.0
[ 3.371574] unregister ISI channel: mxc_isi.1
[ 3.376046] unregister ISI channel: mxc_isi.2
[ 3.380518] unregister ISI channel: mxc_isi.3
[ 3.384993] unregister ISI channel: mxc_isi.4
[ 3.390695] imx-cs42888 sound-cs42888: failed to find codec platform device
[ 3.399327] debugfs: Directory '59050000.sai' with parent 'wm8960-audio' already present!
[ 3.407644] imx-wm8960 sound-wm8960: wm8960-hifi <-> 59050000.sai mapping ok
[ 3.414751] imx-wm8960 sound-wm8960: ASoC: no DMI vendor name!
[ 3.535161] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy
[ 3.535841] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.547399] [drm] No driver support for vblank timestamp query.
[ 3.553409] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 3.561708] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 3.569090] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 3.576708] imx-drm display-subsystem: failed to bind bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops): -517
[ 3.586700] imx-drm display-subsystem: master bind failed: -517
[ 3.599505] imx-cs42888 sound-cs42888: failed to find codec platform device
[ 3.611756] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy
[ 3.612351] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.623995] [drm] No driver support for vblank timestamp query.
[ 3.630019] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 3.638296] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 3.645680] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 3.653294] imx-drm display-subsystem: failed to bind bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops): -517
[ 3.663293] imx-drm display-subsystem: master bind failed: -517
[ 3.675992] imx-cs42888 sound-cs42888: failed to find codec platform device
[ 3.688198] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy
[ 3.688781] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.700441] [drm] No driver support for vblank timestamp query.
[ 3.706461] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 3.714755] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 3.722192] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 3.729822] imx-drm display-subsystem: failed to bind bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops): -517
[ 3.739825] imx-drm display-subsystem: master bind failed: -517

0 件の賞賛
返信
3 返答(返信)

1,304件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi weichushun

 

yes reason may be wrong dts, could you clarify what board used in the case:

i.MX8QXP or i.MX8QM MEK ? Linux usage can be found in documentation

 

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

 

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8QXP-MEK-Display-Selection-Guide/ta...

 

Best regards
igor

 

0 件の賞賛
返信

1,289件の閲覧回数
weichushun
Contributor I
Hi igor, I am using i.MX8QXP. Thank you!
0 件の賞賛
返信

1,284件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

please try Demo Image  i.MX 8QuadXPlus(C0) MEK 

or  i.MX 8QuadXPlus(B0) MEK

on i.MX8QXP MEK board

 

Best regards
igor

 

 

0 件の賞賛
返信