SysLink FAQs

From Texas Instruments Embedded Processors Wiki

Contents 1 Generic questions 1.1 Where do I get SysLink releases? 1.2 What do I get with SysLink, and how do I get started? 1.3 What is the relation between SysLink and IPC software packages 1.4 How does DSP/Link relate to SysLink/IPC packages? 1.5 How to migrate from DSPLink to SysLink? 2 Build questions 2.1 Can I build both HLOS and RTOS sides of SysLink only on a Linux machine? 2.2 Can I build SysLink RTOS side on Windows Machine? 2.3 How do I build SysLink Samples(HLOS/RTOS) for a particular Platform? 2.4 Build warnings/errors! Where do I look?

Generic questions

Where do I get SysLink releases?

• SysLink releases can be downloaded from here

What do I get with SysLink, and how do I get started?

Each SysLink release is available as a full source release including:

• Complete source code for the SysLink product, with associated build system
• Sample applications demonstrating the usage of all modules.
• Release documents: Release Notes, User Guide, Install Guides

To get started with SysLink, you can refer to the release documents mentioned in the release notes in the base of the product. Refer to the SysLink User Guide for high level information. The SysLink API Reference Guide provides details on the APIs, and the samples provided with SysLink demonstrate usage of the APIs.

The SysLink Install Guide provides installation and build instructions, as well as details on running the sample applications.

The Migration Guide gives migration information between DSPLink and SysLink.

What is the relation between SysLink and IPC software packages

SysLink and IPC packages are complementary packages.

• IPC includes the implementation independent headers (e.g. ti/ipc/MessageQ.h), as well as an implementation of that spec for BIOS (e.g ti/sdo/ipc/MessageQ.c)
• SysLink provides Linux-side implementation of the IPC interfaces, as well as additional higher level data transports such as RingIO and FrameQ for both BIOS and HLOS environments. (Note that in a future release, it's likely that FrameQ and RingIO will be moved into a separate product to reduce the scope of core SysLink and allow them to have independent dev cycles).

If you are using Linux on the ARM and BIOS on a slave processor, then both SysLink and IPC packages needs to be used, since SysLink contains the required Linux-side components and IPC contains the BIOS side.

How does DSP/Link relate to SysLink/IPC packages?

Please refer to the following link: http://processors.wiki.ti.com/index.php/SysLink_Overview#How_is_SysLink_different_from_DSPLink

How to migrate from DSPLink to SysLink?

Please refer the SysLink Migration Guide for more information.

Build questions

Can I build both HLOS and RTOS sides of SysLink only on a Linux machine?

Yes! The SysLink make system supports build of both GPP and DSP-side on a Linux machine. In fact, it is advised to use this method when you are using Linux as the HLOS because:

• A single SysLink source base can be maintained for HLOS and RTOS-sides, minimizing any mismatch issues.
• Scripts can be written over basic SysLink make system for doing a single-shot build of both HLOS and RTOS-sides
• An NFS-mounted target file system can be easily used to transfer both generated HLOS and RTOS-side binaries into the target file system.

Can I build SysLink RTOS side on Windows Machine?

Yes! The SysLink RTOS side code, including sample applications, can be built on a windows machine. Details are in the SysLink Install Guide.

How do I build SysLink Samples(HLOS/RTOS) for a particular Platform?

See the SysLink Install Guide.

Build warnings/errors! Where do I look?

Check out the Troubleshooting SysLink Build Issues article. This lists most of the common build failures and their possible causes, and suggests solutions.

Leave a Comment