• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 359 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM6422: Cannot load CCS Profinet project for AM6442 in 8.06 SDK

Jens Nissen
Prodigy 10 points
Part Number: AM6442
Other Parts Discussed in Thread: AM6422,

I have installed the SDK 8.06 (besides 8.03, 8.04, 9.00) to start developing a Profinet device application for AM6422.

I follow the instructions from

file:///C:/ti/mcu_plus_sdk_am64x_08_06_00_48/docs/industrial_protocol_docs/am64x/profinet_device/page_quickstart_ti.html#page_quickstart_ti_run_debug

  • Make sure TI MCU-PLUS-SDK-AM64X version: 08.06.00.22 is used
  • When using CCS projects to build, import the CCS project for the required combination and build it using the CCS project menu. See an example of this process on Using SDK with CCS Projects.

but already the "When using" step - importing the CCS project "profinet_device_demo" fails - error message is

See details below...
Import failed for project 'profinet_device_demo' because its meta-data cannot be interpreted. Please contact support.

What I already noticed is:

- The instructions state that SDK 8.06.00.22 is required, but I got 8.06.00.48, there is no 8.06.00.22 SDK

- The API description at file:///C:/ti/mcu_plus_sdk_am64x_08_06_00_48/docs/industrial_protocol_docs/am64x/profinet_device/modules.html describes a KUNBUS Profinet SDK, but sources, libraries and the demo itself is definitely from Siemens.

How can Ioad / build the example and is there an updated documentation?

EDIT 1: I can install other examples like the RTOS Task Switching sample
EDIT 2: Resource Explorer in Offline mode does not show the SDKs 8.04, 8.06 or 9.00. Only the "Latest" and the ancient (my first installed SDK) 8.03 are visible
EDIT 3: From 8.03 I can load the KUNBUS Profinet Example - but that's not, what I want
EDIT 4: I had messed up the processor name: Should say AM6442, not AM6422 

  • 0
    TI__Intellectual 2135 points

    Hi ,

    Can you add this path "C:\ti\mcu_plus_sdk_am64x_08_06_00_48\source\commercial\industrial_comms_libs" under "Product discovery path:" of CCS as shown below.
    This should add an entry called "MCU+ SDK Industrial Communications Libraries" under "Discovered products:" as shown below. Try to import the project now and see how it behaves. Can you share the screenshot of the error message if this doesn't work?



    Thanks,
    Naresh Kumar A

  • 0 in reply to Naresh A
    Prodigy 10 points

    Setting the path slightly changes the behaviour, now I get a different error.


    See details below...
    Import failed for project 'profinet_device_demo' because its compiler definition is not available. The project does not appear to be a CCS Project. Please try importing it using the 'General > Existing Projects into Workspace' wizard.

    If I follow the suggestion of the error box, then I can open the project, but all relevant settings for building the project are missing now and compilation leads to 


    gmake: *** No rule to make target 'all'. profinet_device_demo C/C++ Problem
     

    Sidenote. I would add a screenshot, but if I select "Insert" / "Image/Video File", a dialog pops up, but the dialog will not allow entering a path to my screenshot. My browser is Chrome.

  • 0 in reply to Jens Nissen
    TI__Intellectual 2135 points

    Hi ,

    You can copy the image and paste it in this text box itself. I assume that using will be using the correct tool chain.
    I am unable to reproduce the error which you are facing.
    I am able to imp[ort and compile the project without any issues.



    Thanks,
    Naresh Kumar A

  • 0 in reply to Naresh A
    Prodigy 10 points

    I deleted the SDK from the file system and reinstalled it from scratch. Looks like the industrial comms folder did not install correctly on my first try - now it works.