SysLink 2.10.03.20 Release Notes

February 2012

This SysLink Release is targeted to SYS/BIOS 6-based platforms.

Introduction, Documentation, What's New, Upgrade Info, Compatibility Information, Device Support, Validation Info, Known Issues, Examples, Version Information, Technical Support.

---

Introduction

SysLink is runtime software that simplifies the development of embedded applications in which either General-Purpose microprocessors (GPP) or DSPs communicate with each other. The SysLink product provides software connectivity between multiple processors. Each processor may run either an HLOS (e.g. Linux) or an RTOS (e.g. SYS/BIOS). In addition, a processor may also be designated as the master for another slave processor, and may be responsible for controlling the slave processor's execution (including boot-loading the slave).

The SysLink product provides the following services to frameworks and applications:

• Processor Manager
• Inter-Processor Communication
• Utility modules

SYS/BIOS operating system is expected to be running on the slaves with all of these platforms.

---

Documentation

The following documentation is available:

• SysLink Users' Guide
• SysLink Install Guide
• SysLink Application Programming Interface (API) Reference Guide (HTML | CHM)
• Package Reference Guide - includes configuration details
• SysLink Migration Guide

In addition, users are encouraged to monitor (and contribute to!) the TI Embedded Processors Wiki.

Release notes from previous releases are also available in the relnotes_archive directory.

---

What's New

The following significant changes have been made since 2.00

2.10.03.20

• New features
  • Added support for Linux on TI813X devices


• The following defects were resolved:

  ID	Headline
  SDOCM00089428	FrameQ_open sometimes hangs in QNX when FrameQ is created on a slave
  SDOCM00088650	Loader raises assert with non-BIOS DSP executable
  SDOCM00088804	RingIO_delete calls Memory_free with the wrong size if RingIO is not empty



• The following enhancements were resolved:

  ID	Headline
  SDOCM00088470	Add TI813X support
  SDOCM00088431	Dynamic memory allocation of temporary variables during SysLink IOCTL calls can create performance issues
  SDOCM00088694	Timeout values needed in Platform_startCallback

2.10.02.17

• The following defects were resolved:

  ID	Headline
  SDOCM00088120	[Ipc] Ipc_control(Ipc_CONTROLCMD_STOPCALLBACK) unmaps SRs from all slaves, even others used by the app
  SDOCM00088314	Null pointer dereference in GateMP_destroy
  SDOCM00087263	Resource leak in ClockOpts on QNX
  SDOCM00087513	Program args for executable crashes SysLink driver on QNX
  SDOCM00087359	HeapBufMP example fails on QNX after several runs
  SDOCM00088050	Resolve compile warning (UInt16 assigned to enum) when TILER enabled



• The following enhancements were resolved:

  ID	Headline
  SDOCM00088123	[ProcMgr] Introduce ProcMgr_maxMemoryRegions(), and remove ProcMgr_MAX_MEMORY_REGIONS from user mode

2.10.01.15

• The following defects were resolved:

  ID	Headline
  SDOCM00087262	VPSS crashes in second sample on QNX
  SDOCM00087115	Mutiple SysLink_setup/destroy calls cause error in NotifyDrv_detach
  SDOCM00087113	SysLink ProcMgr ioctl() calls can crash Linux kernel when ProcMgr_MAX_MEMORY_REGIONS is increased past a certain amou
  SDOCM00086846	Incorrect use of SharedRegion_INVALIDREGIONID as processor id
  SDOCM00087110	Though dual BSD/GPL licensed, some SysLink headers errantly contain GPL-only copyrights



• The following enhancements were resolved:

  ID	Headline
  SDOCM00087221	Increase default ProcMgr_MAX_MEMORY_REGIONS to 96

2.10.00.12

• New features
  • Added initial support for QNX and Android on TI814X devices


• The following defects were resolved:

  ID	Headline
  SDOCM00084067	SysLink crashes Linux kernel when ProcMgr_MAX_MEMORY_REGIONS > 45
  SDOCM00086179	Kernel side MessageQ_get function must break when status is E_FAIL
  SDOCM00080606	[RingIO] RingIO_registerNotifier should return error when a function has already been registered previously
  SDOCM00083784	Detect when notify is enabled in the kernel and auto-assign USE_SYSLINK_NOTIFY
  SDOCM00076425	[RingIO] RingIO_close() returns success even if handle passed is NULL
  SDOCM00079441	[Samples] ringIO_gpp sample application hangs in Ipc_attach()
  SDOCM00083749	ListMP_empty is not returning correct value
  SDOCM00080114	[RingIO] Invalid gate delete assertion observed in RingIO delete
  SDOCM00076871	[RingIO] Application crash is observed when RingIO instance is tried to open twice with same name in HLOS side.
  SDOCM00080378	[RingIO] RingIOShm_delete() is closing and deleting the same clientNotifyMgrGate
  SDOCM00084089	Caching of Shared Region (SR1 onwards) does not happen in user space
  SDOCM00075737	ProcMgr ELF loader does not support argc/argv loading
  SDOCM00084478	[FrameQ] FrameQ fails to initialize 'isRegistered' field for writer during FrameQ creation.
  SDOCM00082706	ClientNotifyMgr_execCallBackFxn crashes upon receiving notifications to recently unregistered and deleted client
  SDOCM00081803	Slaveloader fails on dsp internal memories
  SDOCM00085776	Setting ProcMgr_map()'s addrInfo.isCached field to TRUE doesn't map the memory as cached
  SDOCM00084014	ProcMgr_load() hangs while loading DSP image on TI814X PG 2.1
  SDOCM00068875	[RingIO] RingIO create [RingIO_create() API] crashes if shared region is not set [SharedRegion_setEntry() API] on ARM
  SDOCM00081563	[RingIO] RingIO error codes and RingIOShm error codes are not matching



