New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gadget0 failing control loopback test #592
Gadget0 failing control loopback test #592
Conversation
WIKI proposal how to test usb (linux) :
|
Aim here is to make the loopback test behave the same way as the linux kernel gadget 0 loopback test. (Late thoughts, this is control req loopback? not data loopback?) |
It's definitely a control transfer.. (loopback like..)
the device fails in the first step with the word-loss error)
|
nvic_enable_irq(NVIC_OTG_HS_IRQ); | ||
|
||
volatile int i = 1; | ||
while (i); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"while (i)" ? Is there something else modifying "i" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, it's just a while (1) asm(""); or maybe even while (1);
i'm never sure what the compiler is going to optimise out in the end
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the standard "while (1) {} " construct is pretty invincible, and compiles always to an endless loop.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
I've pulled an ~equivalent ctrl loopback test code locally, (and can confirm some of the other bugs) but I've based it more on the linux gadget0/intel compliance code, rather than making up our own new codes for it. Will close this once it lands. |
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 FIXME Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 FIXME Current status is passing on f3, f0, and failing on f4.
These tests (or equivalent) have merged, along with the fixes for them. thanks for pushing on this. |
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Note that this captures the currently broken control loopback issues on dwc_otg devices. See libopencm3#873 and all linked issues. Current status is passing on f3, f0, and failing on f4.
This is based on linux's gadget0 intel loopback tests, and also github pr: libopencm3#592 Note that this captures the currently broken control loopback issues on dwc_otg devices. See libopencm3#873 and all linked issues. Current status is passing on f3, f0, and failing on f4.
Contents