-
Notifications
You must be signed in to change notification settings - Fork 93
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
add support for stlink #13
Comments
I fully appreciate you can use a Pico to do this, but many of us have lots of random ST-Link's - I've an original and a draw full of the cheap clones off eBay. As my IoT devices have long test times, it would be useful to use these ST-Links for monitoring but I can just double up on Pico's if they can be bought in pairs as an alternative. |
I'm guessing the STLink doesn't support multidrop SWD... That would need to be fixed upstream first |
I belive it does on the latest firmware, there's a couple of dual core STM32 parts. |
I believe ST-Link V3 supports multi-drop, but not necessarily earlier versions. In any case someone has to reverse engineer ST-Link's protocol for it since it's a high level adapter, not one where you could twiddle the lines yourself. |
I'm wondering what happened after https://community.st.com/t5/boards-and-hardware-tools-mcus/does-stlink-support-ad-v2multi-drop-swd/m-p/191145 .. No confirmation from ST yet. |
I remember that ST-Link only supports STM32/STM8 MCUs from ST. |
If you want stlink swd support, then ask ST to merge their OpenOCD patches upstream - https://github.com/STMicroelectronics/OpenOCD |
https://github.com/STMicroelectronics/OpenOCD does not implement multidrop for STlinks. |
I am trying to use an stlink to program my rp2040
openocd -f interface/stlink.cfg -f target/rp2040.cfg
And end up with this issue:
/usr/local/bin/../share/openocd/scripts/target/swj-dp.tcl:30: Error: Unknown param: -dp-id, try one of: -irlen, -irmask, -ircapture, -enable, -disable, -expected-id, or -ignore-version
in procedure 'script'
The text was updated successfully, but these errors were encountered: