• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 299 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.

AM5718: TCP socket server drops connection to client and stops responding to pings

Chris Liegel
Prodigy 20 points
Part Number: AM5718

Hello,

We are running a TCP socket server (TI-RTOS - NDK network stack) task on IPU2-Core0 and GMAC port 0 of the AM5718 SOC.

Recently we believe we may have observed an anomaly in our system related to a previous forum post linked here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/840450/ccs-am3359-tcp-ip-drops-connection. After a period of time the network interface seems to stop communicating, and the interface no longer responds to pings. 

Similar to the poster, setting _RTNoTimer = 1 of stack file C:\ti\processor_sdk_rtos_am57xx_06_03_02_08\ndk_3_61_01_01\packages\ti\ndk\stack\route\rtable.c seemed to be a "workaround" for us. However, we are concerned with possible side effects of disabling the ARP table refresh requests.

Near the end of the post:

This section suggests the fixes to this particular problem will be included in the "next release".

I looked through various NDK stack version change logs and haven't been able to find a mention of this bug being fixed.

Can you verify that this problem is indeed resolved in the latest version (v3.61.1.01) of the NDK stack?

System library versions:

SYS/BIOS: v6.76.3.01

am57xx PDK: v1.0.18

NDK: v3.61.1.01

Regards,

Chris Liegel

  • 0
    TI__Mastermind 31584 points

    Hello Chris,

    Unfortunately this does not seem like it was ever fixed, I found the related internal JIRA and the fix was put off to NDK version NDK_3_85_00 Which will never be available for AM57. For now and the foreseeable future the AM57 RTOS SDK is on maintenance mode. See software-dl.ti.com/.../Release_Specific_Release_Notes.html

    This was not considered to be fixed since the issue was not very reproducible internally on our EVMs and the original reporters had mostly seen this on the Beaglebone Black EVM.

    In conclusion, I believe the workaround you have implemented is the only option available.

    Best,

    Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 20 points

    Hello Josue,

    We are concerned to see your statement above stating the "AM57x RTOS SDK is on maintenance mode". What does this mean exactly? Is this AM57x platform not being supported long term? I cannot find any statements about this SOC not being recommended for new designs. Why is AM57x not getting NDK stack updates?

    I see a statement on the NDK site stating:

    So, it appears the network stack is being obsoleted.

    What are TI's plans going forward. Is there a new network stack in the works, or can you recommend third-party stacks that can be interfaced to the AM57x SDK, and are well supported?

  • +1 in reply to Chris Liegel
    TI__Mastermind 31584 points

    Hello Chris, 

    Chris Liegel said:
    We are concerned to see your statement above stating the "AM57x RTOS SDK is on maintenance mode". What does this mean exactly?

    This means that there will be no updates made to the SW.  Essentially, the statement on TI .com for the NDK is the same for TI RTOS on AM57x.

    Chris Liegel said:
    What are TI's plans going forward. Is there a new network stack in the works, or can you recommend third-party stacks that can be interfaced to the AM57x SDK, and are well supported?

    TI plans to maintain this with no new development. Essentially, between releases there will only be minimal High Priority bug fixes to maintain functionality.

    With respects to this issue, as mentioned before, this was not reliably reproducible so it was never considered for a fix.

    Best,

    Josue