API solutions Forum - Recent Threads

AM6442: Combined Keyring (Signed and Encrypted) Import Failure

ZHEN BEI SIN — Tue, 07 Jul 2026 15:39:36 GMT

Part Number: AM6442

Issue : Combined Keyring (Signed and Encrypted) Import Failure

A combined keyring (asymmetric key + symmetric key) was generated and packaged as a signed-and-encrypted image. (keyring.bin)
The KEYRING import operation fails with return code -19.

Reference:

KEYRING Documentation: https://software-dl.ti.com/tisci/esd/latest/6_topic_user_guides/keyring.html

TI E2E FAQ: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1484330/faq-sysfw-keyring-importing-support-on-am62x

Patch: 0001-calling-sysfw-keyring-import-API-in-r5-spl.patch: calling sysfw keyring import API in r5-spl

The example provided in keyring_init.h appears to cover only:

Single keyring images (Signed-only)

Question

Can TI provide a valid combined keyring (asymmetric key + symmetric key) signed by SMPK and encrypted by SMEK sample image for reference?
Is importing a combined keyring in signed-and-encrypted format supported on AM64x HS-SE devices?
Is there any known limitation or additional requirement when importing a signed-and-encrypted combined keyring on AM64x HS-SE devices?

RE: AM6442: Combined Keyring (Signed and Encrypted) Import Failure

Hong Guan64 — Tue, 28 Jul 2026 22:50:21 GMT

Hi Zhen,

Please refer to the new FAQ on keyring import (asymmetric & symmetric)
[FAQ] SYSFW symmetric keyring import and applications on AM64x

Best,
-Hong

RE: MSP430-FLASHER: Unable to download ti_msp430driver_setup_1.0.1.1-windows.zip – download link returns an error

Brian Dempsey — Tue, 28 Jul 2026 15:28:11 GMT

Hi Nathan,

can you try the following: https://www.ti.com/tool/zh-tw/download/MSPDS-USB-DRIVERS/1.0.1.2

I was able to successfully download the installation from this location.

-Brian

MSP430-FLASHER: Unable to download ti_msp430driver_setup_1.0.1.1-windows.zip – download link returns an error

Nathan Lacroix — Fri, 24 Jul 2026 07:41:54 GMT

Part Number: MSP430-FLASHER

Hello,
I am trying to download the ti_msp430driver_setup_1.0.1.1-windows.zip driver for my MSP430 Programmer.

I am logged into myTI and I receive the download link by email. However, the download does not start automatically. When I click the manual download link, I am redirected to an error page.

I have tried several times, on several computers and networks, and the issue persists. Could you please provide a working download link or help me access the driver?

Browser: Google Chrome on Windows 11
Board: MSP430 Programmer
Software/driver: ti_msp430driver_setup_1.0.1.1-windows.zip

AM62P: Only Validate First boot stage in fused HS-SE device

Hakan Cankaya — Fri, 24 Jul 2026 08:59:39 GMT

Part Number: AM62P

Hello,

We have fused device, mainly for JTAG locking. Secure boot is no requirement, therefor we only want to verify the first boot stage (TIBOOT image via ROM Code) and then not verify anymore images afterwards. We are using the SDK for loading the RPRC images, therefor the API for authentication is automatically called. We can alter the code, but is there a cleaner way to do this (e.g. by setting a parameter or compiler flag etc.).

Thanks

Hakan

RE: AM62P: Only Validate First boot stage in fused HS-SE device

Hong Guan64 — Fri, 24 Jul 2026 16:17:40 GMT

Hi Hakan,

Is AM62P MCU+SDK used in your setup?
If yes, one option is booting SBL_NULL to validate the very first user bootloader.
https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/12_00_00_27/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_SBL_NULL.html
https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/12_00_00_27/exports/docs/api_guide_am62px/SECURE_BOOT.html

Best,
-Hong

TMS320F280025C: TMS320F280025C Flash API Source Code Request

Hakan TOPUZ — Wed, 17 Jun 2026 07:13:19 GMT

Part Number: TMS320F280025C

I am a member of the Software Development Team. We are currently working with the TMS320F280025C microcontroller from the C2000 family and developing a custom bootloader. Therefore, we would like to request access to the source code of the Flash API related to this device.

Can you help us with this?

NOTE: We already have an NDA agreement in place.

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Aswin P — Fri, 24 Jul 2026 10:35:32 GMT

Hakan,

Moving to resolved state.

Thanks

Aswin

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Hakan TOPUZ — Thu, 23 Jul 2026 10:24:59 GMT

Aswin,

I send connect request to you.

