Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Inconsistent Driver Errors on STM32F0 #2509

Closed
1 task done
JMattChiam opened this issue Mar 5, 2024 · 0 comments
Closed
1 task done

Inconsistent Driver Errors on STM32F0 #2509

JMattChiam opened this issue Mar 5, 2024 · 0 comments
Labels

Comments

@JMattChiam
Copy link

Operating System

Windows 10

Board

STM32F072 Custom Board

Firmware

STM32CubeIDE configured following #633 with tusb_config.h to use RHPORT 0 and USB Full Speed instead of High speed.

Main firmware:
examples/device/midi_test
usb_descriptors.c identical to example, other than changing product name.

What happened ?

I'm new to USB and trying to get my custom STM32F072 MIDI controller recognized by windows. I've followed the steps outlined in #633 for my needs and the project builds and uploads fine onto the board.
Windows seems to have a hard time with the controller. Sometimes it connects fine and receives the MIDI messages, other times I get driver errors. Infuriatingly, there seems to be a few different behaviors (as shown on USB devices):

  • USB Composite device (Working correctly)
  • USB Composite device (driver error)
  • Actual device name (Working correctly)
  • Actual device name (driver error)
  • Unknown USB device (Device descriptor request failed)

I've found that for the ones with "driver error", it is encountering error 10 ("This device cannot start").
I've attached three wireshark logs if it helps (one for working correctly, one driver error, and one detected as USB composite device and not working). It seems that the one that works correctly includes a SET_INTERFACE request and response, which is missing from both not working ones.

Wireshark captures.zip
Start Line numbers:
Correct name, driver error: 67
Correct name, working: 63
USB composite device, driver error: 83

Additionally, uninstalling the device on device manager, then clicking "scan for hardware changes" sometimes fixes the issue.

How to reproduce ?

NA

Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)

NA

Screenshots

No response

I have checked existing issues, dicussion and documentation

  • I confirm I have checked existing issues, dicussion and documentation.
Repository owner locked and limited conversation to collaborators Mar 5, 2024
@HiFiPhile HiFiPhile converted this issue into discussion #2511 Mar 5, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

1 participant