Sitara SDK 5.03.03 Release Notes

Sitara SDK 05.03.03 Release Notes

Released February 13, 20112

Content Overview

This is version 05.03.03.00 of the Sitara Software Development Kit (SDK). The SDK provides a fundamental software platform for development, deployment and execution of Linux based applications and includes the following:

Kernel Versions	AM335x	BeagleBone
3.1.0 Internal PSP version (04.06.00.03)	X	X

• Bootloaders & Filesystems
• SDK Installer
• Setup Scripts
• Makefiles
• (Upgraded)Matrix Application Launcher
• Example Applications
• Code Composer Studio v5 (CCSv5)
• Host Tools
  • Flash Tool
  • Pin Mux Utility

Supported Devices

• AM335x
• BeagleBone

What's New

We continue to enhance the features providing in the Sitara SDK.  This version includes the following new features:

• Change in memory timings for u-boot to allow running DDR on all devices at 266MHz

Note - Some applications are platform specifc and highlighted in the Software Developer's Guide.

Installation and Usage

The Software Developer's Guide provides instructions on how to setup up your Linux development environment, install the SDK and start your development.  It also includes User's Guides for various Example Applications and Code Composer Studio.

Host Support

The Sitara SDK is developed, built and verified on Ubuntu 10.04 LTS.  In addition to the Long Term Support provided by Ubuntu on this version, we also recommend use of Ubuntu 10.04 LTS to ensure efforts to resolve any issues are not host related.  Details on how to create a virtual machine to load Ubuntu 10.04 LTS are described in the Software Developer's Guide.

Toolchain

Versions prior to 05.02 used the Codesourcery Lite 2009q1-203 toolchain.  This required pre-installation of the cs-lite toolchain before the SDK could be installed.  Versions after 05.02 utilize the open source gcc4.X toolchain and are fully integrated in the Sitara SDK (linux-devkit) no longer requiring a toolchain installation.  SDK version 05.02 supplies gcc 4.3.3. SDK version 05.03 supplies 4.5.3. 

Technical Support and Product Updates

For further information or to report any problems, contact http://e2e.ti.com or http://support.ti.com.

Known Issues

BUG_ID	IMPACT	CLASS	RELEASE	Platform	SUMMARY	DETAILS
ARM_MPU.XLDR_UBOOT.21	Critical	Other	SDK 05.03.03	AM335x / BeagleBone	u-boot environment not optimally protected in NAND on AM335x EVM	The NAND chips on the AM335x EVM require a minimum of 4 bits ECC. Linux and  u-boot support 8 bit ECC which exceeds the NAND requirements. However the u-boot enviroment is currently stored with only 1 bit ECC which does not meet the minimum requirements of the NAND.
ARM_MPU.KERNEL.39	Critical	Other	SDK 05.03.03	ALL	USB DMA disabled	Devices which use the Mentor MUSB core currently disable the DMA due to instability issues. This will cause degradation from the expected USB throughput performance.
ARM_MPU_SDK.ExApps.22	Not Critical	ARM	SDK 05.03.03	AM335x	Power Management Applications Under Development	Power management applications are under development. They are scheduled for release in Feb. 2012.
ARM_MPU_SDK.BENCHMARKS.14	Not Critical	ARM	SDK 05.03.03	AM335x	LMbench memory bandwidth write test show degradation from previous release.	"bw_mem 1M wr" shows a 20% degradation in performance from release SDK05.03.02. This is under investigation.
ARM_MPU_SDK.KERNEL.40	Not Critical	ARM	SDK 05.03.03	AM335x	USB devices are not detected when plugged to the EVM in after boot up.	USB devices are detected when already plugged in during boot up. If plugged in after boot up, one of the following commands can be issued from the command line to initiate device enumeration: echo F > /proc/driver/musb_hdrc.0 echo F > /proc/driver/musb_hdrc.1
ARM_MPU_SDK.BENCHMARKS.7	Not Critical	ARM	SDK 05.03.03	ALL	Dhrystone results may vary	Dhystone may vary from the expected 1.8 DMIPS/MHz. Increasing the number of iterations that dhrystone runs will decrease the variability of the results.
ARM_MPU_SDK.CCSV5.8	Not Critical	2D/3D Graphics	SDK 05.03.03	ALL	Problem in CCSv5 with Make project GUI page	It is recommend to build QT projects from command line: Building QT Projects - http://processors.wiki.ti.com/index.php/Building_QT_Projects
ARM_MPU_SDK.CCSV5.11	Not Critical	Other	SDK 05.03.03	ALL	CCSv5 Release Note needed to enable capabilities	For the C/C++ and RSE plug-in perspectives to be selectable under Window->Open Perspective->Other each time CCS is started with a new workspace CCS capabilities need to be enabled as show here: Enabling additional CCSv5 Capabilities and Perspectives - http://processors.wiki.ti.com/index.php/Code_Composer_Studio_v5_Users_Guide#Enabling_CCS_Capabilities
ARM_MPU_SDK.FLASH_TOOL.7	Not Critical	Other	SDK 05.03.03	BeagleBone, AM335x	no flash tool support	Flashing may be done using u-boot: AM335 Flash Programming Guide
ARM_MPU_SDK.KERNEL.27	Not Critical	Cryptos/Security	SDK 05.03.03	BeagleBone	no crypto driver support in the Linux kernel	Crypto acceleration driver support is under development and will be available in Feb 2012.
ARM_MPU_SDK.MATRIX.113	Not Critical	Multimedia	SDK 05.03.03	BeagleBone	Multimedia support missing	The Multimedia applications are still under development. They will be available in a future release. The schedule is currently in work.
ARM_MPU_SDK. INSTALLER_SCRIPTS.50	Not Critical	Other	SDK 05.03.03	ALL	uboot-env-setup.sh script cannot save oldbootcmd from default u-boot params because of string length.	After running setup.sh to create a minicom script, when you run the mincom script, you may see a "setenv usage" message.  The oldbootcmd will not be saved.  The result of this is that you may lose your intial bootcmd after you run the script. (NOTE) you can get back to default u-boot enviroment by doing a nand erase of the u-boot parameters partition in NAND.
ARM_MPU_SDK. INSTALLER_SCRIPTS.25	Not Critical	Other	SDK 05.03.03	ALL	setup.sh script may display two IP addresses as default option.	Type the IP address of the Linux host instead of taking the default.
ARM_MPU.ExApps.25	Not Critical	Other	SDK 05.03.03	AM335x	Oprofile -when running a session you can see quite a few 'rm' errors	When running an NFS mounted file system, and running the Oprofile Applications, "Run Signal Parent" and "Run Signal Parent Optimized" you see many can not "rm" errors. This is just an annoyance the rm is successful. This issue will be resolved in the next release.