• The following enhancements were resolved:

  ID	Headline
  SDOCM00084285	Add Android support to SysLink on TI814x
  SDOCM00082644	Enable users to modify SysLink_params via env var (SL_PARAMS) to avoid a rebuild
  SDOCM00085767	SysLink should enable both GP Timer 3 and 4 for TI816x to support recent BIOS releases
  SDOCM00081847	[RingIO] RingIO needs to support non-zero shared regions
  SDOCM00085773	Add explicit dmtimer.Timer frequency assignment to sample config scripts

2.00.00.78

• See the SysLink Migration Guide for new features in this initial SysLink release

---

Upgrade Information

This SysLink release is not suitable for BIOS 5-based DVSDKs. DVSDK users should continue to use the BIOS 5-based DSP Link 1.x releases.

The SysLink packages are available in the "packages/" subdirectory of the product. If you have a previous release of the SysLink product, you can install this release next to it, and modify your build scripts/makefiles to use this newer release.

Compatibility Breaks!

• SysLink 2.10.03.20 requires system integrators to update the following dependencies:
  • XDC Tools 3.23.01.43 (or compatible)
  • SYS/BIOS 6.33.02.31 (or compatible)
• The RTOS (BIOS) FrameQ library was reimplemented in Classic C, and FrameQ users may require some changes. See this article for more details.
• The ProcMgr_ProcInfo struct was modified (affecting users of the ProcMgr_getProcInfo() function. Also, a new ProcMgr_getMaxMemoryRegions() API was introduced. See this article for more details.

Note, if you're upgrading from a release earlier than SysLink 2.00, be sure to review the Upgrade section for each of the releases between your current release and this one. Previous release notes are available in the relnotes_archive directory.

---

Device Support

This release supports the following devices:

• OMAP3530 EVM:
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP)
• OMAP-L138 EVM:
  • multiprocessor configuration, running Linux (ARM 9) and SYS/BIOS (DSP)
• TI816X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
• TI814X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running QNX (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running Android (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running SYS/BIOS on all cores (A8, DSP, VPSS-M3, VIDEO-M3)
• TI813X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)

---

Validation

This release was built and validated against using the following software components:

• XDCtools 3.23.01.43
• SYS/BIOS 6.33.02.31
• IPC 1.24.02.27
• TI816X PSP 04.04.00.01.patch1
• TI814X PSP 04.04.00.01.patch1
• TI813X PSP 04.04.00.01.patch1
• OMAP3 PSP 03.00.00.05
• OMAP-L138 PSP 03.21.00.04
• toolchains:
  • Linux GCC - CodeSourcery 2009q1-203
  • ti.targets.arm.elf.A8F - 4.9.0
  • ti.targets.arm.elf.M3 - 4.9.0
  • ti.targets.elf.C64P - 7.2.2
  • ti.targets.C64P - 7.0.0
  • ti.targets.elf.C674 - 7.2.2
  • ti.targets.C674 - 7.0.0

This release was validated using the following hardware platforms:

• OMAP3530 EVM:
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP)
• OMAP-L138 EVM:
  • multiprocessor configuration, running Linux (ARM 9) and SYS/BIOS (DSP)
• TI816X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
• TI814X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running QNX (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running Android (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)
  • multiprocessor configuration, running SYS/BIOS on all cores (A8, DSP, VPSS-M3, VIDEO-M3)
• TI813X EVM
  • multiprocessor configuration, running Linux (A8) and SYS/BIOS (DSP, VPSS-M3, VIDEO-M3)

---

Known Issues

Consult the SDOWP database for open issues.

• The QNX release samples fail when using dynamic libraries.
• Kernel mode example apps are deprecated and not supported in this release. They are planned to be removed in a future release.

---

Version Information

This product's version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.

To support multiple side-by-side installations of the product, the product version is encoded in the top level directory, ex. syslink_2_10_03_20.

Subsequent releases of patch upgrades will be identified by the patch number, ex. SysLink 2.10.01.XX with directory syslink_2_10_01_XX. Typically, these patches only include critical bug fixes.

---

Technical Support

For technical support, contact softwaresupport@ti.com

Check the following web site for updates: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/syslink/index.html

---

Last updated: February 16, 2012