-
Notifications
You must be signed in to change notification settings - Fork 139
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
[bug #44540] Broken reset mode in jtagmkII_program_enable #377
Comments
I'm not able to reproduce the issue. It may be because my Dragon programmer is a bit flakey at times. I'm able to program the device over JTAG, but I'm always getting the following error at the end, and the program starts immediately.
|
I have not tried jtag node, but dragon_isp mode works fine with my AVR Dragon (tested with ATtiny2313, ATmega328P and ATmega32U4) |
The patch is copied here for easier checking.
|
My jtagmkii stick is a total mess and doesn't work properly. However, the AVR dragon uses the jtagmkii protocol, so I guess we can test this patch using the AVR Dragon. For reference, PR #979 resolves an issue where the program isn't started after programming using JTAG. It may even be that this issue isn't relevant anymore if/when #979 gets merged. |
@mcuee I haven't tried the applied patch, but I can confirm that with #979 applied, the program starts automatically after flashing, even with the OCDEN fuse set. So from what I can see, this issue can be closed as soon as #979 gets merged. But when I look at the patch, I find very similar code in the jtagmkii.c file. Perhaps this has been added in the past, and later re-formatted to replace
|
You are exactly right. This can be closed.
|
Michael Lipp [email protected]
Sat 14 Mar 2015 01:54:50 PM UTC
I think the intended behaviour of trying to enter programming mode first without external reset and then with external reset is broken. The attached patch should fix this.
file #33341: avrdude-progmode.patch
This issue was migrated from https://savannah.nongnu.org/bugs/?44540
The text was updated successfully, but these errors were encountered: