UIA 1.04.00.06 General Availability
Release
Notes
This release note is divided into the following sections:
Introduction,
Documentation, What's
New,
Dependencies and Compatibility, Host
Support,
Device Support, Validation Info, Known Issues, Examples, Version
Information, Technical
Support.
This is a GA release of UIA
1.04.00.
Packages are provided as source code and prebuilt
libraries.
The
following documentation is available:
Release notes from previous releases are also available in the
"docs/relnotes_archive"
directory.
1.04.00.06
-
IAR target support.
-
Misc bug fixes. See below.
Defects Fixed since 1.03.01.08
| ID | Headline |
| SDOCM00102901 |
Add IAR target support to UIA |
| SDOCM00103105 |
UIA examples should use ti.platforms.tiva for TIVA parts (keep using stellaris for M3) |
| SDOCM00103372 |
uia.mak needs MSP430 elf target |
| SDOCM00103583 |
Add IAR targets to uia.bld and uia.mak |
| SDOCM00103804 |
LoggerSM_write2 is incorrect when writing binary data |
| SDOCM00100416 |
Add GCC examples to UIA product |
| SDOCM00104197 |
LoggerIdle's bufferSize doc is wrong. |
| SDOCM00104198 |
LoggingSetup needsto expose the disableMulticoreEventCorrelation parameter on the grace page. |
For information on enhancements and defect fixes in earlier releases,
please refer to the release notes from previous releases that are
available in the relnotes_archive
directory.
The following table lists dependent product versions and compatibility
information. Note that CCS version 5.4 requires XDCTools version 3.25 or
higher. If you are using CCS 5.3, you should use XDCTools 3.24.07. This
release of UIA requires BIOS 6.35.02 or higher.
| CCS Version | XDCTools Version | BIOS Version |
NDK Version | IPC Version |
| 5.3 |
3.24.07 |
6.35.02 or higher |
2.22.02.16 or higher |
1.25.01.09 or higher |
| 5.4 |
3.25 |
The Code Generation tools versions needed with this release of UIA are
listed below.
- TI Code Generation Tools
- C28X version 6.1.0 or later
- C6X version 7.3.1 or later
- ARM version 4.9.1 or later, M3/M4 version 5.0.1 or later
- MSP430 version 4.1.0 or later
- GNU Code Generation Tools
- ARM version gcc-arm-none-eabi-4_7-2012q4
(M3/M4/M4F/A8F/A9F/A15F)
- IAR Code Generation Tools
- ARM version 6.50 (M4/M4F)
- MSP430 version 5.51.2
UIA 1.04.00.06 is backward compatible with the previous 1.03.01.08
release.
This release supports the following hosts:
Windows XP SP2/SP3
Windows Vista
Linux (Redhat 4 and 5)
Expilict Examples
UIA libaries
built for
- C64P (COFF and elf, big and little endian),
- C674 (COFF and elf, little endian),
- C66 (elf, big and little endian),
- C64T (elf, little endian),
- Arm9 (elf, little endian),
- M3 (elf, little endian),
- M4F (elf, little endian)
- A8F (elf, little endian)
- A8Fnv (elf, little endian)
- C28_float
- MSP430X (elf, little endian)
This release was validated using the following components:
- C6000 CodeGen 7.2.0
- Arm CodeGen 5.0.1
- DSP/BIOS 6.37.00.20
- IPC 1.25.01.09
- XDCtools 3.25.04.88
- NDK: 2_22_02_16
- SysLink_02.21.00.03
Note:
This release had minimal evmT816X validation (LoggerSM and
LoggerCircBuf examples for M3 were built. LoggerSM examples did
generate output on the linux console. CircBuf examples did stream
events to System Analyzer).
Here are the known issues with this release.
| ID |
Headline |
| SDOCM00094008 | Overflow logger not supported for JTAGRUNMODE and NONJTAG_AND_JTAGSTOPMODE |
| SDOCM00089387 |
UIA has pthread_join which does not work on Andriod |
| SDOCM00088803 |
Rta/ServiceMgr are not built for C28_float |
| SDOCM00087568 |
Default LoggingSetup logger buffer sizes are too small
- events are always dropped when using JTAGRUNMODE transport |
| SDOCM00087567 |
Need a way to configure ti.uia.sysbios.LoggingSetup to
NOT create an OVERFLOW logger when using JTAGRUNMODE transport |
| SDOCM00086708 |
ServiceMgr module not configured properly if
LoggingSetup.eventUploadMode = JTAGRUNMODE |
| SDOCM00084415 |
UIA's ServiceMgr's Advanced configuration page does not
allow Transport sendFxn to be set |
| SDOCM00084411 |
Registry name is lost with UIA |
| SDOCM00081291 |
UploadMode_NONJTAG_AND_JTAGSTOPMODE does not do
timestamp correlation |
| SDOCM00077654 |
UIA Scripts do not support multi-core well |
| SDOCM00077653 |
Loading DSP on Netra example has lots of warning...but
works |
| SDOCM00077649 |
Rta only obtains events from statically created logger
instances |
| SDOCM00077589 |
IpcMP creates a replyMQ on each processor. It only
needs it on the master. |
| SDOCM00077588 |
IpcMP should not assert in error conditions. It should
log an event and recover. |
| SDOCM00077586 |
Rta's ROV only supports LoggerCircBuf |
| SDOCM00077585 |
Need to remove all compiler warnings in evmti816x
examples |
| SDOCM00077324 |
ServiceMgr's ROV should obtain information from proxies |
| SDOCM00075422 |
LoggerCircBuf writes management of the pad is not
optimal |
UIA ships with with many examples that interact with System Analyzer
Single-core
The
following examples can be built for all the supported targets. The
actual application is the same for all examples. The difference is the
way the data is moved up to System Analyzer. Stairstep varies the Task,
Swi and
Hwi load every 5 seconds. When viewed on the CPU Load Analysis Feature,
it looks like a staircase.
- Stairstep
JTAG Stopmode: The Log data is obtained
when the target is halted
- Stairstep
JTAG RunMode: The Log data is obtained by
reading the running target (only works on C64X+ and C66 CPUs).
- Stairstep
Ethernet:
The Log data is obtained by UDP packets. This example, as is, only
works for the EVM6472 board. Refer to the bottom of the .cfg file on
how to use on a different board.
- Stairstep
Simulator: The Log data is obtained by
temporarily stopping the target when the
Log call is made. To build this example, the XDC version must be 3.22
(or later) or the RTSC Build-Profile must be "release"
or "debug"
(not "whole_program").
- Stairstep
ProbePoint:
The Log data is obtained by temporarily stopping the target when the
Log call is made. To build this example, the XDC version must be 3.22
(or later) or the RTSC Build-Profile must be "release"
or "debug"
(not "whole_program").
- LoggerStreamer:
This example shows how to use the UIA LogUC (unconditional) APIs and
LoggerStreamer. The example does not work with System Analyzer. It is
meant to show how to use LoggerStreamer. It is up to the application to
get the data to System Analyzer..
- LoggerStreamer2:
This example shows how to use the UIA LogUC (unconditional) instance APIs and
LoggerStreamer2 (an enhancement of LoggerStreamer allowing multiple logger
instances). The example does not work with System Analyzer. It is
meant to show how to use LoggerStreamer2. It is up to the application to
get the data to System Analyzer..
Multi-core
- Message:
The message example shows how to use MessageQ on EVM6472 and UIA. It is
a single-image example that must be loaded on all cores. A message is
sent from core 0 to core 1 to core 2...back to core 0. The
UIABenchmark_start and stop is used on core 0 to determine the duration
of a round trip. The Log data is obtained via Ethernet.
- SimpleTask:
This example flips bits on an array. The example can be built for the
DSP and M3 targets on the EVMTI816X. There are two examples. One uses
LoggerCircBuf and one that uses LoggerSM. Refer to the readme.txt in
packages\ti\uia\examples\evmti816x directory and the System Analyzer
User Guide
for more details.
Tutorials
- System
Analyzer and UIA
Tutorial 1: Logging events, benchmarking, controlling
events.
- System
Analyzer and UIA
Tutorial 2: Graphing events, using JTAG Run-Mode (C64X+ or
C66X emulation target)
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.16_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. uia_1_00_00_38.
Subsequent releases of patch upgrades will be identified by
the patch number, ex. UIA 1.00.00.26 with directory uia_1_00_00_38.
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, contact softwaresupport@ti.com
Technical
Support and Product Updates
Last updated: Jan 17, 2013
