SWTOOLS 4.0.0.0 Release Notes
December 18, 2008
Introduction, Documentation, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Known Issues, Version Information, Technical Support.
Introduction
This component contains tools that are shared by other software components during the configuration and build procedures. For example, it contains:
- Perl script support for cygwinxdc.bat files.
- Version.xdt template file that is to be used by all packages to implement the Version interface.
- JavaScript functions that automate creation of ClearCase related files.
- CommonBld module containing common build utilities that can be shared across the packages to avoid duplication.
back to top
Documentation
The following documentation is available:
Release notes from previous releases are also available in the relnotes_archive directory.
back to top
What's New
The following new features were added:
- Commonbld module for common build utilities.
- Archive format changed to ZIP to resolve problem with TAR.
- Common cygwinxdc.bat and config.bld support.
- Automated Release Notes support.
- Modification to labeling script.
- Modified Clearcase Artifacts Generation script for the new XDC tools. The new XDC tools do not generate package.xdc.xml file. For this reason ti.mas.swtools needs to made external dependent package instead of internal.
back to top
Upgrade and Compatibility Information
This ti.mas.swtools version is incompatible with the last released swtools version. To reflect the same the compatibility key has been chnaged from 1.0.4.0 -> 2.0.0.0. This package follows SDO Packaging standard Version 1.0.0.40 which is incompatible with previous version as the Version definition has been changed from V.R.X.P --> M.m.X.P.
Please note that the package compatibility keys are independent of XDC product release numbers.
Package compatibility keys are intended to:
- Enable tooling to identify incompatibilities between components, and
- Convey a level of compatibility between different releases to set end user expectations.
Package compatibility keys are composed of 4 comma-delimited numbers - M, S, R, P - where:
- M = Major - A difference in M indicates a break in compatibility. The package consumer is required to re-write its source code in order to use the package.
- S = Source - A difference in S indicates source compatibility. The package consumer’s source code doesn't require change, but does require a recompile.
- R = Radix - A difference in R indicates an introduction of new features, but compatibility with previous interfaces is not broken. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.
- P = Patch - A difference in P indicates that only bugs have been fixed in the latest package and no new features have been introduced. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.
back to top
Host Support
This release supports the following hosts:
back to top
Dependencies
This release requires the following other software components and tools versions to successfully function
- XDC Tools version 3.10.
- RTSC Packaging Standard version 1.00.00
- XDAIS version 5.21
- C6x Code Generation Tools version 6.0.15.
- C55 Code Generation Tools version 4.0.1.
- C54 Code Generation Tools version 4.10.
back to top
Device Support
This release supports the following device families:
- 64P, C64
- C55
- C54
- Native development host (Windows)
back to top
Validation Information
This release was built and validated against using the following components:
- ti.mas.types
- ti.mas.fract
- ti.mas.util
back to top
Known Issues
- Ccase.js script to generate configspec.clearcase is unable to parse test packages if it is not directly under test folder.
- When creating the mCSPEC file mcspecGen.js will not be able to update the existing maintenance branch information properly. It would always assume a new branch is being created from the current version of the package and would use that new label for the branch origin. One has to manually revert back to the original label for the branch origin in order to prevent problems. The reason for this problem is that the mcspecGen.js was initially written to help in creation of new maintenance branches.
- When creating the iCPSEC file icspecGen.js will look for the VOB name(s) within the label(s) specified for accessing the parent folders of the integrating components. The script has a bug that results in the iCSPEC file which does not remove the VOB name(s) from the label(s) and generates the wrong folder path(s) to be associated with the label(s). Solution is to specify the label(s) the way script wants it and subsequently edit the generated iCSPEC.txt file to substitute away the VOB name(s) from the generated label(s) as well as to fix the wrong path names. An example of a broken path name is /dsps_gtmas/dsps/gtmas/ti/mas. The correct path is /dsps_gtmas/ti/mas. The spurious dsps/gtmas section was inserted by mistake where the script just expanded DEV_DSPS_GTMAS_TI_MAS_<version> label without removing the (capitalized) VOB name.
- When creating the iCPSEC/mCSPEC file icspecGen.js and mcspecGen.js scripts will not find ti/mas/iface/ or similar folders that group multiple components. The script will assume ti/mas is the only folder grouping other components. In order to get other component grouping folders to be properly referenced you will have to paste the ti/mas folder line and substitute the MAS folder name for the corresponding grouping folder, e.g. /dsps_gtmas/ti/mas/iface.
back to top
Version Information
This product's version follows a version format, M.m.x.p, where M is a single digit Major number, m is single digit minor number, x is single digit vertical numbner and p is a single digit patch number
Please note that version numbers and compatibility keys are NOT the same. For an explanation of compatibility keys, please refer to the 'Upgrade and Compatibility Information' section.
back to top
Technical Support
back to top
Copyright 2008, Texas Instruments Incorporated