• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 305 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.

AM2434: Inquiry about linking .lib in SDK ethercat slave beckoff example code

Chen Zhen-Wei
Prodigy 65 points
Part Number: AM2434


Hi,

In our PRU-ICSSG EtherCAT development, we are referencing the SDK example code "ethercat_slave_beckhoff_ssc_demo".

Due to limitations in our MSRAM resources, we place the ecat firmware code in XIP. To achieve this, we removed the link to the ethercat_slave_icss_fwhal.am243x.r5f.ti-arm-clang.release.lib and instead compiled tiescbsp.c directly.

It seems that compiling tiescbsp.c directly also allows normal communication with TwinCAT.

So, my question is:

What are the differences between linking to the ethercat_slave_icss_fwhal.am243x.r5f.ti-arm-clang.release.lib and not linking? Because the example code seems to work without linking to the .lib, and it can still activate the PRU-ICSSG EtherCAT.

  • 0
    TI__Mastermind 27440 points

    Hi ,

    Thanks for your query.

    Chen Zhen-Wei said:
    Due to limitations in our MSRAM resources

    Looks like application is too big to fit in SRAM ?

    Chen Zhen-Wei said:
    Because the example code seems to work without linking to the .lib, and it can still activate the PRU-ICSSG EtherCAT.

    Looks like you are compiling directly the linked FWHAL source file and linking? It should work as well.

    Best Regards

    Ashwani

  • 0
    Prodigy 65 points

    Hi,

    Thanks for your reply.

    Ashwani Goel said:
    Looks like application is too big to fit in SRAM ?

    Yes, we have memory space considerations in our SRAM usage.

    Ashwani Goel said:
    Looks like you are compiling directly the linked FWHAL source file and linking? It should work as well.

    In the SDK example code, we found that excluding the FWHAL library file ( ethercat_slave_icss_fwhal.am243x.r5f.ti-arm-clang.release.lib ) and instead compiling the FWHAL souce code ( tiescbsp.c ) directly seems to still enalbe EtherCAT.

    Therefore, we would like to understand the difference between compiling the source file directly and include the FWHAL library file in the example code.

    Best Regards

  • 0 in reply to Chen Zhen-Wei
    TI__Mastermind 27440 points
    Chen Zhen-Wei said:
    we would like to understand the difference between compiling the source file directly and include the FWHAL library file in the example code.

    You are building source code instead of generated binary. It should not be an issue.

    Regards

    Ashwani