problems building syslink for DSP on the TI816x

Neil Walker

I am using syslink 02.00.00.66 and am trying to build the syslink examples for the DSP by following the instructions in the installation guide. The build fails while compiling some of the syslink libraries due to differences in function prototypes defined in the generated header files versus selected functions in the corresponding C file. For example, the definition FrameQBufMgr.c of ti_syslink_ipc_rtos_FrameQ in the FrameQBufMgr.C file:

Int32 ti_syslink_ipc_rtos_FRameQBufMgr_translateAddr__F(FrameQBufMgr_Ojbect *obj, Ptr *dstAddr, FrameQBufMgr_AddrType dstAddrType, Ptr srcAddr, FrameQBufMgr_AddrType srcAddrType, FrameQBufMgr_BufType bufType)

differs from the prototype in the generated C file FrameQBufMgr.h:

Int32 ti_syslink_ipc_rtos_FRameQBufMgr_translateAddr__F(ti_syslink_ipc_rtos_FrameQBufMgr_Ojbect *obj, xdc_Ptr *dstAddr, ti_syslink_ipc_rtos_interfaces_IFrameQBufMgr_AddrType dstAddrType, xdc_Ptr srcAddr, ti_syslink_ipc_rtos_interfaces_IFrameQBufMgr_AddrType srcAddrType, ti_syslink_ipc_rtos_interfaces_IFrameQBufMgr_BufType bufType)

and generates a compile error.

over 14 years ago

0 Chris Ring over 14 years ago

TI__Genius 17205 points

Can you post your build log (including the link command)? I think this is a benign error that is typically suppressed using the "--diag_suppress=23000" linker option.

Typically this supress option is added within the build process, so most users don't see it - but if your build is structured differently you may need to throw this flag yourself. This is related to this bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=343468

Chris

0 Neil Walker over 14 years ago in reply to Chris Ring

Intellectual 965 points

Chris:

I'm not sure I know what you mean by the build log. Attached is the stdout/stderr output when I enterred the following command:

xdc all XDCBUILDCFG="$SYSLINK_ROOT/config.bld" -PR .

Neil6431.issue_with_RTOS_syslink_build.zip

0 Chris Ring over 14 years ago in reply to Neil Walker

TI__Genius 17205 points

Ah, that's a little different scenario that I thought - you can ignore what I said about that suppress flag. What version of XDC are you using (and does it match what the SysLink .66 release notes say it was validated against)?

Chris

0 Neil Walker over 14 years ago in reply to Chris Ring

Intellectual 965 points

I am using XDC tools version 3.20.06.81. The syslink 02.00.00.66 release notes has been validated with XDC tools 3.20.05.76 for the TI816X platform. Should I downgrade?

Neil

0 Chris Ring over 14 years ago in reply to Neil Walker

TI__Genius 17205 points

No need to downgrade, those are close enough to be fine. Lemme ask around and see if anyone's seen this before - I haven't.

Chris

0 MUGDHA ARORA over 14 years ago in reply to Chris Ring

Genius 4120 points

Neil,

Have you changed anything in the default build options in config.bld or elsewhere, say adding include path for BIOS build as ti/syslink or something? The build seems to be picking up RingIO.h from ti/syslink/RingIO.h instead of the generated one in ti/syslink/ipc/rtos/RingIO.h.

From your log:

RingIO.c:455: error: conflicting types for 'RingIO_close'
/home/vbrick/ti-ezsdk_dm816x-evm_5_00_00_09/syslink_02_00_00_66/ti/syslink/RingIO.h:726: error: previous declaration of 'RingIO_close' was here

The ti/syslink/RingIO.h is for Linux build, and the ti/syslink/ipc/rtos/RingIO.h is for BIOS build.

Regards,
Mugdha

0 Neil Walker over 14 years ago in reply to MUGDHA ARORA

Intellectual 965 points

Mugdhak:

I decided not to use syslink. Thanks for your help.

Neil

0 AmirthaRaj over 12 years ago in reply to MUGDHA ARORA

Expert 1030 points

Hi MugdhaK,

Could you please help us in creating RingIO.c & RingIO.h files in ti/syslink/ipc/rtos folder as we need this in our project. We followed all steps in building syslink, but these files are not getting generated, instead some library files like RingIO.oea8f etc.,

Thanks & Regards,

K.AmirthaRaj

0 janet over 12 years ago in reply to AmirthaRaj

TI__Mastermind 22760 points

RingIO.c and RingIO.h are actually located in the ti/syslink folder, as these files are used in both the hlos and rtos side builds.

Best regards,

Janet

Processors

Processors forum

problems building syslink for DSP on the TI816x