|
|
|
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.
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:
SYS/BIOS operating system is expected to be running on the slaves with all of these platforms.
The following documentation is available:
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.
The following significant changes have been made since 2.00
| ID | Headline |
| SDOCM00085774 | Setting ProcMgr_map()'s addrInfo.isCached field to TRUE doesn't map the memory as cached |
| ID | Headline |
| SDOCM00085764 | SysLink should enable both GP Timer 3 and 4 for TI816x to support recent BIOS releases |
| SDOCM00085771 | Add explicit dmtimer.Timer frequency assignment to sample config scripts |
| ID | Headline |
| SDOCM00083737 | SysLink dependency on Framework Components' tiler support shouldn't use 'requires' statement |
| SDOCM00084203 | Slaveloader fails on dsp internal memories |
| SDOCM00083906 | Support for systems running BIOS as the GPP OS is broken |
| SDOCM00083695 | Detect when notify is enabled in the kernel and auto-assign USE_SYSLINK_NOTIFY |
| SDOCM00084072 | SysLink crashes Linux kernel when ProcMgr_MAX_MEMORY_REGIONS > 45 |
| SDOCM00083912 | Remove errant use of SharedRegion_DEFAULTOWNERID |
| SDOCM00083615 | Caching of Shared Region (SR1 onwards) does not happen in user space |
| ID | Headline |
| ID | Headline |
| SDOCM00082980 | ProcMgr_load() hangs while loading DSP image on Centaurus PG 2.1 |
| ID | Headline |
| ID | Headline |
| SDOCM00082556 | SysLink Platform_stopCallback is not reference counting before checking that sr0MemorySetup has been cleared by slave |
| SDOCM00082080 | Platform_loadCallback() for OMAP3530 does not check for shared region entry.isValid before zeroing out shared region |
| SDOCM00082703 | ClientNotifyMgr_execCallBackFxn crashes upon receiving notifications to recently unregistered and deleted client |
| ID | Headline |
| SDOCM00082682 | Add separate build goal to build HLOS and RTOS samples separately |
| SDOCM00082640 | Enable users to modify SysLink_params via env var (SL_PARAMS) to avoid a rebuild |
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.
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.
This release supports the following devices:
This release was built and validated against using the following software components:
This release was validated using the following hardware platforms:
Consult the SDOWP database for open issues.
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_00_04_83.
Subsequent releases of patch upgrades will be identified by the patch number, ex. SysLink 2.00.01.XX with directory syslink_2_00_01_XX. Typically, these patches only include critical bug fixes.
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: October 27, 2011