Maker Pro
Maker Pro

Programming ATMega8515

R

russ lyttle

I'm trying to program ATMega8515's using STK500 and have not had any
luck. I've programmed ATMega16's and AT90S8515 OK with 3 Stk500 boards,
but get device ID errors with ATMega8515's. I've also looked on the
Atmel site, but haven't found the right FM to read.
thanks
 
T

Tom

russ said:
I'm trying to program ATMega8515's using STK500 and have not had any
luck. I've programmed ATMega16's and AT90S8515 OK with 3 Stk500 boards,
but get device ID errors with ATMega8515's. I've also looked on the
Atmel site, but haven't found the right FM to read.
thanks
Is your STK-500 firmware up to date?
 
R

Rich Webb

I'm trying to program ATMega8515's using STK500 and have not had any
luck. I've programmed ATMega16's and AT90S8515 OK with 3 Stk500 boards,
but get device ID errors with ATMega8515's. I've also looked on the
Atmel site, but haven't found the right FM to read.

The "usual" problem with programming AVRs is that they typically
(all?) come from the factory set to use the internal RC oscillator as
the clock source and that oscillator is typically (always?) set, or
divided down, to 1 MHz.

If the STK500's programming clock is higher than 1/4 of that then
programming will fail. Check the "settings" button under the Main tab
from the STK500 window in AVR Studio.

A good test is to *always* do a signature check before trying to
program. If the signature is wrong or cannot be read then something's
amiss.

Once you're talking to it reliably, set the fuses as needed if you're
using an external clock source or crystal.
 
R

russ lyttle

Tom said:
Is your STK-500 firmware up to date?
Thanks for the reply
Perhaps not. I updated AVR studio4, then updated firmware with the
version on my harddrive. Where do I find for sure the latest firmware?
 
R

russ lyttle

Rich said:
The "usual" problem with programming AVRs is that they typically
(all?) come from the factory set to use the internal RC oscillator as
the clock source and that oscillator is typically (always?) set, or
divided down, to 1 MHz.

If the STK500's programming clock is higher than 1/4 of that then
programming will fail. Check the "settings" button under the Main tab
from the STK500 window in AVR Studio.

A good test is to *always* do a signature check before trying to
program. If the signature is wrong or cannot be read then something's
amiss.

Once you're talking to it reliably, set the fuses as needed if you're
using an external clock source or crystal.
Thanks.
On all ATMega8515 the signatures read 0x1E 0x93 0x01 with a warning that
the signature doesn't match the selected device. On ATMega8515L nothing
is readable, neither signature or fuses.
The clock is set for 28k
Firmware version is 0x020a
 
R

Rich Webb

On all ATMega8515 the signatures read 0x1E 0x93 0x01 with a warning that
the signature doesn't match the selected device. On ATMega8515L nothing
is readable, neither signature or fuses.
The clock is set for 28k
Firmware version is 0x020a

An Atmega8515's signature should be 0x1E 0x93 0x06, where 0x1E is the
manufacturer (Atmel), 0x93 is memory size (8K), and 0x06 is a
sequential code for that memory size.

The signature you're getting is for the older AT90S8515.
 
R

russ lyttle

Rich said:
An Atmega8515's signature should be 0x1E 0x93 0x06, where 0x1E is the
manufacturer (Atmel), 0x93 is memory size (8K), and 0x06 is a
sequential code for that memory size.

The signature you're getting is for the older AT90S8515.
Now that is strange. Although plainly marked as ATMega8515, the do
program as AT90S8515. I'll have to find out where purchasing got them.
thanks a lot
 
T

Tom

russ said:
Thanks for the reply
Perhaps not. I updated AVR studio4, then updated firmware with the
version on my harddrive. Where do I find for sure the latest firmware?

When you install a newer version of Studio it will read the firmware in
the STK500 and tell you if it needs to be updated, and will do it from
within the program.
 
Top