Part Number: AM263P4

Hi team,

I am using the MCU_PLUS_SDK AM263Px version v11.0 and I am facing issues running ethernet examples. From the logs I suspect issues with MAC Port IOCTL calls. This is causing example failure, failures to read PHY registers and the IOCTL calls to MAC port fail with error codes. 

Can you please help me resolve these errors?

Part Number: AM2612

Hi experts,

Can you please provide the steps to enable Packet time-stamping in CPSW. What changes do I need in my application code and syscfg to enable the hardware time-stamping. Can you provide sample code snippets for the same.

Part Number: AM2612

Hi TI experts,

Can you please help me understand CPSW's InterVLAN feature and provide steps to enable the same.

Part Number: AM2612

  Announcement: Zephyr RTOS Pre-release available on the AM261x SoC!

We’re excited to announce that preliminary support for Zephyr RTOS is now available on the AM261x microcontroller. This integration unlocks a modern, highly scalable, open-source operating system for developers building industrial networking and real-time applications on the AM261x platform.

---

  Why Zephyr on AM261x?

  Getting Started

1. Toolchain Setup

- Install the Zephyr SDK (v0.16.1 or newer).
- Use the recommended GCC‑Arm Embedded toolchain (`arm-none-eabi-gcc >= 10.3`).

2. Clone the Zephyr fork from TI Github

west init -m https://github.com/TexasInstruments/zephyr/tree/am261x/release zephyrproject
cd zephyrproject
west update

3. Select the AM261x LP

Zephyr now ships a ready‑to‑use board definition: `am261x_lp`

west build -b am261x_lp samples/hello_world

4. Flash the Image

Use existing tools like TI Uniflash GUI tool to flash the image. Steps here
More info - Link

5. Debugging

It is recommended to use CCS for flashing & debugging the binary image. Steps here 

More info - Link

6. The key enablement in the first release

Launch Pad support for AM261x
R5F (arch) support for interrupts, Cache, MPU configs
IOMUX controls via pinctrl
Systick support with RTI as Tickless Kernel enablement
MBox Driver enabled in compatibility with IPC notify Layer
UART, GPIO Peripheral Support

  Resources

  Support & Feedback

- Technical Support: Open a ticket in the E2E forum (Tags “Zephyr – AM261x”).
- Community Contributions: Pull requests adding drivers, board configurations, or sample applications are always welcome!

---

  Let’s Build the Future Together!

The AM261x series now has the power and flexibility of Zephyr RTOS at its fingertips. Whether you’re prototyping a Motor Controller or a small robot, Zephyr gives you a modern, open‑source foundation to accelerate development.

Happy coding!

The AM261x & Zephyr Integration Team

Part Number: AM2612

Step-by-Step Guide to running profinet example on LP-AM261x.

Requirements:

1. IND COMMS SDK

2. CCS

3. Compiler

4. Syscfg

5. Uniflash GUI

6. Python and OpenSSL

7. LP-AM261x

Make sure you have installed above requirements. Follow the links/steps below for setting up tools:

https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/10_02_00_15/exports/docs/api_guide_am261x/SDK_DOWNLOAD_PAGE.html

https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/10_02_00_15/exports/docs/api_guide_am261x/CCS_SETUP_PAGE.html

Install all requirements mentioned in requirements.txt (Location - ind_comms_sdk/mcu_plus_sdk/requirements.txt)

/*Navigate to mcu_plus_sdk folder and then run the following command*/
pip install -r requirements.txt

Steps to run the Profinet example:

Overview- The Profinet demo on AM261x-LP supports execution from external flash i.e XIP. So to properly run the example we need to program the sbl_ospi_mcelf and application image(.mcelf) into flash using Uniflash tool, then set boot mode to OSPI, and then we can see successful run logs. Follow the below steps:

1. Open CCS and import the Profinet example in project explorer

2. Build the project and make sure profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf and mcelf_xip image  is generated correctly, see the success log below. If there are any error see this post.

