- Attention
- Also refer to individual module pages for more details on each feature, unsupported features, important usage guidelines.
-
For release notes of MCU+ SDK, please refer to AM64X MCU+ SDK Release Notes 09.02.00.
- Note
- The examples will show usage of SW modules and APIs on a specific CPU instance and OS combination.
Unless noted otherwise, the SW modules would work on all supported EVMs
-
Examples uses ICSS EMAC driver from Industrial Communication SDK package in 9.2 Release. This driver support will be moved to MCU SDK from 10.0 onwards
New in this Release
Feature |
PROFINET RT/IRT support with Siemens ERTEC stack on TMDS64EVM |
EtherNet/IP Intercore Network tunneling example on AM64x |
ICSSG0 instance support for EtherCAT Stack |
Custom PHY integration reference for DP82826 and DP83869 |
Ethernet over EtherCAT EoE |
File access over EtherCAT FoE |
Integrate NVM library for persistent data storage - EtherCAT examples now use EEPROM and not Flash memory to store EtherCAT EEPROM data |
Ethernet/IP - The object dictionary size should be possible to change without rebuild of stack |
Ethernet/IP - Added functionality to enable/disable forwarding of the LLDP frames in the firmware. |
IOLINK Controller - Added NVRAM support for AM243 LP and EVM in example app |
Bug Fixes |
Device and Validation Information
SOC | Supported CPUs | Boards | Host PC |
AM64x | R5F | AM64x PG2 EVM (referred to as am64x-evm in code) | Windows 10 64b or Ubuntu 18.04 64b |
Tools, Compiler and Other Open Source SW Module Information
Tools / SW module | Supported CPUs | Version |
Code Composer Studio | R5F, M4F, A53 | 12.7.0 |
SysConfig | R5F, M4F, A53 | 1.20.0, build 3587 |
TI ARM CLANG | R5F, M4F | 3.2.2.LTS |
GCC AARCH64 | A53 | 9.2-2019.12 |
GCC ARM | R5F | 7-2017-q4-major (AM64x only) |
FreeRTOS Kernel | R5F, M4F, A53 | 10.4.3 |
FreeRTOS SMP Kernel | A53 | 202110.00-SMP |
Tiny USB | R5F | 0.14.0 |
LwIP | R5F | STABLE-2_2_0_RELEASE |
Mbed-TLS | R5F | mbedtls-2.13.1 |
Features not supported in release
Feature Not Supported in Profinet Device |
RGMII Mode |
Fixed Issues
ID | Head Line | Module | Applicable Releases | Resolution/Comments |
PINDSW-5668 | PR0_IEP0_EDIO_DATA_IN_OUT30 is not functioning as AL event | EtherCAT Device | 09.01.00 | |
PINDSW-7521 | Drift Compensation issue for filter values other than 0 | EtherCAT Device | 09.01.00 | |
PINDSW-7712 | DLR : Active Supervisor IP Address gets updated regardless of Supervisor change | EtherNet/IP Adapter | 09.01.00 | |
PINDSW-7593 | Correct Host Name Attribute is not returned in TCP/IP Object in Bootp mode | EtherNet/IP Adapter | 09.01.00 | |
PINDSW-7554 | Incorrect Watchdog timer configuration for Beacon time out | EtherNet/IP Adapter | 09.01.00 | |
PINDSW-7042 | ACD - Active phase not getting restated on Second Link up event | EtherNet/IP Adapter | 09.01.00 | |
Known Issues
ID | Head Line | Module | Applicable Releases | Workaround |
PINDSW-5122 | DLR does not work in RGMII mode | EtherNet/IP Adapter | 08.04.00 | |
PINDSW-5508 | Observed "tcp_err_handler: Connection aborted (-13) while running CTT | EtherNet/IP Adapter | 08.06.00 | |
PINDSW-5666 | EtherNet/IP : PTP Device is unable to keep offset under 1000 ns | EtherNet/IP Adapter | 08.04.00 | Value of OFFSET_THRESHOLD_FOR_RESET is set to 10000 ns by default in SDK |
PINDSW-6587 | EtherCAT syscfg - Rx MLINK enable does not enables MLINK if it is disabled from application | EtherCAT Device | 08.06.00 | |
PINDSW-7791 | SysRed Part 2 - Scenario 3 and 4 failing | Profinet Device | N/A | N/A
|
PINDSW-8035 | EtherNet/IP Tunneling : Wrong IP and MAC address returned by DUT through ENIP Messaging | EtherNet/IP Tunneling | 09.02.00 | |
PINDSW-8036 | EtherNet/IP Tunneling : DHCP and BOOTP does not work in EIP Tunneling example | EtherNet/IP Tunneling | 09.02.00 | |
PINDSW-8037 | EtherNet/IP Tunneling : ARP messages are sent out with Source Address of ICSS EMAC MAC address when ACD is enabled | EtherNet/IP Tunneling | 09.02.00 | |
Upgrade and Compatibility Information
This section lists changes which could affect user applications developed using older SDK versions. Read this carefully to see if you need to do any changes in your existing application when migrating to this SDK version relative to previous SDK version. Also refer to older SDK version release notes to see changes in earlier SDKs.
Examples
Drivers
Module | Affected API | Change | Additional Remarks |
| | | |