Here's an issue from the customer may need your help:
A customer's mirror product (DUT) uses the tcpip stack of the TDA2HG chip and has the following issues:
Precondition: 1. Firewall is off. 2.Normal power-on wake-up, start the UT of the DUT, and wait for the DUT communication to stabilize.
Action: Step1. Configure the DUT to enter the time wait state. Step2. Configure the DUT to execute the Abort command. Step3. Tester confirms that the DUT enters the closed state.
Expect result: At Step3: The DUT immediately enters the closed state.
Actual result: At Step3, DUT not entering closed state. The protocol stack phenomenon is that the abort instruction is ignored, TCP_call_abort_03_01, TCP_call_abort_03_02 is passed, proving the abort instruction is valid, but 03 is not in closed state.
What is the specific handling inside the stack? What specification does the protocol stack need to be handled in a way that meets?
Could you help check this case? Thanks.