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

How to get video working again after syslink upgrade?

Lee Holeva
Genius 4615 points
Other Parts Discussed in Thread: SYSBIOS

To get around a bug in the syslink driver, I am forced to upgrade syslink to version 2.00.00.78.  I rebuilt the kernel followed by building and installing the new syslink driver, but now the display does not work.  I get:

SysLink version : 2.00.00.78
SysLink module created on Date:Jul 20 2011 Time:09:39:31
FIRMWARE: Could not open ProcMgr: -2
Starting telnet daemon.
Loading HDVPSS Firmware
FIRMWARE: Could not open ProcMgr: -2
VPSS_FVID2: Failed to send version command to M3 0xfffffff9.
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
ti81xxfb ti81xxfb: no grpxs
ti81xxfb: probe of ti81xxfb failed with error -22
open /dev/fb0: No such file or directory
cat: write error: No space left on device
cat: write error: No space left on device
Starting syslogd/klogd: done
Starting thttpd.
ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device
ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device
expr: syntax error
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven


Usage: fbset [options] [mode]

Valid options:
  General options:
    -h, --help         : display this usage information
    --test             : don't change, just test whether the mode is valid
    -s, --show         : display video mode settings
    -i, --info         : display all frame buffer information
    -v, --verbose      : verbose mode
    -V, --version      : print version information
    -x, --xfree86      : XFree86 compatibility mode
    -a, --all          : change all virtual consoles on this device
  Frame buffer special device nodes:
    -fb <device>       : processed frame buffer device
                         (default is /dev/fb0)
  Video mode database:
    -db <file>         : video mode database file
                         (default is /etc/fb.modes)
  Display geometry:
    -xres <value>      : horizontal resolution (in pixels)
    -yres <value>      : vertical resolution (in pixels)
    -vxres <value>     : virtual horizontal resolution (in pixels)
    -vyres <value>     : virtual vertical resolution (in pixels)
    -depth <value>     : display depth (in bits per pixel)
    -nonstd <value>    : select nonstandard video mode
    -g, --geometry ... : set all geometry parameters at once
    -match             : set virtual vertical resolution by virtual resolution
  Display timings:
    -pixclock <value>  : pixel clock (in picoseconds)
    -left <value>      : left margin (in pixels)
    -right <value>     : right margin (in pixels)
    -upper <value>     : upper margin (in pixel lines)
    -lower <value>     : lower margin (in pixel lines)
    -hslen <value>     : horizontal sync length (in pixels)
    -vslen <value>     : vertical sync length (in pixel lines)
    -t, --timings ...  : set all timing parameters at once
  Display flags:
    -accel <value>     : hardware text acceleration enable (false or true)
    -hsync <value>     : horizontal sync polarity (low or high)
    -vsync <value>     : vertical sync polarity (low or high)
    -csync <value>     : composite sync polarity (low or high)
    -gsync <value>     : synch on green (false or true)
    -extsync <value>   : external sync enable (false or true)
    -bcast <value>     : broadcast enable (false or true)
    -laced <value>     : interlace enable (false or true)
    -double <value>    : doublescan enable (false or true)
    -rgba <r,g,b,a>    : recommended length of color entries
    -grayscale <value> : grayscale enable (false or true)
  Display positioning:
    -move <direction>  : move the visible part (left, right, up or down)
    -step <value>      : step increment (in pixels or pixel lines)
                         (default is 8 horizontal, 2 vertical)
Starting PVR
omaplfb: OMAPLFB_Init: OMAPLFBInit failed
FATAL: Error inserting omaplfb (/lib/modules/2.6.37/kernel/drivers/gpu/pvr/omapl
fb.ko): No such device

For this I had to also install new versions of xdctools, sysbios, and IPC.  I need to install a new version of ProcMgr, how do I build it and where does it go? I found the source code for ProcMgr, but there is no dedicated makefile.

