Sitara SDK 5.05.00 Release Notes

Return to the Sitara Linux Software Developer's Guide

Sitara SDK 05.05.00 Release Notes

Released July 27, 2012

Content Overview

This is version 05.05.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 EVM	AM335x EVM-SK	BeagleBone	AM180x	AM35x	AM37x	Beagleboard-xM
3.2.0 Internal PSP version (04.06.00.08)	X	X	X
3.3.7							X
2.6.37 Internal PSP version (03.21.00.04)				X
2.6.37 Internal PSP version (04.02.00.07)					X	X

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

Supported Devices

• AM335x EVM
• AM335x EVM-SK
• AM37x EVM
• AM35x EVM
• AM180x EVM
• BeagleBone
• BeagleBoard-xM

What's New

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

• Support for the AM335x EVM-SK platform including
  • Dual-EMAC
  • DDR3 support
• WiFi Direct support
• Addition of Smart Reflex Power Management drivers
• Support for HW accelerated cryptography for AM335x platforms

Note - Some applications are platform specific 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.  SDK version 05.04 and later supplied 4.5.3 with dynamic libgcc and libstdc++ libraries.

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

The table below lists the known issues in this release. You should check this site periodically for workarounds/solutions to the known issues as they become available.

1. The issue with the board-port labs for u-boot has been resolved and a new set of sources has been pushed to the git repository. Performing the following commands in the u-boot tree should be sufficient to update your system, or you can just clone another copy of the https://gitorious.org/sitara-board-port/sitara-board-port-uboot tree.

   git tag -d 05.05.00.00-template

   git tag -d 05.05.00.00-mmc

   git tag -d 05.05.00.00-ethernet

   git checkout master

   git pull

2. When booting from NFS on AM335x devices (beaglebone, EVM, EVM-SK) you may see messages like DHCP/BOOTP: Ignoring delayed packet when using some routers. This has currently been observed with some Linksys and Trendnet routers. The result of this issue is that the NFS boot will not succeed. This issue is under investigation and appears to be related to how these routers pass back the response to the DHCP request and this response not being properly routed to the proper interface. In the mean time if you do not require the second network interface (i.e. beaglebone and EVM or EVM-SK with only one interface in use) you can disable the Device Drivers -> Networking Device Support -> Ethernet driver support -> TI CPSW Switch as Dual EMAC option in the kernel configuration. This issue does not affect u-boot or the user space from obtaining a DHCP IP address, only the Linux kernel network initialization is affected.

