• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 724 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.

SYSLINK for QNX

Sharath Chandrashekar
Prodigy 215 points

How to build TI syslink examples for QNX target DM814x on Windows build environment? 

  • 0
    TI__Genius 17205 points

    Generally same as all other OS's: http://processors.wiki.ti.com/index.php/SysLink_Install_Guide

    • set up products.mak
    • make syslink
    • make samples
    • make install

    Running is a little different, but that SysLink Install Guide has all the details.

    Chris

  • 0 in reply to Chris Ring
    Prodigy 10 points

    Hi,

    I managed to build the Syslink Driver and the applications for QNX platform for TI814x target. But when i try to run the syslink examples (i.e MessageQ). I get the following error

    Can any one tell me how to fix this ? Is syslink functional on QNX. I am using  syslink_2_10_03_20 . Syslink is offcially supported in this version. 

    # run syslink_drv

    sh: run: cannot execute - No such file or directory

    # sh run_syslink_drv.sh

    + export TRACE=1

    + export TRACEFAILURE=1

    + syslink_drv

    <1>Trace enabled

    <1>Trace SetFailureReason enabled

    # sh run_messageqapp_debug.sh

    frameq_g                                messageq_ti81xx_dsp.xe674

    inetd.pid                               messageq_ti81xx_videom3.xem3

    libsyslink.so.1                         messageq_ti81xx_vpssm3.xem3

    libsyslink_common.so.1                  resolv.conf

    libsyslink_common_g.so.1                run_messageqapp_debug.sh

    libsyslink_g.so.1                       run_syslink_drv.sh

    libsyslink_slave_loader.so.1            slaveloader

    libsyslink_slave_loader_g.so.1          slaveloader_g

    messageQ                                syslink_drv

    messageQ_g                              syslink_shm

    # sh run_messageqapp

    run_messageqapp.sh        run_messageqapp_debug.sh

    # sh run_messageqapp.sh

    + /dev/shmem/slaveloader_g startup DSP /dev/shmem/messageq_ti81xx_dsp.xe674

    Attached to slave procId 0.

    Loading procId 0.

    Loaded file /dev/shmem/messageq_ti81xx_dsp.xe674 on slave procId 0.

    Started slave procId 0.

    + /dev/shmem/slaveloader_g startup VIDEO-M3 /dev/shmem/messageq_ti81xx_videom3.xem3

    Attached to slave procId 1.

    Loading procId 1.

    Loaded file /dev/shmem/messageq_ti81xx_videom3.xem3 on slave procId 1.

    Started slave procId 1.

    + /dev/shmem/slaveloader_g startup VPSS-M3 /dev/shmem/messageq_ti81xx_vpssm3.xem3

    Attached to slave procId 2.

    Loading procId 2.

    Loaded file /dev/shmem/messageq_ti81xx_vpssm3.xem3 on slave procId 2.

    Started slave procId 2.

    + /dev/shmem/messageQ_g

    MessageQApp sample application

    Run for all supported proc IDs

    Entered MessageQApp_startup

    After Ipc_loadcallback:

        status [0x0]

    <1>Assertion at Line no: 136 in /db/atree/library/trees/sl/sl-c20/src/packages/ti/syslink/product/export/syslink_2_10_03_20/packages/ti/syslink/../../ti/syslink/ipc/hlos/knl/Qnx/Ipc_devctl.c: (out->apiStatus >= 0) : failed

    Error in Ipc_control Ipc_CONTROLCMD_STARTCALLBACK[0xffffffff]

    Leaving MessageQApp_startup ffffffff

    + /dev/shmem/slaveloader_g shutdown VPSS-M3

    Stopped slave procId 2.

    Unloaded slave procId 2.

    Detached from slave procId 2.

    + /dev/shmem/slaveloader_g shutdown VIDEO-M3

    Stopped slave procId 1.

    Unloaded slave procId 1.

    Detached from slave procId 1.

    + /dev/shmem/slaveloader_g shutdown DSP

    Stopped slave procId 0.

    Unloaded slave procId 0.

    Detached from slave procId 0.

    + /dev/shmem/messageQ_g 1 DSP /dev/shmem/messageq_ti81xx_dsp.xe674

    MessageQApp sample application

    Entered MessageQApp_startup

    Loading and starting procId [0] with [/dev/shmem/messageq_ti81xx_dsp.xe674]

    Attached to slave procId 0.

    Loading procId 0.

    Loaded file /dev/shmem/messageq_ti81xx_dsp.xe674 on slave procId 0.

    Started slave procId 0.

    SlaveLoader_startup status [111693824]

    After Ipc_loadcallback:

        status [0x0]

    <1>Assertion at Line no: 136 in /db/atree/library/trees/sl/sl-c20/src/packages/ti/syslink/product/export/syslink_2_10_03_20/packages/ti/syslink/../../ti/syslink/ipc/hlos/knl/Qnx/Ipc_devctl.c: (out->apiStatus >= 0) : failed

    Error in Ipc_control Ipc_CONTROLCMD_STARTCALLBACK[0xffffffff]

    Leaving MessageQApp_startup fffffff

    - Thanks in Advance.

    Srinivas

  • 0 in reply to srinivas belur
    TI__Genius 12865 points

    Hi Srinivas,

    Could you check your products.mak to see what value you have for the variable TI81XXDSP_DMTIMER_FREQ? By default it is set to 32768, but it may or may not match your actual dmtimer frequency (another common value is 20000000). You need to match it up if it isn't already done, otherwise the slave would configure timer interrupts at the wrong rate.

    Let us know afterwards if you are still having issues.

    Best regards,

    Vincent