UIA 1.00.03.25 GA Release Notes

This release note is divided into the following sections:
Introduction, Documentation, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Known Issues, Examples, Version Information, Technical Support.

Introduction

This is a GA release of UIA 1.00.03.

Packages are provided as source code and prebuilt libraries.

Documentation

The following documentation is available:

Release notes from previous releases are also available in the relnotes_archive directory.

What's New

Updated Dependencies

Defects Fixed in UIA_1_00_03.25

ID	Headline
SDOCM00085484	UIA needs to provide makefile.defs file for each example to better support clean for custom build
SDOCM00085472	LoggerSM's sharedBuffer should be in Module_state, not a config parameter
SDOCM00085285	docs links in UIA 1.00.02.22 GA Release Notes are broken (UG and GSG have bad links)

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.

Upgrade and Compatibility Information

UIA 1.00.03.25 is backward compatible with the previous 1.00.02.22 release.

Host Support

This release supports the following hosts:

Windows XP SP2/SP3

Windows Vista

Linux (Redhat 4 and 5)

Dependencies

This release requires the following other software components and tools versions to successfully function:

C6000 CodeGen 7.0.0 for COFF
C6000 CodeGen 7.2.0 (or higher) for ELF
Arm CodeGen 4.9.0 (or higher)
DSP/BIOS 6.32.02.39 (or higher)
IPC 1.23.02.27 (or higher)
XDCtools 3.22.01.21 (or higher)
NDK: 2_20_04_26 (for evm6472) (or higher)
SysLink_02.00.00.78 (or higher)

Device Support

Expilict Examples

EVM6472
evmT816X

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),
A8F (elf, little endian)
A8Fnv (elf, little endian)

Validation Information

This release was validated using the following components:

C6000 CodeGen 7.2.0
Arm CodeGen 4.9.0
DSP/BIOS 6.32.02.39
IPC 1.23.02.27
XDCtools 3.22.03.41
NDK: 2_20_04_26 (for evm6472)
SysLink_02.00.00.78

Known Issues

Here are the known issues with this release.

ID	Headline
SDOCM00081893	LoggingSetup.loadLoggingRuntimeControl is being ignored
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
SDOCM00084410	UIA's ServiceMgr cannot be stopped and restarted without reloading the targets
SDOCM00084411	Registry name is lost with UIA
SDOCM00084415	UIA's ServiceMgr's Advanced configuration page does not allow Transport sendFxn to be set

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").

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 (C64X+ or C66X simulator).
System Analyzer and UIA Tutorial 2: Graphing events, using JTAG Run-Mode (C64X+ or C66X emulation target)

Version Information

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.

Technical Support

For technical support, contact softwaresupport@ti.com

Last updated: Sept. 07, 2011