Closed saper closed 3 years ago
Hi! You are right - the instructions here are a bit outdated at the moment. I will update them a bit. In the meantime, the recent OpenOCD is working just fine, and in fact it is used in one of the development helpers [1] available in the repo. Hopefully the development guide at [2] will be more resourceful too.
[1] https://github.com/Nitrokey/nitrokey-pro-firmware/blob/master/Makefile#L52 [2] https://github.com/Nitrokey/nitrokey-pro-firmware/blob/master/DEVELOPMENT.md
Corrected in 9e2489bbd03275eb9be74e88b70aa923c8ffc335. Closing as done.
Wow! Perfect, this is was fast. I think we can remove https://github.com/Nitrokey/nitrokey-pro-firmware/blob/master/scripts/flash-versaloon.sh from both branches I guess...
Indeed, we had not used it for a while. Actually, this script should be valid when used stlink-v2
instead of the versaloon provided right now. Will keep in mind to correct that next time. PR's are always welcomed :-)
I understand "PR's are always welcomed" as "Nitrokey GmbH sends me 10 engineering devices for free"? Geee
In this particular case I meant a simple change in the docs / running scripts if you have already introduced them in your fork / locally. We do however support hobby development with hardware/development samples, assuming it covers at least some of our targets. If you are interested in such please let us know over email at support@nitrokey.com
.
One of the OpenOCD forks listed is dead and in the another one can't find the
vsllink-swd.cfg
file. But it seems that OpenOCD itself supports SWD for quite a long time (just tried 0.11.0 release with some other ARM Cortex-M chip and it worked).Maybe just using
transport select swd
would work?(don't have a SWD-enabled token yet to try)