• 状态 TI Thinks Resolved
  • 回复 4 回复
  • 答案 1 答案
  • 订户 17 订户
  • 视图 72 视图
  • 用户 0 会员在此处
选项
选项
相关

Original question:

[参考译文] AM625：在 SDK 9.0的 u-boot 中启用显示 DPI

AM625: am625 ,How to display the logo in U-boot

gong yaxuan
Prodigy 50 points
Part Number: AM625


I referred to the device tree and defconfig specified in the linked document and enabled the LVDS backlight. However, on the LVDS screen, there was no display at all.

3.1.2.9. U-Boot Splash Screen — Processor SDK AM62x Documentation

 

device tree:

/ {
    chosen {
        tick-timer = &main_timer0;
    };

    panel_lvds: panel-lvds {
        bootph-pre-ram;
        compatible = "simple-panel";
        status = "okay";
        width-mm = <154>;
        height-mm = <85>;
        data-mapping = "vesa-24";
        panel-timing {
            bootph-pre-ram;
            clock-frequency = <38000000>;
            hactive = <1024>;
            hfront-porch = <88>;
            hsync-len = <6>;
            hback-porch = <176>;
            vactive = <600>;
            vfront-porch = <25>;
            vsync-len = <5>;
            vback-porch = <20>;
            hsync-active = <0>;
            vsync-active = <1>;
            de-active = <1>;
        };
        port {
            panel_lvds_in: endpoint {
                remote-endpoint = <&oldi0_out>;
            };
        };
    };
};

&dss {
    bootph-all;
    clocks = <&k3_clks 186 6>,
        <&k3_clks 186 0>,
        <&k3_clks 186 2>;
    ti,am65x-oldi-io-ctrl = <&dss_oldi_io_ctrl>;
};

&oldi0 {
    bootph-all;
    status = "okay";
};

&oldi0_ports {
    #address-cells = <1>;
    #size-cells = <0>;

    port@0 {
        reg = <0>;
        oldi0_in: endpoint {
            remote-endpoint = <&dpi0_out>;
        };
    };

    port@1 {
        reg = <1>;
        oldi0_out: endpoint {
            remote-endpoint = <&panel_lvds_in>;
        };
    };
};

&dss_ports {
    #address-cells = <1>;
    #size-cells = <0>;

    /* VP1: Output to OLDI */
    port@0 {
        reg = <0>;
        dpi0_out: endpoint {
            remote-endpoint = <&oldi0_in>;
        };
    };
};

&main_timer0 {
    clock-frequency = <25000000>;
};

=> ls mmc 1
            EFI/
 25676288   Image
   279913   tiboot3-am62x-gp-evm.bin
   282502   tiboot3-am62x-hs-evm.bin
   279913   tiboot3.bin
    12285   ti_logo_414x97_32bpp.bmp.gz
  1336827   tispl.bin
  1412403   u-boot.img
      574   uEnv.txt
            System Volume Information/

8 file(s), 2 dir(s)

=> fatload mmc 1 $loadaddr ti_logo_414x97_32bpp.bmp.gz
12285 bytes read in 2 ms (5.9 MiB/s)
=> bmp display $loadaddr m m
=> bmp info
Image size    : 414 x 97
Bits per pixel: 32
Compression   : 3

 

I would like to know how to troubleshoot the problem. How can I make the Uboot display the logo properly? If any information is needed from me, please let me know. Thank you.

  • 0
    TI__Mastermind 43040 points

    感谢您对TI产品的关注。
    我们正在核实您的问题，请等待我们的答复。

  • 0
    TI__Mastermind 36400 points

    Hi,

    Can you please share the part # of the OLDI panel you are using (and is it a single link or dual-link OLDI panel) and if you are using TI EVM or a custom board? You mentioned that you were able to enable the backlight, is the backlight getting on during the U-Boot stage? To isolate a display+backlight issue vs OLDI signals issue, can you try probing the OLDI lines on your board during boot to see if there is any activity? Have you verified the OLDI panel working with Linux kernel?

  • 0 回复 Links
    Prodigy 50 points

    Thank you for your help.I using custom board .I raised the backlight pin at the U-boot stage, and I could see the LVDS backlight turning on.The test I conducted used a single-channel LVDS. Under Linux, the single-channel LVDS display functioned normally. I previously saw a post asking whether U-boot does not support single-channel LVDS?

    I'll go and measure the clock and the data pins again. Are there any other points that need attention?

  • 0 回复 gong yaxuan
    TI__Mastermind 36400 points

    Hi,
    Yes, Single-Link OLDI panels are currently not supported in the U-Boot splash drivers. It is expected to be enabled in the 12.0 SDK release (around March-April, 26 timeframe).