UAC2.0 on STM32

[EvSap]

Hello! I am trying to make USB Audio class 2 device based on STM32 MCU.
Hardware: a board with STM32F722 and external USB HS PHY.
Software: USB Audio class 1 example from ST as a base. I changed USB desctriptor and add code for new entites requests and made board work in HS mode. But in device manager in Windows the device appears with exclamation mark. USB Descriptor analyzer shows no errors. USB traffic analyzer shows no errors. But after some actions on the bus - IOCTL_USB_GET_DEVICE_CHARACTERISTICS (ioctl 0x00220480) 134, 135 positions in log - the device gets "Surprise Removal". Investigating MCU software by means of debugger ended up without any certain results: application is running, no faults detected.
I am confused by this situation and do not know what further steps I should take to get the device enumerated properly. Any help would be much appriciated.

Spoiler: USB analyzer log

 

[bohrok2610]

As part of the enumeration Windows UAC1&2 driver will make several control requests to the device to find out the device characteristics. Your device probably does not send correct response to some of those requests. You should debug (or add logging) the setup functions in your code.

This may also prove useful:
https://matthewvaneerde.wordpress.c...gs-for-microsofts-usb-audio-2-0-class-driver/

 

[EvSap]

Thank you for reply. Yes, I definitely missed something I cannot find out. Moreover, I have another UAC2.0 device that is enumerated properly. I compared two USB logs - of my not working device and of a working one - they are absolutely the same except for behaviour after positions 134, 135: not working device gets "Surprise Removal" and the working one gets endpoint reguests and ends up enumeration properly. Something wrong happens with IOCTL_USB_GET_DEVICE_CHARACTERISTICS (ioctl 0x00220480). But how can one detect what exactly is happening here? As I understand during IOCTL_USB_GET_DEVICE_CHARACTERISTICS host does not send requests to device. Instead it gathers information from internal PC USB hubs.

 

[bohrok2610]

Have you checked the Windows UAC2 driver logs (see my previous reply)?

 

[EvSap]

I am on this way. Thanks for the link, it should shed light on the situation. I need some time to get and check logs. I will provide results.

 

[EvSap]

I have just took a look into Event Viewer. It registered error: source - usbaudio2; Event ID - 16.

Error description: "A system call failed. The specific status code is contained in this event."

Event data:
Words
0000: 00000000 00000001 00000000 C0440010
0010: 00000000 C000028C 00000000 00000000
0020: 00000000 00000000

Bytes
0000: 00 00 00 00 01 00 00 00 ........
0008: 00 00 00 00 10 00 44 C0 ......DÀ
0010: 00 00 00 00 8C 02 00 C0 ......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Investigating...

 

[EvSap]

I did not manage to decode log by TMF files as described on the link. I tried all of them and always the same error appeared:

"UAC2_log.elf"
+ CategoryInfo : ParserError: ( : ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnexpectedToken

It is like the TMF files are old and incompatible with current Windows version.
In device manager problem state is 0xC000028C. That is another mysterious number.

 

[bohrok2610]

What Windows version are you using?

 

[EvSap]

Windows 10 Pro 21H2 19044.2251

 

[EvSap]

Actually I could not even manage to get "tracefmt.exe" from Microsoft. I have Visual Studio installed, but "tracefmt.exe" is not with it as it is said on Microsoft docs. I installed "Windows Kits 10". But again, "tracefmt.exe" is not with it. Finally, I found "tracefmt.exe" somewhere on the Internet.

 

[bohrok2610]

I have a newer version and TMF files for 2004 do work. Can you list the commands you used for collecting the logs.

 

[EvSap]

I have been experimenting some time, and now got the following situation. I get the error described above when "tracefmt.exe" is launched from not system disk. When it is placed in " C:\Windows\system32\" I am faced with another situation:

Anyway log file is always generated (attached).

 

[EvSap]

Tried collecting log to different disks. The result is always the same.

 

[bohrok2610]

There should not be a backslash at the end of tmf -path (-p option).

Here is the log output.

At least proper response for sampling frequencies request is missing.

 

[EvSap]

Thank you very much for help! I am going to investigate the log file.
I want to understand where in my cmd mistake is. I deleted backslash at the end of tmf -path but got the same message

Could you please point what is wrong in cmd with tracefmt?

 

[bohrok2610]

You should probably have single quotes around the path in -p option.

 

[EvSap]

Thank you very much! I managed to decode log file.
You were right about proper response for sampling frequencies request: frequenies bytes were disordered. Now the device is enumerated without exclamation mark and appears in sound devices list. But it is not working yet .
Thank you for your time!

 

[NickKUK]

Hehe you sound about the same position as me - check out the ADC thread in the equipment subforum. There’s some good points about the rate of frames to prevent over/under run and errors in windows.

 

[EvSap]

Thanks, NickKUK. I am porting the rest part of ST example to hardware I have. I will give feedback.

 

[NickKUK]

Thanks, NickKUK. I am porting the rest part of ST example to hardware I have. I will give feedback.

The ST example is UAC1 so it has a slower frame rate, UAC2 with microframes and a few more things. There is a different UAC record/playback example but that doesn’t really follow the firmware layout!