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,
SYS/BIOS 6.32.01.38 is a release of SYS/BIOS
6.32.00.
SYS/ BIOS is a real-time operating system that provides
pre-emptive deterministic multithreading.
The SYS/BIOS 6.x releases introduce a completely new SYS/BIOS kernel
and toolset. The SYS/BIOS 6.x releases include numerous major
enhancements, including completely new kernel APIs. They also include
compatibility layers and tooling to facilitate easy porting of
applications
developed on DSP/BIOS 5.x releases.
A number of
tools and libraries that were provided as an
integrated part of DSP/BIOS 5.x releases must now be downloaded
separately to
obtain a functional solution. It is essential for even experienced
DSP/BIOS
users to refer to the Getting Started
Guide and to the Upgrading and Compatibility Information
section for
further details.
Please read the Getting Started Guide for help installing and setting
up your environment to use SYS/BIOS 6.32.01.38.
back to top
The following documentation is provided with this release. These
documents are also available via teh CCS Eclipse help table of
contents.
License and manifest.
Additional online sources of documentation.
Release notes from previous releases are also available in the
release notes archive
directory.
back to top
SYS/BIOS 6.32.01.38
Release (this release).
- Project wizard improvements for 28x (generic platform and linker .cmd files).
- More graphical configuration tool improvements.
- Updates to custom build flow.
- Bug fixes (see list below).
Defects Fixed in SYS/BIOS 6.32.01.38 (Fixes since SYS/BIOS 6.32.00.28):
ID
Headline
SDOCM00081682 gptimer: Timer_setPeriodMicroSecs is slightly off calculating TLDR value based on desired clock period
SDOCM00081681
(Parent) dmtimer: Timer_setPeriodMicroSecs is slightly off calculating
TLDR value based on desired clock period
SDOCM00081645 put 28x interrupt vectors in const/FLASH and copy to 0xd00 at runtime to allow easy FLASH boot
SDOCM00081609 update rtdx to use .text:rtdx_text and .ebss:rtdx_data (for 28x) (or .far:rtdx_data for 6x)
SDOCM00081580 BIOS 6 examples build but do not run for 28x devices with external memory
SDOCM00081549 BIOS HeapBuf and Mailbox to use Hwi_disable/restore rather than Gate_enterSystem/Gate_leaveSystem.
SDOCM00081404 update BIOS and IPC custom builds to avoid "unused variable i" (etc) warnings
SDOCM00081403
(Child) dmtimer: Timer_setPeriodMicroSecs is slightly off calculating
TLDR value based on desired clock period
SDOCM00081264
update BIOS.xs to allow BIOS profile to be "release" whill allowing
other content to still use "whole_program" profile
SDOCM00081221 MSP430 - Change the default clock source when a timer is dedicated for timestamping to be ACLK
SDOCM00081201 Comment out the blinking of the LED in the MSP430-specific examples
SDOCM00081200 MSP430 interrupt stubs should call Hwi begin/end hooks before/after logging of LM_begin/LD_end
SDOCM00081017 Create separate configuation and build chapter in user guide
SDOCM00081012 2806x support is missing from BIOS 6.x conversion package
SDOCM00081010 Setting Power.idle to false for MSP430 causes build failure
SDOCM00080920 Problems rebuilding sysbios after installation
SDOCM00080890 (Child) configuring FatFS for no ramdisk causes warning
SDOCM00080854 BIOS 6: Heap manager module gates should be the same as gate BIOS uses for rts lock
SDOCM00080833 Provide an MSP430 Hwi-module config that globally turns on Hwi logging for all interrupts
SDOCM00080794 Should inline Hwi_enable(), Hwi_disable() and Hwi_restore() for MSP430
SDOCM00080782
fat filesystem utils
(bios_6_31_00_18\packages\ti\sysbios\fatfs\utils\bin) are not supported
on the windows platform
SDOCM00080746 update Agent.xdc to use 'Ptr' instead of Stream_Handle to break hard dependency on Stream.
SDOCM00080744 custom build option needs to display the sub-options in Grace view w/o needing the refresh step
SDOCM00080700 Group MSP and Stellaris devices in delegate HTML table
SDOCM00080673 Should ship a barebones SYS/BIOS example that will build for all supported MSP430 devices
SDOCM00080671 c28x .taskStackSection should be renamed as a subsection of a compiler section.
SDOCM00080665 add validation to the build flow to make sure config parameters make sense for inst/non-inst libraries
SDOCM00080614 Clock-tick related fields in ROV can show stale data when doing dynamic tick suppression
SDOCM00080609 review 28x Boot module and include BIOS/ Grace "Device Support" page for 28x
SDOCM00080464 optimize Hwi enter/exit stubs for MSP430 to use single function or file level optimization
SDOCM00079912 For MemoryProtection module, UMC_P0_BADDR is incorrect for DM647/8 device
SDOCM00079697 genx examples need to be fix to not get the GateMutex badContext assert
SDOCM00078956 BIOS 6: Verify 28x Generic Platform
SDOCM00078950 BIOS 6: Prepare Stellaris specific BIOS wiki page
SDOCM00078887 MSP430/Hwi module should warn if Log statements are enabled, but Diags bits are set to always off
SDOCM00078675 Load's ROV view needs enhancing (wrt Task and Swi)
SDOCM00071672
28x should be supported with generic platform similar to MSP430 (BIOS
side of bugzilla Bug 317539)
back to top
SYS/BIOS 6.x releases have many significant changes from
DSP/BIOS 5.x. It is important to understand the information
below in order to
successfully use SYS/BIOS 6.x and to migrate applications from DSP/BIOS
5.x.
SYS/BIOS software downloads
SYS/BIOS 6.32
- We
are planning to remove support for the whole_program and
whole_program_debug profiles because of build time problems and
compatibility problems when using different compiler
versions. SYS/BIOS 6.32 will output a warning message when
the whole_program or whole_program_debug profiles are used.
We are now providing pre-built libraries which can be selected via the
BIOS.libType configuration parameter (see section 7.6.1 of the BIOS
User's Guide for details). The instrumented
library contains Assert() and Log statements. The
non-instrumented library does not. The custom library can
be used to build a custom BIOS library which will be built using
#define constants reflecting some of the key configuration parameters
from your application .cfg file. The non-instrumented
library and custom library should give you similar or better
performance
to SYS/BIOS 6.31 using the whole_program profile.
- .taskStackSection
has been renamed – The .taskStackSection linker section has been
renamed to be a subsection of .far, .bss, or .ebss as appropriate for
the given target. This allows BIOS to be used with CCS-supplied
linker .cmd files for the MSP430, Stellaris and 28x devices. This
section is used to place the stacks for tasks created at configuration
time. The new name is provided in the
Task.defaultStackSection field in your configuration. If you
reference ‘.taskStackSection’ in your .cfg file, you should change the
code to use Task.defaultStackSection.
SYS/BIOS 6.31- Added
an assert to GateMutex. GateMutex_enter() calls
BIOS_getThreadType() to validate the calling context.
GateMutex_enter() will raise an assert if called from Hwi or Swi
context. GateMutex internally calls Semaphore_pend/post to
provide the mutex. Semaphore_pend() cannot be called from Swi or
Hwi context if the semaphore is not available. Note that a
GateMutex gate is registered with the TI compiler’s RTS library to make
the RTS library reentrant. Calling printf() and a few other
RTS functions from Swi or Hwi context will yield this
assert.
- This assert check will catch bad code
that could cause a rare crash. While not recommended, this assert
can be disabled by adding ‘GateMutex.common$.diags_ASSERT =
Diags.ALWAYS_OFF;’ to your .cfg file.
- Text footprint on the C6x
increased by 2K due to Exception.enablePrint default now being set to
‘true’ by default. This enables better diagnostic output when an
exception occurs. You can set this config parameter to ‘false’ to
save memory and get a shorter, less informative diagnostic string.
- MMU and Cache are now enabled by default for Arm9.
- Arm9 applications will have larger data/text footprint due to the 16kbyte MMU table and MMU initialization code.
- Moved
ti.sysbios.arm.Cache module to ti.sysbios.arm.arm9.Cache since this
module is Arm9-specific. .cfg scripts will have to be updated to
use new name (‘ti.sysbios.family.arm.arm9.Cache’) and .c files will
have to change to use ‘#include <ti/sysbios/arm/arm9/Cache.h>’.
- Use
BIOS_exit() rather than System_exit() if called from ISR or Swi context
to avoid Assert() in GateMutex module. BIOS_exit() and
System_exit() both flush the SysMin trace buffer using CIO. The
CIO library is protected by GateMutex.
DA830
ROM
- BIOS 6.30 and 6.31 cannot be used with the
DA830 ROM. BIOS 6.21 is the preferred version for DA830 ROM.
The
'ti.sdo.io' and 'ti.sdo.utils' packages are no longer provided with
SYS/BIOS
- These packages are now provided in a
separate
"IPC" product. Users of these packages simply need to add
this
other product directory to their package path (XDCPATH) to build their
applications.
The ti.sysbios.ipc package and its modules have been deprecated
- The
Semaphore, Event, and Mailbox modules were moved from the
ti.sysbios.ipc package into the ti.sysbios.knl package. Please update
your applications to use the ti.sysbios.knl package versions of the
Semaphore, Event, and Mailbox modules. Using the ipc package versions
of these modules will result in build warnings. In a subsequent release
of BIOS, using any module within the ipc package will result in a build
error.
The ti.sysbios.family.arm.m3.Exception module has been deprecated
- The
ti.sysbios.family.arm.m3.Exception module functionality has been
enhanced and merged into the ti.sysbios.family.arm.m3.Hwi module.
Please update your applications to use the ti.sysbios.family.arm.m3.Hwi
module to configure exception handling. By default, exceptions will be
reported to CIO with an Error message. Details of the exception can be
seen using Hwi module's "Exception" ROV view. At the expense of
additonal code size, some of this detailed information can ALSO be
routed to the CIO console by setting the Hwi.enableException
configuration flag to true.
Placing of sections using MEM configs is no longer supported (ie MEM.TEXTSEG is unsupported)
- All
of the legacy MEM memory segment placment functionality has been
removed. Legacy BIOS users must use Program.sectMap to place memory
sections.
The ti.sysbios.family.c64p.Cache.initSize configuration item is no longer supported
- The
ti.sysbios.family.c64p.Cache module no longer supports setting the
Cache sizes. These settings are now managed within a platform and can
be configured using the platform wizard.
SYS/BIOS no
longer
contains all the tools and objects you will need
- The XDC tools now provide the
SYS/BIOS configuration tools and Platform support.
XDC also includes a minimal run-time environment that provides the LOG,
System,
Asserts, Error handling, Timestamp, and Memory Allocation APIs that
will be
used by SYS/BIOS applications. Please refer to the Getting Started Guide on where to
download the XDC tools and
run-time.
Migrating DSP/BIOS
5.x applications to SYS/BIOS 6.x
- SYS/BIOS 6.x has different APIs
compared to those in
DSP/BIOS 5.x. Configuration scripts are also incompatible between the
two
releases. To provide easy migration of DSP/BIOS 5.x
applications, an API
compatibility layer is provided along with a conversion tool that
converts
configuration scripts to work with XDC and SYS/BIOS 6.x. The
API compatibility
layer provides 100% C source code compatibility with the exception of a
few
APIs that are no longer supported. For more complete details
of migrating
DSP/BIOS 5.x applications and configuration scripts, please refer
to Migrating
a DSP/BIOS 5 Application to SYS/BIOS 6.
- As mentioned
above, some APIs previously supported in
DSP/BIOS 5.x releases will no longer be supported in this release or
the
compatibility layer. Complete details are provided in the
Migration document referenced
above.
back to top
- Supported Operating Systems
- Windows 7, Windows XP, Windows Vista
- Linux [RH4], Ubuntu [10.1]
back to top
- Required
Software
- Code Composer Studio
v4.2.4, Code Composer Studio v5.0, Code Composer Studio v5.1 or later
- Code Generation
Tools
- C28X version 6.0.1 or later
- C6X
version 7.2.3 or later
- ARM version
4.9.0 or later
- MSP430 version
3.3.3 or later
- XDCtools
3.22.01.21 or later
- IPC 1.23.01.25 or later
- Required
Hardware
- See Device Support
Section below.
back to top
Click here
for the list of supported devices.
back to top
Click here
for the list of compilers used to build and validate this release (scroll down to Supported Targets section).
back to top
The following issues are known to affect this release:
- If
this version of SYS/BIOS is installed on the same system
as SYS/BIOS 6.31.00.xx or older, and use the same version of
CCS, the user may see two "SYS/BIOS" folders in the examples when
creating a new project. The Eclipse plugins were updated to
fix this in SYS/BIOS 6.31.01.19 and later. To work around this
issue remove all versions of SYS/BIOS older than 6.31.01.19.
ID
Headline
SDOCM00081912 BIOS needs to support Flash boot on Concerto
SDOCM00081684 DM8168: Timer0 interrupts at twice expected frequency
SDOCM00074130 ROV should reference kernel object names versus object addresses
SDOCM00069043
BIOS 6.x must support Concerto (dual-core M3/28x) including changes to
timestamp. Work is mostly complete on this but complete
validation is still in progress. There will be a 6.32.02 patch release in
mid-July after validation on Concerto hardware has been completed.
SDOCM00068360 No data displayed in RTA Exec Graph when attaching to running target
SDOCM00064397 RTA crashes CCS 4.1 after a few reset/reload with USB emulator
back to top
For a full description of Benchmarks please see the
appendices in the SYS/BIOS
6 User's
Guide.
back to top
All releases have 4 digits (M.mm.pp.bb).
This includes GA and pre-releases (engineering, alpha/EA, beta, etc.).
Pre-releases are denoted with a suffix (e.g. 6.30.00.00-eng or
6.30.00.10-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 (e.g. bios_6_30_00_00).
Subsequent
releases of patch upgrades will be identified by the patch number, ex.
SYS/BIOS 6.30.01.15 with directory bios_6_30_01_15. 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
back to top
Last updated: June 16, 2011 Build Ver: 6.32.01.38 Rev: h38
