mraja-brooks opened a new issue, #13224:
URL: https://github.com/apache/nuttx/issues/13224

   ### Description
   
   Hello Community,
   
   We have had very interesting issue that we have been struggling for over a 
year now as it is intermittent but being in Semiconductor industry, it is not 
acceptable to our customers.
   
   We are currently running NuttX 9.1.8 with small customization for 
communication on STM32H7.
   
   **Symptom**: 
   
   1. No reply is received from STM32H7 based board, ACK is received for the 
packet 
   2. Any connection like telnet, etc causes code to crash
   3. Putting debugger showed execution thread stuck on Send()
   
   **Things we tried**:
   1. Added timeout on Send: This helped, we now get into retry mode but before 
this change we used to have intermittent timeouts; now we have many more 
timeouts; almost daily!
   2. Added retry on main controller: The sequence is one timeout, disconnect 
socket, wait 3.5secs, connect socket.. all successful. Then resend same message 
to the board; no response is received (if the board gets errno128 due client 
disconnecting socket, then no response is received by the client, but if error 
was 116 then we do get response)
   3. In the process of upgrading to 12.6 hoping the changes in stack helps 
resolve the issue
   
   We also send unsolicited messages from the board which we believe every now 
on then do not get to the client. Please let us know if you need more info; I 
can share the code as needed.
   
   Few other things:
   We use KSZ8051 on some boards and KSZ8895 PHY on other boards
   Original issue was reported on boards that are daisy chained over KSZ8895 
but since we made change #1 we are seeing the issue on all boards.
   
   Thank you in advance.
   
   
   ### Verification
   
   - [X] I have verified before submitting the report.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to