iMX8QXP MIPI DSI clk and lanes no signal

cancel
Showing results for 
Search instead for 
Did you mean: 

iMX8QXP MIPI DSI clk and lanes no signal

5,800 Views
ruodong_bai
Contributor II

Hello, I want to apply a MIPI DSI to FPD-Link III serializer in iMX8QXP with a Cortex-M4.

HW Platform NXP IMX8QXP

SW OS : Android 9.0 Automative

NXP release base line  P9.0.0_2.1.0-AUTO-ga  

Linux Kernel LA 4.14.98

UBoot 2018.03

mipi dsi output: 4 lanes MIPI DSI0

 

when device runs in M4, the mipi dsi0 output a normal signal(4 lanes and clk),

but no mipi dsi signal when into kernel.

could you help support me, and give me some advice to check this issue?

0 Kudos
14 Replies

5,006 Views
sunyunchen
Contributor I

ruodong.bai@hirain.com

I have the same problem.I debug car version with m4 ,run in imx8qxp board.When boot from m4. the android screen is dark.And the kernel report "Could not get DPHY lock".

How can you solve it?

0 Kudos

5,006 Views
ruodong_bai
Contributor II

yes, I met this issue.  because the dphy clock initial failed.. 

in dts file M4 node, the dphy ref is dummy, after change it , this issue will be resolved.

need this:

