This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2631: SDK Compactibility

Part Number: AM2631

Hi Experts,

My customer is adding the industrial comm sdk 9.02 and the mcu+ sdk 11.0 to the same project, and have the below error when opening the syscfg: 

image.png

Looks like the two sdk is not compatiable.

Although industrial comm sdk v9.02 already contains mcu+ sdk v 9.02, customer needs mcu+ sdk v11.00 for the supports of mcelf image generation and the mcelf sbl supports, which is required by the tifs functions. 

They need the industrial comm sdk for ethercat functions. for now, they have two CCS projects

  1. Standard function project,with TIFS configuration, using mcu+ sdk 11.00
  2. EtherCAT project, using industrial comm sdk 9.02

They need to merge to two projects and the best is the add EtherCAT to the standard project. To do so we need to solve two issues:

  1. How to make the two sdk compatiable?
  2. How to merge the syscfg file? Standard project syscfg do not have ethercat options

 

Regards,

Hang

  • Hi Hang,

    Please note that it's not recommended to use two different versions of SDK together.

    Standard project syscfg do not have ethercat options

    If you change the dependent product options of the project, you can see Ethercat in the syscfg

    Also is it possible that customer can migrate to latest version on IND COMMS SDK?

  • Hi Nilabh,

    I believe the latest version of ind comms sdk is v.10.00, I assumes it contains the mcu+ sdk 10.00 right? We need sdk v11.00 for the security features. Does industrial comm SDk tested with TIFS sdk?

    Please note that it's not recommended to use two different versions of SDK together.

    Could you provide an suggestion on with combination should we use to achieve security and tifs at this point?

    Is it possible to integrate the EtherCAT functions to the standard project which uses mcu+ sdk? 90% of work is done in the standard project, it could really reduce the work load and risk if we can add EtherCAT based on the standard project but not the other way around.

    Regards,

    Hang

  • One way would be to use the .out generated by ethercat project separately and feed it to the post-processing script, which generates the .mcelf image. I believe it would be the simplest way forward.

    genimage.py

    Python script used to generate multicore elf image from individual core elf images.

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/latest/exports/docs/api_guide_am261x/TOOLS_BOOT.html

    Let see if the below id possible or not

    Is it possible to integrate the EtherCAT functions to the standard project which uses mcu+ sdk? 90% of work is done in the standard project, it could really reduce the work load and risk if we can add EtherCAT based on the standard project but not the other way around.

    Rega

  • Hi Nilabh,

    I believe the EtherCAT functions should be integrated in their standard project, or the other way around. I am not sure how generating a .mcelf from the EtherCAT project itself can help... 

  • Hi Hang,

    What I am suggesting is that if the Ethercat project is not interacting with multicore environment, i.e. sending data or talking to other core over ipc, then they could just use the.out/.elf generated in ethercat project , use the post processing script to generate the final .mcelf image

  • Otherwise if it is an IPC project, they will need to migrate to new sdk, in order to make sure the project works properly