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.32.04 is a patch release of DSP/BIOS 5.32.
Please read the Setup Guide for help installing and setting
up your environment to use DSP/BIOS 5.32.04.
back to top
The following documentation is provided with this release:
Additional release note documentation:
Release notes from previous releases are also available in the
release notes archive
directory.
back to top
5.32.04.08 Release (this release)
- Id
Headline
- SDSCM00025432
CLK_getprd() API does not work when .ebss section is mapped to off-chip
memory
- SDSCM00026127
BIOS hangs in CLK_enableTimer because PSC not modeled in DM6437 and 6424 CCS
simulator
- SDSCM00026331
MPC module is not included in library for some of the 64x+ targets
- SDSCM00026673
C6421 chip config file has incorrect L1P and L1D cache settings
- SDSCM00026827
TSK_isTSK() and SWI_isSWI() return incorrect value in some cases
- SDSCM00026910
generated .cmd file creates invalid heap _base/_length values if
'bios.MEM.REUSECODESPACE = 1'
- SDSCM00027061
PWRM/3430/3530 load monitor always reports same total cycles per slot
- SDSCM00027068
add evm5505 platform package for 5.32
back to top
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.32 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.
DSP/BIOS 5.32 no longer contains RTDX examples.
DSP/BIOS 5.32 does
continue to provide the RTDX libraries so existing applications using
RTDX will
continue to build and execute without any issues. To obtain RTDX
examples,
users should download the RTDX 2.0 release from:
https://www-a.ti.com/downloads/sds_support/targetcontent/index.html
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 [RH3 and RH4]
back to top
- Required Software
- Code Composer Studio Version 3.3 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 |
|
|
55x |
5501,
5502, 5503, 5505, 5507, 5509, 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, DM6431, DM6433, DM6435, DM6437, DM6441,
DM6443, DM6446, DM6467, 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, TNETV2685
|
|
|
67x |
6701, 6711,
6711 - 250, 6712, 6713, 6713 - 300
|
|
|
67x+ |
6722, 6726, 6727, DA700, DA705, DA707, DA710 |
|
|
back to top
This release was built using the following components:
- C28x Code Generation Tools version 5.0.0B2
- C55x Code Genereation Tools version 3.3.2
- C6x Code Generation Tools version 6.0.14
This release was validated using the following components:
- CCS 3.3
- C28x Code Generation Tools version 5.0.0B2
- C55x Code Genereation Tools version 3.3.2
- C6x Code Generation Tools version 6.0.14
back to top
The following issues are known to affect this release:
Please
check the following link for additional information when
upgrading from 4.90 to 5.x --
Knowledge
base with known 4.90 to 5.x upgrade issues
- Davinci
1.x IDMA0 problem workaround -- A custom version of
the HWI dispatcher was created to work around an IDMA0/MMR
problem in rev 1.x DM644x devices (see SPRZ241 - "TMS320DM6446 Digital
Media System-on-chip Silicon Errata" for more information about this
errata). This errata is only present in Rev 1.x DM644x
devices and is not present on other 64x+ devices.
The
HWI dispatcher has been updated to poll the IDMA0 status register and
wait for IDMA0 transfer to complete before calling the actual
ISR. This will ensure that the ISR will not reference an MMR
register while the IDMA0 is active. This will also ensure
that an asynchronous task switch will not occur while the IDMA0 is
active. This may affect interrupt response time, but should
not be a problem in most applications since IDMA0 jobs are usually
fairly short. This workaround is only supported by the HWI
dispatcher (the
HWI_enter/exit macros do not contain the workaround).
A
hidden configuration parameter (bios.GBL.USEIDMA0DISPATCHER) is used to select
this alternate version of the dispatcher. This parameter has
default value 'true' for DM644x and DM42x configurations.
This parameter has default value 'false' for all other 64x+
configurations. The user can set this parameter to 'false' if
they do not want this workaround used in their Davinci applications
(e.g., if their application is not using IDMA0 and/or they know that
that their ISRs do not reference MMR registers).
-
Memory
heap issue when updating existing configuration files --
Prior versions of the configuration tool allowed for an inconsistent
memory heap configuration. The tool allowed users
to enable heaps when no heaps were actually configured and the default
for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to
'MEM_NULL'. This was causing problems in applications since
malloc() and MEM_alloc() were failing even when user thought they had
configured BIOS for dynamic memory allocation. The
configuration tool is now checking to make sure that configurations
that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set
to a valid heap. Update from existing projects might yield an
error message. The work around is to either remove the
'bios.enableMemoryHeaps(prog);' line from your configuration, or to add
a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO
accordingly. See the
ti/bios/examples/common/evmDM6446_common.tci file (or others) for an
example of how to do this.
- Gconf
uses wrong parameters when more than one pjt is opened and they share
the same .tcf file -- When
more than one CCS project
(.pjt file) share the same .tcf file, and two or more of the projects
are opened in CCS, opening a .tcf from one of the projects will launch
GConf using the DspBiosBuilder builder parameters defined for the most
recently opened project. This may result in incorrect base seed
properties and import file paths in the .tcf file being edited. To
workaround, do not share .tcf files between projects. This is tracked
by SDSCM00003834
- BIOS
RTA has problems
reading data in stop mode for some 64x+ devices
-- Currently,
stop mode reads will only work for DaVinci. This is tracked by
SDSCM00010400
- DSP/BIOS
examples
that are using RTA halt when run every other time on
DSK5510/DSK5509A via XDS560 -- This is tracked by
SDSCM00005820.
- CCS
window closes on
refreshing KOV Window when it receives illegal
values -- KOV will crash if Module Objects have illegal
values. For e.g if a dynamic task has a bad name, KOV will try to print
the illegal name and crash. This is tracked by
SDSCM00006694.
- KOV
window shows wrong names for dynamic objects --
This
is tracked by
SDSCM00007151.
- KOV
displays wrong names for memory sections --
This is tracked by SDSCM00004917.
- Incorrect
platform name in Tconf User's Guide in
"Create New Platform"
section --
The spru0007h.pdf
document contains the correct instructions for creating a new platform
using the Tconf's User's Guide, the help files were not updated to
reflect the same naming convention. This is tracked by SDSCM00003471.
- RTDX
tutorial examples do not all execute as
expected when
run on TCI6482 simulator little endian --
This is tracked by SDSCM00010736.
- RTDX
Hot-Connect does not work for C64P -- This is tracked by
SDSSCM00011954
- DSP/BIOS
RTA Control Panel does not update values correctly when using comma
decimal separator in Windows -- The RTA Control Panel
does not work as expected when using Windows Regional
Settings where ',' is used instead of '.' for the decimal
separator. Only workaround is to use Regional Settings where
'.' is the decimal separator, or use default 1 second update
rate. This is tracked by SDSCM00017755.
- HWI_isHwi()
documentation has
contradictory statement -- In
previous versions of DSP/BIOS, " calling HWI_isHWI() from main()
resulted in TRUE. This is no longer the case;" main() is
identified as part of the TSK context. This is tracked by
SDSCM00020436.
- Some
of the help files in BIOS
5.32 refers to BIOS 5.31 -- This
is tracked by SDSCM00020437.
back to top
back to top
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_32.
Subsequent releases of patch upgrades will be
identified by
the patch number, ex. BIOS 5.32.01 with directory bios_5_32_01.
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: Jul 31, 2008