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.

Blaze omapfb failed to setup omapfb with HDMI

Other Parts Discussed in Thread: 4430

Hi all,

I use blaze 4430 ES2.2 board, and remove the LCD panel. I can't get the HDMI work with Android 4.0. I follow omappedia to build u-boot, xloader, kernel and ASF file.

http://www.omappedia.org/wiki/L27.IS.1_OMAP4_Icecream_Sandwich_Release_Notes

The kernel can't setup framebuff. How to make the HDMI work when there is no other VIDEO devices?

<7>[    5.272766] omapdss OVERLAY: check_overlay 0: (0,0 640x480 -> 640x480) disp (640x480)
<7>[    5.281311] omapdss MANAGER: omap_dss_mgr_apply(lcd)
<6>[    5.286712] cannot apply mgr(lcd) on inactive device
<4>[    5.292022] omapfb omapfb: failed to apply dispc config
<7>[    5.297607] omapdss MANAGER: omap_dss_mgr_apply(tv)
<7>[    5.302764] omapdss OVERLAY: check_overlay 0: (0,0 640x480 -> 640x480) disp (640x480)
<7>[    5.311065] omapdss MANAGER: configure_overlay(0)
<7>[    5.316070] omapdss DISPC: dispc_setup_plane 0, pa a9a00000, sw 640, 0,0, 640/1x480/1 -> 640x480, ilace 0, cmode 800, rot 0, mir 0 chan 1 3tap
<7>[    5.329620] omapdss DISPC: calc_rot(0): scrw 640, 640x480
<7>[    5.335327] omapdss DISPC: offset0 0, offset1 0, row_inc 1, pix_inc 1
<7>[    5.342132] omapdss DISPC: 0,0 640*1x480*1 -> 640x480
<7>[    5.347503] omapdss DISPC: fifo(0) low/high old 1272/1279, new 944/1279
<7>[    5.354492] omapdss DISPC: dispc_enable_plane 0, 1
<7>[    5.359558] omapdss MANAGER: configure_manager(1)
<7>[    5.364562] omapdss DISPC: GO DIGIT
<7>[    5.368286] omapdss MANAGER: omap_dss_mgr_apply(lcd2)
<6>[    5.373657] cannot apply mgr(lcd2) on inactive device
<4>[    5.378997] omapfb omapfb: failed to apply dispc config
<7>[    5.384552] omapdss: ENTER hdmi_panel_enable
<4>[    5.389068] omapfb omapfb: Failed to enable display 'hdmi'
<3>[    5.394897] omapfb omapfb: failed to initialize default display
<7>[    5.402587] omapdss MANAGER: omap_dss_mgr_blank(tv,wait=1)
<7>[    5.408416] omapdss MANAGER: configure_overlay(0)
<7>[    5.413391] omapdss DISPC: dispc_enable_plane 0, 0
<7>[    5.418457] omapdss MANAGER: configure_overlay(1)
<7>[    5.423431] omapdss DISPC: dispc_enable_plane 1, 0
<7>[    5.428497] omapdss MANAGER: configure_overlay(2)
<7>[    5.433471] omapdss DISPC: dispc_enable_plane 2, 0
<7>[    5.438537] omapdss MANAGER: configure_overlay(3)
<7>[    5.443511] omapdss DISPC: dispc_enable_plane 3, 0
<7>[    5.448608] omapdss MANAGER: configure_manager(1)
<7>[    5.453582] omapdss DISPC: GO DIGIT
<6>[    5.465118] omapdss HDMI: Enter hdmi_display_disable
<6>[    5.478546] omapdss HDMI: Release c-state constraint for HDMI
<6>[    5.478546]
<7>[    5.486206] omapdss HDMI: hdmi_runtime_put
<7>[    5.490570] omapdss DISPC: dispc_runtime_put
<7>[    5.495086] omapdss DISPC: dispc_save_context
<7>[    5.499969] omapdss DISPC: context saved, ctx_loss_count -2
<7>[    5.505950] omapdss DSS: dss_runtime_put
<7>[    5.510101] omapdss DSS: dss_save_context
<7>[    5.514373] omapdss DSS: context saved
<6>[    5.518371] hdmi: clearing EDID info
<3>[    5.522186] omapfb omapfb: failed to setup omapfb
<4>[    5.527191] omapfb: probe of omapfb failed with error -22
<3>[    5.534820] omaplfb: OMAPLFB_Init: OMAPLFBInit failed

  • Hi guy,

        I have the same issue,did you solved it? If you solved it ,please give me some points,thanks.  If you use skype or msn,please chat me.Skype:coollu925,msn:coollu925@msn.cn.

    Regards

    Tommy

     

  • Try the following patch. It will help to cross one step.
    I still have some problems with HDCP key loading error.

    It looks like when hdmi panel is default and connected at boot, both hdmi_hotplug_detect_worker and omapfb_init_display are trying to enable the display panel.
    This seems to be design issue.

    -------------------------------------------------------------------------------------------------------------------------
    diff --git a/drivers/video/omap2/dss/hdmi_panel.c b/drivers/video/omap2/dss/hdmi_panel.c index 883897b..4017c3f 100644 --- a/drivers/video/omap2/dss/hdmi_panel.c +++ b/drivers/video/omap2/dss/hdmi_panel.c @@ -96,6 +96,12 @@ static int hdmi_panel_enable(struct omap_dss_device *dssdev) mutex_lock(&hdmi.hdmi_lock); + if (dssdev->state == OMAP_DSS_DISPLAY_ACTIVE) { + DSSWARN("%s: HDMI already active, returning 0\n", __fun__); + r = 0; + goto err; + } + if (dssdev->state != OMAP_DSS_DISPLAY_DISABLED) { r = -EINVAL; goto err;
    -------------------------------------------------------------------------------------------------------------------------
  • Hi Navaneetha,

        Thanks for you reply,it solvd my "omaplfb: OMAPLFB_Init: OMAPLFBInit failed" problem.But i have another issue as below:

    cannot apply mgr(lcd) on inactive device                        
    omapfb omapfb: failed to apply dispc config                     
    cannot apply mgr(lcd2) on inactive device                       
    omapfb omapfb: failed to apply dispc config                     
    omapdss: Tommy: HDMI already active, returning 0

    What should i do to solve it ? and when my system booted,there is no FBx node in the /dev path.

    Regards

    Tommy

     

     

      

  • Hi Tommy,

    Glad that the patch helped you. are you able to see anything on screen? at least the android splash screen?

    You will be able to find fb0 and fb1 under /dev/graphics/

    I guess the manager for lcd and lcd 2 should not be a problem as HDMI doesn't use them, It uses digital channel instead.

    Br,

    Navaneetha

  • Hi Navaneetha,

           Thanks for patch and  your reply,i set the hdmi as default device and the display always "blank screen" and when i entered system, i can see dev/graphics/fb0 and dev/graphics/fb1 node.

        I guess there is some issue in the bootargs,i use the bootargs like GB filesystem  as below:

    #define CONFIG_BOOTARGS "console=ttyO2,115200n8 androidboot.console=ttyO2" \
     " mem=456M@0x80000000 mem=512M@0xA0000000" \
     " root=/dev/mmcblk0p2 rw rootdelay=2 init=/init" \
     " vram=32M omapfb.vram=0:16M" \
     " omapdss.def_disp=hdmi consoleblank=0"

    Whether if the VRAM should change?  or other parameters?

    Regards

    Tommy

     

     

  • Hi Navaneetha,

        Below is my system boot log:

    0871.log.txt

    I just can see a blank screen ~~

    Regards

    Tommy

     

  • Hi Tommy,

    can you enable omapdss and omapfb logs?

    Steps to enable dss logging

    Change your boot args to:

    #define CONFIG_BOOTARGS "console=ttyO2,115200n8 androidboot.console=ttyO2 consoleblank=0" \
                                                            " mem=456M@0x80000000 mem=512M@0xA0000000" \
                                                            " root=/dev/mmcblk0p2 rw rootdelay=2 init=/init" \
                                                            " vram=32M omapfb.vram=0:16M" \
                                                            " omapdss.def_disp=hdmi omapdss.debug=y omapfb.debug=y"

    check if CONFIG_OMAP2_DSS_DEBUG_SUPPORT is set in you defconfig file

  • Hi Navaneetha

        Thanks for your reply,i will try do that. And are you chat use MSN or Skype? May i get you chat number? My skype num:coollu925  ,MSN num:coollu925@mns.cn.

    Regards

    Tommy