is there a way to make this work?

Hi Lee,

I add in the Syslink Repository. Hit the Add button and browse for Syslink. See attached 8322.screenshot.doc

Todd

Lee Holeva said:

xdc.PACKAGE_NOT_FOUND: C:\Program Files\Texas Instruments\syslink_02_00_00_56_alpha2\ti\syslink\ipc\rtos\package.xdc found along the package path, but no schema file was found.  Ensure that the package 'ti.syslink.ipc.rtos' is completely built. notifyapp Notify_ti81xx_dsp.cfg line 59 1304526359649 63

You need to build the SysLink RTOS libraries.  The SysLink Install Guide (in the product) describes how to do this.

Lee Holeva said:

This works when building using xdc on the command line.

I can't explain this.  Perhaps you have 2 installations of SysLink (one on your Linux box and another on Windows?) and you only built one of them?  The error clearly indicates the ti.syslink.ipc.rtos package isn't built - so I'm not sure how the same [unbuilt] package  would work when building from the command line.

Chris

ToddMullanix said:

Hi Lee,

I add in the Syslink Repository. Hit the Add button and browse for Syslink. See attached 8322.screenshot.doc

Todd

From where did you get the "syslink-prebuilt" package?  I installed syslink 02.00.00.56_alpha2 as a repository for CCS, to match that included in the EZSDK, from:

http://software-dl.ti.com/dsps/dsps_public_sw/SysLink/index.html

Lee Holeva

Chris Ring said:

You need to build the SysLink RTOS libraries.  The SysLink Install Guide (in the product) describes how to do this.

The install Guide for Syslink 002.00.00.56 alpha2 says nothing about "Syslink rtos libraries".  There is a "hlos user library", but that is for building Linux-side apps.  Now there is instructions for making something at <syslink install dir>/ti/syslink/ipc.  Is this the rtos library?  No mention is made what this is.

Lee Holeva

My SysLink 2.00.00.56_alpha2 release has the install guide in ti/syslink/docs/SysLink_02.00.00.56_alpha2_InstallGuide_Linux_TI81XX.pdf.  That doc has a section titled "Building RTOS SysLink and sample applications".

No argument that this is confusing; the build and docs are areas we're actively cleaning up.

Chris

Here is what I did:

I built the Syslink rtos library in linux and then copied the rtos directory over to the syslink install in Windows for CCS.  The code builds, but it still isn't correct.  Compare the file sizes:

made in the EZSDK: -rw-r--r--    1 root     root      2606855 May  4  2011 notify_ti81xx_dsp.xe674

made by CCS in XP: -rwxr--r--    1 1000     1000      7112054 May  4  2011 notifyapp.out

Both should be in ELF format and the source codes are identical.

And now I have an additional problem with the ProcMgr hanging regardless of the source of the rtos file.  For example, this is as far as I now get with teh notifyapp demo, notify_ti81xx_dsp_xe674 was made by the EZSDK:

./notifyapp.exe 0 notify_ti81xx_dsp.xe674
NotifyApp sample application
Entered NotifyApp_startup
Loading and starting procId [0] with [notify_ti81xx_dsp.xe674]
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x0]
After attach: ProcMgr_getState
    state [0x1]
ProcMgr_load status: [0x3046000]
After load: ProcMgr_getState
    state [0x3]
ProcMgr_start passed [0x6a85000]

Lee Holeva