[172] Boot multi-core ELF image: am261x:r5fss0-0:freertos:ti-arm-clang C:/Users/a0492123/workspace_ccstheia/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang/Release/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf ...
[173]python C:/ti/ind_comms_sdk_am261x_10_02_00_15/mcu_plus_sdk/tools/boot/multicore-elf/genimage.py --core-img=0:Release/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.out --output=C:/Users/a0492123/workspace_ccstheia/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang/Release/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf --merge-segments=true --tolerance-limit=0 --ignore-context=false --xip=0x60000000:0x68000000 --xlat=none --max-segment-size=8192
[174] Boot multi-core ELF image: C:/Users/a0492123/workspace_ccstheia/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang/Release/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf Done !!!
[175] .
[176] Boot image: am261x:r5fss0-0:freertos:ti-arm-clang C:/Users/a0492123/workspace_ccstheia/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang/Release/profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.appimage Done !!!
[177] .

3. Take LP-AM261x, put it in dev boot mode. Then, open the Uniflash GUI tool and select 

SBL - sbl_ospi_multicore_elf.release.tiimage (location - ind_comms_sdk/mcu_plus_sdk/tools/boot/sbl_prebuilt/am261x-lp)

Application profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf (location - CCS workspace)

XIP Image - profinet_device_demo_am261x-lp_r5fss0-0_freertos_ti-arm-clang.mcelf_xip ((location - CCS workspace)

Click on load image.

4. After loading is successful. Disconnect the power cable and Change the boot mode pins to OSPI Boot mode

5. Next power on the device and open the UART COM port to see success log of Profinet example:

Connect to PLC: https://software-dl.ti.com/processor-industrial-sw/esd/ind_comms_sdk/am261x/latest/docs/am261x/profinet_device/create_TIA_project.html

software-dl.ti.com/.../pnd_app.html

LP User guide - www.ti.com/.../sprujf1a.pdf

Part Number: AM2612

Hi ASM team, 

I get the following error after trying to build a simple GPIO toggle program on a clean install of the 10_02_00_15 SDK. Have we seen this before? 

All the best,

Ethan Cope

Part Number: MCU-PLUS-SDK-AM263X

Tool/software:

Hi TI experts,

I'm trying to run the sbl_qspi_enet application on AM263x. I see that the documentation (software-dl.ti.com/.../EXAMPLES_DRIVERS_SBL_QSPI_ENET_AM263X.html) mentions about the "enet_uniflash.py" file, which should be present in mcu_plus_sdk/tools/boot folder. I don't see any such file in the v10.02 and v11.0 SDK. Can you please help find the file.

Thanks

Part Number: MSPM0C1104

Tool/software:

Here provide an script to do factory reset with J-Link, there is an readme file to show you how to do it. Important thing is remember to modify the device in open factory_reset.bat and connect the reset pin with J-link.

3678.Factoryreset_Jlink.zip

Part Number: LP-AM261

Tool/software:

Hi TI experts,

I am using TI AM26x MCUs and trying to connect the board to my PC. When I try to connect to a CPU in CCS target configuration & debug window, I see the following error codes in the console:  

CS_DAP_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package xx.xx.xx.xx)
 
-----[An error has occurred and this utility has aborted]----
 
This error is generated by TI's USCIF driver or utilities.
 
The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
 
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

Can you please help me resolve the error?

Part Number: MSPM0L1306

Tool/software:

This thread just for update the BSL_GUI_EXE. Due to some software release limitation, we can't put the MSPM0_BSL_GUI.exe file into our SDK < …\mspm0_sdk_xxxx\tools\bsl\BSL_GUI_EXE >.

It need customer use the source file to generate the MSPM0_BSL_GUI.exe with the open source file in the folder BSL_GUI_source_code. More details please refer to README file. But it need to install some python and some support packages environment that may block some users. Here I will put the MSPM0_BSL_GUI.exe file here and you just need to download and unzip

2480.BSL_GUI_EXE.zip