-
Notifications
You must be signed in to change notification settings - Fork 76
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
Usage with global allocator #110
Comments
usb-device doesn't use allocator, so the problem is located somewhere else. |
Ok, I found out that with the debugger, it hangs in this line:
line 365 in full output of the debugger:
|
Please check that clocks are correct and 48MHz clock is supplied to the USB peripheral. |
I agree, it looks like there is a clock issue.. |
It appears that usb-device works when compiled with default rust, but it fails when compiled with nightly (no changes in the code, just added '+nightly' to the cargo build command). Should I open another issue for that? (FreeRTOS requires nightly because of the allocator, that's why I noticed it) |
I think the best approach is to reduce the software to a minimal version which reveals the difference between stable and nightly and then file a bug to |
I ran into this as well. Linking the related issue chain for reference, in case anyone else has the same issue: stm32-rs/stm32f4xx-hal#567 |
Fixed in stm32-rs/synopsys-usb-otg#34 |
I have been using this library on my STM32F405 and it has work flawlessly with interrupt polling:
The setup is as follows:
However, now I am trying to use it with a FreeRTOS wrapper for rust which requires nightly build with a global allocator:
and now the USB setup fails, I assume the allocations conflict? Does anybody have an idea on how to mitigate this?
The text was updated successfully, but these errors were encountered: