Roel Postelmans
Roel Postelmans
Thanks for the closer look Thomas, the first case should indeed work. I'll check it out
While picoTCP is in the Delaying Member state, a compatibility switch can take place which will cause the final state machine to be in a deadlock. Which is the cause...
The Issue should be fixed in 6ad04feeb5475c3d42144fcdc6fe036cea3d17a6 However I have currently no test setup, I will verify as soon as possible.
That's weird, I will setup the testframework in order to debug it.
Does your virtual machine have a route to the tap device picotcp is using?
The last sha1 seems to fix all the issues I'v seen, but it's a ugly dirty hack but for now the only possible way to be 100% sure, that after...
This script causes 100%Cpu usage on one core, which makes it unusable.
Well, 1. If I use the the official STM32 USB library (yikes), it works fine and I get 3 usb interrupts when receiving a 64 bytes from my linux host...
The issue appears when CFG_TUD_CDC_RX_BUFSIZE CFG_TUD_CDC_TX_BUFSIZE and CFG_TUD_CDC_EP_BUFSIZE have a different definition than CFG_TUD_ENDPOINT0_SIZE. It's still a mystery to me why that is the case