• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 105 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.

AM6421: Ethernet/IP stack Issue

Nikhil Jarande
Intellectual 420 points
Part Number: AM6421

Tool/software:

For Ethernet/IP stack following are queries

1) get_attribute or set_attribute callbacks are blocking API which was affecting cyclic data If data is not immediately available. Is this issue resolve ? Somewhere in e2e forum its mention your are moving LWIP stack packet buffer memory dynamic to static. As we getting memory errors !

2) is Patch mention in Forum for Ethernet/ip stack available with new Industrial SDK 11 ? Is this same issue mention in point one ?

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1471366/am6421-ethernet-ip-class-1-connection-gets-interrupted-by-class-3-connection/5675175?tisearch=e2e-sitesearch&keymatch=ethernet%252Fip%2520blocking%2520API#5675175

Thanks for your support ...

  • 0
    TI__Prodigy 10 points

    Hello Nikhil,

    Yes, the issue with blocking of cyclic data (Class 1) by get_attribute or set_attribute callbacks (Class 3) described in attached link of E2E thread is fixed. The fix is already available in IND_COMMS_SDK 11.00.

    LWIP is using PBUF_POOL memory allocation type. This means that memory is allocated in initialization phase based on configuration parameters located in lwipopts.h file. In runtime the packet data are stored to the pre-created PBUF_POOL memory. Due to that, there is no need to dynamically allocate the memory when packet is received.

    With best regards
    Jiri