-
Notifications
You must be signed in to change notification settings - Fork 2k
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
dist/openocd.sh: added shutdown to flash commands #2471
Conversation
Does this fix the problem for STM32f4 as well? |
yapp. That problem was no real problem, it was just because of my own stupidity... |
actually without this PR the stm shows the same behavior than the atmel board with the newest OpenOCD version... |
hm, but there seems to be some other trouble - Make is exiting from |
Like I've written in #2470. ;) |
ups, that part I did not read... |
ok, here is a small workaround - what do you say? |
Can't you figure out why openocd exits with a non-zero exit code? |
probably, but not at the moment... |
Then at least add a comment in there. |
I made a patch for OpenOCD: OlegHahm/openocd@61c1263 To me it looks like that the command value for shutdown is interpreted as an error value without this patch. |
The behavior was introduced in openocd-org/openocd@a35712a8 |
So ... the comment should point to the issue (which has to be created first?) over at openocd? |
#2472 should do the trick in a sensible way. |
How about we merge this, but leave #2472 open until newer OpenOCD versions are available in most distributions (preferably even in Ubuntu LTS)? |
We have issues that are open for far more time and I hope that even Ubuntu people aren't that slow. Ignoring the OpenOCD return value is not a clean solution in my opinion. |
true |
dist/openocd.sh: added shutdown to flash commands
Seems upstream openocd got fixed. See #2897. |
But OpenOCD in Ubuntu is still 0.8, right? |
fixes #2470