[GitHub] [incubator-nuttx] slorquet commented on issue #7138: stm32h7 UART drain problem

[GitBox <gi...@apache.org>]

slorquet commented on issue #7138:
URL: https://github.com/apache/incubator-nuttx/issues/7138#issuecomment-1274320139

   Hi,
   
   I'm already on :
   
   nsh> uname -a
   NuttX 10.3.0-RC0 40144a652d
   
   The bug has disappeared thanks to our programming tricks. I have no time 
   to test again.
   
   But the echo shell command shows this behaviour easily if needed.
   
   I think the device->close() operation incorrectly flushes the tx queue 
   instead of waiting for drain.
   
   Sebastien
   
   
   Le 11/10/2022 à 09:02, Alin Jerpelea a écrit :
   > Hi 
   > @slorquet<https://urldefense.com/v3/__https:/github.com/slorquet__;!!JmoZiZGBv3RvKRSx!7anlEGW9HhZz5Um-coXutgI3V586d1CKOjhQENBtbIhhAyNmq2t-bVyRRVjN9Hms6sSxxFgGlVcZ0byGsRQ8v7_dig$>,
   >
   > 10.0 or 10.1 should be good candidates for this test
   >
   > Best regards
   > Alin
   >
   >
   > From: slorquet ***@***.***>
   > Sent: den 20 september 2022 14:09
   > To: apache/incubator-nuttx ***@***.***>
   > Cc: Subscribed ***@***.***>
   > Subject: Re: [apache/incubator-nuttx] stm32h7 UART drain problem 
   > (Issue #7138)
   >
   >
   > It's quite related to accurate implementation details, eg if an app 
   > sends a frame and waits for an answer, this wait will allow the 
   > transmission.
   >
   > My case is touchy since I found the bug by using "fire and forget", I 
   > send a frame and dont wait for any answer before closing,
   >
   > Picking differences from reference manuals will be tedious. I'll try 
   > that later.
   >
   > Do you recommend a particular mid-2021 release to test?
   >
   > Thanks.
   >
   > —
   > Reply to this email directly, view it on 
   > GitHub<https://urldefense.com/v3/__https:/github.com/apache/incubator-nuttx/issues/7138*issuecomment-1252262855__;Iw!!JmoZiZGBv3RvKRSx!8SxKNe0D3lm0Y7QcJl6NP8BAXZR_h8Pl4bPN5u4AUx2nkLQVGZWYa91G4pQ9jro1xmcG7bR18zltGu2TpLnkXCRADw$>, 
   > or 
   > unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AB32XCRXQGMMFEWZFJ553CTV7GSPDANCNFSM6AAAAAAQQ5VGEE__;!!JmoZiZGBv3RvKRSx!8SxKNe0D3lm0Y7QcJl6NP8BAXZR_h8Pl4bPN5u4AUx2nkLQVGZWYa91G4pQ9jro1xmcG7bR18zltGu2TpLnS58VwNA$>.
   > You are receiving this because you are subscribed to this 
   > thread.Message ID: ***@***.******@***.***>>
   >
   > —
   > Reply to this email directly, view it on GitHub 
   > <https://github.com/apache/incubator-nuttx/issues/7138#issuecomment-1274180072>, 
   > or unsubscribe 
   > <https://github.com/notifications/unsubscribe-auth/AAVEVNMG2OLDFHTWLCO53ILWCUGJ7ANCNFSM6AAAAAAQQ5VGEE>.
   > You are receiving this because you were mentioned.Message ID: 
   > ***@***.***>
   >


-- 
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: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org