-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyocd does not detect debug probe #68
Comments
Hi, @AILIFE4798 , I haven't tested pyocd. Can the device be detected if you use openocd? |
If possible, could you provide more information about pyocd, such as the version you're using and related commands? |
I have reproduced the problem. It may take some time to adapt pyocd :) |
need change wifi credentials |
ota also does not work |
Some of pyocd's usb operations don't seem to be well adapted. It may take a while to fix this. |
ok |
Hello, you can try the latest code in the master branch. I've done a simple test using pyocd :) |
Sometimes usbip can cause BSOD. For your device, is it always unable to erase? |
yes always hangs for a long time then says no ack received |
usb ip on windows is really not easy maybe better way is to upload hex or bin file via a website and itll get flashed to device |
Well, I don't have too many chips to test. Looks like you have mm32 and gd32 boards? If you use the gd32, will it work? |
It's weird. looks like the behavior is the same between the different chips. I tested it on stm32f103rc and it work well :( |
dont have a f103rc now |
okay i found some problem. we should use 10MHz speed when we use esp8266. pyocd erase -t stm32f103c8 --chip --frequency=10000000 |
esp8266 version worked just fine with usbip on keil i can upload and debug
but i want to erase flash to unlock readout protection with pyocd but it does not detect the debug probe
The text was updated successfully, but these errors were encountered: