• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 1510 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM8148 U-Boot Splash Screen

Nick Reed
Intellectual 465 points

Using the latest patch files from the EZSDK we have been able to enable the splash screen on the DM8148 from U-Boot.  Ideally, we would like the splash screen to show up until we can make a smooth handoff to the framebuffer/vpss/hdmi kernel modules.

Right now, the behavior we are seeing is immediately upon the kernel starting execution, the bitmap we have displayed disappears.  The HDMI/DVO2 outputs are still being driven with a proper video signal, but it appears the VPDMA transfers have been halted.  We have verified the logo time is long enough to not be the cause.

Dumping some registers in U-Boot and in the kernel afterwards, it looks like the HDVPSS is being reset . PM_HDVPSS_PWRSTCTRL has bits 0 & 1 low, RM_HDVPSS_RSTST is 0. (The names to which the U-Boot patches refer)

I was hoping to get some insight as to what could be causing this, if this is the expected behavior of the splash screen (Does anyone else have a splash screen staying on longer?), or if something that has changed in our board file or boot loader could be causing it.  Regardless, we will need the splash screen to maintain throughout the kernel boot process for as long as possible.

Thanks.

  • 0
    TI__Guru 59700 points

    logo should continue to display even after kernel boots up.

    I can think of couple of issues:

    1.Check your memory map and ensure VPDMA descriptor memory address assigned to boot logo is not getting corrupted when the kernel starts execution.

    2. We had an issue in DVR RDK on 8168 where the kernel on boot up would modify the pinmux settings. Below patch resolved the issue:

    diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
    index 6d6370f..ba23ddc 100755
    --- a/arch/arm/mach-omap2/devices.c
    +++ b/arch/arm/mach-omap2/devices.c
    @@ -1871,8 +1871,13 @@ static void __init ti81xx_video_mux(void)
       omap_mux_init_signal("vin0_d19", OMAP_MUX_MODE1);
       omap_mux_init_signal("vout0_r_cr0", OMAP_MUX_MODE1);
       omap_mux_init_signal("tsi5_data", OMAP_MUX_MODE1);
    +  #ifdef CONFIG_MACH_TI8168_DVR
    +  omap_mux_init_signal("tsi5_bytstrt", OMAP_MUX_MODE2);
    +  omap_mux_init_signal("tsi5_pacval", OMAP_MUX_MODE2);
    +  #else
       omap_mux_init_signal("tsi5_bytstrt", OMAP_MUX_MODE1);
    -  omap_mux_init_signal("tsi5_pacval", OMAP_MUX_MODE1);
    +  omap_mux_init_signal("tsi5_pacval", OMAP_MUX_MODE1);  
    +  #endif
       omap_mux_init_signal("tsi5_pacerr", OMAP_MUX_MODE1);
       omap_mux_init_signal("vin1_clk1",   OMAP_MUX_MODE2);
       omap_mux_init_signal("vin0_hsync0", OMAP_MUX_MODE1);

     

    The patch may not be applicable in your case as we saw the issue on 8168 but it way be worth checking. 

  • 0
    Intellectual 350 points

    May I know where can download the latest patch to enable the splash screen? Thank you very much.

  • 0 in reply to Wade Xu
    TI__Guru 59700 points

    I don't know about EZSDK .If you are referring to DVR RDK pls refer this post: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/247546/867752.aspx#867752

     

  • 0 in reply to Badri Narayanan
    Intellectual 350 points

    Thanks a lot. Download the code from http://arago-project.org/git/projects/?p=u-boot-dvr-rdk-dm81xx.git;a=shortlog;h=refs/heads/dvrrdk_uboot_int_branch

    It can display the bitmap from u-boot  on my DM1848 board. However, when Linux boot up, after load and start the m3 firmware. I got the following error.

    Configuring fb0 to LCD
    [ 10.600000] VPSS_FVID2: contrl event 0x5 timeout
    [ 10.610000] ti81xxfb ti81xxfb: failed to star.
    [ 12.610000] VPSS_FVID2: delete time out

    Any ideal what should I do to get a smooth handover? do I need to stop the m3 before load firmware? How?

    BTW, I am sure my memory for m3 and linux is NOT overlapped.

  • 0 in reply to Wade Xu
    TI__Guru 59700 points

    Pls check if the HDVPSS descriptor address is correct.This is different from the M3 address. If you are not sure pls share the vpss xem3 map file and your kernel bootargs

  • 0 in reply to Badri Narayanan
    TI__Guru**** 476235 points

    Or it could be that timeout parameters is really big, so fb display is not stopped. Could you provide your boot args.

    Regards,

    Brijesh

  • 0 in reply to Badri Narayanan
    Intellectual 350 points

    Thanks. it's the memory issue. after move to a complete no use memory space. things are normal