ATmega325 on STK501?

[Ruud Vlaming]

The ATmega325 is listed for the addon device STK502.
i don't have that one, but i have the STK501. And, the atmega325
is pin compatible in all relevant aspects with the atmega64 (supported
on the STK501). So i tried it out, but ... no succes, i cannot
communicate with the device:

./avrdude -C ../etc/avrdude.conf -p m325  -F -c stk500v2 -P /dev/ttyS1 -t
avrdude: stk500v2_command(): command failed
avrdude: stk500v2_recv(): checksum error
avrdude: stk500v2_program_enable(): bad STK600 connection status: Unknown (0x64)
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
avrdude: Expected signature for ATMEGA325 is 1E 95 05

Looking into the avrdude configuation file i see this

#------------------------------------------------------------
# ATmega325
#------------------------------------------------------------

part
    id               = "m325";
    desc             = "ATMEGA325";
    signature        = 0x1e 0x95 0x05;
    has_jtag         = yes;
#   stk500_devcode   = 0x??; # No STK500v1 support?
#   avr910_devcode   = 0x??; # Try the ATmega16 one
    avr910_devcode   = 0x74;

So i played around with some values of these parameters,
but no succes eigther. (0xA0; 0x45;)

But i see no fundamental reason why this is not possible.
Has anyone an idea how to make this working?

Ruud



_______________________________________________
AVR-chat mailing list
AVR-chat@...
http://lists.nongnu.org/mailman/listinfo/avr-chat

[Joerg Wunsch]

Ruud Vlaming <ruud@...> wrote:

> The ATmega325 is listed for the addon device STK502.
> i don't have that one, but i have the STK501. And, the atmega325 is
> pin compatible in all relevant aspects with the atmega64 (supported
> on the STK501).

Nope, it isn't: the historical ATmega103-compatible (mis)routing of
the ISP data lines (PDI/PDO rather than MISO/MOSI) no longer applies
to the 64-pin LCD ATmegas and their LCD-less counterparts.

You could probably try routing the ISP lines manually.  Alternatively,
programming by JTAG ought to work.

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

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


_______________________________________________
AVR-chat mailing list
AVR-chat@...
http://lists.nongnu.org/mailman/listinfo/avr-chat

[Ruud Vlaming]

On Wednesday 02 September 2009 21:07, Joerg Wunsch wrote:

> Ruud Vlaming <ruud@...> wrote:
>
> > The ATmega325 is listed for the addon device STK502.
> > i don't have that one, but i have the STK501. And, the atmega325 is
> > pin compatible in all relevant aspects with the atmega64 (supported
> > on the STK501).
>
> Nope, it isn't: the historical ATmega103-compatible (mis)routing of
> the ISP data lines (PDI/PDO rather than MISO/MOSI) no longer applies
> to the 64-pin LCD ATmegas and their LCD-less counterparts.

Thanks a lot Joerg! Checking the circuit indeed revealed that
connection. I would never suspected that! With this info
it was a piece of cake to get the mega325 running on the
STK501. Just manually connect reset and sck on the isp
connectors, but reroute mosi/miso to pbt2/pbt3 on the
Expand1 connector.

Ruud.


_______________________________________________
AVR-chat mailing list
AVR-chat@...
http://lists.nongnu.org/mailman/listinfo/avr-chat