[GitHub] [incubator-nuttx] edsut commented on issue #6531: IMXRT USB speed may need to be forced to FULL when CONFIG_USBDEV_DUALSPEED is not configured

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

edsut commented on issue #6531:
URL: https://github.com/apache/incubator-nuttx/issues/6531#issuecomment-1172586030

   @acassis  I did post the question there prior to this... https://discuss.px4.io/t/mavlink-hardfault-on-usb-connection/27856
   No response.
   My gut says its not QGC specific (my hunch is still that it is deep in the USB driver).
   Prior to enabling CONFIG_USBDEV_DUALSPEED, I was able to cause the crash with a snippet of code that just wrote a large chunk of data to USB (see https://discuss.px4.io/t/possible-bug-in-imxrt-usb-interface/28005).  Now (with CONFIG_USBDEV_DUALSPEED enabled, that reproduction snippet doesn't crash, so at the moment my only way to reproduce it is with certain interactions with QGC.
   One new bit of information...
   I wrote a Linux program that monitors the connection between QGC (on laptop) and my Teensy4.1.  With that inserted between the two devices the above crash does NOT occur!!  Clearly with that inserted, buffering is different from end-to-end, but data (messages sent between the two) should be identical. 


-- 
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