From: Philip M. <in...@bi...> - 2014-10-14 14:46:10
|
Avrdude was running in JTAG mode, I tried it in PDI mode: > avrdude -p x128a1 -cjtag2pdi -P usb -U > flash:w:\Projects\XMega\test\Debug\test.hex > avrdude: jtagmkII_setparm(): bad response to set parameter command: > RSP_FAILED > > avrdude done. Thank you. Then I saw that my cabling was not correct and I tried this cabling: http://www.avrfreaks.net/comment/715428#comment-715428 Still the same response, then I saw this: http://www.avrfreaks.net/comment/716360#comment-716360 > > I got PDI to work on the Xplained A1 Board by disabling the JTAGEN > fuse. PDI is apparently made to take priority over JTAG, however this > does not seem to be the case for whatever reason on the A1 Board. > > As of right now i can program and debug with JTAG with the Dragon, Use > PDI (When JTAGEN fuse is disabled) With AVRISP MII. > So, it looks like it's the setup of my board. I will stick to JTAG for the moment. Thanks! On 14.10.2014 16:00, Joerg Wunsch wrote: > As Philip Mulrane wrote: > >> 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: a0 >> recv: 0xcf >> recv: 0xa2 >> CRC OK >> Got message seqno 1 (command_sequence == 1) >> response: A0 > That's trying to switch the emulator mode to PDI, which is > responded by a very informative "failed" (0xa0). :( > > There's unfortunately not much AVaRICE can do here about it. > > You told that AVRDUDE can successfully talk to the chip through PDI, > so this suggests the cabling were OK. Can you verify the initial > command sequence between AVRDUDE and AVaRICE? I tried it here, and > the initial sequence is mostly the same: right after the "sign on" > command, it sets parameter 3 (emulator mode) to value 6 (PDI). -- Bittrace14 UG Immanuel-Kant Str.59b 31812 Bad Pyrmont Fax: +49 32223945096 HRB 209338 Amtsger. Hannover Geschäftsführer Pauline Atkinson |