Vadim Kaushan
Vadim Kaushan
Thank you! I'll try to look into this when I have time. This looks really strange as in your chip these two USB peripherals should be identical.
I don't have any. Maybe someone will implement it one day...
I think that one of the ways to support both FS and HS is to define a superset of registers and use it. Maybe HS register set is already a...
Yes, this crate is outdated, most of the examples are already moved to HALs. It would be nice to update the README of stm32-usbd.
Is it still relevant? If you want to go this way, you need to pass additional feature flags.
I believe Forth language defines this behavior unambiguously. Forth uses a concept of "dictionary" with a specific word search order (newest word first) and you can't compile a new word...
Apparently the project is not migrated: https://github.com/bouffalolab/bl-pac/commit/eb62bbb0c102fa0d8bf18d1c667d479ab6332868
Reproducible both with Lenovo X230 USB 3.0 ports, as well as ACER USB 3.0 hub. Tested with `synopsys-usb-otg` version 0.4.0. OTG_FS works ok against both X230 and ACER USB hub.
May have common root cause with https://github.com/stm32-rs/synopsys-usb-otg/issues/44
For STM32F411 this workaround works: ```rust let dp = Peripherals::take().unwrap(); dp.DBGMCU.cr.modify(|_, w| { w.dbg_sleep().set_bit(); w.dbg_standby().set_bit(); w.dbg_stop().set_bit() }); dp.RCC.ahb1enr.modify(|_, w| w.dma1en().enabled()); ``` This `DMA1EN` is required to keep at least one...