2022-06-23 07:41 AM
Hi,
lately I realized that there are tracer errors from the USB-C stack in STM32CubeMonitor. I haven't seen them with older version of the USBPD libraries.
Currently I'm using:
- FW pack STM32Cube_FW_G0_V1.5.1
- USBPD core library is now V4.0.0
- USBPD device library is now V3.3.1
Where do these errors come from?
Thanks!
BR, Christoph
Solved! Go to Solution.
2022-06-24 12:28 AM
Hello @Christoph Rüdisser
I don't have issues on my side, but I'm using STM32CubeMonitor-UCPD 1.2.0.
What is your version ?
The parts of trace that you are missing are related to USBStack notifications, or ErrorRecovey CAD states.
2022-06-23 10:06 AM
Hello @Christoph Rüdisser
Could you please share the .cpd file so that we can replay the trace on our side to try to see what is wrong ?
Wiki : The trace files are saved in c:\Users\%username%\AppData\Local\Temp\STM32CubeMonitor-UCPD\Acquisition\ with ".cpd" extension.
Thanks
Nicolas
2022-06-24 12:13 AM
Hi @Nicolas P
Thanks for your fast response.
I have attached the cpd file, but I had to remove the filename extension (uploading a cpd file was not allowed).
I've connected and disconnected the STM32G071B-DISCO multiple times, selected different PDOs, initiated datarole swaps and hard resets. I think there is still a problem with hard resets, but I thought I should fix the tracing at first.
The trace contains several of the following errors:
Thanks,
Christoph
2022-06-24 12:28 AM
Hello @Christoph Rüdisser
I don't have issues on my side, but I'm using STM32CubeMonitor-UCPD 1.2.0.
What is your version ?
The parts of trace that you are missing are related to USBStack notifications, or ErrorRecovey CAD states.
2022-06-24 01:05 AM
Hi @Nicolas P
I didn't realize that a new version of the CubeMonitor-UCPD is available. I was still using 1.1.1.
With 1.2.0 there are no error messages anymore.
Thanks for your help!
Christoph