This release note is divided into the following sections:
Introduction,
Documentation,
What's New,
Upgrading And
Compatibility Information,
Host Support,
Dependencies,
Device Support,
Validation Information,
Known Issues,
Benchmarks,
Versioning,
Technical Support
And Product Updates,
DSP/BIOS 5.41.01.09 is
a patch release based on DSP/BIOS 5.41. This release includes
separate installers for CCSv3 and CCSv4. The target content
(libraries and .h files) are identical in both installations. The
main difference is that different tools are provided in each release as
necessary to work with CCSv3 or CCSv4. It is ok to install both CCS versions on the same computer but they must not be installed under same root directory.
The main changes in this release are bug fixes (listed below) and two new examples for PWRM (for evm6748 and evmOMAPL138).
back to top
The following documentation is provided with this release:
Release notes from previous releases are also available in the
release notes archive
directory.
back to top
- Enchanements and Defects Fixed:
id
Headline
SDOCM00062712 single LOG_printf (like hello world example) for BIOS 5.41 does not show ROV/LOG data
SDOCM00062198 BIOS 5 RTA - RTA broken for 6x big endian targets
SDOCM00062126 BIOS 5 ROV & RTA broken on some targets
SDOCM00062300 myplatforms and mycompany removed from 5.33.06 need to add back for 5.41.01
SDOCM00062199
First call to PWRM_setDependency for EMIFA fails; takes very long for
first transition out of power-up SwRstDisable state
SDOCM00062137 PWRM_setDependency may return success code when in reality, a LSPC transition timeout occurred
SDOCM00060215 Add PWRM examples for Freon to BIOS product
back to top
DSP/BIOS is binary compatible with DSP/BIOS 5.33 (and all the way
back to DSP/BIOS 5.21). Users do not need to recompile your source
files or libraries when updating to BIOS 5.41. However users *must*
rebuild their configuration since the generated linker .cmd file
(<prog>cfg.cmd) is different.
Solaris host is no longer supported in this release.
Customer-critical bug
fixes to earlier releases will be available to Solaris users if
required.
DSP/BIOS 5.41 does not support TMS320C54xx devices. Users of
such devices
should continue use DSP/BIOS 5.31.xx earlier releases. For
customer-critical
54xx-related issues, TI will continue to provide fixes to earlier
versions when
needed.
Compatibility Key Definitions
Compatibility keys are intentionally independent of Marketing
product
numbers and are intended to:
- Enable tooling to
identify incompatibilities between components, and
- Convey a level of
compatibility between different releases to set end user expectations.
Compatibility keys are composed of 3 comma-delimited numbers -
M,S,R -
where:
- M = Major.
A difference in M indicates a break in compatibility.
- S = Source.
A difference in S indicates source compability.
That is, the user's source doesn't require change, but does
require rebuilding.
- R = Radix.
A difference in R indicates an introduction of new features, but
compatibility with previous interfaces has not broken. If libraries are
provided by the package, an application must re-link with the new
libraries, but not rebuild from source.
back to top
- Supported Operating Systems
- Windows XP, Windows Vista
- Linux [RH4 and RH5]
back to top
- Required Software
- Code Composer Studio Version 3.3, 4.0 or higher
- Required Hardware
- See Device Support Section below.
back to top
- This release supports the following devices:
|
Device |
|
|
28x |
F2801,
F2806, F2808, F2810, F2811, F2812, F28232,
F28234, F28235, F28332, F28334, F28335, F2802x, F2803x, F2834x |
|
|
55x |
5501,
5502, 5503, 5504, 5505, 5507, 5509A, DA255, DA295,
DA300, 5510,
5510A, 5561, DA255, DA295, DA300, OMAP1035,
OMAP1510, OMAP1610, OMAP1710, OMAP5903, OMAP5905, OMAP5910,
OMAP5912, OMAP5944,
OMAP5946, OMAP5948, OMAP2320, OMAP2420, TNETV1050, TNETV1055 |
|
|
62x |
6202, 6203,
6203B, 6204, 6205, 6211, 6211B |
|
|
64x |
6410, 6411, 6412, 6413, 6414, 6415, 6416, 6418, DM415,
DM420, DM421, DM425, DM426, DM640, DM641, DM642, DRI300 |
|
|
64x+ |
6421,
6424, 6428, 6452, 6454, 6455, 6474, DM6431, DM6433, DM6435, DM6437, DM6441,
DM6443, DM6446, DM6467, DM6467T, DM357, DM647, DM648, TCI6482,
DRA402,
DRA404, DRA406, DRA414, DRA416, DRA442, DRA444,
DRA446,
F761990,
OMAP2420, OMAP2430, OMAP2431, OMAP2530, OMAP2531, OMAP3425, OMAP3430, OMAP3525,
OMAP3530, TCI6482, TCI6484, TCI6486, TCI6487, TCI6488,
TCI6486, TNETV107X, TNETV2685
|
|
|
67x |
6701, 6711,
6711 - 250, 6712, 6713, 6713 - 300
|
|
|
67x+ |
6722, 6726, 6727, DA700, DA705, DA707, DA710 |
|
|
674x | OMAPL137, OMAPL138, DA830, 6747, 6748 |
back to top
This release was built using the following components:
- C28x Code Generation Tools version 5.2.1
- C55x Code Genereation Tools version 3.3.2
- C6x Code Generation Tools version 6.1.14 (except 674x)
- C674x Code Generation Tools version 6.1.5
This release was validated using the following components:
- CCS3.3 and CCSv4
- C28x Code Generation Tools version 5.2.1
- C55x Code Genereation Tools version 4.2.2
- C6x Code Generation Tools version 6.1.9
back to top
The following issues are known to affect this release:
- The
new Power Manager (PWRM module) for C6748 devices optionally uses two
packages (PMI and PSCL) for implementing low-level power control
functionality. When the PWRM module is enabled in your DSP/BIOS
configuration, it will attempt to link to the libraries in these
packages. This requires that the paths to the PMI and PSCL
libraries be included in the linker search path. These paths are
included by default in the CCSv3 project files for the DSP/BIOS
examples for
the evm6748 and evmOMAPL138 platforms. If you are creating your
own CCSv3 project files you should similarly include the following
paths
for the linker: -i"%BIOS_INSTALL_DIR%/packages/ti/pscl/lib"
-i"%BIOS_INSTALL_DIR%/packages/ti/pmi/lib". CCSv4 projects using
PWRM will also require the user to add the libraries to the linker
search path.
- The
default V/F setpoints for PWRM are not included in the documentation.
The following table represents the default V/F setpoints.
For the evm6748 and evmOMAPL138 platforms, the default setpoints supported by the default scaling configuration libraries are:
For the CPU domain (PLL0):
Setpoint SYSCLK1(MHz) Voltage(volts)
--------
------------
--------------
2
300
1.2
1
200
1.1
0
100
1.0
For the PER domain (PLL1):
Setpoint SYSCLK1(MHz) Voltage(volts)
--------
--------------
--------------
1
300
1.1
0
264
1.1
SDOCM00062971
BIOS 5.41.01 PWRM sleep6x and vfscale6x examples for
evm6748/evmOMAPL138 requires user to add libraries to project manually
SDOCM00058656 BIOS 5 ROV - LOG view should use RTA decoder
SDOCM00058389 Stairstep RTA example does not run correctly for simulator
SDOCM00058088 BIOS 5 RTA - Primus simulator requires reset in between loads
SDOCM00058087 BIOS 5 RTA - On primus simulator, fails if RTA already open
SDOCM00057506 BIOS 5 RTA control panel should separate STS and CPU Load
SDOCM00057326 BIOS 5 RTA - Support LOG_printf4
SDOCM00056732 BIOS 5 RTA - CPU Load broken on 55x simulator
SDOCM00056731 BIOS 5 RTA - Over XDS560, RTDX fails if RTA is open when program loaded
SDOCM00056730 BIOS 5 RTA Over USB or 510USB, RTDX fails after 2nd time program is loaded
SDOCM00054997 RTA stops streaming for the stairstep example on 64P targets when program reloaded
back to top
back to top
All
releases have 4 digits (M.mm.pp.bb). This includes GA and
pre-releases (engineering, EA, beta, etc.). Pre-releases are denoted with
a suffix (e.g. 5.41.00.17_eng or 5.41.00.17_beta).
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. bios_5_41_00_17.
Subsequent
releases of patch upgrades will be identified by the patch number, ex. BIOS 5.41.01.18 with directory bios_5_41_01_18. Typically, these patches
only include critical bug fixes.
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 And Product Updates
- Please contact softwaresupport@ti.com for
technical
support.
back to top
Last updated: October 21, 2009