This is a GA release of UIA
1.02.00.
The following documentation is available:
Release notes from previous releases are also available in the "docs/relnotes_archive" directory.
ID | Headline |
SDOCM00097700 | add Log_iprint(), etc. APIs that take Logger handle, update LoggerStreamer to support multiple instances | SDOCM00097359 | loggerSMDump segfaults when dumping codec engine logs |
SDOCM00098476 | Single-image project on multiple cores (e.g. for OpenMP) locks up when adding logger to QueueDescriptor linked list |
SDOCM00098024 | Adding System Analyzer/Logging support to SYSBIOS examples with default RTSC platform results in XDC runtime error |
SDOCM00097621 | New UIA needed in CCS5.4 to resolve failure to build UIA tutorial projects for C28X and CortexM3/M4 |
SDOCM00097497 | Boot.getFrequency() does not work for concerto M3 |
SDOCM00096493 | BIOS CPU frequency does not match Program.cpu.clockRate in config for F28069 |
SDOCM00095360 | Tutorial 1 needs to build for all UIA targets |
SDOCM00095164 | UIA ServiceMgr.xml has an invalid comment which impacts the Grace page |
SDOCM00094926 | Add TREX to UIA |
SDOCM00092313 | Need seperate .cfg files for C28 and other "small" targets |
SDOCM00092226 | UIA templates (stairstep examples) do not automatically add the linker cmd file for Concerto causing build failure |
SDOCM00095825 | UIA fails with 'dataMemory' is sealed error on EZDSPF28335 |
SDOCM00095614 | Adding LoggingSetup into C28 example causes build error |
ID | Headline |
SDOCM00093458 | Memory leak in UIA |
SDOCM00092495 | LoggerStreamer does not support logging of protocol events needed to provide visibility into MCSDK applications |
SDOCM00092228 | UIA example gives errors on Load Module and does not build by default |
SDOCM00091672 | UIA needs to update steps to rebuild based on new top level make |
SDOCM00091554 | Loggers Java code generates a noisy build |
SDOCM00091318 | UIA: LoggingSetup pulls in LoggerStreamer if upload mode is IDLE |
SDOCM00090812 | LoggerStopMode is brought in unnecessarily |
SDOCM00088806 | Need to complete graphical configuration of UIA modules |
SDOCM00084410 | UIA's ServiceMgr cannot be stopped and restarted without reloading the targets |
ID | Headline |
SDOCM00090728 | Errors in ti.uia.runtime.LogUC.h macro definitions |
SDOCM00090709 | uia.xml file contains invalid <N/A> tags in the customfield metadata entries |
SDOCM00090708 | UIA Tutorial 1 build fails with error xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.sysbios.knl' |
SDOCM00090509 | ti.uia.runtime loggers fail at configuration time when configured with a buffer size of 0 |
SDOCM00090508 | LoggingSetup should not create an Overflow logger if LoggingSetup.overflowLoggerSize = 0 |
SDOCM00087601 | System Analyzer's time base is wrong for Concerto |
SDOCM00087583 | Compiler warnings from UIA and XDC redefining events [complete fix] |
ID | Headline |
SDOCM00089079 | getDefaultTransport return causes build error |
SDOCM00088802 | Need C28_float support |
SDOCM00087602 | UIA needs a productview |
SDOCM00087583 | Compiler warnings from UIA and XDC redefining events [partial fix] |
SDOCM00086803 | C6474 target does not support multicore event correlation - need to provide global timestamp module |
SDOCM00085472 | LoggerSM's sharedBuffer should be in Module_state, not a config parameter |
SDOCM00084512 | LoggerSM does not support filenames for most XDC modules |
SDOCM00081893 | LoggingSetup.loadLoggingRuntimeControl is not being ignored |
SDOCM00077648 | Cannot rebuild services and runtime libraries from commandline |
This release supports the following hosts:
Windows XP SP2/SP3
Windows Vista
Linux (Redhat 4 and 5)
This release requires the following other software components and tools versions to successfully function:
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 |
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
Last updated: Jan 17, 2013