You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running pyOCD on a virtual machine, with the debug probe connected to a port on a AnywhereUSB remote USB hub. The probe itself is detected correctly-It's a ST-LINK V3. When opening a session with ConnectHelper, the code eventually steps into flush_rx in pyocd\probe\stlink\usb.py. This is the fix I implemented in order to get it working:
Normally, it would get stuck in this while loop forever, never hitting an exception. I also noticed, the rx_buffer was normally an empty list, but in my case it was a list full of 0's. So, to exit the loop, I added a check to see if the rx_buffer only contained 0's.
To clarify, the device and probe connections were all fine. I was able to connect and flash with STMCubeProgrammer for example.
Let me know if you would like any more information.
The text was updated successfully, but these errors were encountered:
I was running pyOCD on a virtual machine, with the debug probe connected to a port on a AnywhereUSB remote USB hub. The probe itself is detected correctly-It's a ST-LINK V3. When opening a session with ConnectHelper, the code eventually steps into
flush_rx
inpyocd\probe\stlink\usb.py
. This is the fix I implemented in order to get it working:Normally, it would get stuck in this while loop forever, never hitting an exception. I also noticed, the
rx_buffer
was normally an empty list, but in my case it was a list full of0
's. So, to exit the loop, I added a check to see if therx_buffer
only contained0
's.To clarify, the device and probe connections were all fine. I was able to connect and flash with STMCubeProgrammer for example.
Let me know if you would like any more information.
The text was updated successfully, but these errors were encountered: