Currently, we start pyocd with the option --reset-break. This causes a failure for my device (PSoC62).
If runToMain is true, it works normally near as I can tell. Otherwise, while it does stop at the reset vector but if I do a continue and a pause, I get no/bogus stack trace, no threads, etc.
But if I remove the --reset-break arg, everything works like normal whether runToMain is true or false. This puzzled me for a long long time until I found the culprit arg.
I recommend removing this default command-line argument as it has been deprecated and causes problems. I think the new behavior naturally does the break on reset. Also, there is no way to undo the default args that I know of -- even with serverArgs
Currently, we start pyocd with the option
--reset-break
. This causes a failure for my device (PSoC62).If runToMain is true, it works normally near as I can tell. Otherwise, while it does stop at the reset vector but if I do a continue and a pause, I get no/bogus stack trace, no threads, etc.
But if I remove the
--reset-break
arg, everything works like normal whetherrunToMain
is true or false. This puzzled me for a long long time until I found the culprit arg.I recommend removing this default command-line argument as it has been deprecated and causes problems. I think the new behavior naturally does the break on reset. Also, there is no way to undo the default args that I know of -- even with
serverArgs
I already made the changes and can make a PR soon