Follow-up Comment #3, bug #37942 (project avrdude):
That firmware's behaviour is really strange, but I noticed you've also
got a earlier hardware revision than me (6 vs. 7), no idea whether
that makes a notable difference. The result codes are really
unexplainable. 0x84 in response to "program enable" is the result
code for "read PC", but it rather starts that your Dragon is not
generating the expected "break" event after the "program enable".
Likewise, the response 0x80 to the "read memory" command (for the
signature) is quite odd. 0x80 is just "RSP_OK", but of course, a
"read memory" command expects "RSP_MEMORY" (0x82) in return.
Curious, do you have the chance to downgrade the Dragon's firmware to
an earlier version?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?37942>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
avrdude-dev mailing list
avrdude-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
