rk3399 androind7.1 mipi-dsi驱动 uboot logo不显示

q303341192

各位大神 我的设备现在uboot logo不显示，kernel和android系统的logo可以正常显示，能帮忙分析分析怎么回事吗？rk3399开发板 官网提供的android7.1源码 mipi-dsi驱动。dts设备树中同样的dsi配置，kernel logo能显示，uboot无法显示。uboot模式下，通过rockchip_show_logo和rockchip_show_bmp命令也无法显示图片，开机启动后uboot的背光正常，附件是从开机启动到进入uboot模式的全部log。进入uboot模式前的log如下：
[Tue Dec 17 10:51:38.343 2019] rockchip_show_logo ulogo[logo.bmp]
[Tue Dec 17 10:51:38.343 2019] Failed to find part: 'logo'
[Tue Dec 17 10:51:38.343 2019] get_content: base_offset = 0x0
[Tue Dec 17 10:51:38.343 2019] get_entry: base_offset = 0x8000
[Tue Dec 17 10:51:38.344 2019] Failed to find part: 'logo'
[Tue Dec 17 10:51:38.344 2019] get_content: base_offset = 0x0
[Tue Dec 17 10:51:38.344 2019] get_entry: base_offset = 0x8000
[Tue Dec 17 10:51:38.344 2019] fdtdec_get_addr_size_auto_noparent: fdtdec_get_addr_size_auto_parent: na=2, ns=2, fdtdec_get_addr_size_fixed: reg: addr=ff960000
[Tue Dec 17 10:51:38.344 2019] fdtdec_get_int: dsi,lanes: 0x4 (4)
[Tue Dec 17 10:51:38.344 2019] fdtdec_get_int: dsi,format: 0x0 (0)
[Tue Dec 17 10:51:38.344 2019] fdtdec_get_int: dsi,flags: 0xa03 (2563)
[Tue Dec 17 10:51:38.344 2019] fdtdec_get_int: reg: 0x0 (0)
[Tue Dec 17 10:51:38.350 2019] rockchip_dw_mipi_dsi_init-859:dsi->lanes=4, dsi->format=0x0, dsi->mode_flags=0xa03, dsi->channel=0
[Tue Dec 17 10:51:38.350 2019] fdtdec_get_int: hactive: 0x320 (800)
[Tue Dec 17 10:51:38.350 2019] fdtdec_get_int: vactive: 0x500 (1280)
[Tue Dec 17 10:51:38.350 2019] fdtdec_get_int: clock-frequency: 0x3dfd240 (65000000)
[Tue Dec 17 10:51:38.350 2019] fdtdec_get_int: hsync-len: 0xa (10)
[Tue Dec 17 10:51:38.350 2019] fdtdec_get_int: hfront-porch: 0x4 (4)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: hback-porch: 0x4 (4)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: vsync-len: 0x2 (2)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: vfront-porch: 0x12 (18)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: vback-porch: 0x12 (18)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: hsync-active: 0x0 (0)
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_int: vsync-active: 0x0 (0)
[Tue Dec 17 10:51:38.351 2019] Using display timing dts
[Tue Dec 17 10:51:38.351 2019] Detailed mode clock 65000 kHz, flags[a]
[Tue Dec 17 10:51:38.351 2019]     H: 0800 0804 0814 0818
[Tue Dec 17 10:51:38.351 2019]     V: 1280 1298 1300 1318
[Tue Dec 17 10:51:38.351 2019] bus_format: 100e
[Tue Dec 17 10:51:38.351 2019] fdtdec_get_addr_size_auto_noparent: fdtdec_get_addr_size_auto_parent: na=2, ns=2, fdtdec_get_addr_size_fixed: reg: addr=ff900000
[Tue Dec 17 10:51:38.352 2019] rk lcdc aclk config: aclk = 400000000HZ, pll select = 2, div = 2
[Tue Dec 17 10:51:38.352 2019] rk lcdc hclk config: hclk = 100000000HZ, div = 4
[Tue Dec 17 10:51:38.352 2019] rkclk_pll_set_any_freq, pll_id[3], freq=65000000
[Tue Dec 17 10:51:38.358 2019] fin=24, fout=65000000, gcd=2, refdiv=12, fbdiv=455, postdiv1=2, postdiv2=7, frac=0
[Tue Dec 17 10:51:38.358 2019] rk lcdc - 0 dclk set: dclk = 65000000HZ, pll select = 1, div = 1
[Tue Dec 17 10:51:38.358 2019] Warning: not support pin_pol
[Tue Dec 17 10:51:38.358 2019] pwrctr: set lcd-en(260)=1,delay:10ms
[Tue Dec 17 10:51:38.361 2019] pwrctr: set lcd-rst(1053)=1,delay:6ms
[Tue Dec 17 10:51:38.369 2019] rockchip_dw_mipi_dsi_prepare-892:enter
[Tue Dec 17 10:51:38.371 2019] rockchip_phy_power_on: failed to find phy power on funcs
[Tue Dec 17 10:51:38.389 2019] failed to wait for phy clk lane stop state
[Tue Dec 17 10:51:39.113 2019] rockchip_dw_mipi_dsi_enable-942:enter
[Tue Dec 17 10:51:39.113 2019] rockchip_dw_mipi_dsi_enable-959:vop BIG output to dsi0
[Tue Dec 17 10:51:39.120 2019] rockchip_panel_enable: zxl compatible[simple-panel-dsi]
[Tue Dec 17 10:51:39.234 2019] gpio = 0xffffffff is not valid!
[Tue Dec 17 10:51:39.234 2019] rk_pwm_bl_config: brightness: 0
[Tue Dec 17 10:51:39.242 2019] zxl display_logo end
[Tue Dec 17 10:51:39.242 2019] Failed to find part: 'logo'
[Tue Dec 17 10:51:39.242 2019] get_content: base_offset = 0x0
[Tue Dec 17 10:51:39.243 2019] get_entry: base_offset = 0x8000
[Tue Dec 17 10:51:39.243 2019] Failed to find part: 'logo'
[Tue Dec 17 10:51:39.244 2019] get_content: base_offset = 0x0
[Tue Dec 17 10:51:39.244 2019] get_entry: base_offset = 0x8000
[Tue Dec 17 10:51:39.303 2019] checkKey
[Tue Dec 17 10:51:39.307 2019] vbus = 1
[Tue Dec 17 10:51:39.307 2019] board_fbt_key_pressed: ir_keycode = 0x0, frt = 0
[Tue Dec 17 10:51:39.308 2019] initcall: 0000000000215df4 (relocated to 0000000005906df4)
[Tue Dec 17 10:51:39.308 2019] ### main_loop entered: bootdelay=3
[Tue Dec 17 10:51:39.309 2019]
[Tue Dec 17 10:51:39.309 2019] ### main_loop: bootcmd="bootrk"
[Tue Dec 17 10:51:39.309 2019] Hit any key to stop autoboot:  3  2  1  0
[Tue Dec 17 10:51:41.926 2019] rkboot #  

