Answering to my own post... > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > ] On Behalf Of Egbert Jan > Sent: Wednesday, November 22, 2006 3:11 PM > To: 'Joerg Wunsch'; [email protected] > Subject: RE: [avrdude-dev] Mega163 problem > > > > -----Original Message----- > > From: Joerg Wunsch [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, November 22, 2006 2:59 PM > > To: [email protected] > > Cc: Egbert Jan > > Subject: Re: [avrdude-dev] Mega163 problem > > > > > > As Egbert Jan wrote: > > > > > Previous commands succeeded; they returned the values as expected. > > > Next is the failing command (it is much longer than all previous > > > commands): > > > > > avrdude: Send: . [1b] . [0b] . [00] . [0c] . [0e] . [10] . > > [00] . [00] > > > . [00] . [00] . [00] . [00] . [00] . [ac] S [53] . [00] . > > [00] . [fd] > > > avrdude: Recv: . [1b] > > > avrdude: Recv: . [0b] > > > avrdude: Recv: . [00] > > > avrdude: Recv: . [02] > > > avrdude: Recv: . [0e] > > > avrdude: Recv: . [10] > > > avrdude: Recv: . [c0] > > > avrdude: Recv: . [cc] > > > avrdude: stk500v2_command(): command failed > > > avrdude: initialization failed, rc=-1 > > > > Command 0x10 is ENTER_PROGMODE_ISP (the command code is > > always the 6th octet sent to the STK500). I think that's the > > first command where the STK500 is actually going to talk ISP > > to the target (everything before has been setting up the > > parameters in the STK itself). So if that fails, it means > > the target isn't responding at all. Either one of the > > connections is not OK, or ISP programming had been disabled > > somehow (which on the ATmega163 could only happen through > > high-voltage parallel programming as there is no JTAG), or > > the target's clock is not operational (perhaps due to a wrong > > fuse setting). > > TNX so far. I'll hook up to the windows/AVRstudio again. It > can also make a detailed trace. I seem to remember that the > fuses looked OK but the ISP enable was grayed out with a > question mark. I'll be back... > > CU > Egbert Jan
It seems that avrdude doesn't fill in some essential values in the CMD_ENTER_PROGMODE_ISP command (10). On the AVRStudio I get: Command timeout $c8 (200) ms Delay pin stability $64 (100) ms Cmdexedelay $19 (25) ms Syncloops $20 (32) Byte delay 0 ms Poll value $53 (for AVR) Poll index $03 (for AVR) Why are these al 0 with avrdude? Should they have been returned with previous CMD_GET_PARAMETER calls? Egbert Jan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