&vehicle_rpmsg_m4 {

   ...

   mipi_dsi1: mipi_dsi@56228000 {
      ...
-     <&clk IMX8QXP_CLK_DUMMY>;
+    <&clk_post IMX8QXP_MIPI0_DSI_PHY_CLK>;

   }

I am not sure if need below change.. because up to now I am not display well yet..

mipi_dsi_bridge1: mipi_dsi_bridge@56228000 {

     ...

-    <&clk_post IMX8QXP_MIPI0_BYPASS_CLK>,

+   <&clk_post IMX8QXP_MIPI0_DSI_PHY_CLK>,

0 Kudos

5,006 Views
sunyunchen
Contributor I

&vehicle_rpmsg_m4 {

   ...

   mipi_dsi1: mipi_dsi@56228000 {
      ...
-     <&clk IMX8QXP_CLK_DUMMY>;
+    <&clk_post IMX8QXP_MIPI0_DSI_PHY_CLK>;

   }

我修改了这行,界面不显示,但是我kill surfaceflinger就可以正常显示了,我看log第一次开机并没有调用到

mixel_mipi_phy_power_on. 你有碰到这个问题吗?另外有微信吗,加下我13404105289
0 Kudos

5,006 Views
sunyunchen
Contributor I

Thank you very much.

0 Kudos

5,006 Views
ruodong_bai
Contributor II

Hello, Yunchen,

after the dphy issue resolved, did your display work well in Android with a M4 EVS booting?

I still can't find the reason now..

0 Kudos

5,006 Views
nxf47746
NXP Employee
NXP Employee

Have you enabled the dsi node in the imx8qxp device tree?

0 Kudos

5,006 Views
ruodong_bai
Contributor II

Hello, I am sorry I only just noticed your reply..

now I had enable the mipi signal output..

but still some issue below:

1. When I boot without M4(EVS), the display works well.

When I boot with M4, M4 display normal (progress bar logo interface),

but after switching to android, the screen display nothing.

And when I measure the mipi signal, the android dark screen(booting with M4) signal is almost same with the signal from the normal display(booting without M4).

2. and, sometimes, the interface frame is flashing by, when switching to android from EVS booting.

3. by the way, I found some guides written by you, I am unauthorized to visit your document(seamless ui switch between m4 and AP on imx8qxp android ga) https://community.nxp.com/docs/DOC-344009 ,

how to get the acess for that..

Thank you for your reply!

0 Kudos

5,006 Views
ruodong_bai
Contributor II

I don't know why I can't attach or insert images in comment...

in the latest comment:

2. and, sometimes, the interface frame is flashing by, when switching to android from EVS booting.

sometimes, when I enter android frome EVS, screen will has a flicker, which is a incomplete or displacement UI frame in vertical.

0 Kudos

5,006 Views
nxf47746
NXP Employee
NXP Employee

1. for attachment please extend the reply editor to advance one.

2. Android will default to use lvds for displaying, and make sure the kernel has recognized the dsi as a display,

see the /sys/class/drm/* for the dsi node.

0 Kudos

5,006 Views
ruodong_bai
Contributor II

hello, for the attachment, I guess it is network issue in my side...

for the /sys/class/drm/*

pancake:/sys/class/drm # ls
card0 card1 card1-DSI-1 renderD128 renderD129 version

And attach the debug state node below, I think the driver connected right now.

pancake:/sys/kernel/debug/dri/1 # ls
DSI-1 clients crtc-0 crtc-1 gem_names name state
pancake:/sys/kernel/debug/dri/1 # cat state
plane[29]: plane-0
crtc=crtc-0
fb=61
format=AR24 little-endian (0x34325241)
modifier=0x600000000000002
size=1920x768
layers:
pitch[0]=7680
offset[0]=0
crtc-pos=1920x720+0+0
src-pos=1920.000000x720.000000+0.000000+0.000000
rotation=1
plane[33]: plane-1
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[36]: plane-2
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[39]: plane-3
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[42]: plane-4
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[46]: plane-5
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[49]: plane-6
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
plane[52]: plane-7
crtc=(null)
fb=0
crtc-pos=0x0+0+0
src-pos=0.000000x0.000000+0.000000+0.000000
rotation=1
crtc[32]: crtc-0
enable=1
active=1
planes_changed=1
mode_changed=0
active_changed=0
connectors_changed=0
color_mgmt_changed=0
plane_mask=1
connector_mask=1
encoder_mask=1
mode: 0:"1920x720" 60 108000 1920 2033 2077 2250 720 739 744 800 0x48 0xa
crtc[45]: crtc-1
enable=0
active=0
planes_changed=0
mode_changed=0
active_changed=0
connectors_changed=0
color_mgmt_changed=0
plane_mask=0
connector_mask=0
encoder_mask=0
mode: 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
connector[56]: DSI-1
crtc=crtc-0
0 Kudos

5,006 Views
nxf47746
NXP Employee
NXP Employee

check the "status" and "enable" node under the card1-DSI-1.

And for the linux kernel dsi related drivers, you should build them as kernel modules and put them to  the "setup.core.cfg“, they will not be probed until the m4 release the display resource.

0 Kudos

5,006 Views
ruodong_bai
Contributor II

Hello, Xu

I change the FakeKms resolution(change to 1920*720 which match our panel), then flash a normal resolution frame image, but it still display for a short time..

Could you help give some advice.  where it is possible to lead this issue..

Many Thanks!

我改了一下FakeKms的分辨率(符合我们屏幕的1920*720),闪屏的那一个画面已经不是之前那样撕裂的了,已经是正常的一个画面了,,但是还是一闪而过。

您方便的话帮忙给些建议,有哪些方面可能导致这种现象。

非常感谢!

0 Kudos

5,006 Views
ruodong_bai
Contributor II

Hello, Xu

below is the enabled node, and status:

pancake:/sys/class/drm/card1-DSI-1 # ls
device dpms edid enabled modes power status subsystem uevent
pancake:/sys/class/drm/card1-DSI-1 # cat enabled
enabled
pancake:/sys/class/drm/card1-DSI-1 # cat status
connected

yes, I have build them as module, and has ismod the ko file.

感觉英语有点表述不清,不好意思,可以直接用中文吗。。

事实上,我从M4切换到A核的时候,A核有一瞬间display了一下android界面,,但是通常这一闪而逝的画面都是残缺的,或者重影的,是那种纵向错乱的图象,然后紧接着就没有了画面。

但是同样的配置,不启动M4核的情况下就可以正确显示。

已经解决了不可以附件的问题,您帮忙看一下我现在的现象吧~

图片是 不启动EVS的情况下,直接用A核启动android,是可以正常显示的。

视频是 启动M4 EVS的情况下,切换到A核以后,闪烁一下屏幕的视频。。 之后虽然还是有Mipi信号,但是就没有图象了,此时的adb节点都是正常的,enable connected这些都是对的。。

还有您能有办法让我有权限看到您之前在别的文章里提到过的文档吗?我现在没有权限看https://community.nxp.com/docs/DOC-344009 。。

十分感谢!!

0 Kudos

5,003 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi Bai,

I’m afraid that i.MX8QXP family is still on preproduction and no additional information/support could be provided yet. For further assistance, please contact with your Sales/FAE.


Additionally, Android Auto is supported under Professional Services scheme. You could refer to the following link for additional details:

Commercial Support and Engineering Services | NXP 

Hope this will be useful for you.
Best regards!
/Carlos
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

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

0 Kudos