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.

AM2432: how to enable KUNBUS ethernet/IP and Lwip at the same time

Part Number: AM2432

Hi Expert,

Could you let me know whether or not we can use both KUNBUS stack for EIP and Lwip stack for general TCP/IP (eg. for applications using tftp, http) in parallel?

I would like you to revisit the link below and update your current status.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1084486/am2432-is-ethernet-ip-supporting-standard-tcp-ip-as-well/4014412#4014412

FYI, when I tried to simply link Lwip library into the example of KUNBUS EIP in SDK 08.02.00.31, there were lots of the "redefined Lwip function" errors during compilation, which means the KUMBUS EIP library has already included a part of Lwip core. I think if KUNBUS EIP had linked Lwip library externally as one application using Lwip, other applications could have used Lwip core stack without any problem. I was wondering the reason why they included a part of Lwip core inside of their library. Please correct me if my idea is wrong.

I would appreciate it if you share a plan of SDK including this feature Or your experience and knowledge about how to enable/use both at the same time with the current SDK version.

Regards,

Moonil

  • Hi

    Could you let me know whether or not we can use both KUNBUS stack for EIP and Lwip stack for general TCP/IP (eg. for applications using tftp, http) in parallel?

    Yes, technically it is possible to use. But it is not possible with our current SDK  example.

    FYI, when I tried to simply link Lwip library into the example of KUNBUS EIP in SDK 08.02.00.31, there were lots of the "redefined Lwip function" errors during compilation, which means the KUMBUS EIP library has already included a part of Lwip core. I think if KUNBUS EIP had linked Lwip library externally as one application using Lwip, other applications could have used Lwip core stack without any problem. I was wondering the reason why they included a part of Lwip core inside of their library. Please correct me if my idea is wrong.

    Your understanding is correct. Right now, lwip sources are built as a part of EtherNet/IP Adapter stack library directly and therefore it leads to redefinition issues.

    I would appreciate it if you share a plan of SDK including this feature Or your experience and knowledge about how to enable/use both at the same time with the current SDK version.

    It is not possible with current SDK version. We plan to enable separate lwIP build in SDK 8.4 (August) release.

    Regards
    Dhaval