• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 445 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.

DSPLINK-problem while installing SDK

Rico Schulze
Intellectual 480 points

while walking through the getting started guide i get a failure in "Step 2: Configure what platform you are building DSPLink for " of the building the OMAP SDK - guide.

performing  

perl config/bin/dsplinkcfg.pl --platform=OMAPL1XX --nodsp=1 --dspcfg_0=OMAPL1XXGEMSHMEM --dspos_0=DSPBIOS5XX --gppos=MVL5G --comps=ponslrmc --DspTskMode=1

results in the prompt :


  Welcome to DSP/BIOS(TM) Link Configuration Utility
------------------------------------------------------

  !!DSPLINK will be configured for Build OS: LINUX!!

  DSPLINK variable is not set!!
  Please set it:
 On Windows:
  set DSPLINK=<path to DSPLINK base directory>
 On Linux:
  export DSPLINK=<path to DSPLINK base directory>

the command  printenv DSPLINK shows the following path has been set :
/home/mkastner/OMAPL137_arm_1_00_00_xx/dsplink-1_61_03-prebuilt/packages/dsplink

What is the recommanded path, as far as i understood the getting started guide.

How do i have to set DSPLINK to continue installing the sdk?

best regards Rico

 

  • 0
    TI__Mastermind 24340 points

    Hi Rico,

    What version os the SDK are you using?

    Rico Schulze said:
    /home/mkastner/OMAPL137_arm_1_00_00_xx/dsplink-1_61_03-prebuilt/packages/dsplink

    It seems that in your variable the OMAPL137_arm_1_00_00_xx part should not have an xx at the end but the actual version/name of the folder you are using.

    Check where the DSPLink is installed and make sure that the DSPLINK variable is correct.

     

  • 0 in reply to Mariana
    Intellectual 480 points

    I am sorry for this mistake, the prompt i am getting of course has no XX ..

    /home/mkastner/OMAPL137_arm_1_00_00_11/dsplink-1_61_03-prebuilt/packages/dsplink

    is the right one, wich provokes the Link Configuration Utility to tell me the Link was not set ..

    here the versions of the bin-files i used to install the several parts of the SDK:

    bios_setuplinux_5_33_05

    mvl_5_0_0801921_demo_sys_setuplinux.bin

    OMAPL137_arm_setuplinux_1_00_00_11.bin

    ti_cgt_c6000_6.1.9_setup_linux_x86.bin

    xdctools_setuplinux_3_10_05_61.bin

    and  LPTB-02.03.00.02-beta (which i do not have installed yet)

     

    the whole SDK seems a litte strange to me... but unfortunately i see no easier way to get full network-access  (via  tcp - sockets)  for my application that is supposed to run on the dsp ..

     

  • 0 in reply to Rico Schulze
    TI__Mastermind 24340 points

    Hi Rico,

    if the path is correct I'm not sure what could be wrong.

    Can you send me a screen shoot of the perl command, the error message, and a pwd of the DSPLink directory?

    I will move this post to the DSP/bios forum, so maybe someone else has a better idea of what could be the issue.

  • 0 in reply to Mariana
    TI__Mastermind 18260 points

    Just a hunch...is your DSPLINK env variable exported?

    If "% printenv DSPLINK" shows a value, try doing
        % export DSPLINK
    and see how the DSPLink config goes after that.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Intellectual 480 points

    OK..

    I am one step further..

    I performed the perl script with sudo in front, as superuser, to give it Permissions to change Data if it wants to.

    But it seems thet the environmental variable DSPLINK is not set, if you perform something as a superuser

    printenv DSPLINK results in a correct prompt of the variable

    while sudo printenv DSPLINK does not.

    (trying to export the variable as superuser, expecting that superuser should know it then failed unfortunately, the commands export or source are "unknown" in this case)

    running the perl script without super-user-permissions works, telling me the configuration was done successfully.

    The only thing that scares me a little is the following prompt at the end:

    Configuration done successfully!!
    Generating CURRENTCFG.MK file...
    !! Couldn't open file: /home/mkastner/OMAPL137_arm_1_00_00_11/dsplink-1_61_03-prebuilt/packages/dsplink/config/BUILD/CURRENTCFG.MK

    is this file important?

    Sorry for not thinking that sudo could have caused the mistake. 

  • 0 in reply to Rico Schulze
    Intellectual 480 points

    installation works properly, if you switch into a "root-shell"

    where you do not need to type sudo, to perform things with super-user-permissions

    (sudo -i)

    thanks for the help