avrdude-dev
[Top][All Lists]
Advanced

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

RE: [avrdude-dev] Mega163 problem


From: Egbert Jan
Subject: RE: [avrdude-dev] Mega163 problem
Date: Wed, 22 Nov 2006 15:31:20 +0100

> -----Original Message-----
> From: Joerg Wunsch [mailto:address@hidden
> Sent: Wednesday, November 22, 2006 2:59 PM
> To: address@hidden
> 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).

Hi again J'org.

I hooked up to AVRStudio and tried a chip erase. No problems... No jumpers
were changed, only the serial port changed to the other PC.

Here is the log that AVR studio spits out:

... Some blocks deleted...
Sending packet 11/22/2006 15:19:40.004
(1200ms) > 1B 0A 00 0C 0E
(1200ms) > 10 C8 64 19 20 00 53 03 AC 53 00 00
(1200ms) > 39
Sequence number 10, message size 12, checksum 57
CMD_ENTER_PROGMODE_ISP

Receiving packet 11/22/2006 15:19:40.004
(1200ms) < 1B 0A 00 02 0E
(1180ms) < 10 00 0D
Sequence number 10, message size 2, checksum 13
CMD_ENTER_PROGMODE_ISP
Returned status: Command succeeded

Sending packet 11/22/2006 15:19:40.024
(1000ms) > 1B 0B 00 07 0E
(1000ms) > 12 21 00 AC 80 00 00
(1000ms) > 06
Sequence number 11, message size 7, checksum 6
CMD_CHIP_ERASE_ISP

Receiving packet 11/22/2006 15:19:40.034
(1000ms) < 1B 0B 00 02 0E
(1000ms) < 12 00 0E
Sequence number 11, message size 2, checksum 14
CMD_CHIP_ERASE_ISP
Returned status: Command succeeded

Sending packet 11/22/2006 15:19:40.034
(1000ms) > 1B 0C 00 03 0E
(1000ms) > 11 01 01
(1000ms) > 0B
Sequence number 12, message size 3, checksum 11
CMD_LEAVE_PROGMODE_ISP

Receiving packet 11/22/2006 15:19:40.034
(1000ms) < 1B 0C 00 02 0E
( 970ms) < 11 00 0A
Sequence number 12, message size 2, checksum 10
CMD_LEAVE_PROGMODE_ISP
Returned status: Command succeeded

Any suggestions???
EJ

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

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