TI-RTOS 2.11.01.09
Release
Notes
This release note is divided into the following sections:
Introduction,
Documentation,
Products Included,
What's New, Upgrade &
Compatibility
Information, Host
Support, Dependencies,
Target and Compiler Support,
Validation Info, Known Issues, Examples, Version
Information, Technical
Support.
This
is an General Availability release of TI-RTOS. This version of
TI-RTOS is focused at CC26xx support. It is intended
for selected customers that are supported by FAEs. This release is not
intended
for CC3200 users. It requires CCS 6.0 or IAR 7.30.1 + CC26xx
Patch or later.
The TI-RTOS delivers
components
that enable engineers to develop applications on Texas Instruments
micro-controller devices. The product is comprised of multiple
software
components and examples of how to use these components together.
The TI-RTOS gives developers a one-stop RTOS solution for developing
applications for TI embedded microcontrollers. It provides an OS
kernel, communications support, drivers, and more. It is tightly
integrated with TIs Code Composer Studio development environment. In
addition, examples are provided to demonstrate the use of each
functional area and each supported device and as a starting point for
your own projects.
This release note covers all the TI-RTOS products:
| Product |
Kernel
(SYS/BIOS) |
Instrumentation
power enhancements(UIA) |
Wired
Networking (NDK) |
Wireless
Networking
(via CC3000) |
IPC |
Drivers
(refer to the product's Getting Started Guide for more details) |
*Ware |
| TI-RTOS
for SimpleLink™ Wireless MCUs |
Included |
Included |
Not
included |
Not
Included |
Not
included |
Included |
Included
(cc3200-sdk and cc26xx driverlibs) |
The
following documentation is available:
Please note,
there are TBD's in the Getting Started Guide and User Guide. This will
be addressed in the next release.
Release
notes from previous releases are also available in the
release notes archive
directory.
The following is a list of all the products bundled into the TI-RTOS
installation (with exceptions as noted).
- bios_6_41_02_41
- uia_2_00_02_39
- xdctools_3_30_06_67* (included only in stand-alone installer. It is not
include via an App Center download)
- CC3200_driverlib_1.0.2
- cc26xxware_2_20_06_14829
(Default) & cc26xxware_2_00_06_14829
- CC2650DK
- CC2650STK-BLE
(SensorTag)
* XDCtools is installed at the same level at TI-RTOS. If the xdctools_3_30_06_67
version is already present at that location, that version is
used.
2.11.01.09
Please refer to the Getting
Started
Guide and/or User
Guide for more detail about the following new features.
- New TI-RTOS Kernel and CC26xx Driverlib versions
- Smaller IAR code footprint
- CC26xx Driverlib defaults to use cc26xxware_2_20_06_14829.
- Updates to CC2650 SensorTag
- Enhancements to the CC26xx drivers
- Power enhancements
- Bug fixes
Defects Fixed since
2.11.00.07
| ID |
Headline |
| SDOCM00114453 |
spi loopback timeout regression test fails for CC2650 |
- This
release is API compatible with 2.11.00.07.
- Existing
projects must point to the new CC26xx Driverlib (i.e. include path
and libraries) and be rebuilt.
- The size of the customer
configuration structure (__ccfg found in ccfg.c by default) has changed
by one
word. If you are using a custom version of this structure, you will
need
to review and update your structure to be consistent with the new
structure
defined in cc26xxware_2_20_06_14829.
To migrate
existing applications using TI-RTOS 2.11.00.07 to TI-RTOS
2.11.01.09:
- Update
CCS/IAR to point to TI-RTOS
2.11.01.09
- CCS:
Open and select "TI-RTOS for xxx" in Project
Properties->General->RTSC->Product and Repositories
- IAR:
Replace the Global Argument Variables as described in "Integrating
TI-RTOS Examples with IAR IDE" in the TI-RTOS Getting
Started Guide.
- Update
the CC26xx Driverlib as described in "Updating
driverlib for CC26xx" in the TI-RTOS Getting Started Guide.
- TI-RTOS
2.11.01.09 includes CC26xx driverlibs: cc26xxware_2_20_06_14829 and cc26xxware_2_00_06_14829.
- Supported
Operating Systems
- Windows
7, Windows XP, Windows Vista
- Linux
[RH4], Ubuntu [10.04]
This release requires the following other software
components
and tools versions to successfully function:
- CCSv6.0
or higher
- IAR
for ARM 6.70.1 or higher (7.30.1 +
CC26xx patch or
higher for CC26xx)
- IAR
for MSP430 5.60.1 or
higher
- Compiler versions are noted in the next section
The following table contains the targets available for each product. It
also contains the compiler toolchains that were used to build the
TI-RTOS binaries.
| Product |
Supported
Targets |
Compiler
Toolchains |
Compiler
Versions |
| TI-RTOS
for SimpleLink™ Wireless MCUs |
ti.targets.arm.elf.M3
iar.targets.arm.M3
ti.targets.arm.elf.M4
iar.targets.arm.M4
gnu.targets.arm.M4 |
Texas
Instruments |
5.1.5 |
| GCC
(in CCS 6) |
gcc-arm-none-eabi-4_7-2013q3 |
| IAR
for ARM |
7.30.1
(+ CC26xx patch) |
This release was validated using the following components:
- CCSv6.0.1
- IAR
for ARM 7.30.1 (+ CC26xx patch)
- IAR
for MSP430 5.60.1
- xdctools_3_30_06_67
There are several
know issues with this release.
The following use cases are discussed in more detail (and work-arounds)
on the following wiki site: https://processors.wiki.ti.com/index.php/TI-RTOS_Support
- GCC and IAR users: By default semi-host is
enabled for both GCC and IAR users. Many of the
TI-RTOS examples will not run without the IDE attached (e.g. after a
power-reset).
- IAR
7.20 users: There is a problem when loading both the
CC32SDOCM0010777600 or Tiva devices. Please replace the C:\Program
Files (x86)\IAR Systems\Embedded Workbench 7.x\arm\bin\armlmftdi.dll
file with the one on the wiki site listed above.
- IAR users: The
imported TI-RTOS projects are using the default linker files. The
examples should use the ones supplied in the TI-RTOS
examples.
- GCC users: The TI-RTOS kernel and
instrumentation examples are not getting a linker file. Simply copy one
from one of the TI-RTOS driver examples.
| ID |
Headline |
| SDOCM00099460 |
ping flood causes Concerto board to stop receiving
interrupts |
| SDOCM00104253 |
MSP430 Launchpad ez-FET UART emulation issue at
buadrate > 28.8kbps |
| SDOCM00104686 |
UART in Stellaris launchpad not working above 9600 baud
when used with windows apps that use rxtxSerial.dll driver |
| SDOCM00105778 |
MSP430 UART logging to System Analyzer does not work |
| SDOCM00106264 |
UART driver doesn't handle RX FIFO overruns. |
| SDOCM00107260 |
ROV view for GPIO doesn't work for MSP430 |
| SDOCM00107276 |
ROV for GPIO exception if opened before
Board_initGeneral() is called |
| SDOCM00107319 |
makedef's XDCTOOLS_JAVA_HOME default is bad in supplied
examples for stand-alone installer |
| SDOCM00107336 |
GPIO's ROV module does not work on the TM4C1294 because
of a missing entry in the gel file. |
| SDOCM00107337 |
BIOS and UIA examples will not link with default
MSP430FR5969 linker file. |
| SDOCM00107366 |
Grlibdemo on MSP430FR5969LP not working for IAR |
| SDOCM00107418 |
UIA examples don't run on Beaglebone |
| SDOCM00107701 |
TI-RTOS filters out BIOS' 64T libraries |
| SDOCM00108264 |
UIA hello and stairstep examples do not build for some
MSP430 devices |
| SDOCM00113440 |
TI-RTOS installer segfaults on a Ubuntu 14.04 LTS
machine |
| SDOCM00113708 |
UDP echo WiFi example only gets IP address every other
program load |
| SDOCM00113726 |
GNU kernel and instrumentation examples do not build
for CC3200 |
| SDOCM00113733 |
ROV for UART with DMA is broken |
| SDOCM00113750 |
fatsd usb copy example fails even though SD card is
present |
| SDOCM00113751 |
Can't run 'gmake clean' before 'gmake all' in
command-line generated examples. |
| SDOCM00114667 |
CCS injects a -DCC2650F128RGZ, causing CC26xx build
errors with cc26xxware_2_00_06_14829 Driverlib |
There are driver examples for CC2650DK and CC2650STK_BLE boards.
There are kernel and instrumentation examples for all supported
devices.Please refer to the Getting Started Guide for more details.
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. 1.01.00.15_eng or
1.01.00.21-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. tirtos_1_00_01_11.
Subsequent releases of patch upgrades will be identified by
the patch number, ex. TI-RTOS 1.00.00.68 with directory tirtos_1_00_01_70.
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.
For
technical
support, please refer to the Texas Instruments E2E BIOS Support Forum http://e2e.ti.com/support/embedded/tirtos/default.aspx
or other forums in http://e2e.ti.com/
as needed.
Last updated: January 30, 2015
