• State Resolved
  • Replies 13 replies
  • Subscribers 30 subscribers
  • Views 277 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM2434: INDUSTRIAL-COMMUNICATIONS-SDK-AM243X v11.x, EthertNet/IP, unsufficient stack size

Vit Triska
Prodigy 60 points
Part Number: AM2434


Tool/software:

Hello,

I see stack overflow in precompiled EtherNet/IP Industrial SDK, specifically in the FreeRTOS task named "packet". How to enlarge the "packet" task stack in case the EtherNet/IP is already precompiled?
Applied: INDUSTRIAL-COMMUNICATIONS-SDK-AM243X v11.x (the same issue in 11.00.00.08 as well 11.00.00.13).
Screenshot attached.

Regards,
Vit

  • 0
    TI__Intellectual 1870 points

    Hi Vit,

    In general, the task size for internal tasks used by EtherNet/IP stack are currently not configurable from the application side. I'll inform you whether this will be added as a feature in the next release.

    Out of curiosity, are you establishing numerous Explicit messages? The default size is actually quite sufficient for most use cases, so I'm interested in understanding your specific requirements.

    Best regards,
    Pourya
  • 0 in reply to Pourya Eskandari
    Prodigy 60 points
    Pourya Eskandari said:
    Out of curiosity, are you establishing numerous Explicit messages? The default size is actually quite sufficient for most use cases, so I'm interested in understanding your specific requirements.

    How to control/set/limit them?

  • 0 in reply to Vit Triska
    Prodigy 60 points

    And which tasks the EtherNet/IP creates in the background?
    Just this 4 - the "LinkTask", "RxTask", "phymdix task" and "packet" (my issue)?
    What size (each of them)?

  • 0 in reply to Vit Triska
    TI__Intellectual 1870 points

    Hi Vit,

    you are not supposed to limit the communication, my question was targeted to understand the context in which your problem happens.
    In short, the "packet" task's stack usage could go high when there are heavy UDP and TCP communication going on on your device.
    Have you maybe changed priority in the tasks (in app.c) ?

    Regards,
    Pourya

  • 0 in reply to Pourya Eskandari
    Prodigy 60 points

    Truth, EtherNet/IP communication priority is almost the highest from all tasks. But it is the default as your EthertNet/IP example.

    In case the UART driver is fixed to local temporary array as requested (because DRV_UART_printf(***) needs to be reentrant!), the stack overflow arise in case the EtherNet/IP communication (with PLC) is runned.

    Screenshot attached to see all priorities and the issue.

  • 0 in reply to Vit Triska
    Prodigy 60 points

    Please fix these two bugs as soon as possible (immediatelly), because the "packet" task stack overflow bug really blocks me from finishing the project (due in 2 days, 30/09/2025). This is not a complex error (moreover fully explained), so I think you don't need more than 0.5 days to fix it.

    Please keep me informed of the progress.
    Thank you in advance.

  • 0 in reply to Vit Triska
    TI__Intellectual 1870 points

    Hello Vit,

    Unfortunately, you'll need to wait for the next release to address this issue. If you require expedited or customized stack support, I recommend contacting your local TI Sales office to discuss potential solutions.

    In the meantime, you can resolve this problem by optimizing your application to reduce "packet" task stack memory consumption. Consider implementing these modifications:

    1. Examine any callbacks registered for your objects and eliminate large arrays or big structures within them.

    2. Review services added to your objects and similarly avoid incorporating large arrays or structures in these services.

    These optimizations are within your control, and with appropriate adjustments, you should be able to prevent stack overflow issues in the "packet" task.

    Best regards,
    Pourya

  • 0 in reply to Pourya Eskandari
    Prodigy 60 points

    How long the release cycle is? (A week, month, year ...?)
    And when is the next release planned?

  • 0 in reply to Vit Triska
    TI__Intellectual 1870 points

    Hi Vit,

    I cannot provide exact date, but the next release should be available in November.

    Best regards,
    Pourya

  • 0 in reply to Pourya Eskandari
    Prodigy 60 points

    Hello, please, what is status of this issue (insufficient stack size in "packet" task inside Industrial Communication SDK 11.00.00.xx of "EthertNet/IP")?

  • 0 in reply to Vit Triska
    TI__Intellectual 1870 points

    Hello Vit,

    The configurable internal task stack size is a feature planned for future releases. However, due to shifted priorities, this change will likely not be included in the next release.

    Regards,
    Pourya

  • 0 in reply to Pourya Eskandari
    Prodigy 60 points

    And will the task stack size at least be enlarged (approx. +512 bytes) in the next release (though not configurable yet)?

  • +1 in reply to Vit Triska
    TI__Intellectual 1870 points

    Hello Vit,

    We will not increase the task stack size for the "packet" task in the upcoming release, as this adjustment is tailored to your specific use case and would otherwise lead to increased memory consumption, reducing available memory for the application and end users. 

    The better solution would be the configurable task stack size, which is unlikely to be part of the next release.

    Regards,
    Pourya