Lee Holeva

 

  • 0
    Intellectual 745 points

    Hello Lee,

     

    If you're referring to how to build the procmgrapp, there's a section in the Syslink Install guide (not the PSP docs)

    that should be in your EZSDK tree that walks you through how to build individual syslink apps (usr/knl and rtos portions).

    As you've probably have noticed the source is in a samples sub-directory. The global Makefile at the root of your EZSDK

    should have a make target for syslink but you'll notice that there's a 'grep -v samples' in one of them (I'm working from

    memory here so I don't have the exact one at hand). That's why the global EZSDK skips the sample apps if you build

    syslink yourself with that Makefile. The Syslink Install guide is more targeted in it's approach and should get you there.

     

    Hope this helps.

     

    - Juan

     

  • 0 in reply to Juan Solis
    Genius 4615 points

    Juan Solis said:

    If you're referring to how to build the procmgrapp, there's a section in the Syslink Install guide (not the PSP docs)

    that should be in your EZSDK tree that walks you through how to build individual syslink apps (usr/knl and rtos portions).

    No, I am not referring to procmgrapp,  (the PSP Video Driver User's Guide says that procmgrapp is used to load the M3 firmware, but a search for procmgrapp only shows it at ti-syslink-examples, what app actually loads the firmware?) though I suspect its mostly the same code (I need to check this).  In Syslink 2.00.00.78, procmgrapp is replaced by slaveLoader.  EZSDK 5.01.01.80 uses ProcMgr to load the M3 firmware and this is failing.

    I mis-spoke.  It is not ProcMgr actually that I need to rebuild, that's part of Syslink, but the app that uses Syslink to load the M3 firmware.  Can someone tell me where I may find it?  This needs to be remade using the hlos-side libraries from Syslink 2.00.00.78.  I checked the syslink minor apps, and they're getting made:

    ls -l syslinkipc*
    crw-rw----    1 root     root     253,  14 Jun  1 15:06 syslinkipc_ClientNotifyM
    gr
    crw-rw----    1 root     root     253,  16 Jun  1 15:06 syslinkipc_FrameQ
    crw-rw----    1 root     root     253,  15 Jun  1 15:06 syslinkipc_FrameQBufMgr
    crw-rw----    1 root     root     253,   8 Jun  1 15:06 syslinkipc_GateMP
    crw-rw----    1 root     root     253,   4 Jun  1 15:06 syslinkipc_HeapBufMP
    crw-rw----    1 root     root     253,   5 Jun  1 15:06 syslinkipc_HeapMemMP
    crw-rw----    1 root     root     253,  11 Jun  1 15:06 syslinkipc_Ipc
    crw-rw----    1 root     root     253,   7 Jun  1 15:06 syslinkipc_ListMP
    crw-rw----    1 root     root     253,   9 Jun  1 15:06 syslinkipc_MessageQ
    crw-rw----    1 root     root     253,  10 Jun  1 15:06 syslinkipc_MultiProc
    crw-rw----    1 root     root     253,   2 Jun  1 15:06 syslinkipc_NameServer
    crw-rw----    1 root     root     253,   1 Jun  1 15:06 syslinkipc_Notify
    crw-rw----    1 root     root     253,  12 Jun  1 15:06 syslinkipc_Osal
    crw-rw----    1 root     root     253,   0 Jun  1 15:06 syslinkipc_ProcMgr
    crw-rw----    1 root     root     253,  17 Jun  1 15:06 syslinkipc_RingIO
    crw-rw----    1 root     root     253,  35 Jun  1 15:06 syslinkipc_RingIOShm
    crw-rw----    1 root     root     253,   3 Jun  1 15:06 syslinkipc_SharedRegion
    crw-rw----    1 root     root     253,  13 Jun  1 15:06 syslinkipc_SyslinkMemMgr

    Update:

    The problem has something to do with the install of omaplfb.ko failing:

    insmod omaplfb.ko
    omaplfb: OMAPLFB_Init: OMAPLFBInit failed
    insmod: error inserting 'omaplfb.ko': -1 No such device

    Perhaps the module needs to be rebuilt?  No documentation on omaplfb is included in the EZSDK.

    Lee Holeva

     

  • 0 in reply to Lee Holeva
    TI__Expert 6535 points

    Hi Lee,

    which EVM are you using ? I assume it is TI816X ..

    Looks like you have not specified the correct device while building slaveloader app, It should not get OMAP errors..Also Are you building with SYSLINK_USE_NOTIFY=1 ?

    Regards

    Vimal

  • 0 in reply to Vimal Jain
    Genius 4615 points

    Vimal Jain said:

    which EVM are you using ? I assume it is TI816X ..

     

    I have the DM816x/C6A816x/AM389x DDR3 EVM

    Vimal Jain said:

    Looks like you have not specified the correct device while building slaveloader app, It should not get OMAP errors..Also Are you building with SYSLINK_USE_NOTIFY=1 ?

     

    I started with EZSDK 5.01.01.80 with PSP 4.00.00.10, does this use slaveLoader?  The PSP docs refer to procmgrapp. I built syslink.ko following the instructions given in syslink 2.00.00.78 :

    make syslink

    There was no mention of any other procedure.

    Update:

    I found this:

    http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide

    Does this mean that I have to wait for PSP 4.00.00.12, before my display works again?  When will this be released?

    Lee Holeva

     

  • 0 in reply to Lee Holeva
    TI__Expert 6580 points

    It appears that the frame buffer module is not functional. Are you able to run "fbset -i" or check with any standalone Framebuffer examples ? The error that you are seeing is on the SGX Graphics SDK - this is not needed to get the display  running. Once Framebuffer is functional, you can try the Graphics SDK. Also, note that if you are making changes to syslink - it is better to rebuild all kernel modules.

     

     

     

     

  • 0 in reply to Prabindh Sundareson
    Genius 4615 points

    Prabindh Sundareson said:
    Are you able to run "fbset -i"

    No:

    fbset -i
    ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device

    Everything worked fine before I upgraded Syslink, which I had to do because version 68 was crashing my code.  When is either the next version of the EZSDK or the new PSP package coming out?

    Lee Holeva