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

does SYSLINK must be include in SYS/BIOS project for DM8148.

Biao Yang
Intellectual 480 points

I am working on a CCS 5.4 project with SYS/BIOS 6.35 / DM8148/ win7

In the DSP.CFG file, there's a line :

xdc.useModule('ti.syslink.ipc.rtos.syslink'); 

this line  was comment out when I use xds200 to debug the program, on window

But when I use slave-loader to load the elf out put  file to run on DSP,  dsp core  hang's.

I found out that when I uncomment  thits line above in DSP.CFG file and rebuild the project in linux with EZSDK,

it can be load and run correctly.

I didn't use any sys link function  in my program, but I am not sure about SYS/BIOS.

So, is SYSLINK module must be include in my project? And where to find the windows version of SYSLINK?

  • 0
    TI__Genius 12025 points

    Biao,

    Yes, you must include the following line in your DSP configuration file if you are using slaveloader to load and run your program.

    xdc.useModule('ti.syslink.ipc.rtos.Syslink');

    Even if your application does not use any SysLink or IPC libraries, slaveloader is looking for symbols in your DSP executable which are generated by the Syslink module above.

    It sounds like you are using the EZSDK product. The EZSDK uses SysLink and IPC to implement its higher level API libraries. So, even if your program does not use them directly, they are being used indirectly by the EZSDK.

    You can download the latest EZSDK release here: EZSDK 5.05.02.00

    The EZSDK Software BOM and Feature List might also be helpful.

    I don't understand your question regarding the 'Windows version of SysLink'. The SysLink libraries are included in the syslink_2_20_02_20 folder. Look for this in your EZSDK components folder. Maybe you have your EZSDK installed on a Linux machine? And your are trying to build your DSP program on Windows? If so, your Windows machine must have access to the SysLink folder. You can either mount your Linux file system onto your Windows machine or copy the EZSDK. But it sounds like you already solved this issue because you have it working. I must not be understanding your question.

    ~Ramsey

  • 0 in reply to Ramsey
    Intellectual 480 points

    Thanks Ramsey. You answer is very helpful, and I know what to do now. 

    My question is just as what you say : I am building my project in window for a easy ENV to debug.

    (the XDS200 perform badly in my Ubuntu 12.10  :( ,  but work well in win7  ).

    Thanks again!