BUG_ID	IMPACT	CLASS	RELEASE	Platform	SUMMARY	DETAILS
ARM_MPU.XLDR_UBOOT.21	Critical	Other	SDK 05.03.02+	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.02+	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. The DMA support can be enabled in the kernel depending on your use case. The most commonly affected use cases are when the USB core is being used in host mode and there is both DMA and PIO traffic occurring at the same time. This has been observed with many USB WiFi adapters as well as when doing I/O operations to one device which inserting or removing another device. If you choose to enable DMA you should extensively test your use case to verify that no lockup occurs.t
ARM_MPU_SDK.BTS_MATRIX.122	Critical	Other	SDK05.04.00+	AM37x, AM335x	PRCM Suspend/resume does not work completely with touchscreen as a wake-up source	This issue was previously noted under Suspend/resume power demo description in MatrixGUI.
ARM_MPU_SDK.BTS_MATRIX.121	Critical	Other	SDK05.04.00+	AM37x	AM37x - suspend resume does not work at 300MHz and 600MHz with 1.2 (revD) silicon	Summary is that SDKs 05.02.00.00, 05.02.00.01, 05.03.02.00, 05.04.00.00 all fail to resume on 1.2 silicon when the clock is set to 300MHz. All work on 1.1 silicon for all clocks. If the MPU voltage is increased the suspend/resume will work.
ARM_MPU_SDK.BTS_WLAN.33	Critical	Kernel	SDK 05.05.00	AM335x	Wake on Wireless LAN does not work	WoWLAN is not working on the EVM SK 1.2B. When using WLAN as a wakeup source a firmware panic is seen even when using UART to wake up the board.
ARM_MPU_SDK.BTS_WLAN.30	Critical	Kernel	SDK 05.05.00	AM335x	WiFi-Direct Demo gui does not function correctly when rootfs is in nfs	See Summary
ARM_MPU_SDK.BTS_WLAN.28	Critical	Kernel	SDK 05.05.00	AM335x	Delay before BT keyboard work with HID test	When running the HID test in the bluetooth gui a delay is seen between when the test is started and when key presses are recognized. This does not occur with command line testing. The delay can be up to 2 minutes with the bluetooth gui.
ARM_MPU_SDK.Installer_Scripts.63	Critical	Kernel	SDK 05.05.00	All	create-sdcard.sh: if the SDK path doesn't have the last '/', the script throw Invalid SDK path	Add the / when specifying the path to work around this issue
ARM_MPU_SDK.BTS_MATRIX.93	Critical	Kernel	SDK 05.05.00	AM335x	Multimedia demo Mepg4+AAC dec has noise in audio.	The system is running out of resources during the decode operation of both audio and video which can lead to the audio noise heard.
ARM_MPU_SDK.BTS_Documentation.47	Not Critical	Other	SDK 05.05.00	AM335x	u-boot source tree for board port does not build for 05.05.00.00 release	The board port u-boot tree for 05.05.00.00 release found in the SDK does not build properly. This has been updated and fixed in the git repository at https://gitorious.org/sitara-board-port/sitara-board-port-uboot
ARM_MPU_SDK.BTS_MATRIX.140	Not Critical	Cryptos/Security	SDK 05.05.00	AM335x	openssl server cannot be accesses from external device	When running the openssl server demo the server cannot be accessed from an external device. Messages like the following are seen: A PKCS #11 module returned CKR_DEVICE_ERROR, indicating that a problem has occurred with the token or slot. (Error code: sec_error_pkcs11_device_error) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.
ARM_MPU_SDK.BTS_KERNEL.85	Critical	Kernel	SDK 05.05.00	AM37x	suspend takes much longer to complete when other processes are running in parallel	Time to suspend while other processes are running can be as long as 30 seconds
ARM_MPU_SDK.BTS_KERNEL.84	Critical	Kernel	SDK 05.05.00	AM37x	rtc wakeup resume does not work when another process is running through telnet shell	Telnet to AM37x. Run an LTP test. Now, from console log, send " rtcwake -d /dev/rtc0 -m mem -s 2" to set rtc to be the wakeup source. Wakeup will not be successful. Similar behaviour can be seen when running "ifconfig" or some cat message from telnet shell as well. No issues waking up when no process is running in parallel.
ARM_MPU_SDK.BTS_KERNEL.79	Critical	Kernel	SDK 05.05.00	AM335x	ifdown/ifup eth0 interface in dual cpmac mode and with ping traffic	This is filed as issue SDOCM00094019 in the PSP kernel
ARM_MPU_SDK.BTS_KERNEL.	Critical	Kernel	SDK 05.05.00	AM335x	Multicast packets are not received when in dual cpmac mode	When in switch mode, SK target is able to receive multicast packets. When kernel is built with dual_cpmac option, these packets are not received.
ARM_MPU_SDK.BTS_KERNEL.77	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	Kernal panic on inserting g_ether module.	Patch to fix this has been submitted to the upstream kernel
ARM_MPU_SDK.BTS_KERNEL.72	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	USB ISO mode not working	USB ISO mode does not work properly with the 3.3.7 kernel. This includes both video and audio.
ARM_MPU_SDK.BTS_KERNEL.69	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	USB: File allocation error during simultaneous file copy.	When copying a 1.5GB file from one pendrive to another pendrive "file allocation" errors were observed. It appears that the system was running low on memory and beginning to shutdown processes.
ARM_MPU_SDK.BTS_KERNEL.67	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	Black video grains artifacts are observed for 320x240 video capture through HOST port	With some cameras black grain artifacts were observed during the capture.
ARM_MPU_SDK.BTS_KERNEL.66	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	Multiple capture of video through usb hangs the board	Scenario : To capture the video through uSB camera for different resolutions. Expected Results: To camera should be stable and capture video with given inputs. Observations : Board hangs for video capture for multiple times and could not telnet the board. Note: Hang observed for the first video capture run also. Steps: cd /opt/ltp/testcases/bin/ddt ./usb_video_capture -w 320 -l 240 -d /dev/video0 -i /home/root/320x240_1.YUV ./usb_video_capture -w 176 -l 144 -d /dev/video0 -i /home/root/176x144_1.YUV ./usb_video_capture -w 640 -l 480 -d /dev/video0 -i /home/root/640x480_1.YUV repeat the capture for 10 times
ARM_MPU_SDK.BTS_KERNEL.62	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	Audio continues to play after reset	When we boot Beagle XM with amsdk filesystem the moment ALSA is configured audio loopback starts working. Audio loopback continues even if you do soft reset of the board. Once Linux is booted if we do audio loopback a second instance audio can be heard i.e. parallel loopback 2 sounds heard. Steps are as given below Provide audio input to BeagleXM from a stereo input Connect headset to audio out Boot BeagleXM The moment ALSA is configured you can listen to audio playing Do console login Run audio loopback arecord -f cd | aplay -f cd You can listen to double sound Do soft reboot by pressing reset button Audio is still working Remove power: Audio stops Reconnect power: No sound heard
ARM_MPU_SDK.BTS_KERNEL.61	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	watchdog timer hangs system after timeout	When we do a write on /dev/watchdog system get hung after timeout (60 seconds) instead of restarting. root@beagleboard:~# uname -a Linux beagleboard 3.3.7 #1 Tue Jun 12 15:03:25 IST 2012 armv7l unknown root@beagleboard:~# zcat /proc/config.gz | grep NOWAY CONFIG_WATCHDOG_NOWAYOUT=y root@beagleboard:~# echo 1 > /dev/watchdog [ 82.969482] omap_wdt: Unexpected close, not stopping!
ARM_MPU_SDK.BTS_KERNEL.60	Critical	Kernel	SDK 05.05.00	AM180x	some SATA harddisks could not be enumerated	One of the problematic one is WD2500BEKT which is SATA-II device. After plugin WD2500BEKT, it could not be enumerated; then I unplug this harddisk and plug in a different one which is WD5000AAKX, no any message comes to console. This WD5000 can be enumerated before on this kernel
ARM_MPU_SDK.BTS_KERNEL.51	Critical	Kernel	SDK 05.03+	AM35x	failed to get can_stb error when setting timing parameters for can interface	Error frames observed with the xmit tool and no reception on the end device.
ARM_MPU_SDK.BTS_KERNEL.55	Critical	Kernel	SDK 05.05.00	Beagleboard-xM	eth interface up/down under high traffic causes event drop errors	When connecting BBXM eth interface to traffic generator (in this case, smartbits), and if eth interface is put up and down a couple of times, the following type of event drop errors are constantly scrolling on serial output [ 274.822479] smsc95xx 1-2.1:1.0: eth0: kevent 4 may have been dropped This stops only when incoming traffic is stopped.
ARM_MPU_SDK.BTL_WLAN.20	Critical	WiFi	SDK 05.04.00+	All	Leaving Bluetooth demo running for an hour causes a stale list of devices and stale pairing information	Leaving the demo running can result in a stale scan list such that pressing the "start scan" button will fail to find new devices. Restarting the demo will allow finding the new devices, but devices that were previously paired need to be re-paired.
ARM_MPU_SDK.BTS_BENCHMARKS.5	Not Critical	Boot Time	SDK 05.02+	All	Boot stalls at gnome-vfs	During the first boot of a clean file system the boot will stall for a while at the "Configuring gnome-vfs" step. Depending on the SD card speed or network speed this could be a couple of seconds or could take a minute. During this time the gnome-vfs package is doing a large amount of read operations and not all SD cards are read optimized. On subsequent boots this is not required and should no longer cause a delay. Scenarios where this might be encountered are when making a new NFS or SD card file system from the SDK pre-built file system found in the filesystem directory.
ARM_MPU_SDK.BTS_MATRIX.131	Not Critical	WiFi	SDK 05.04.00+	AM37x	console message "NOHZ: local_softirq_pending 08" seen when running wifi	When running the soft AP WiFi example the message "NOHZ: local_softirq_pending 08" message may be seen on the console but does not affect functionality.
ARM_MPU_SDK.BTS_MATRIX.135	Not Critical	Other	SDK 05.04.00+	All	When booting from NFS the /etc/resolv.conf file is not populated	When booting from NFS the user space udhcpc command is not run since the root file system is using the network. This prevents the /etc/resolv.conf file from being populated by the DHCP server which can lead to not being able to browse to web sites such as ti.com. Updating the contents of /etc/resolv.conf and rebooting will configure the network to allow the DNS lookup to occur.
ARM_MPU_SDK.BTS_Make.18	Not Critical	Makefiles	SDK 05.04.00+	All	top-level SDK Makefile matrix-gui target fails install	The top-level Makefile in the SDK directory will fail the "make matrix-gui_install" target since the Makefile.build file no longer exists.
ARM_MPU_SDK.BTS_CCSV5.16	Not Critical	Other	SDK 05.04.00+	All	QT projects report error during build	When building projects like qt-tstat in CCSv5 an error is reported while processing the .pro file. The project builds successfully and this error can be ignored.
ARM_MPU_SDK.BENCHMARKS.7	Not Critical	ARM	SDK 05.03.02+	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.FLASH_TOOL.7	Not Critical	Other	SDK 05.03.02+	BeagleBone, AM335x	no flash tool support	Flashing may be done using u-boot: AM335 Flash Programming Guide
ARM_MPU.KERNEL.35	Not Critical	Other	SDK 05.03.02+	AM35x	Warning message during boot	The following message may be ignored. It does not apply to AM35x: [ 0.000000] WARNING: at arch/arm/mach-omap2/pm.c:94 _init_omap_device+0x7c/0) [ 0.000000] _init_omap_device: could not find omap_hwmod for iva [ 0.000000] Modules linked in: [ 0.000000] [<c0049690>] (unwind_backtrace+0x0/0xe0) from [<c006f58c>] (warn) [ 0.000000] [<c006f58c>] (warn_slowpath_common+0x4c/0x64) from [<c006f624>] ) [ 0.000000] [<c006f624>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0050c80>] (_i) [ 0.000000] [<c0050c80>] (_init_omap_device+0x7c/0x9c) from [<c000ff5c>] (om) [ 0.000000] [<c000ff5c>] (omap2_common_pm_init+0x30/0x104) from [<c003a470>]) [ 0.000000] [<c003a470>] (do_one_initcall+0xb0/0x188) from [<c0008c2c>] (ker) [ 0.000000] [<c0008c2c>] (kernel_init+0x98/0x14c) from [<c0044ad4>] (kernel_) [ 0.000000] ---[ end trace 1b75b31a2719ed1c ]---
ARM_MPU_SDK.KERNEL.27	Not Critical	Cryptos/Security	SDK 05.03.02+	BeagleBone	no crypto driver support in the Linux kernel	Crypto acceleration driver support is under development and will be available in 2Q 2012.
ARM_MPU_SDK. INSTALLER_SCRIPTS.50	Not Critical	Other	SDK 05.03.02+	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.02+	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_SDK. INSTALLER_SCRIPTS.31	Not Critical	Other	SDK 05.03.02+	BBxM	Minicom script generated by uboot-env-setup.sh script is not effective on BBxM because BBxM has no NAND flash.	Need to modify the uEnv.txt on the boot partition of SD Card to change u-boot parameters.
ARM_MPU_SDK.FLASH_TOOL.8	Not Critical	Other	SDK 05.03.02+	AM180x	Need to get FlashAndBootUtils v2.35 to be able to rebuild CCS/JTAG-based flash writers with CCSv5.1	Go to this location http://sourceforge.net/projects/dvflashutils/files/OMAP-L138/ and download FlashAndBootUtils_v2.35.
ARM_MPU.XLDRBOOT.19	Not Critical	Other	SDK 05.03.02+	AM37x	when booting from SD card, you may see "timedout" messages	When loading uImage from SD card, you may get some warning messages:  mmc_send_cmd: timedout waiting for stat!
ARM_MPU.ExApps.25	Not Critical	Other	SDK 05.03.02+	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.
ARM_MPU.GFX.1	Not Critical	Other	SDK 05.03.02+	AM35x, AM37x	Graphics driver initialization causes a stack dump on the 2.6.37 kernel.	At boot up, during initialization of the Graphics driver you will see: [ INFO: possible recursive locking detected ] followed by a stack trace dump. This message can be ignored, there is further information here: http://processors.wiki.ti.com/index.php/SGXDbg
ARM_MPU.GFX.4	Not Critical	Other	SDK 05.03.02	AM35x, AM37x+	OGLESShadowTechniques can lockup and hang the system.	OGLESShadowTechniques application can lock up and only reboot will bring the system back up and running. It is recommended not to run this application.
ARM_MPU.KERNEL.18	Not Critical	Other	SDK 05.03.02+	AM180x	SDK missing Source code for UBL.	Currently the UBL source code is missing from this release.
ARM_MPU_SDK.BTS_MATRIX.136	Not Critical	Other	SDK05.03+	All	3D demos could not run when running NFS	When rebuilding the kernel and installing the kernel modules, the existing modules are removed by the modules_install step of the kernel build. For out-of-tree driver modules such as the SGX modules this requires that those modules be re-built against the re-built kernel. Not rebuilding and re-installing these modules to the target file system will result in the applications that use those drivers, such as the 3D demos to fail to run.