• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 259 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.

About BeagleBoard's Dsplink

kumar bhimesh3
Intellectual 695 points
Other Parts Discussed in Thread: OMAP3530

Hi all,

       This bhimesh . Presently i am looking for dsplink Beagleboard -c4(OMAP3530) .But i find the url  http://ossie.wireless.vt.edu/trac/wiki/BeagleBoard_DSPLink . I followed the procedure give in the that link . like i was downloaded the dsp/bios link version dsplink_1_61_03.tar.gz and BIOS 5.33.02, XDCtools 3.10.03 and C6000 Code Generation Tools v6.0.16 Linux Host and i installed the al these tools as how it is explianed in the url and  Built DSPLink Files .

But when i

 cd $DSPLINK/gpp/src/api
  $ make -s clean

/home/bhimesh/dsplink_1_61_03/dsplink//make/start.mk:26: /home/bhimesh/dsplink_1_61_03/dsplink//config/BUILD/CURRENTCFG.MK: No such file or directory
/home/bhimesh/dsplink_1_61_03/dsplink//make/current.mk:22: /home/bhimesh/dsplink_1_61_03/dsplink//make//systools.mk: No such file or directory
/home/bhimesh/dsplink_1_61_03/dsplink//make/current.mk:24: /home/bhimesh/dsplink_1_61_03/dsplink//make//osdefs.mk: No such file or directory
make: 2: Command not found
make: *** [/home/bhimesh/dsplink_1_61_03/dsplink//make/rulebase.mk] Error 127

This is the error coming .how to resolv it. Here in the first error  i.e  /home/bhimesh/dsplink_1_61_03/dsplink//make/start.mk:26: /home/bhimesh/dsplink_1_61_03/dsplink//config/BUILD/CURRENTCFG.MK: No such file or directory
there is no build  folder in conifg .Therefore there is no CURRENTCFG.MK

Plese help me on this 

Thanks 
bhimesh

 

  • 0
    Prodigy 120 points 

    "/home/bhimesh/dsplink_1_61_03/dsplink//make/start.mk:26:"


    You have two "//" which probably means there is an environment variable that is not being set 
    that's supposed to place some text in between those slashes. 
    I've had a similar issue - mine was due to a malformed initial configuration file.
     I suspect there is an initial configuration script you need to run in order to generate a currentcfg.mk file.
    Make sure your user has permissions for the whole directory tree, and don't use "sudo" if on ubuntu.