2.1. Release Notes

2.1.1. Overview

The Processor Software Development Kit (Processor-SDK) provides the core foundation and building blocks that facilitate application software development on TI’s embedded processors. This Release Notes focuses on the Real-time operating system (RTOS).


2.1.2. Licensing

Please refer to the software manifest, which outlines the licensing status for all packages included in this release. The manifest can be found on the SDK download page or in the installed directory as indicated below.


2.1.3. Documentation

  • Getting Started Guide: Provides information on getting the software and running basic examples/demonstrations bundled in the SDK.
  • Migration Guide Provides migration information for applications built on top of the Processor SDK for RTOS.
  • Software Developer Guide Provides information on features, functions, delivery package and, compile tools for the Processor SDK RTOS release. This also provides detailed information regarding software elements and software infrastructure to allow developers to start creating applications.
  • Software Manifest: Provides license information on software included in the SDK release. This document is in the release at /processor_sdk_rtos_<SOC>_<version>/docs and available to view from the software download page.
  • EVM Quick Start Guide: Provides information on hardware setup and running the demonstration application that is loaded on flash. This document is provided as part of the EVM kit.

2.1.4. Processor SDK v05.03.00

Warning

Big-endian support for C66x and C674x platforms shall be deprecated in Processor SDK RTOS from the Release 6.0 (2Q-2019)

Released March 2019

What’s New

New Features

Note

C64P big endian targets are no longer supported since this release.

Component Version

The following software components and host tools are bundled with the SDK installer. See the Software Developer Guide for more information on each item.

Note

This release has been tested with the following component and tool versions. It is recommended to use the versions listed here to avoid compatibility issues.
Component Version AM335x AM437x AM57x AM65x K2H/K2K K2E K2L K2G C665x C667x OMAP-L137 OMAP-L138
CG_XML 2.61.0 X X X X X X X X X X X X
CTOOLSLIB 2.2.0.0     X   X X X X X X    
DSPLIB 3.4.0.3     X   X X X X X X X X
EDMA3 LLD 2.12.5.30 X X X     X X X X X X X
FC 3.40.2.7     X   X X X X X X    
FFTLIB 3.1.0.0                   X    
IMGLIB 3.1.1.0     X   X X X X X X    
IPC 3.50.3     X X X X X X X X   X
LIBARCH 1.0.0.0         X         X    
LINALG 1.2.0.0         X         X    
MATHLIB 3.1.2.3     X   X X X X X X X X
MPM 3.0.4.0         X X X X        
NDK 3.40.1 X X X X X X X X X X X X
NS 2.40.1 X X X X X X X X X X X X
OPENCL 1.1.18.0     X                  
OPENMP 2.6.3.0     X   X X X X X X    
PDK   1.0.14 1.0.14 1.0.14 1.0.4 4.0.13 4.0.13 4.0.13 1.0.13 2.0.13 2.0.13 1.0.8 1.0.8
SYS/BIOS 6.75.2 X X X X X X X X X X X X
UIA 2.30.1.2     X X X X X X X X X X
XDAIS 7.24.0.4     X   X X X X X X X X
XDCTOOLS 3.51.01 X X X X X X X X X X X X

The following compilers are bundled with the SDK installer:

Compiler Version AM335x AM437x AM57x AM65x K2H/K2K K2E K2L K2G C665x C667x OMAP-L137 OMAP-L138
GNU ARM Embedded 7-2018-q2 A8 A9 A15   A15 A15 A15 A15        
GNU Linaro GCC 7.2.1       A53                
TI ARM CGT 18.1.5     M4 R5     A15(SBL)     ARM9 ARM9  
TI C6000 CGT 8.3.2     C66x   C66x C66x C66x C66x C66x C66x C74x C74x
TI PRU CGT 2.2.1 PRU PRU PRU       PRU          

The SDK uses Code Composer Studio (CCS) as the integrated development environment (IDE) for all devices and EVMs:

Component Version AM335x AM437x AM57x AM65x K2H/K2K K2E K2L K2G C665x C667x OMAP-L137 OMAP-L138
CCS 8.3.0 X X X X X X X X X X X X
EMU Pack Sitara Device 1.4.4 X X X X                
TI

Emulators

 8.0.903.2 X X X X X X X X X X X X

If you need to install CCS, see the CCS installation section in the Getting Started Guide for options to select for Processor-SDK.

2.1.5. Fixed Issues

