USB Communication Error

[Sebastian Juch]

Posted on April 11, 2018 at 09:42

Hi,

strange problem here.

With STM32 ST-LINK Utility V4.10 & V4.20 i got an USB communication error with ST-Link/V2 Firmware V2J28S7, V2J29S7 and V2J30S7. With Version V2J30S7 and STM32 ST-LINK Utility V4.20 i got

OLD ST-LINK firmware/ST-LINK already used

under Settings.

With Firmware Version V2J23S4 i had not this problems.

I found this in the Trace Log.

SB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00

ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00ST-Link get version failureThe detected STM32 firmware version (V0.J0) does not support the DAP read command.

Thanks in advanced.

Sebastian

[kerp0w]

Posted on June 14, 2018 at 11:42

I've seen this as well... and I know some other members of our team have seen a similar issue.

I resolved it once before by replacing a DLL, I can't remember what or where I got the DLL from.

I also fixed it by using a fresh copy of windows, someone else just moved the device to a different USB port and that worked... so not really sure what the exact solution is or the root cause.