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 is a point release of DSP/BIOS. DSP/BIOS 5.32 highlights
include:
- TMS320F283xx device support
- RTDX 2.0 support
- Removal of TMS320C54xx
support
Please read the Setup Guide for help installing and setting
up your environment to use DSP/BIOS 5.32.
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.00.01 Release (this release)
- TMS320F283xx device
support: DSP/BIOS now supports the floating point 283xx family
- RTDX 2.0 support:
DSP/BIOS is compatible with the new RTDX 2.0 release that includes
features such as enabling CIO to be used over RTDX and a host scripting
interface to use RTDX for automated product testing. Although the RTDX
2.0 target libraries are included in DSP/BIOS 5.32, to obtain the updated
host-side libraries, documentation, and examples, you must download RTDX
2.0 from: https://www-a.ti.com/downloads/sds_support/targetcontent/index.html
- TMS320C54xx devices
are not supported in this release
- Defects Fixed:
- Id Headline
- SDSCM00001295 Placing .sysdata at address > 0xffff causes CLK initialization/start problem for 28x
- SDSCM00003686 MEM Module API is needed to get starting address of memory segment
- SDSCM00003738 document restrictions about NMI interrupts for 55x BIOS
- SDSCM00003782 Calling TSK_create twice causes causes crash if KOV is open
- SDSCM00009870 psl does not create complete RTSC package
- SDSCM00010183 Document that apps can use, but not return from, NMI with 28x BIOS
- SDSCM00011270 Make LOG timestamp "TS" visible and document "TS" so users can control for LC and Davinci
- SDSCM00012471 RTA (VBD) crash after lots of disconnects and connects
- SDSCM00013497 CLK_start() uses incorrect mask to enable CLK interrupt
- SDSCM00014096 Add BASEADDR config params to documentation (AppNote SPRAA98)
- SDSCM00014100 Incorrect code example for setting wakeup event in SPRAA98
- SDSCM00014120 gconf/tconf do not generate correct files if .tcf file has '+' character (e.g. c64x+test.tcf)
- SDSCM00014176 Memory leak in Project Manager
- SDSCM00015238 Need clarifications to BCACHE API descriptions
- SDSCM00015608 Generated asm file fails to build when the TSK Stack Memory Segment is set to MEM_NULL
- SDSCM00015714
Calling context appendix in BIOS API guide should state that
LCK_pend()/LCKpost() cannot be called from main()
- SDSCM00015944 KOV should check if MSGQ has been initialized before reading MSGQ data structures
- SDSCM00016107 New HWI/WUGEN APIs for 2430/3430 should to be included in API Guide
- SDSCM00016272 Error 1722. There is a problem with this windows installer package
- SDSCM00016821 GIO_new() API description is missing from the BIOS API Manual
- SDSCM00017560 KOV shows incorrect value for stack peak when stackSize > 0x7fff
- SDSCM00017622 remove sectti, nmti, etc. from BIOS documentation (supported by codegen now)
- SDSCM00018091 BIOS 4.90 docs state there is a 28xx Audio example when there is not
- SDSCM00018342 Documentation error in GBL_getFrequency().
- SDSCM00018557 Constraint contradiction with DEV_CreateDevice API and MEM_alloc
- SDSCM00018594 SPRAA98 needs updating with pwrm changes for BIOS 5.31.08 release
- SDSCM00018608 BIOS 5 omap2320 "SELF" interrupt masking option doesn't work for L2 interrupts greater than 31.
- SDSCM00018615 GIO_create() should have constraint warning against sharing handle by multiple threads
- SDSCM00018678 Cannot build BIOS HST with HS-RTDX
- SDSCM00018707 BIOS overwriting pre-scalar value for TIM34 on evm6437
- SDSCM00018808 TSK_getpri() macro should cast the priority field to be volatile
- SDSCM00018913
STS_delta jumps into STS_add (instead of function call) which confuses
function profiler (need hack for trace analyzer)
- SDSCM00019001
RTA objects do not deallocate from the memory segment even if Enable
Real Time Analysis is disabled
- SDSCM00019108 HWI_isHwi() returns "TRUE" when within SWI_disable/enable block
- SDSCM00019333 Add 28FP to BIOS 5
- SDSCM00019360 Remove C55x support from HS-RTDX
- SDSCM00019364 RTDX must support the 283xx
- SDSCM00019365 RTDX libraries must include an RTDX_write callback API
- SDSCM00019366 need catalog files and bios_*.tci files for 283xx parts (335, 334 and 332)
- SDSCM00019400 update codegen to 6.0.14 (or latest 6.0.x) for 6x targets
- SDSCM00019535 BCACHE_setMode needs to be separately placeable for Cache freezing
- SDSCM00019639 GBl_getVersion returns incorrect version number.
- SDSCM00019663 DSP/BIOS clock startup writing to read-only counter registers causes a bus error
- SDSCM00019678 MEM_increaseTableSize documentation has wrong return type
- SDSCM00019860 DSP/BIOS release_notes.html refers to 5.20.00
- SDSCM00019864 need platform file for ezdsp28335
- SDSCM00019996 Edit constraint section of DEV_CreateDevice in API Guide
- SDSCM00020065 Need to document new BIOS API's and config parameter
- SDSCM00020066 TSK_isTSK() API description needs to be updated with BIOS 5.32
- SDSCM00020070 CPU Load Graph is out of synch with MessageLog window on OSK5912
- SDSCM00020217 Description for eZdsp2812 configuration seed file needs correction
- SDSCM00003180 Flash plugin error: BIOS version is not compatible with RTA
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 |
Runtime Model |
|
|
|
28x |
F2801, F2806, F2808, F2810, F2811, F2812, F28335 |
Large model |
|
|
|
55x |
5501,
5502, 5503, 5507, 5509A, DA255, DA295, DA300, 5510,
5510A, 5561, OMAP5903, OMAP5905, OMAP5910, OMAP5912, OMAP5944,
OMAP5946, OMAP5948, OMAP1035, OMAP1510, OMAP1610, OMAP1710
(OMAP), OMAP2320, OMAP2420, TNETV1055 |
Large model on Laijin 2.x core devices |
|
|
|
62x |
6202, 6203, 6204, 6205, 6211
|
Big and Little Endian |
|
|
|
64x |
6410, 6411, 6412, 6413, 6414, 6415, 6416, 6418, DRI300, DM420, DM640, DM641, DM642
|
Big and Little Endian |
|
|
|
64x+ |
DM420, DM415, DM425,
DM426, DM647, DM648, DM6431, DM6433, DM6435, DM6437, DM6443, DM6446,
6421, 6424, 6452, 6454, 6455, TCI6482, TCI6486, TCI6487, TCI6488,
DRA442, DRA446, OMAP2430, OMAP3430, TNETV2685
|
Big and Little Endian |
|
|
|
67x |
6701, 6711, 6711 - 250, 6712, 6713, 6713 - 300
|
Big and Little Endian |
|
|
|
67x+ |
6727, DA705, DA707, DA710 |
Little Endian |
|
|
|
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.0B1
- C55x Code Genereation Tools version 3.3.2
- C6x Code Generation Tools version 6.0.8
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 SDSSCM00010736.
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
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: Oct 02, 2007