Record ID Board/s Component/s Summary
PRSDK-3482 am335x-evm, am335x-ice, am335x-sk, am437x-evm, am437x-idk, am437x-sk, am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk, amic110-ice, beagleboneblack, c6657-evm, c6678-evm, c6748-evm, c6748-lcdk, k2e-evm, k2g-evm, k2g-ice, k2h-evm, k2k-evm, k2l-evm, omapl137-evm, omapl138-lcdk CCS CCSV8.1: Intermittent issue not able to connect target while using DSS script
PRSDK-5094 am437x-idk, am571x-idk, am572x-idk, am574x-idk Control Drivers QSPI flash R/W performance issue in MMAP (DAC) mode
PRSDK-4994 am572x-evm, am572x-idk, am574x-idk PDK CSL CPTS spec mismatch with TRM spec
PRSDK-4108 omapl138-lcdk High-Speed Drivers USB Audio: Lag when trying to adjust volume
PRSDK-4950 am654x-evm, am654x-idk Networking am65xx: icssg-fw: TX lockup observed when trying to transmit and maintain 96ns IPG.
PRSDK-4464 am654x-evm, am654x-idk Networking ICSS-G-FW: Dual-emac: ping with 16K packet size fails
PRSDK-5179 am571x-idk, am572x-evm, am572x-idk, am574x-idk Control Drivers FATFS multi-partition fails to load file from windows formatted SD card with only Boot Record
PRSDK-4725 am335x-ice, am437x-idk PDK PTP: ICSS-EMAC LLD Master Mode config does not sync with slave
PRSDK-4462 am654x-evm System IPC A53 ROV log won’t show correctly because of XDCtools bug
PRSDK-4965 am335x-ice Networking PRU-ICSS EMAC TX queuing performance issue
PRSDK-5489 am335x-evm, am335x-ice, am335x-sk, am437x-evm, am437x-hsevm, am437x-idk, am437x-sk, am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk, am654x-evm, am654x-hsevm, am654x-idk High-Speed Drivers USB bulk in wrong state when task preempted
PRSDK-5533 am335x-evm, am335x-ice, am335x-sk High-Speed Drivers USB enumeration failure intermittently with unplug/plug test
PRSDK-5248 am654x-idk Networking, PDK packet loss with ICSSG emac driver
PRSDK-5522   Chip Support Typo in hw_control_am437x.h file for PWM SS mask and shift
PRSDK-5021 am654x-evm, am654x-idk Boot SBL Needs to set CTRLMMR_MCU_TIMER0_CLKSEL to 0x0 for timer to work in RTOS applications
PRSDK-5461 omapl138-lcdk Audio, Video, & Display McBSP driver does not account for TX data delay
PRSDK-5559 am572x-evm, am572x-idk, am574x-idk Control Drivers QSPI clock doesn`t change when bitrate field in SPI driver Params is setup
PRSDK-5029 am437x-evm, am437x-idk, am571x-idk, am572x-evm, am572x-idk, am574x-idk Board Support Incorrect placement of dummy read cycles in SPI LLD test code
PRSDK-5234 k2g-evm, k2g-ice Board Support Invalid DDR_PHY_MR2 setting in K2G board library
PRSDK-4972 am572x-idk, k2g-evm Control Drivers Inconsistent TCC handling for UART Rx and Tx in DMA mode.
PRSDK-5414 am654x-evm, am654x-idk Board Support Board library VTT Enable for DDR config is missing RMW in GPIO setup
PRSDK-4911 am571x-idk, am572x-idk Networking Poll IEEE defined register for speed and duplexity instead of PHYSTS
PRSDK-5126 am335x-evm OSAL Add error block in TaskP OSAL implementation
PRSDK-5288 am437x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk Control Drivers Redundant OSAL_pendLock code in QSPI_transfer_v1 API that needs to be removed
PRSDK-5207 am335x-evm Audio, Video, & Display AM335x LCDC_RasterExample build failure
PRSDK-5217 am572x-idk Chip Support Need add L1/L2 ECC functions into CSL
PRSDK-5157 am572x-evm, am572x-idk Control Drivers AM57x UART DMA test linked with wrong library

2.1.6. Known Issues

This section contains the list of known issues at the time of making the release and any known workaround.

Record ID Board/s Component/s Summary Workaround
PRSDK-1760 am437x-idk Board Support Support for Sector erase function in QSPI library for AM437x in Starterware Use sector erase command 0x20 instead of block erase command 0xD8 (QSPI_LIB_CMD_BLOCK_ERASE) for erase operation in S25FLFlash_BlockErase function (packagestiboardsrcidkAM437xdeviceqspi_flash.c)
PRSDK-5247 am654x-evm Unknown RTOS builds are very slow on Windows machines No Workaround is presently available on Windows. However we have found that building on linux is much faster. Customers are encouraged to build on linux if possible while this issue on windows is being worked on.
PRSDK-4654 am654x-idk System Integration CCS fails to see symbols from *.out This issue is seen only if the sysbios based applications build using a CCS project file via CCS. This issue is not seen if the projects are built using makefile. A workaround to this issue would be to use makefile based projects.
PRSDK-5635 am572x-evm, am572x-idk, am574x-idk, c6657-evm, c6678-evm, c6748-lcdk, k2e-evm, k2g-evm, k2g-hsevm, k2g-ice, k2h-evm, k2k-evm, k2l-evm, omapl137-evm, omapl138-lcdk Optimized Libraries DSPLIB and MATHLIB performance degrades with C6000 8.3.x code gen tools To get better performance, can use the C6000 Codegen tools v7.4.2. Here are the details. 1. Download C6000 Code Generation Tools v7.4.2 https://software-dl.ti.com/codegen/non-esd/downloads/download.htm 2. Clone DSPLIB from https://git.ti.com/ep-processor-libraries/dsplib, and follow readme.txt in root folder to recompile DSPLIB. 3. Clone MATHLIB from https://git.ti.com/ep-processor-libraries/mathlib, and follow readme.txt in root folder to recompile MATHLIB.
PRSDK-5645 am654x-evm Emupack GEL file not working properly for AM654x-EVM platform causing DDR not to be configured properly Processor SDK RTOS v5.03 users will need to use Device support package 1.4.4. and TI emulation driver 8.0.903.2 . Customers are required to disable Automatic updates to prevent auto update to latest 1.4.5.
PRSDK-4706 am654x-evm, am654x-idk Boot SBL: MCU0 Boot in R5 Split Mode not supported in SBL The SBL currently cannot reset the MCU1 subsystem to restart the cores in split mode. To workaround this, the MPU needs to reset the MCU1 sub-system. To configure the MCU1 susb-system in split mode, do the following. a) Create a multi-core image with a MCU1_0 image, a MCU1_1 image and an MPU image. b) The MPU1 image must contain code to reset the MCU sub-system. Refer the function sblTestResetMcu in sbl/example/k3MulticoreApp/sbl_amp_multicore.c for example code on how to reset the MCU subsystem c) Before resetting the MCU, the MPU must wait for the SBL to boot MCU1_0
PRSDK-2892 am571x-idk, am572x-evm, am572x-idk PDK Incorrect A15 MMU configurations in default config file Set MMU attribute to not executable for device memory attrs0.noExecute = true; // Not executable
PRSDK-5612 am437x-idk OSAL, PDK Missing interrupt enable/disable option in OSAL HwiP_Params  
PRSDK-5539 c6748-lcdk, omapl138-lcdk Control Drivers SPI loopback example not working in interrupt mode on OMAPL138 Polling mode can be used instead.
PRSDK-5624 am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk, c6678-evm, k2h-evm Optimized Libraries FFTLIB documentation for AM57xx and K2H devices is missing  
PRSDK-5485 am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk Networking Intermittent ping packet loss when running AM57x EMAC at 10 mbps  
PRSDK-5473 am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk Networking NDK TCP packet re-transmission timeout when running ARM at a lower speed  
PRSDK-5667 am654x-evm, am654x-idk Board Support AM65xx diagnostic test hang on R5 core Use the diagnostic tests built for A53 core.
PRSDK-5620 am572x-idk PDK I2C_BasicExample_TestProject: I2C EEPROM test failure UT0 Same test passed on AM571x IDK and AM572x-EVM platforms but only failed on AM572x IDK platform.
PRSDK-5272 k2g-hsevm Networking EMAC_BasicExample: error #10099-D: program will not fit into available memory Move .stack and .cinit sections to L2SRAM to MSMCSRAM in tidrvemactestEmacLoopbackTestk2gc66biosemac_example_k2g.cfg.
PRSDK-5638 am654x-evm Diagnostics AM65xx diag self test hangs during memory test on R5 core The similar test can be run from A53 instead
PRSDK-5655 am654x-hsevm Boot Allow windows users to selectively enable JTAG for AM65x HS  
PRSDK-5448 am654x-evm, am654x-idk Boot SBL boot from MMCSD fails intermittently  
PRSDK-5403 am437x-idk Control Drivers iolink: channel 7 has ISDN read/write response error Increase the cycle time will reduce the read/write response error
PRSDK-5470 am654x-hsevm, am654x-idk Boot R5 cannot boot an app if entry point is in DDR Please refer the How To Guide Run applications from DDR on R5 cores
PRSDK-5626 am654x-hsevm Boot, DMA OSPI Read using UDMA fails on AM65x HS devices. Non-DMA mode could be used for the read operation
PRSDK-5080 am654x-evm, am654x-idk Board Support AM65xx diag failures on R5 core Can run failing test from A53 cores
PRSDK-3344 am572x-idk, am574x-idk Diagnostics Diagnostics icssEmac_TEST idkAM57{2/4}x : LINK IS DOWN, pluggin loopback cable ICSS-EMAC LLD TI-RTOS example can be used for similar test.
PRSDK-3383 am574x-idk Diagnostics Diagnostics: lcdTouchscreen_TEST hangs Issue expected to be specific to TI EVM. For TI EVM, test need to be bypassed from the diagnostic menu.
PRSDK-4667 am572x-evm Demonstrations, Networking Image Processing Demo lock up on AM572x GP EVM Issue seen using 1Gig router on ETH0. Replace with 100Mbps
PRSDK-335 AM4X, k2g-evm High-Speed Drivers USB host MSC fails to re-enumerate Re-enumeration support for the case of device unplugged and plugged back currently fails for the example. Workaround is to avoid disconnecting drive while running example.
PRSDK-5177 am574x-idk Board Support Uniflash: Flash programmer hangs when qspi flash is programmed with DDRECC enabled MLO Issue will be seen while flashing with prebuilt MLO image. Workaround will be to rebuild MLO with DDRECC disabled and program the flash device. Commands to rebuild MLO with DDRECC disabled: cd $(PDK_INSTALL_PATH)tibootsbl gmake all BOARD=idkAM574x SOC=AM574x BOOTMODE=qspi
PRSDK-1975 am572x-evm Diagnostics timer_DiagExample_evmAM572x_arm7.out doesn’t work on ARM1 core Example can run on ARM Core 0
PRSDK-1682 am571x-idk, am572x-idk Diagnostics Board diagnostics LCD Touchscreen test does not work with new version of LCD TSC For LCD/Display checkout example under VPS component could be used
PRSDK-2336 am335x-evm, am437x-evm Power AM3 & AM4 PM Examples experience I2C bus lockup when communicating with PMIC The debug versions of the PM apps are still functional. To build them: From the top-level makefile in pdk.../packages folder run “make BUILD_PROFILE=debug pm” This will build the debug versions of the PM RTOS and measurement apps.
PRSDK-2166 am572x-idk High-Speed Drivers USB3.0 host problem with Sandisk Extreme USB3.0 stick Start the example without the USB plugged in. Once the example is up and waiting for USB stick, plug the USB stick in and it will enumerate properly.
PRSDK-4214 k2g-hsevm System create-sdcard script does not boot OOB Default generated App image is not signed follow the steps mentioned in User Guide of the Processor SDK Secdev Build and Install Guide to sign the app
PRSDK-4121 am654x-evm Boot make all fails for Windows due to missing openSSL package
  1. For Windows : Download and install Strawberry Perl. The Strawberry Perl installer automatically installs and sets up OpenSSL. 2) For Linux : Execute the command “sudo apt-get install openssl” at the linux command prompt. 3) Check if OpenSSL is installed by typing “openssl version” at the command prompt.
PRSDK-5267 am570x-evm, am571x-idk, am572x-evm, am572x-idk, am574x-idk, k2e-evm, k2g-evm, k2g-hsevm, k2g-ice, k2h-evm, k2k-evm, k2l-evm DMA AM57x A15 EDMA library doesn’t support SMP mode  
SYSFW-2239 am654x-evm, am654x-idk Boot Boot time degradation in AM65x Boot time has increased due to an overall increase in the system firmware init, mainly caused due to an increase in resource manager initialization. To work around this, Sciclient_boardCfgRm must be invoked from the application rather than the SBL. UDMA relies on the resource manager, so when the SBL skips Sciclient_boardCfgRm, it must make sure that it does not use DMA. To build the SBL so that it skips the call to Sciclient_boardCfgRm and does not use DMA, in sbl_component.mk, uncomment the line SBL_CFLAGS += -DSBL_SKIP_BRD_CFG_RM and update the line SBL_CFLAGS = -DSBL_USE_DMA=1 to SBL_CFLAGS = -DSBL_USE_DMA=0

2.1.7. Supported Platforms

2.1.7.2. Evaluation Modules

See Processor SDK Supported Platforms page for a list of supported EVMs per platform and links to more information.

2.1.7.3. Demonstrations

See Examples and Demonstrations page for a list of demonstrations per platform and EVM.

2.1.7.4. Drivers

The following tables show RTOS driver availability per platform and EVM. A shaded box implies that the feature is not applicable for that platform/EVM.

Sitara devices

Feature Platform/SOC AM335x EVM AM437x EVM AM57x EVM AM65x EVM
  AM335x AM437x AM57x GP ICE SK BBB GP IDK SK GP IDK GP IDK
CSL X X X X X X X X X X X X X X
EMAC X X X X X X X X X X X X X X
EDMA3 X X X X       X     X      
GPIO X X X   X   X X   X X X X X
GPMC X X     X     X            
I2C X X X X X X X X X X X X X X
PRUSS-I2C f/w X X X   X       X     X    
PRUSS-eSPI f/w X X                        
ICSS-EMAC X X X   X       X     X    
McASP X X X X       X     X   X  
McSPI X X X   X       X     X X X
MMC-SD X X X X X X X X X X X X X X
PCIe     X                 X X  
PM X   X X             X   X X
PRUSS X X X   X       X     X X X
QSPI   X X           X X   X    
OSPI                         X X
UART X X X X X X X X X X X X X X
USB X X X X       X     X X X X
USB Device Audio X     X                    
USB Device Bulk X X X X       X     X X X X
VPS     X               X X    
UDMA                         X X
OSPI                         X X
SCICLIENT                         X X
SA                         X X
CAL                         X X
DSS                         X X

DSP devices - K2x, C66x

Feature Platform/SOC K2 EVM C66x EVM
  K2H/K2K K2E K2L K2G C665x C667x K2H K2E K2L K2G K2G-ICE C665x C667x
CSL X X X X X X X X X X X X X
AIF2 X           X            
BCP X   X       X   X        
CPPI X X X X X X X X X X X X X
DFE     X           X        
EDMA3 X X X X X X X X X X X X X
EMAC       X X         X X X  
FFTC X   X       X   X        
GPIO X X X X X X X X X X X X X
HYPLNK X X     X X X X       X X
ICSS-EMAC       X             X    
I2C X X X X X X X X X X X X X
IQN2     X           X        
McASP       X           X      
McBSP       X X         X   X  
MMAP X X         X X          
MMC-SD       X           X X    
NWAL X X X     X X X X       X
PA X X X     X X X X       X
PCIe X X X X X X X X X X   X X
QMSS X X X X X X X X X X X X X
RM X X X X X X X X X X X X X
SA X X X X   X X X X X     X
SPI X X X X X X X X X X X X X
SRIO X       X X X         X X
TCP3D X   X   X   X   X     X  
TSIP   X       X   X         X
UART X X X X X X X X X X X X X
USB       X           X      
USB Device Audio                          
USB Device Bulk       X           X      

DSP devices - OMAP-L13x, C674x

Feature Platform/SOC OMAP-L137 EVM OMAP-L138 EVM
  OMAP-L137 OMAP-L138 L137/6747 SK LCDK138 LCDK6748
CSL X X X X X
EDMA3 X X X X X
EMAC X X X X X
GPIO X X X X X
I2C X X X X X
McASP X X X X X
MMC-SD X X X X X
SPI X X X X X
UART X X X X X
USB X X X X X
USB Device Audio X X X X X
USB Device Bulk X X X X X

Unsupported Features

  • In general driver support is available across all cores within an SOC with following exceptions
Feature Not supported
  SOC CPU/Core
McASP AM57x M4
USB AM57x C66x
USB AM57x M4
USB K2G C66x
McBSP K2G A15
McBSP OMAP-L13x ARM9
All Drivers K2E/L/K A15

2.1.7.5. Other Features

The following table shows other feature availability per platform and EVM:

Sitara devices

Feature Platform/SOC AM335x EVM AM437x EVM AM57x EVM AM65x EVM
  AM335x AM437x AM57x GP ICE SK BBB GP IDK SK GP IDK GP IDK
Board Support X X X X X X X X X X X X X X
Boot (SBL) X X X X X X X X X X X X X X
Diagnostics X X X X       X     X X X X
FATFS X X X X X     X X   X X X X
NDK-NIMU(CPSW) X X X X X X X X X X X X X X
NDK-NIMU(ICSS) X X X   X       X     X X X
CC-LINK IE Field Basic(CPSW) X X X X X X X X X X X X    
CC-Link IE Field Basic(ICSS) X X X   X       X     X    

DSP devices - K2x, C66x

Feature Platform/SOC K2 EVM C66x EVM
  K2H/K2K K2E K2L K2G C665x C667x K2H K2E K2L K2G K2G-ICE C665x C667x
Board Support X X X X X X X X X X X X X
Boot (IBL/SBL) X X X X X X X X X X X X X
Diagnostics       X           X X    
FATFS       X           X X    
Fault Management X X X       X X X        
IPC Transport (QMSS) X X X   X X X X X     X X
IPC Transport (SRIO) X       X X X         X X
MAD-UTIL         X X           X X
Network (CPSW) X X X X X X X X X X X X X
Network (ICSS)       X           X      
CC-Link IE Field Basic(ICSS)       X           X      
Platform Library (obsolete) X X X   X X X X X     X X
PKTLIB X X X     X X X X       X
POST X X X   X X X X X     X X
SERDES Diagnostics X X X       X X X        
Trace Framework X X X       X X X        

DSP devices - OMAP-L13x, C674x

Feature Platform/SOC OMAP-L137 EVM OMAP-L138 EVM
  OMAP-L137 OMAP-L138 137/6747 SK LCDK138 LCDK6748
Board Support X X X X X
Boot (SBL) X X X X X
Diagnostics X   X    
FATFS X X X X X
Network (CPSW) X X X X X

2.1.8. Installation and Usage

The Getting Started Guide provides instructions on how to setup up your development environment, install the SDK and start your development.

To uninstall the SDK, remove the individual component directories from the installed path. This is safe to do even in Windows since these components do not modify the Windows registry.


2.1.9. Host Support

The recommended development host is

  • Windows: Windows 10 on 64-bit machine
  • Linux: Ubuntu 14.04, 16.04 on 64-bit machine

Note

The Windows installer is a 32-bit binary, but is compatibile with 64-bit machine.


2.1.10. Technical Support and Product Updates

For further information or to report any problems, contact: - TI E2E Processor Support for all supported platforms


2.2. Supported Platforms and Versions

Supported Host Operating Systems

The following operating systems have been validated to work with our SDK.

  • Linux SDK
Operating System
Version
Ubuntu
14.04 (64-bit)
16.04 (64-bit)
18.04 (64-bit)
  • RTOS SDK
Operating System
Version
Windows
7 (64-bit)
Ubuntu
14.04 (64-bit)
16.04 (64-bit)
  • Android SDK
Operating System
Version
Ubuntu
14.04 (64-bit)

Supported Platforms and EVMs

The following platforms and EVMs are supported with Processor SDK

Platform EVM Tested Version Document Processor SDK Linux Processor SDK RT Linux Processor SDK RTOS Processor SDK Android
AM65x/DRA80xM AM65x/DRA80xM EVM Beta Hardware User’s Guide Hardware Setup with CCS X X X X
AM65x/DRA80xM IDK Beta Hardware User’s Guide Hardware Setup with CCS X X X X
AM57x AM572x EVM A3 Hardware User’s Guide X X X X
AM572x IDK 1.3A Hardware User’s Guide Hardware Setup with CCS X X X X
AM571x IDK 1.3A Hardware User’s Guide Hardware Setup with CCS X X X X
AM574x IDK 1.0A Hardware User’s Guide Hardware Setup with CCS X X X X
AM437x AM437x EVM 1.5B Hardware User’s Guide X X X  
AM437x SK 1.1A Hardware User’s Guide X   X  
AM437x IDK 1.4A Hardware User’s Guide   X X  
AM335x AM335x EVM 1.6A Hardware User’s Guide X X X  
AM335x SK 1.2 Hardware User’s Guide X   X  
BeagleBone Black B6 Hardware User’s Guide X   X  
AM335x ICE 2.1A Hardware User’s Guide Hardware Setup with CCS   X X  
K2H/K2K 66AK2Hx EVM 4.0 Hardware User’s Guide X X X  
TCI6638K2K EVM 4.0 Hardware User’s Guide X X X  
K2E 66AK2Ex EVM 1.0.3.0 Hardware User’s Guide X X X  
K2L 66AK2L06 EVM 1.0.3.0 Hardware User’s Guide X X X  
K2G K2G EVM 1.3D

Hardware User’s Guide

Hardware User’s Guide

 X X X  
K2G 1G EVM 1.5D X X X  
K2G Audio Daughtercard D Software Support     X  
K2G ICE EVM 1.0C Beta Hardware User’s Guide Hardware Setup with CCS X X X  
C665x C665x EVM 1.1-44 Hardware User’s Guide N/A N/A X  
C667x C667x EVM 3B Hardware User’s Guide N/A N/A X  
OMAPL137/C6747 OMAP-L137/C6747 Starter kit EVM J Hardware User’s Guide Hardware Setup with CCS N/A N/A X  
OMAPL138/C6748 OMAP-L138/C6748 LCDK A7A Hardware User’s Guide X N/A X  
AMIC110 AMIC110 ICE 1.1 Hardware User’s Guide Hardware Setup with CCS     X  

2.3. Migration Guide

2.3.1. Overview

This page covers migration information from last Processor SDK RTOS release (Processor SDK RTOS 05.02.00) to the present release (Processor SDK RTOS 05.03.00)

2.3.2. EMAC

Migration-1: ICSS-G EMAC firmware binary directory location update for future extension

Impact Scope: Applicable for all applications using EMAC driver with ICSS-G dual EMAC firmware

Additional Details: Applications will need to update the include path to location of firmware header files for ICSSG use case

prevous location: ti/drv/emac/firmeare/icss_eth/src/dm

new location: ti/drv/emac/firmware/icss_dualmac/bin

Migration-2: Release introduces support for additional firmware specific configuration files. Added for future extension to support multiple firmwares using same EMAC driver

Impact Scope: Applicable for all applications using EMAC driver with ICSS-G dual EMAC firmware

Additional Details: Firmware configuration has been moved to firmware specific configuration files, emac_fw_config_dual_mac.h and emac_fw_config_dual_mac.c. Previously the firmware configuration was specified in the test application It is not expected that applicatons will need to modify these files as the are closely tied to the firmware.

Previous location: firmware specific configuration was specified in the text application (ti/drv/emac/test/EmacLoopbackTest/test_utils_k3.c)

New location: ‘ti/drv/emac/firmware/icss_dualmac/config/’

Applications will need to update their makefiles to include c source file emac_fw_config_dual_mac.c At time of emac_open API call, applications need to udpate configuruation parameters to pass get firmware configuration pointer :

EMAC_HwAttrs_V5 emac_cfg;

EMAC_socGetInitCfg(0, &emac_cfg);

emac_cfg.portCfg[port_num].getFwCfg = &emacGetDualMacFwConfig;

EMAC_socSetInitCfg(0, &emac_cfg);

2.3.3. CSL

Migration: API changes on CSL-FL of AM65xx on ecc aggregator, vim, esm modules

Impact Scope: Limited to the case if application is using the CSL-FL APIs

Additional Details: The CSL-FL for ECC aggregator, ESM and VIM are modified to return API functionality success/failures and additional arguments are added as and when needed (especially during the cases where the return was the value instead of API success/failure). Applications that use these CSL-FL calls are impacted and are needed to align to new calling conventions. If applicable application modification required to align to updated APIs, refer doxygen API documentation for API details.

2.3.4. DSP- TI CGT Compiler

Migration: In DSP TI CGT compiler version 8.3.2 the rts library boot object file name is changed from boot.obj to boot.c.obj.

Impact Scope: Limited only to DSP applications that explicitly uses rts library object files in linker command file.

Additional Details: The DSP application which is using linker command file of CSL module should change boot object name from boot.obj file to boot.c.obj. If the user is using cpp version of boot object file then it should be mentioned as boot.cpp.obj. In general it can be also be used as boot.*.obj This can be referred from the following linker command file in the PDK package <PDK>/packages/ti/csl/example/lnk_dsp.cmd