Thanks

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Aswin P — Thu, 23 Jul 2026 08:29:58 GMT

Hi Hakan,

Can you connect with me on e2e? Let me connect with the team and get you a link to request access to the Flash API source.

Thanks

Aswin

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Hakan TOPUZ — Thu, 23 Jul 2026 07:37:01 GMT

Hello Aswin,

Can you help me about this topic ?

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Aswin P — Thu, 23 Jul 2026 07:17:39 GMT

Hi Hakan.

Sira is Out of Office this week, please expect a delay in response.

Thanks

Aswin

RE: TMS320F280025C: TMS320F280025C Flash API Source Code Request

Hakan TOPUZ — Thu, 23 Jul 2026 07:15:41 GMT

Hello Sira,

I send connect request to you.

Thanks

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

Harsha Begihally Shanmukhaswamy — Wed, 22 Jul 2026 06:17:34 GMT

Hello,

Could you please share the binary that you have tested? Let me know if you have adapted the demo application.

Kind Regards,

AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

?? ?? — Mon, 20 Jul 2026 04:56:16 GMT

Part Number: AM2434

Hello, Developer Team.

#1621803
Since the previous thread was locked, I am posting the continuation here.
(Please note that I am posting this as a "New Question" because the "Related Questions" section did not appear.)

After asking my last question in the previous thread, I investigated the sub-device processing further and discovered the following:

While the Sync0_Isr call interval was 250 µs, the PDI_Isr call interval was approximately 310 µs. Consequently, roughly every four cycles, the Sync0_Isr was triggered before the PDI_Isr, creating the appearance that the output was not being updated every 1 ms. (Synchronization setting: DC synchronization with a 250 µs cycle time.)

Additionally, having noted in another thread that CPU load reaching 100% could potentially delay sub-device processing timing, I used the FreeRTOS Run Time Statistics feature to measure the CPU usage of each task while in the OP state.

Below are the test results obtained by taking measurements every second over a 10-second test period.

Based on these results, the IDLE task accounts for a significant portion of the CPU load; therefore, it appears that the phenomenon where output updates are skipped is not caused by the CPU processing load.

Given this information, could you please assist me in resolving this issue?

Kind regards,

TMS320F28P659SH-Q1: Request for Memory Stack APIs for NvM → MemIf → Ea → EEPROM

Ngu Do — Wed, 22 Jul 2026 02:21:05 GMT

Part Number: TMS320F28P659SH-Q1

Request for Memory Stack APIs for NvM → MemIf → Ea → EEPROM

Hello TI Team,

I am currently developing an AUTOSAR-based application on a TI C2000 MCU and would like to clarify my previous request regarding memory read/write APIs.

I believe my previous question may have been misunderstood as a request for Flash programming APIs such as Fapi_issueProgrammingCommand(). However, this is not what I am looking for.

My requirement is to have a memory abstraction stack compatible with the AUTOSAR architecture, for example:

Application
    ↓
   NvM
    ↓
  MemIf
    ↓
    Ea
    ↓
 EEPROM / Emulated EEPROM
    ↓
TI MCU Flash / EEPROM hardware

More specifically, I am looking for APIs or TI-supported implementations that allow the AUTOSAR NvM module to perform persistent data storage through the lower memory abstraction layers.

For example, I would like to have functionality equivalent to:

NvM_WriteBlock()
    ↓
MemIf_Write()
    ↓
Ea_Write()
    ↓
EEPROM / Emulated EEPROM Driver
    ↓
TI Flash / EEPROM hardware

and:

NvM_ReadBlock()
    ↓
MemIf_Read()
    ↓
Ea_Read()
    ↓
EEPROM / Emulated EEPROM Driver
    ↓
TI Flash / EEPROM hardware

I am not asking for a low-level Flash programming API only. APIs such as Fapi_issueProgrammingCommand() are useful for directly programming Flash memory, but they do not provide the AUTOSAR memory abstraction required between NvM, MemIf, and Ea.

Could you please clarify whether TI provides any of the following:

An AUTOSAR-compatible Ea (EEPROM Abstraction) implementation.
An AUTOSAR-compatible MemIf implementation or integration example.
An EEPROM Emulation driver that can be integrated with Ea.
An example showing how NvM can be connected to TI Flash-based EEPROM Emulation.
Recommended TI APIs or drivers for implementing the following flow:

NvM
 ↓
MemIf
 ↓
Ea
 ↓
EEPROM Emulation
 ↓
TI Flash Driver / FAPI
 ↓
C2000 Flash

