zephyr: drivers: USB MSC: STM32U585: can't pass Compliance Test by using USB3CV

Describe the bug

USB MSC test failed when using test tool USB3CV, below is the screenshot:

Image

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:

  1. Install USB3CV on Windows 11
  2. Choose USB device on USB3CV
  3. Run Compliance Test
  4. 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

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 16 (7 by maintainers)

Most upvoted comments

@marwaiehm-st When you scroll down your html test report, you will see the command fails when handling 0xA8 & 0x9E.

Note: below 2 screenshots are from your test report.

Image Image

@marwaiehm-st Not only “Command Set Test.”, the first two tests also fail on my side. So we are having the same test result now. We need all of test cases passed.

@testo-jeff Thank you for the response.

I have reproduced the issue on my side as well. In my case, the first two tests also fail consistently.

Please find below screenshots illustrating the test failures: Image Image

In addition to the failures on commands 0xA8 and 0x9E, I am also seeing failures on the following SCSI opcodes during the USB MSC compliance test:

  • 0xAA
  • 0x15
  • 0x55
  • 0x2F
Image

Additionally, I have shared the full MSC test report for reference: MSC Tests - Failed - 2025-07-08 14-40-13.zip

Based on your USB MSC test capture, it appears your failures are limited to the “Command Set Test.” Could you please confirm if that is the case?

For context, I am testing on the board b_u585i_iot02 (BU585IIOT2A$GT1, MB1551_U585I_C02).