• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 515 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.

Pandaboard syslink issues

Janak Pundit
Prodigy 80 points

I have pandaboard that runs Ubuntu Maverick. I followed omapedia and get pre-installed ubuntu images. I installed all ti-omap-tools and then installed all ti packages such as ducat multimedia firmware , omap4-multimedia-dev, etc..

I can successfully (it seems)  run omap-ducati-setup.

After that, when when I try to use gstreamer, I get Nameserver related errors in system log (dmesg).

[  575.328948] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
[  575.329010] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
[  575.329010] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
[  575.330352] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
[  575.330383] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
[  575.330383] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
[  575.331329] proc4430_attach num_mem_entries = 6
[  575.335906] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
[  575.336975] proc4430_attach num_mem_entries = 6
[  575.341522] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
[  575.342254] nameserver_get_local entry not found!

 

 What is wrong?  I also noticed there is no /dev/syslinkipc directory.


I followed omapedia instruction to build L24.11 kernel, so that I can build syslink drivers as modules. But that does not compile the driver as modules, it has to be builtin.

 

 

  • 0
    Prodigy 80 points

    Can somone help? Someone from TI?

    It looks like There is no support from TI , for using Ducati MM and video capture,  using Ubuntu or Android on TI development platforms such as Blaze and pandaboard.

    There is lack of documentation, maybe video capture is not supported yet. Just like to know if it is or if it is not.

    Syslink does not work, since there are Nameserver errors (not sure what is causing them, missing devices in /dev ??)

     

    Thank you

  • 0 in reply to Janak Pundit
    TI__Genius 10210 points

    Pandaboard is a community effort.  Please post your questions at the Pandaboard forum http://groups.google.com/group/pandaboard

  • 0 in reply to Vishveshwar Bhat
    Prodigy 80 points

    Vishveshwar, thank you for your reply but this question was not particulary addressed to pandaboard. 

    The issue is present in TI's Blaze platform.

    So can anyone from TI can help for video capture on Blaze platform using either Ubuntu or Android, or is all this not supported yet by TI. Seems like TI's syslink support is very very limited and syslink is not matured yet. Is this true or not? so I can stop working on this syslink  things that are still TI proprietary items and are not made available to user community.

     

    Thank you

  • 0 in reply to Janak Pundit
    TI__Genius 10210 points

    This forums topic description clearly says "This group contains forums for questions on OMAPL-1 and OMAP35x based processors". OMAP4 is not supported here.

    You will need to contact your TI rep/distributor for support with OMAP4

  • 0 in reply to Vishveshwar Bhat
    Prodigy 80 points

    Vishveshvar,

    There is no forum for omap4 processor and support for omap4 from ti. TI sell blaze platform but there is no support. 

    There are several question in this forum regarding OMAP4 which have been answered by well informed and intelligent TI engineeres, or they at least point to correct links.

    The question is not about OMAP4 or BLAZE or PandaBOARD or Ubuntu or Android. If you read, it is about syslink errors.