If TI does not provide the complete AUTOSAR stack, could you please provide guidance or reference implementations for the Ea and EEPROM Emulation layers that should be placed above the TI Flash API?

The main goal is to implement persistent NVM storage following the AUTOSAR architecture, where the application interacts with NvM and does not directly call TI Flash programming APIs.

Thank you for your clarification and support.

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

?? ?? — Wed, 22 Jul 2026 01:46:38 GMT

Hello,

Thank you for your advice.

I tried the Industrial Communications SDK 2026 and confirmed that the sub-device starts up according to the cycle time when using the debugger.

However, I have encountered a different issue.
When attempting an OSPI boot for a multi-core project that includes this EtherCAT sub-device sample, the system hangs during the initialization process.

The console log is as follows:

DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

Start: load_firmware: cpuId=[255]
Done: Bootloader_Params_init
Done: Bootloader_BootImageInfo_init
Done: Bootloader_open
OK: bootHandle[cpuId] != NULL
OK: Bootloader_parseMultiCoreAppImage
OK: Bootloader_loadSelfCpu
RESULT: load_firmware: cpuId=[1], status=[0]
exec_firmware: cpuId=[1], clkHz=[800000000], rprcOffset=[0x20], entryPoint=[0x00000000]

Pruicss  max =3 selected PRU:3
pRegPerm = 0x30082000, dram1=0x3

Looking at the log, it appears to stop while outputting "pRegPerm = 0x30082000, dram1=0x30082000, offset = 0x00000000, size = 0x00001400".

I tried adding more logging to the software to investigate,
but upon checking the relevant process with the debugger, I found that the output is generated by the function `PRU_EC_FW_load` within `pru_EtherCAT.c` (part of the library `ethercat_subdevice.am243x_lp.r5f.ti-arm-clang.release.lib`), leaving me with no way to investigate further.

Could you please advise me on how to resolve this issue?

I am happy to open a separate thread if necessary.

Kind regards,

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

Harsha Begihally Shanmukhaswamy — Mon, 20 Jul 2026 10:40:02 GMT

Hi,

Thanks for the wireshark logs. I will check and provide you the feedback.

Could you please also test it with the latest Industrial Communications SDK available for AM243x target? INDUSTRIAL-COMMUNICATIONS-SDK-AM243X Software development kit (SDK) | TI.com

Kind Regards,

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

?? ?? — Mon, 20 Jul 2026 10:22:04 GMT

Hello
I will send you the Wireshark log.
The data captured in Wireshark consists of frame logs obtained using the EC-Master's built-in functionality.

However, upon reviewing the Wireshark log, I confirmed that the frames themselves are arriving in accordance with the cycle time.

I would appreciate it if you could check this.

e2e.ti.com/.../20260720_5F00_182542.zip

Kind Regards,

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

?? ?? — Mon, 20 Jul 2026 09:52:59 GMT

Hello
Thank you for your confirmation.

I will provide an answer in advance.

The test configuration is as follows:

Main Device
Board: TMDS64EVM board
Protocol Stack: acontis's EC-Master

Sub-Device
Board: LP-AM243 board
SDK: Industrial Communications SDK ind_comms_sdk_am243x_2025_00_00_08 and the MCU+SDK mcu_plus_sdk_am243x_11_01_00_19
Sample: 401_simple from the Industrial Communications SDK's

Connection Configuration
The test environment is directly connected as follows:
[EtherCAT MainDevice]<----->[EtherCAT SubDevice].

Synchronization Method
Cycle time: 250 µs DC synchronization

Please wait a moment for the Wireshark logs.

Kind Regards,

RE: AM2434: In EtherCAT sub-devices, the callback for reading input process data may not be invoked in some cases. (Continued)

Harsha Begihally Shanmukhaswamy — Mon, 20 Jul 2026 09:11:14 GMT

Hi,

[quote userid="615798" url="~/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1665610/am2434-in-ethercat-sub-devices-the-callback-for-reading-input-process-data-may-not-be-invoked-in-some-cases-continued"]While the Sync0_Isr call interval was 250 µs, the PDI_Isr call interval was approximately 310 µs. Consequently, roughly every four cycles, the Sync0_Isr was triggered before the PDI_Isr, creating the appearance that the output was not being updated every 1 ms. (Synchronization setting: DC synchronization with a 250 µs cycle time.)[/quote]

The PDI Isr call interval should also be ~250us. It is recommended to use the real time port extenders, for example, CU2508 for DC testing.

Could you please share the wireshark logs? Also, could you please verify the minimum cycle time supported and tested by the EtherCAT MainDevice in your test setup?

Kind Regards,

