SYS/BIOS 6.33.07.53 is a GA release of SYS/BIOS
6.33.07.
SYS/BIOS is a real-time operating system that provides
pre-emptive deterministicmultithreading.
The SYS/BIOS releases introduce a completely new SYS/BIOS kernel
and toolset. The SYS/BIOS 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.33.07.53.
Beginning with
6.33.07, all SYS/BIOS M3, M4, and M4F libraries are being generated
using version 5.0.1 (or newer) of the Texas Instruments ARM code
generation tools.
It was discovered that prior to version 5.0.1, the internal intrinsic
used to implement the Hwi_enable(), Hwi_disable(), and Hwi_restore()
SYS/BIOS APIs for the M3, M4, and M4F targets was not treated by the
Compiler as a code-reordering optimization barrier. Consequently, it
was possible for critical section code that appeared between the
Hwi_disable() and Hwi_restore() APIs in the C code to actually find its
way OUTSIDE the interrupt protected region.
After carefully reviewing all of the SYS/BIOS M3 target libraries
shipped in SYS/BIOS version 6.33.06, we found no instances where code
seemingly protected within a Hwi_disable/Hwi_restore bracket actually
fell outside the Hwi_restore() call (nor after a Hwi_enable() call).
Furthermore, we verified that several test cases built using the
BIOS.LibType_Custom build flow also did not exhibit this potentially
disastrous code-reordering behavior.
Nonetheless, we are advising that all user applications and libraries
be built with 5.0.1 or later ARM codegen tools.
In CCSv5, the Help->Check for Updates function searches for
updates to your currently installed versions based on the first two
digits of the compiler version number.
In order to update to ARM v5.0.1 in CCSv5.x, you will have to use
Help->Install New Software to bring up the Available Software
window, then select the “Code Generation Tools Updates” site from the
“Work with:” drop down list. This will show you the latest
versions of all of the compiler tools that are available.
Uncheck “Show only the latest versions of available
software”. Then you will see ARM v5.0.1 under “TI
Compiler Updates”. Select the checkbox for ARM v5.0.1 and
click "Next". Select "Next" on the following page as well.
Accept the license agreement and then click on finish.
The update will download, install and request a restart of
CCSv5.
If you choose not to
upgrade to the 5.0.1 version of Code Generation Tools, you will get
the following warning when building with
SYS/BIOS 6.33.07: Warning:
xdc.cfg.INCOMPATIBLE_TARGET_VERSION: current target
'ti.targets.arm.elf.M3' [1,0,4.9,0,2] is not compatible with targets
used to build the following packages; package ti.sysbios [in
<Install Directory>/packages/ti/sysbios/] was built using
'ti.targets.arm.elf.M3' [1,0,5.0,1]
Defects Fixed in
SYS/BIOS
6.33.07.53 GA (Fixes since SYS/BIOS 6.33.06.50):
ID
Headline
SDOCM00095036 Arm9 Cache_wbAll() missing
return statement
SDOCM00094946
BIOS 6:
intrinsic used in M3 ARM's Hwi_disable()/Hwi_restore() macros is not a
code-reordering optimization barrier
SDOCM00094944
BIOS 6: AMMU module should not autogenerate small page descriptor 1 for
C64T target
SYS/BIOS
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 and to migrate applications from DSP/BIOS
5.x.
The
default directory for SYS/BIOS is changing to match CCSv5.1.0, "C:\ti"
is the new default directory (SDOCM00086138 -- BIOS installer needs to
change its default directory to match CCSv5.1.0)
RTDX
has been removed and is no longer supported.
Only stop mode is supported for Realtime Analysis (RTA).
SYS/BIOS 6.32
For
TI816X devices (ie Netra), GPTimers 3 and 7 have been removed from the
list of usable timers due to anomalous behavior when clocked at 32KHz
resulting in two interrupts for every period when run in continuous
mode.
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
SYS/BIOS
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. 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.
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.
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
SDOCM00082528 Linker command file
inserted regardless of platform selected for C28 examples
SDOCM00074130 ROV should reference kernel
object names versus object addresses
SDOCM00068360 No data displayed in RTA
Exec Graph when attaching to running target
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.