Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.
Sitara SDK 5.06.00 Release Notes
Return to the Sitara Linux Software Developer's Guide
Sitara SDK 05.06.00 Release Notes
Released December 21, 2012
This is version 05.05.01 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|
|3.2.0 Internal PSP version (04.06.00.09)||X||X||X|
- Bootloaders & Filesystems
- SDK Installer
- Setup Scripts
- Matrix Application Launcher
- Example Applications
- WLAN/Bluetooth support
- Code Composer Studio v5 (CCSv5)
- Host Tools
- Flash Tool
- Pin Mux Utility
- AM335x EVM
- AM335x EVM-SK
We continue to enhance the features providing in the Sitara SDK. This version includes the following new features:
- Updated U-Boot to version v2012.10.
- Minor kernel changes.
- Migrated to OE-Core based build system.
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.
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.
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
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.
- Sitara board port git trees have not been updated as of December 21, 2012 to use the latest PSP U-Boot and kernel from this SDK release. The update will be made in January.
- 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.
The user can add a parameter to the bootargs to give a longer timeout to allow for the DHCP server to respond. This parameter is:
Setting the value to 200 will double the timeout length and works in most cases. i.e.
|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_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)
|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.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.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_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.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_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.|