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). -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ avarice-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/avarice-user