RE: AM2431: Inquiry Regarding CRA Compliance and Industrial Ethernet Security Support

Karim Jamal — Fri, 17 Jul 2026 08:21:25 GMT

the answer is yes.

All Security requirements are part of our Roadmap and be part of next releases.

For early access please reach out to your sales representative

regards

Karim

AM2431: Inquiry Regarding CRA Compliance and Industrial Ethernet Security Support

Lee Uie-Tae — Thu, 16 Jul 2026 07:58:05 GMT

Part Number: AM2431

Dear TI Support,

We are currently developing an industrial communication device based on the AM243x platform using the TI Industrial Communications SDK. Our device supports PROFINET IO-Device, EtherNet/IP Adapter, and Modbus TCP.

As part of our preparation for the EU Cyber Resilience Act (CRA), we are evaluating whether our current product can support the required industrial communication security features.

Could you please provide information on the following?

PROFINET
- Does the TI Industrial Communications SDK have a roadmap to support PROFINET V2.5 Secure Access and Secure Realtime?
- If yes, is there an expected release schedule?
EtherNet/IP
- Does the EtherNet/IP stack provided with the TI Industrial Communications SDK support CIP Security?
- If not, is there a roadmap or any recommended solution for implementing CIP Security on AM243x?
Modbus TCP
- Does TI provide any reference implementation or example for Modbus Security (TLS) on the AM243x platform?
Security Libraries
- Which TLS/DTLS libraries are officially recommended for use with the Industrial Communications SDK (for example, mbedTLS or wolfSSL)?
- Are there any reference examples for integrating TLS/DTLS with industrial communication protocols on AM243x?

Any guidance, roadmap information, or relevant documentation would be greatly appreciated.

Thank you for your support.

Best regards,

RE: AM2431: Inquiry Regarding CRA Compliance and Industrial Ethernet Security Support

PratheeshGangadhar — Fri, 17 Jul 2026 00:19:58 GMT

[quote userid="672252" url="~/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1664845/am2431-inquiry-regarding-cra-compliance-and-industrial-ethernet-security-support"]

PROFINET
- Does the TI Industrial Communications SDK have a roadmap to support PROFINET V2.5 Secure Access and Secure Realtime?
- If yes, is there an expected release schedule?
EtherNet/IP
- Does the EtherNet/IP stack provided with the TI Industrial Communications SDK support CIP Security?
- If not, is there a roadmap or any recommended solution for implementing CIP Security on AM243x?
Modbus TCP
- Does TI provide any reference implementation or example for Modbus Security (TLS) on the AM243x platform?
Security Libraries
- Which TLS/DTLS libraries are officially recommended for use with the Industrial Communications SDK (for example, mbedTLS or wolfSSL)?
- Are there any reference examples for integrating TLS/DTLS with industrial communication protocols on AM243x?

[/quote]

TI is actively working on enabling security support and committed to be CRA ready with industrial communication software stack products.

Schedules at this time are tentative due to development work, qualification etc. involved - EtherNet/IP, Modbus TCP and Security libraries will be available by end of 4Q 26 /1Q 27 timeframe. PROFISEC support is expected by end 2Q/3Q 27.

I suggest getting in touch with TI sales for further details.

AM2434: Inquiry: Frame-Loss Tolerance of PRU-ICSS EtherCAT Slave Sample in DC Sync Mode

Shimodome Ryo — Tue, 07 Jul 2026 22:58:02 GMT

Part Number: AM2434

Dear TI Support Team,

We are developing an EtherCAT slave device using your Industrial Communications SDK, and would like your guidance on the recommended approach to improve frame-loss tolerance in DC Sync mode.

Environment

Target device: AM2434
Industrial Communications SDK version: 2025_00_00_08
Synchronization mode: DC Sync (SYNC0 enabled)
Cycle time: 500 µs

Our Goal

We would like the slave to remain in the OP state even when several process data frames (e.g., 5 to 10 frames) are lost consecutively, while continuing to use DC synchronization.

Questions

In DC Sync mode, with the default TI sample configuration, after how many consecutive lost process data frames does the slave transition from OP to SAFEOP? Also, which AL Status Code is reported in that case?
Could you advise the simplest way to increase frame-loss tolerance? We are considering the following options:
- (a) Modifying only the initial values of ESC registers
- (b) Modifying only the ESI XML / EEPROM settings
- (c) Modifying the TI sample source code
Are there any side effects we should be aware of when applying such changes — for example, DC clock drift, SYNC0 jitter, or impact on ETG Conformance Test compliance?

Thank you very much for your support. We look forward to your response.

Best regards,