jpchen

kernel/logo.bmp 这个是否存在

q303341192

jpchen 发表于 2019-12-17 11:31
kernel/logo.bmp 这个是否存在

存在的，hdmi输出可以正常显示uboot logo。

jpchen

q303341192 发表于 2019-12-17 11:44
存在的，hdmi输出可以正常显示uboot logo。

可以先检查一下，uboot上电屏的供电是否正常，mipi指令通讯是否ok

q303341192

jpchen 发表于 2019-12-17 12:01
可以先检查一下，uboot上电屏的供电是否正常，mipi指令通讯是否ok

mipi的bist测试模式正常是否能说明供电和指令通讯都ok？

jpchen

q303341192 发表于 2019-12-17 12:14
mipi的bist测试模式正常是否能说明供电和指令通讯都ok？

你是开机后uboot不显示logo,到开机动画再显示的吗？

q303341192

jpchen 发表于 2019-12-17 14:27
你是开机后uboot不显示logo,到开机动画再显示的吗？

嗯 只有uboot的logo显示不出来，kernel和android系统的动画都能显示。

jpchen

q303341192 发表于 2019-12-17 14:29
嗯 只有uboot的logo显示不出来，kernel和android系统的动画都能显示。

可以试一下修改

&route_dsi {
        status = "okay";
        logo,mode = "center";
};

q303341192

jpchen 发表于 2019-12-17 14:36
可以试一下修改

&route_dsi {

dts已经是这样配的了，附件是我的dts文件。

jpchen

q303341192 发表于 2019-12-17 14:57
dts已经是这样配的了，附件是我的dts文件。

那不应该咯，如果这个配上，有android动画，说明uboot的时候mipi已经通讯成功了。
不然android动画都不显示，是不是logo有问题，有换过其他的logo吗？