ms1omap3530 Codec Server 1.00.00 Release Notes
May 24, 2010
Codec Server Definitions:
|
NAME |
ms1omap3530 |
|
VERSION |
01.00.00 |
|
PLATFORM(S) SUPPORTED |
OMAP3530 |
|
USE CASE(S) |
General purpose
audio/video/speech/image |
|
SERVER PACKAGE |
ms1omap3530_1_00_00 |
|
SERVER START ADDRESS |
0x87200000 |
|
SERVER END ADDRESS |
0x88000000 |
|
TOTAL SERVER SIZE |
14 Mbytes |
The following release notes are
applicable to the ms1omap3530 codec server.
The release notes are divided into the following sections:
Upgrade and Compatibility Information
Codec, Test Environment, Use Case Test Result Details
Technical Support and Contact Information
LICENSE
INFORMATION
·
The codec server
is bound to the Non-TSPA License Agreement(Note1)
RELEASES
- The release 1.00.00.02 provides the following
This
is the “Beta” release of this codec server
·
New Features
o
None
·
IRs Fixed in this Release
o
SDOCM00069142: Release notes are not present
for the deinterlacer
o
SDOCM00068579:
SW manifest missing entries for deinterlacer
o
SDOCM00069126:
Build failure in MP3 decoder
o
SDOCM00059208:
AAC Audio Decoder is not preserving all important performance in any framework
via link.xdt
o
SDOCM00059206:
MPEG4 Video Decoder is not preserving all important performance in any
framework via link.xdt
o
SDOCM00058809: JPEG Image
Decode - output file is often overwritten by an earlier output
- The release 1.00.00.01 provides the following.
This is the “Early Adaptor 1” release of this codec server
·
New features
o Mega single codec server executable
is built for encode, decode and encodedecode operations.
o Contains the MP3 decoder as well as
AAC HE/LC encoder
o Built on the cs1omap3530_1_01_00
single codec server release
·
IRs Fixed in
this Release
o
None
INSTALLATION
This codec
server is tested for the DVSDK WinCE 1.0 and DVSDK 3.01 releases. Download and
run the installation executable for Linux and Windows. The installation
produces the following structure.
The
directory structure is as follows:
ms1omap3530_1_00_xx
|----------- packages
|----------- ms1omap3530_release_notes.htm
|----------- config.bld
|----------- Makefile
|----------- package.xdc
packages directory is a place holder for the
codecs, servers.
config.bld file specifies the compiler tools
path and target platform.
Makefile is the ‘make’ utility file to build
the codecs and server.
packages contains the following directory
structure
ti
|----------- sdo
|----------- codecs
|----------- server
codecs directory is the place holder for
all the codecs that the codec server supports.
server contains the following directory
structure
|----------- cs
cs contains the following directory structure
|----------- bin
|----------- docs
The bin directory is intended to hold the
codec server executable cs.x64P, which gets generated. Please note that it is not part of the codec server
delivery. This is to
allow building the server with unique dependent packages.
The docs directory contains the following
files.
o
TILAW_216026_v1_Non_TSPA_License_Agreement_OMAP3530_Codec_Server.DOC - Non-TSPA license document for the
codec server
o
logocorp.gif -
Texas Instruments Logo
o
ms1omap3530_master_build_specification.xls -
Codec Server Master Build Sheet
o
ms1omap3530_software_manifest.pdf -
Codec Server Software manifest document
o
producttable.xml
– the product table for the codec server
o
ms1omap3530_data_sheet.htm -
Data Sheet describing the link to the generated server data sheet and links to
the codec documents.
The “cs”
directory contains the following files.
o
codec.cfg - Codec Configuration
files for the codec server
o
server.cfg - Codec Server
Configuration files
o
server.tcf - Codec Server tconf
script for the DSP binary
o
main.c -
Codec Server source main file
o
link.cmd
- Any additions to
the linker command files should be placed here
o
package.bld - RTSC package file
o
package.xdc -
RTSC package file
o
package.xs - RTSC package file
BUILDING
THE CODEC SERVER
·
The codec server
is typically built under DVSDK context; however it can be built standalone.
·
Please refer to the
variables listed in the sample csRules.mak that need to be specified for your
unique build environment, if it is not built from Linux DVSDK environment.
·
type make clean, to make sure any metadata and server executables are cleaned
·
To build the
codec server, type make or gmake under the ms1omap3530_1_01_xx directory
(make sure that the path includes the GNU make.exe).
Note: Please do “make clean” before building the codec server
executable, to make sure any metadata and server executables are cleaned.
UPGRADE AND COMPATIBILITY INFORMATION
This product's version follows a version format, M.m.p.b,
where M is a single digit Major number, m is single digit minor number, p is a
single digit patch number and b is the build number.
DEVICE SUPPORT
This release supports the
following device families:
- OMAP3530
KNOWN ISSUES
|
Sl.No. |
SDOCM ID |
Description |
Issues/Workaround |
|
1 |
SDOCM00058962 |
JPEG Image Encode -
when qfactor above 96 is used, jpeg compressed output is incorrect |
The documentation
says Q factor till 100 is supported. But when system test used high Q
factor (97 to 100) for boundary condition testing, the images are distorted.
The documentation regarding q factor
has to be corrected. |
|
2 |
SDOCM00058964 |
JPEG Image Encode -
bottom part of output for 88x72 422p images for is incorrect |
The codec user guide
mentions "arbitrary size allowed", documentation needs to be
corrected accordingly. |
|
3 |
SDOCM00059735 |
The g711enc and g711dec
RTSC packages share a common symbol (mentioned below). When a codec server is
built with both the libraries, the below warning is seen. Warning 1 >> package/cfg/bin/cs_x64P.xdl,
line 313: warning: multiple definitions of SECTION named
'.const:_G711_TII_CODER_version' |
This does not impact
any functionality of G711. This can be safely ignored. |
CODEC,
TEST ENVIRONMENT AND USE CASE TEST RESULT DETAILS
Please refer to the excel sheet ms1omap3530_master_build_specification.xls(Note1) for versions of the list of
multimedia codecs integrated in the codec server, test environment and the use
cases for which the server is designed.
TECHNICAL
SUPPORT AND CONTACT INFORMATION
Contact local TI Field
Application Engineer for technical support.
SPECIAL NOTES
Note1
The following links
referred in this document will not function properly, when this document is not
opened from the ms1omap3530 installation directory.
·
ms1omap3530_master_build_specification.xls
·
Non-TSPA License
Agreement
·
Top level “
Copyright
2009-10,