• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 245 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: EIP stack : Adapter does not response the "register session " and " connection manager"

sigong
Prodigy 250 points
Part Number: AM2432

Tool/software:

Hi experts,

As is show in the below.

Why the adatpter does not response  "register session "  and  " connection manager" of scanner? The abnormal Adapter's ip is 192.168.1.115.

And now,the eip communication is abnormal.

02.zip

Thanks.

  • 0
    Prodigy 250 points

    Here is another adapter's packets in 02.zip .And this is true.

    We found the phenomenon in a power-on and power-off experiment.

  • 0 in reply to sigong
    TI__Mastermind 26230 points

    Hi ,

    Thanks for your query.

    As our Ethernet/IP expert is out of office, response may be delayed.

    Regards

    Ashwani

  • 0 in reply to sigong
    Prodigy 250 points

    Here is the abnormal adapter's terminal output.

    In the end,I made the soc restart because of debug.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    tcp_err_handler: Connection reset. (-14)
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    tcp_err_handler: Connection reset. (-14)
    tcp_err_handler: Connection reset. (-14)
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    0x1 0x40 0x2 0x60 0x27 0x43 0x4 0x43 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x1 0x60 0x0 0x60 0x2d 0x0 0x1 0x1 0x16 0x1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
    tcp_err_handler: Connection reset. (-14)
    tcp_err_handler: Connection reset. (-14)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to sigong
    TI__Intellectual 2400 points

    Hi ,

    Can you please share information regarding the following:

    1. Which SDK version are you using?
    2. Which SDK example are you using?
    3. Are you running the example on a TI EVM or a custom board?
    4. What is the test topology where this issue is encountered?
    5. What is the test procedure where you encounter this issue?

    Regards
    Archit Dev

  • 0 in reply to Archit Dev
    Prodigy 250 points

    Hi,

    Thanks for the response.And below is the answer of  question.

    1. ind_comms_sdk_am243x_09_02_00_08;

    2. the example used is located in the way of "C:\ti\ind_comms_sdk_am243x_09_02_00_08\examples\industrial_comms\ethernetip_adapter_demo\device_profiles\generic_device\mii\am243x-lp";

    3.It is a custom board;

    4.

    5.We found this issue by conducting power-on and power-off experiments on eight EIP boards simultaneously. In the end,the issue occurred in one of them and its ip is "192.168.1.115".Please refer to the wireshark record for more details.

    sigong said:
    02.zip
  • 0 in reply to sigong
    TI__Intellectual 2400 points

    Hi ,

    Thank you for the detailed response.

    In order to isolate whether the issue occurs on the communication only with the EthernetIP Stack or the lwIP stack as well, can you try pinging the DUT where the failure has occurred ? Does the ping to that device return a successful response?

    Also, can you try unplugging and replugging the Ethernet cables to the DUT where the failure has happened? Does it help in the resolution of the issue?

    Regards
    Archit Dev

  • 0 in reply to Archit Dev
    Prodigy 250 points

    Hi,

    I tried pinging the DUT when the issue occurd and found the device return a successful response not every time. Mostly,the successful pecent is 25% or none.

    I did not try unplugging and replugging the Ethernet cables to the DUT.

    Thanks.

  • 0 in reply to sigong
    TI__Intellectual 2400 points

    Hi ,

    We have identified and fixed some critical bugs in the stack and have seen the stability improve with these.

    We are currently running a week-long test (till Friday, 23rd August) to confirm the working of the fixes. If no issues occur, we shall share the fixes next week.

    Your patience is really appreciated.

    Regards
    Archit Dev