-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Description
Describe the bug
USB MSC test failed when using test tool USB3CV, below is the screenshot:
Per debug, Zephyr can receive command A8 and 9E from USB3CV, and Zephyr USB protocol layer has handled the command, but in low layer(probably ST driver? not sure) can't send out the response to USB3CV, lead to test failed(100% reproduced).
Regression
- This is a regression.
Steps to reproduce
Configurations:
CONFIG_USB_DEVICE_STACK_NEXT=y
CONFIG_USB_MASS_STORAGE=y
CONFIG_MAIN_STACK_SIZE=2048
CONFIG_USBD_PID=0x0045
CONFIG_USBD_VID=0x128d
CONFIG_USBD_PRODUCT="xxx Test kit"
CONFIG_USBD_MANUFACTURER="xxx CO.,LTD"
CONFIG_USBD_MSC_CLASS=y
CONFIG_USBD_MSC_LUNS_PER_INSTANCE=3
CONFIG_DISK_ACCESS=y
CONFIG_DISK_DRIVERS=y
CONFIG_FILE_SYSTEM=y
CONFIG_FAT_FILESYSTEM_ELM=y
CONFIG_UDC_STM32=y
CONFIG_USB_DC_STM32=n
Steps:
- Install USB3CV on Windows 11
- Choose USB device on USB3CV
- Run Compliance Test
- Test failed in 100%.
Relevant log output
Impact
Annoyance – Minor irritation; no significant impact on usability or functionality.
Environment
- OS: Windows 10/11
- USB3CV: v3.1.8.0
- Zephyr version: 4.1.99/35af7b88b369a1aaa469e214b20c7f3c50a79f52, zephyr-sdk-0.17.0
Additional Context
No response