• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 791 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.

DM8168 EVM, Android & HDMI / Component Output

Jeff Cody
Prodigy 40 points


I have a DM8168EVM that I am using as a target Android development system.  I built Froyo, from the rowboat-froyo-am389x.xml manifest, per the instructions found at: http://processors.wiki.ti.com/index.php/Android_am389x_build_procedure

Android seemingly boots up OK (via the terminal, I can configure ethernet and debug via ADB remotely over ethernet, and see Android processes running).  However, the video out to the display is blank (both HDMI and Component).  There is a valid signal, my test monitors lock onto 1080p60 on HDMI and for Component, the signal seems valid as well (1080i).  However, the image on both displays is blank/black. 

Is there anything that needs to be configured for proper output?  For instance, transparency on a video buffer overlay on top of the graphics plane, etc..

Thanks.

 

  • 0
    TI__Expert 4390 points

    Hi Jeff,

     

    1. As such in Android, video out is redirected to video driver configured by kernel.

    2. In case of AM37x,OMAP35x video out configured by kernel - parsing boot arg

    ex. To configure DVI out, one need to use following bootargs

    omapfb.mode=dvi:1280x720MR-16 omapdss.def_disp="dvi"

    Similarly,on DM37x following is bootargs
    setenv bootargs mem=71M@0x80000000 mem=128M@0x88000000 console=tty0 console=ttyS0,115200n8 androidboot.console=ttyS0 root=/dev/mmcblk0p2 rw rootfstype=ext3 init=/init rootwait ip=off omap_vout.vid1_static_vrfb_alloc=y omapdss.def_disp=dvi omapfb.mode=dvi:1280x720MR-16 mpurate=1000

    3. Would you check if your video driver for HDMI is configured in kernel?
    4.  Would you check you sysfs entry is proper or not? Following might give you light on this.

    http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#Using_S-VIDEO_Monitor

    5. Kindly send us bootlogs and android log : Type logcat on terminal to get anroid logs.

    BR,
    satish

  • 0 in reply to Satish Patel
    Prodigy 40 points

    Thanks for the reply.  Sorry for the delay in response.  I am using an 8168 processor, with the SGX530.  The problem appears to be with the SGX - after a short while, I get the following error message repeatedly:

     

     # # # PVR_K: HWRecoveryResetSGX: SGX Hardware Recovery triggered

    PVR_K: EUR_CR_EVENT_STATUS:     20000000

    PVR_K: EUR_CR_EVENT_STATUS2:    8

    PVR_K: EUR_CR_BIF_CTRL:         0

    PVR_K: EUR_CR_BIF_INT_STAT:     4002

    PVR_K: EUR_CR_BIF_FAULT:        f097000

    PVR_K: EUR_CR_BIF_MEM_REQ_STAT: 0

    PVR_K: EUR_CR_CLKGATECTL:       222220

    PVR_K: EUR_CR_PDS_PC_BASE:      0

    PVR_K: SGX Host control:

    PVR_K:  0x0: 0x00000000 0x00000000 0x00000000 0x00000000

    PVR_K:  0x10: 0x00000069 0x0000000A 0x0003D090 0x00000065

    PVR_K:  0x20: 0x00000000 0x00000001 0x00000029 0x00000000

    PVR_K:  0x30: 0x00001A82 0x00000000 0x00000000 0x00000000

    PVR_K: SGX TA/3D control:

    PVR_K:  0x0: 0x0F002000 0x0F002120 0x0F001000 0x0F0CCCC0

    PVR_K:  0x10: 0x00000001 0x00000002 0x00000001 0x0F0BA4E0

    PVR_K:  0x20: 0x00000000 0x00000000 0x00000018 0x00000000

    PVR_K:  0x30: 0x00000002 0x00000000 0x00000000 0x00000000

    PVR_K:  0x40: 0x00000000 0x00000000 0x00000000 0x00000000

    PVR_K:  0x50: 0x00000000 0x00000000 0x00000000 0x00000000

    PVR_K:  0x60: 0x00000000 0x00000000 0x0F097420 0x00000000

    PVR_K:  0x70: 0x00000000 0x0F0BA4E0 0x00000000 0x00000000

    PVR_K:  0x80: 0x00000000 0x00000000 0x00000000 0x0F000000

    PVR_K:  0x90: 0x8B790000 0x0F0C0400 0x00000000 0x0F098A00

    PVR_K:  0xA0: 0x0F0BA4E0 0x00000000 0x0F098420 0x00000000

    PVR_K:  0xB0: 0x0F006880 0x00000003 0x00000000 0x00000000

    PVR_K:  0xC0: 0x00000001 0x00000000 0x00000000 0x00000000

    PVR_K:  0xD0: 0x00000000 0x00000000 0x00000000 0x00000000

    PVR_K:  0xE0: 0x00000022 0x00000022 0x0F000000 0x80007000

    PVR_K:  0xF0: 0x80047000 0x0F003000 0x00000000 0x00000000

    PVR_K:  0x100: 0x00000000 0x00000000 0x00000000 0x00000000

    PVR_K: Command Complete Data for display device 1:

    PVR_K:  SRC 0: (Not in use)

    PVR_K:  SRC 1: (Not in use)

  • 0 in reply to Jeff Cody
    TI__Expert 5400 points

    Hi Jeff,

    Do you get SGX error message everytime?

    Kindly verify whether syslink, vpss and ti81xxfb modules are loaded properly.

    Please provide output of logcat.

    Thanks and Regards,

    Pankaj Bharadiya.

  • 0 in reply to Pankaj Bharadiya
    Prodigy 40 points

    Pankaj,

     

    Thank you.  No, I don't always get the SGX error message.   Eventually, the system also locks up after a while (the UART console is frozen, and the network fails to respond).  Yes, the syslink, vpss, and ti81xxfb modules are loaded (via rc.syslink):

     

    # lsmod

    ti81xxfb 21974 0 - Live 0xbf18e000

    cfbimgblt 1701 1 ti81xxfb, Live 0xbf188000

    cfbfillrect 2700 1 ti81xxfb, Live 0xbf182000

    cfbcopyarea 2465 1 ti81xxfb, Live 0xbf17c000

    pvrsrvkm 134921 0 - Live 0xbf14d000

    vpss 38284 1 ti81xxfb, Live 0xbf13a000

    syslink 1080898 1 vpss, Live 0xbf000000

     

     

    I've attached the logcat output to this message.

    7080.logcat.txt

    Thanks,

    Jeff

  • 0 in reply to Jeff Cody
    Prodigy 40 points

    Further data point - if I comment out the SGX startup in init.rc, there is no lockup:

    #service pvr /system/bin/sgx/rc.pvr start

    Once I start the SGX stuff up on the command line manually, it locks up shortly after that, just like it is doing on boot if I let it start the SGX up from init.rc.

  • 0 in reply to Jeff Cody
    TI__Expert 5400 points

    Hi Jeff,

     

    Not sure why this is not working for you. Logcat seems to be ok for me.

    Will you please try by modifying your system/bin/syslink/rc.syslink file with the following.

    insmod /system/lib/modules/2.6.32/kernel/drivers/video/ti81xx/vpss/vpss.ko hdcomp_out=0  for compoment or

    insmod /system/lib/modules/2.6.32/kernel/drivers/video/ti81xx/vpss/vpss.ko hdcomp_out=1 HDMI display.

     

    Thanks and Regards.

    Pankaj Bharadiya.