avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] Mega163 problem


From: Joerg Wunsch
Subject: Re: [avrdude-dev] Mega163 problem
Date: Wed, 22 Nov 2006 14:59:12 +0100
User-agent: Mutt/1.5.11

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).

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]