We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
see pyocd/pyOCD#1646
Workaround is to use versions earlier than 0.36.
Or use https://github.com/probe-rs/probe-rs - supports the hk32f030m, and is quite a bit faster than pyocd anyway.
The text was updated successfully, but these errors were encountered:
Thank you for the information, I am still using 0.34.3 so I didn't notice the issue. probe-rs looks quite nice, I will have a try later.
Sorry, something went wrong.
Yeah, I'm a fan of probe-rs.
The only real issue I have with it is that its GDB stub is somewhat limited (e.g. it doesn't support GDB 'load').
~/Embedded/HK32F030M-base/Projects/blink$ probe-rs download --chip-erase ./Build/blink.elf --chip hk32f030mf4p6 Erasing ✔ [00:00:00] [--------------------------------------------------------------] 0 B/1.88 KiB @ 0 B/s (eta 0s ) Programming ✔ [00:00:01] [##############################################################] 1.88 KiB/1.88 KiB @ 1.76 KiB/s (eta 0s ) Finished in 1.467s ~/Embedded/HK32F030M-base/Projects/blink$ probe-rs reset --chip hk32f030mf4p6
pyocd takes about 7 seconds, where probe-rs is 1.5.
No branches or pull requests
see pyocd/pyOCD#1646
Workaround is to use versions earlier than 0.36.
Or use https://github.com/probe-rs/probe-rs - supports the hk32f030m, and is quite a bit faster than pyocd anyway.
The text was updated successfully, but these errors were encountered: