• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 553 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.

RTOS/AM4378: Ethercat Master demo build errors

sayali pathak
Expert 1325 points

Part Number: AM4378

Tool/software: TI-RTOS

Hi,

I want to implement the Ethercat Master Demo Code on AM437x Board using CCSv6.2.0

I have implemented code "

EtherCAT Master demo application" given by acontis. when i build the code i got around 16,000 errors that is "Bad Expressions". 

How could I resolve the error?? Is there any problem in locating file??

  • 0
    TI__Mastermind 40580 points

    Hi Sayali, could you please let me know how are you building EC-Master? are you using the correct Processor SDK version? also how did you create the CCS project? or acontis shared it with you? 

    Are using Linux PSDK or TI-RTOS PSDK? 

    Link to AM437x PSDK just for your reference

    Can you copy some of the errors (in a doc, or screen shot) here?

    thank you,

    Paula

  • 0 in reply to Paula Carrillo
    Expert 1325 points

    I imported the code "ECMasterDemoCPSW"from acontis website. When i first time build the code i got the compiler version error. I downloaded the correct compiler version.I downloaded the code from acontis site and import directly in CCS version6.
    I am using TI-RTOS PSDK.
    Now i got the following error:-
    1) cannot find -lsoc
    2) gmake: *** [all] Error 2
    3) gmake[1]: *** [EcMasterDemoCPSW.out] Error 1 
    4) recipe for target 'all' failed
    5) recipe for target 'EcMasterDemoCPSW.out' failed
    I import the file "isoc.c"in this ccs project but still i got the same error.
    Please help me how can i add the file in my ccs project??

  • 0 in reply to sayali pathak
    TI__Mastermind 40580 points

    Hi Sayali, probably a path is not correct.. In attached image I see few of the include paths in light-gray. Maybe iso.c is include in a library that cannot be reach or a path not found.. just a guess.

    In any case, I will take a look tomorrow,

    thank you,

    Paula