AM2612: SysConfig processor package migration issue

Part Number: AM2612
Other Parts Discussed in Thread: SYSCONFIG,

Hi,

In my previous thread (https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1693024/am2612-sysconfig-peripherals-from-multiple-sdks), you told me that the only way to have project with both EtherCAT and position encoder is to use example from motor SDK.

I want to configure a project for ZEJ package to run on a custom board, so I imported bissc_diagnostic_dual_channel_am261x-lp_r5fss0-0_freertos_ti-arm-clang example and tried to change package

2026-11-17 16_25_55-CCStudio IDE.png

I get the following error

2026-11-17 16_04_44-CCStudio IDE.png

I did this test with all exact versions required by motor SDK

2026-11-17 16_16_22-CCStudio IDE.png

I also tried with newer SysConfig version:

  • 1.28.1 -> same issue (with 500 MHz variant)
  • 1.28.2 -> SysConfig is unabled to open file

I also tried to remove biss-C and PRU (ICSS) before doing the migration. Migration is working but I can't re-enabled biss-C

2026-11-17 16_36_17-CCStudio IDE.png

What is the solution to have a project with biss-C + EtherCAT on a ZEJ package?

Regards

  • Hi Gildas,

    The error is a SysConfig/SDK metadata gap for ZEJ, not a hardware limitation on your custom board.

    • The BiSS-C module's pinmuxRequirements() requests a PRU_ICSSG0_PRU interface that is not defined in the device/pinmux metadata for AM261x packages, confirmed on ZNC, same class of issue on ZEJ 1.
    • Root cause confirmed: the AM261x Industrial Communications SDK infrastructure originally did not support ZEJ/ZNC because we had no EVM in those packages, which directly produces these pinmux/interface resolution failures when migrating to ZEJ 2.
    • Our engineering team traced the concrete bug for the analogous EnDat case to device-detection logic in the SDK .meta JavaScript (e.g. source/drivers/.meta/pruicss/m_v0/ in MCU+ SDK and source/.meta/position_sense/endat/am26x_pins.js + endat.syscfg.js in Motor Control SDK), which calls common.getDeviceName() instead of common.getSocName(). TI supplied a fix replacing the check with common.getSocName() == "am261x" and stated the same change is required for the other position-sense modules, explicitly including BiSS-C 3.
    • We confirmed this is a tooling bug, not a user error: PRU-ICSS GPIO/pinmux options are visible on ZFG but missing or broken on other AM2612 packages, with a TI engineer stating "Raised a bug, It will be fixed in next sdk release" 1.

    The silicon is fine: PRU-ICSS (2 instances) exists on all four packages including ZEJ 4, and the data sheet defines ZEJ-specific PRU-ICSS pins (e.g. PR0_MDIO0_MDC at ZEJ K16, PR1_MDIO0_MDC at ZEJ A14) 5.

    Why removing and re-adding BiSS-C doesn't help (task 2)

    Removing BiSS-C and PRU (ICSS) only removes the consumer of the broken metadata — it does not add the ZEJ definitions. On re-add, addInstance() runs pinmuxRequirements() again, which still resolves to the ZFG-only PRU_ICSSG0_PRU interface, so the same exception reappears. Because the defect is in the SDK .meta device-detection code 3, upgrading SysConfig alone cannot fix it — consistent with 1.28.1 reproducing the identical error. This class of failure has been reported across SysConfig 1.23.1, 1.25, and 1.27 with multiple SDK generations, confirming it tracks the ZEJ metadata gap rather than a specific tool build 21.


    Recommended path for BiSS-C + EtherCAT on ZEJ (task 3)

    The combination itself is valid: the AM2612 reference design TIDUFF7 implements two BiSS-C encoders plus an EtherCAT stack simultaneously, splitting encoder and Ethernet MAC duties across the two PRU-ICSS cores 6. BiSS-C firmware runs on PRU0 of PRU-ICSSM1, with the remaining PRUs reserved for Industrial Ethernet 7. So your problem is tooling, not architecture.

    Steps, in priority order:

    1. Request the ZEJ-enabled Industrial Communications SDK. Our software team released an updated Industrial Communications SDK with ZEJ package support, distributed only via the AM261X-EARLY-SDK early-access request portal on ti.com, not the public SDK download 2. This path addresses the root cause rather than patching around it.
    2. Patch the .meta device detection in your installed SDKs as the interim workaround: replace common.getDeviceName() checks with common.getSocName() == "am261x" in source/drivers/.meta/pruicss/m_v0/ (MCU+ SDK) and the BiSS-C files under source/.meta/position_sense/ (Motor Control SDK) 3. We also shared a complete replacement archive of the Motor Control SDK .meta/position_sense directory to overwrite the originals for exactly these ZCZ/ZEJ/ZNC migrations request that file rather than hand-editing 3.
    3. Keep the project linked to the Industrial Communications SDK. The plain MCU+ SDK does not contain the "TI INDUSTRIAL COMMS TOOLKIT" module, so EtherCAT pinmux/PRU-ICSS configuration is only possible with the Industrial Communications SDK 2.
    4. Assign the two peripherals to non-conflicting PRU resources. EtherCAT in SysConfig sets "ICSS Instance" and a CONFIG_PRU_ICSS* pinmux config in the PRU (ICSS) TI Drivers module 8. Note that on AM2612 ZEJ specifically, industrial Ethernet (EtherCAT/PROFINET) must be implemented via the ICSS_EMAC module on PRU-ICSS1 — not ICSSG0 as on the ZCZ/ZFG LaunchPad — with the shared PRU-ICSS1-MDIO bus feeding both PHYs in dual-port designs 9. Since BiSS-C occupies ICSSM1-PRU0 7, confirm the exact slice split with TI for your dual-channel BiSS-C + EtherCAT case.
    5. Preserve the BiSS-C clocking constraint after migration: ICSS UART clock must be exactly 160 MHz when the ICSS core clock is 225 MHz 10. This matters because you tested a 500 MHz variant — re-verify the clock tree after any variant change.


    1. E2E: AM2612 SysConfig – how to set PRU-ICSS GPIO
    2. E2E: AM2612 SysConfig error when switching package
    3. E2E: AM2612 endat_diagnostic_single_channel with ZCZ/ZEJ/ZNC
    4. AM261x Technical Reference Manual (SPRUJB6B)
    5. AM261x Data Sheet (SPRSPA7C)
    6. TIDUFF7A Reference Design Guide
    7. Motor Control SDK: BiSS-C Design
    8. Ind. Comms SDK: EtherCAT Subdevice ICSSG0 Usage Guide
    9. E2E: AM261x ZEJ PROFINET pinout for 2 ports
    10. Motor Control SDK: BiSS-C

    Best Regards,

    Zackary Fleenor

  • Hi,

    Your answer is really clear as usual.

    However, I'm not able to access to your links to thread about early-access or to thread about complete replacement archive (may be due to '---internal' in the path)
    Could you send me, may be by private message, the links to request early-access and to download replacement archive.

    Do you know when future release of MCU+, industrial communication and motor SDKs are planned

    Thanks
    Gildas