>the problem could be the SPI timing. The mega162 runs at 1MHz when the
>fuses are not programmed.
>There is a command in the STK500 protocol to slow down the SPI.
>However, I don't know about the STK500 utility, because I use Linux.
If that is the problem then
Just lower the STK500 clock on the first programming , until fuses are
Reply by Meindert Sprang●October 6, 20042004-10-06
"Carsten" <email@example.com> wrote in message
> >the problem could be the SPI timing. The mega162 runs at 1MHz when the
> >fuses are not programmed.
> >There is a command in the STK500 protocol to slow down the SPI.
> >However, I don't know about the STK500 utility, because I use Linux.
> If that is the problem then
> Just lower the STK500 clock on the first programming , until fuses are
> set correctly.
And the $64.000 question is: How?
Reply by Meindert Sprang●October 7, 20042004-10-07
"Meindert Sprang" <mhsprang@NOcustomSPAMware.nl> wrote in message
> Hi all,
> I have a very annoying problem: I have an existing design with an
> ATmega8515, with an ISP connector setup as specified in one of the Atmel
> appnotes about implementing an ISP connector. It uses a network on the
> line, with a 10k resistor to VCC, a 4n7 cap to ground and a diode across
> resistor for protection. This has always worked on a 2313, a 8515 and a
> Mega8515. I recently upgraded the design to a Mega162 and since then 1 out
> of three times the board refuses to have the configuration fuses
> Also reading the chip ID gives random results many times. Once the fuses
> programmed successfully (to use an external crystal at 8MHz), everything
> runs fine and the code can be programmed too.
Ok guys, thanks for all the suggestions. I completely failed to notice
the -! option to set the clock frequency. I have set it to 1MHz and all
devices program fine now.