At some point after 5.11 avrdude started leaving the target stopped upon completion of a JTAG transaction. I filed a github issue about this issue: https://github.com/avrdudes/avrdude/issues/366 This is super annoying because, for example, the target does not boot after JTAG programming. Others were seeing this and shortly after 7.0 was released, MCUdude created a PR which has since been merged: https://github.com/avrdudes/avrdude/pull/979 Here's a patch to apply this PR.
Created attachment 236323 [details] patch
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=dc3fbc6a0213e8f02348d29695254253440ce254 commit dc3fbc6a0213e8f02348d29695254253440ce254 Author: Craig Leres <leres@FreeBSD.org> AuthorDate: 2022-11-26 21:13:27 +0000 Commit: Craig Leres <leres@FreeBSD.org> CommitDate: 2022-11-26 21:13:27 +0000 devel/avrdude: Add patch for AVR Dragon JTAG fix that didn't make it into 7.0 At some point after 5.11 avrdude started leaving the target stopped upon completion of a JTAG transaction. I filed a github issue about this issue: https://github.com/avrdudes/avrdude/issues/366 This is super annoying because, for example, the target does not boot after JTAG programming. Others were seeing this and shortly after 7.0 was released, MCUdude created a PR which has since been merged: https://github.com/avrdudes/avrdude/pull/979 Apply this patch. PR: 266186 Approved by: joerg (maintainer timeout, 12 weeks) devel/avrdude/Makefile | 2 +- devel/avrdude/files/patch-src_jtagmkII.c (new) | 13 +++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-)
Seriously, I don't see much point in pulling individual patches out of an ongoing development. Where would you want to stop, which patches to include? I would have preferred to wait until AVRDUDE 7.1 is released.
(In reply to Joerg Wunsch from comment #3) Sorry about that, I was just trying to solve a problem I've been banging into since 2014 and I never received any maintainer feedback on this PR.