• Locked Locked
  • Replies 9 replies
  • Subscribers 101 subscribers
  • Views 997 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.

Error running dsplink sample programs

sressler
Prodigy 40 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I'm trying to get the sample DSPLINK programs running on my system and am having some problems. I am developing on a linux host PC, and have montavista linux running on the arm core of a Davinci DM6446 processor. I've compiled both the gpp and dsp sides of DSPLINK and then compiled the sample programs. I'm trying to run the sample program "loop" and get the following output:

root@10.0.0.106:/# ./loopgpp loop.out 100 5
=============== Sample Application : LOOP ==========
Entered LOOP_Create ()
dsplink driver open: /dev/dsplink: No such device or address
PROC_setup failed. Status =  [0x80008008]
Leaving LOOP_Create ()
Entered LOOP_Delete ()
Assertion failed (((drvObj != NULL) && (IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj == NULL) && (cmdId == CMD_PROC_ATTACH))). File : drv_api.c Line : 421
CHNL_freeBuffer () failed (output). Status = [0x80008002]
Assertion failed (((drvObj != NULL) && (IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj == NULL) && (cmdId == CMD_PROC_ATTACH))). File : drv_api.c Line : 421
CHNL_delete () failed (input). Status = [0x80008002]
Assertion failed (((drvObj != NULL) && (IS_OBJECT_VALID (drvObj, SIGN_DRV))) || ((drvObj == NULL) && (cmdId == CMD_PROC_ATTACH))). File : drv_api.c Line : 421
CHNL_delete () failed (output). Status = [0x80008002]
Leaving LOOP_Delete ()
====================================================

I've already executed "mknod /dev/dsplink c 230 0" according to the wiki page at:

http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues

and I can see the /dev/dsplink device file. Can anyone shed some light as to why this is failing? Thanks,

-Steve

 

  • TI__Mastermind 37340 points

    Are you performing "insmod" before "mknod"? also, are you getting any errors during insmod?

  • in reply to Juan Gonzales
    Prodigy 40 points

    Thanks, it looks like that was the problem. Now I'm seeing:

    root@10.0.0.106:/# insmod dsplinkk.ko
    dsplinkk: no version for "struct_module" found: kernel tainted.

    dsplinkk: module license 'DSP/BIOS(TM) LINK' taints kernel.

    DSPLINK Module (1.50) created on Date: Dec  8 2008 Time: 12:57:45

    root@10.0.0.106:/# mknod /dev/dsplink c 230 0
    root@10.0.0.106:/# ./loopgpp loop.out 100 5
    =============== Sample Application : LOOP ==========
    Entered LOOP_Create ()
    Leaving LOOP_Create ()
    Entered LOOP_Execute ()
    Leaving LOOP_Execute ()
    Entered LOOP_Delete ()
    Leaving LOOP_Delete ()
    ====================================================

     

    -Steve

  • in reply to sressler
    TI__Mastermind 37340 points

    FYI, you can safely ignore kernel tainted errors; they appear for any software module that does not conform to GPL license; we are working on getting our dsplink and cmem kernel modules GPLed, but we are not quite there yet.

     

  • in reply to Juan Gonzales
    Prodigy 130 points

    I too am having problems running the sample program.  I have however installed the module,

    the readwrite program spits out

    Entered rdwr_create()

    Proc_attach_failed. Status [0x80008008]

    and a bunch more messages all stating the same status.

     All the samples do this. Any suggestions on finding the cause or fixing it would be appreciated.

    Curtis

  • in reply to Curtis Zaiss
    Prodigy 130 points

    I should clarify  that I am building for an Omap L138

  • in reply to Curtis Zaiss
    TI__Expert 4930 points

    Curtis,

    Please can you ensure that both the mknod step and insmod of DSPLink device driver has been done.

    Does insmod step give any error?

    Has DSPLink been built with the same Linux kernel version that it is being used with?

    You can also enable trace http://wiki.davincidsp.com/index.php/Enabling_trace_in_DSPLink and see which API is giving the error.

    Deepali

  • in reply to Deepali Uppal
    Prodigy 130 points

    Here are the returns


    root@arago:/media/sdb1/dsplink# insmod ./dsplinkk.ko
    DSPLINK Module (1.64) created on Date: Mar 22 2010 Time: 10:44:00

    I have inserted trace into the dsplink, but it has provided an equally cryptic response,  Ive looked in the file specified and have no insight into the problem.

    Assertion failed (ipsEventList [i].eventHandlerCount == 0). File : /media/VISTA/CCStudio_v3_3/dsplink_linux_1_64/dsplink/gpp/src/../../gpp/src/ldrv/IPS/ips.c Line : 604
    ============= Sample Application : READWRITE ==========
    Entered RDWR_Create ()
    PROC_attach failed. Status: [0x80008008]
    Leaving RDWR_Create ()
    Create phase failed. Status: [0x80008008]
    Entered RDWR_Delete ()
    Assertion failed (IS_VALID_MSGQ (msgqQueue)). File : msgq.c Line : 478
    MSGQ_release () failed. Status = [0x8000800b]
    MSGQ_transportClose () failed. Status = [0x80008002]
    Assertion failed (IS_VALID_MSGQ (msgqQueue)). File : msgq.c Line : 329
    Leaving RDWR_Delete ()
    =======================================================

  • in reply to Curtis Zaiss
    Prodigy 130 points

    Does anyone have a working configuration combination of the kernel, dsplink, bios, tools etc for the omap l138

    Someone that has gotten it to work prefferably.

    If so, could you post the configuration and possibly the links.  Maybe also the steps you used, changes to makefiles and stuff.  

     I'm still having problems building u-boot,   some problems in the board.c file   declarations of weak

    cant use menuconfig   because it cant find ncurses libraries

     dsplink doesn't seem to work and thus cant use the sample programs.

     

  • in reply to Curtis Zaiss
    TI__Mastermind 24340 points

    This one should work, and the read me file has the versions and preparation that you need to do:

    http://e2e.ti.com/support/arm174_microprocessors/omap_applications_processors/f/42/p/38132/133210.aspx#133210