0
\$\begingroup\$

I am trying to make a PoC USB device using STM32WB55RGV6 (using their dev kit p-nucleo-wb55 board&dongle). I started with just following STM's example code for USB HID device (using mouse profile). However I am unable to get the device recognized on the host. dmesg is filled with errors like below (I don't have a Linux box at hand now to see which errors it would be there):

128548.104118 IOUSBHostFamily::validateEndpointMaxPacketSize: USB 2.0 5.[5-8].3: endpoint 0x00 invalid wMaxPacketSize 0x0083
128548.104852 IOUSBHostDevice@00221000: IOUSBHostDevice::start: bNumConfigurations of 0 is not permitted
128548.107384 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to start device
128548.107436 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to create device (0xe00002e9), disabling port
128549.184845 IOUSBHostFamily::validateEndpointMaxPacketSize: USB 2.0 5.[5-8].3: endpoint 0x00 invalid wMaxPacketSize 0x0083
128549.185685 IOUSBHostDevice@00221000: IOUSBHostDevice::start: bNumConfigurations of 0 is not permitted
128549.188256 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to start device
128549.188298 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to create device (0xe00002e9), disabling port
128550.279460 IOUSBHostFamily::validateEndpointMaxPacketSize: USB 2.0 5.[5-8].3: endpoint 0x00 invalid wMaxPacketSize 0x0083
128550.280305 IOUSBHostDevice@00221000: IOUSBHostDevice::start: bNumConfigurations of 0 is not permitted
128550.282835 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to start device
128550.282875 AppleUSB20HubPort@00221000: AppleUSB20HubPort::resetAndCreateDevice: failed to create device (0xe00002e9), disabling port

What I've tried so far -- working through a clock frequencies as was advised for STM32F MCUs (but WB uses crystal-less USB implementation, which I understand would isolate USB from HSE/LSE clocks), regenerating code with older versions of SDKs (since people commented that new version is full of bugs), etc. All end up in same errors.

Meantime I've found this errata for this series of MCU's. Which makes me think that is perhaps what I am seeing (even though my APB clock is well above 8 at a 32MHz).

Now, my question is: is there any way to workaround this issue without having external USB controller on a board?

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.