Hello Joerg, Thank you for your reply. I downgraded the firmware to 7.21 (from AVR Studio 5). It performed differently in that it got receive timeouts when attempting additional commands. I'll spare you the likely useless dumps of debug data that accompanied these tests. Even with this firmware version though, it would still get a return code of 0xAE in certain situations, so at least far back as 7.21 this error code exists. Your output shows 7.24, so.. Hmm.
I attempted to use the Dragon to connect to 2 different XMEGA devices, one is a custom PCB I made with an xmega16d4, the other is a development board with an xmega128d4 using AVR Studio 7 in programming mode. It could read the reference voltage but not the device ID. So I think something is wrong with the interface or I don't know what I'm doing (or both). I'm giving up for now and will have to proceed with the painful process of debugging my code without a real debugger (GPIO ports and a scope). Both of these boards program fine with AVRDUDE and a ZeptoProg II, so the physical interface should work at least. My impression is, that if you can program with the PDI interface, then you should be able to debug with it too right? At least as far as the physical interface goes. Or perhaps there is something I should pay attention to in the design of my PCB circuit? For reference, I tried programming the device with AVR dude and it also returned the same 0xAE error code with the AVR Dragon. As I said though, works fine with the ZeptoProg II. Thanks again and cheers! Element Green On Mon, Oct 19, 2015 at 3:33 PM, Joerg Wunsch <j...@uriah.heep.sax.de> wrote: > > response: AE > > set paramater command failed: Unknwon response code 0xae > > Failed to activate PDI debugging protocol > > That (sadly) probably means they have broke^H^H^H^H^Hchanged the > protocol with their new firmware version. As an indication, error > codes known to me (for the JTAGICEmkII/Dragon protocol) go to 0xAD > by now, so it appears they have added a new code here. > > You might try requesting some explanation from Atmel by opening a case > on their support web site, albeit I'm not very enthuasiastic about the > success of such an inquiry. > > Next step would be to reverse-engineer how Atmel Studio is handling > this situation, sigh. :( > > Here's the transcript from my older Dragon firmware (note that Atmel > usually writes firmware versions in Hex, while AVRDUDE and AVaRICE > in Decimal): > > % ./src/avarice -g -j usb -X -d > AVaRICE version 2.13svn20141210, Jul 13 2015 21:28:57 > > Found JTAG ICE, serno: 00A200007BFE > JTAG config starting. > Attempting synchronisation at bitrate 19200 > > command[0x01, 1]: 01 > recv: 0x1b > recv: 0x00 > recv: 0x00 > recv: 0x1a > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 26 bytes > read: 86 01 ff 18 07 01 ff 18 07 07 00 a2 00 00 7b fe 41 56 52 44 52 41 > 47 4f 4e 00 > recv: 0xfb > recv: 0x39 > CRC OK > Got message seqno 0 (command_sequence == 0) > response: 86 01 FF 18 07 01 FF 18 07 07 00 A2 00 00 7B FE 41 56 52 44 52 > 41 47 4F 4E 00 > Found a device: AVRDRAGON > Serial number: 00:a2:00:00:7b:fe > JTAG ICE mkII sign-on message: > Communications protocol version: 1 > M_MCU: > boot-loader FW version: 255 > firmware version: 7.24 > hardware version: 1 > S_MCU: > boot-loader FW version: 255 > firmware version: 7.24 > hardware version: 7 > > command[0x02, 1]: 02 03 06 > recv: 0x1b > recv: 0x01 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0xcd > recv: 0x83 > CRC OK > Got message seqno 1 (command_sequence == 1) > response: 80 > > command[0x0a, 1]: 0A 01 > recv: 0x1b > recv: 0x02 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0x1d > recv: 0x09 > CRC OK > Got message seqno 2 (command_sequence == 2) > response: 80 > recv: 0x1b > recv: 0xff > recv: 0xff > recv: 0x08 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 8 bytes > read: e0 ff ff 00 00 40 00 00 > recv: 0xee > recv: 0x63 > CRC OKAutomatic device detection: jtagRead > command[0x14, 1]: 14 > recv: 0x1b > recv: 0x03 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0xa2 > recv: 0x88 > CRC OK > Got message seqno 3 (command_sequence == 3) > response: 80 > > command[0x05, 1]: 05 B4 03 00 00 00 00 00 00 00 > recv: 0x1b > recv: 0x04 > recv: 0x00 > recv: 0x04 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 4 bytes > read: 82 1e 94 42 > recv: 0x4e > recv: 0x99 > CRC OK > Got message seqno 4 (command_sequence == 4) > response: 82 1E 94 42 > > command[0x15, 1]: 15 > recv: 0x1b > recv: 0x05 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0x13 > recv: 0x95 > CRC OK > Got message seqno 5 (command_sequence == 5) > response: 80 > Reported PDI device ID: 0x9442 > Configured for device ID: 0x9442 atxmega16d4 > > command[0x36, 1]: 36 02 00 2F 00 00 80 00 00 40 80 00 00 00 8C 00 20 00 8F > 00 27 00 8F 00 00 04 8E 00 00 02 8E 00 00 00 00 01 00 40 00 00 00 10 00 01 > 00 04 20 C0 01 90 00 > recv: 0x1b > recv: 0x06 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0xc3 > recv: 0x1f > CRC OK > Got message seqno 6 (command_sequence == 6) > response: 80 > JTAG config complete. > > command[0x37, 1]: 37 00 00 00 00 00 00 00 00 00 00 00 00 00 > recv: 0x1b > recv: 0x07 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0x7c > recv: 0x9e > CRC OK > Got message seqno 7 (command_sequence == 7) > response: 80 > > command[0x08, 1]: 08 > recv: 0x1b > recv: 0x08 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0xce > recv: 0x2f > CRC OK > Got message seqno 8 (command_sequence == 8) > response: 80 > > command[0x23, 1]: 23 > recv: 0x1b > recv: 0x09 > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0x71 > recv: 0xae > CRC OK > Got message seqno 9 (command_sequence == 9) > response: 80 > > command[0x00, 1]: 00 > recv: 0x1b > recv: 0x0a > recv: 0x00 > recv: 0x01 > recv: 0x00 > recv: 0x00 > recv: 0x00 > recv: 0x0e > sDATA: reading 1 bytes > read: 80 > recv: 0xa1 > recv: 0x24 > CRC OK > Got message seqno 10 (command_sequence == 10) > response: 80 > > > -- > cheers, Joerg .-.-. --... ...-- -.. . DL8DTL > > http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) >
------------------------------------------------------------------------------
_______________________________________________ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
