Skip to content

Wrong USB Polling Rate #3106

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

Open
1 task done
jun-qu opened this issue Apr 30, 2025 · 0 comments
Open
1 task done

Wrong USB Polling Rate #3106

jun-qu opened this issue Apr 30, 2025 · 0 comments
Labels

Comments

@jun-qu
Copy link

jun-qu commented Apr 30, 2025

Operating System

Windows 10

Board

STM32F427VIT6 demo board

Firmware

tinyusb_min_struct.zip
we pulled the code from your master branch on Apr 4, 2025.

What happened ?

Tested plaftform:
STM32F427VIT6,USB-FS(PA11/PA12), FS Mode, Host
HUB IC: CH334P
Mouse: Logitech G502(set to 1000hz and 500hz)

issue 1:
tested board: STM32F427VIT6 -> CH334P(USB HUB) -> HID MOUSE(1000hz)

What happened:
polling rate can not be kept at 1000hz according to the reported polling rate in the description of a HID mouse

Suspected Cause:
USB HUB IN transter in B channel will interrupt mouse IN transfer in A channel.

issue 2:
tested board: STM32F427VIT6 -> CH334P(USB HUB) -> HID MOUSE(500hz)

What happened:
when IN transfer get some data from the mouse, not NAK.
polling rate can not be kept at 500hz according to the reported polling rate in the description of a HID mouse

Suspected Cause:
This function: tuh_hid_receive_report(dev_addr, instance) is called instantly in this function tuh_hid_report_received_cb(),
we think this kind of usage will bring the issue.

How to reproduce ?

Issue 1: How to reproduce:
connect peripherals as listed here:
STM32F427VIT6 -> CH334P(USB HUB) -> HID MOUSE(1000hz)
you can find the issue on USB with a USB analyzer

Issue 2: How to reproduce:
connect peripherals as listed here:
STM32F427VIT6 -> CH334P(USB HUB) -> HID MOUSE(500hz)
you can find the issue on USB with a USB analyzer

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

no log in need

Screenshots

Issue 1: screenshot
Image

issue 2: screenshot
Image
Image

I have checked existing issues, dicussion and documentation

  • I confirm I have checked existing issues, dicussion and documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant