Vadim Kaushan

I tried to build this example with stable 1.59.0 and nightly compilers and observed no problems. Could you describe your environment? Rust compiler version, RISC-V gcc compiler version, OS version,...

Thanks! Would you like to create a PR to fix the typo?

@agausmann Why do you think the copyright notice text should be included in the *firmware binary*? Why not put the license into a separate file and distribute it along with...

I'm not sure what is the right way of implementing this, but as the first approximation this could be implemented in this driver as a regular method (if the hardware...

I'm not sure I can help you with this. Try reproducing real device's descriptors and endpoint structure in your device.

@bitbegin Did you manage to solve the problem?

The biggest problem so far is testing: I'd like the PR to be tested before merge, not only with GD32V, but also with other STM32 chips to avoid regressions. I...

I used the following chips/boards: STM32F401 (WeAct Black Pill) STM32F407 (XCore407I) - external PHY support testing STM32F429 (NUCLEO-F429ZI) STM32F446 (NUCLEO-F446ZE) STM32F723 (32F723EDISCOVERY) - internal HS+FS PHY testing GD32VF103 (Longan Nano)...

@katyo this PR is completed, but it needs to be rebased to the latest head and then tested again.

Thank you for the information! Do you know if the same problem happens with OTG1_HS?