STK500 - Atmega8 - Invalid Device Signature

Go To Last Post
17 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

when trying to program via avrdude and STK500 my ATMEGA8

avrdude -p atmega8 -c stk500 -P /dev/ttyUSB0 -U first.out -F

I get an error message regarding invalide device signature: (attached the whole, verbose output)

avrdude: stk500v2_command(): command failed
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x70f049
avrdude: Expected signature for ATmega8 is 1E 93 07

Unfortunately the device signature reported by avrdude (0x70f049) changes each time.

Same problem when replacing the Atmega8 with an Atmega16.

 

The STK itself seem to work, as the program which is currenylt on the Microcontroller works, and the status LED is green.

 

My setup already worked. But i think I broke it/the STK when i attach a stepmotor to the Atmega.. :( The Status Led switched immediately to red (short circuit), I assume this was because too much current has been drained..

Is there a way to fix this?

This topic has a solution.
Last Edited: Tue. Apr 7, 2020 - 06:51 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Welcome to AVRFreaks!

 

paul2244 wrote:
Is there a way to fix this?

Fix what, the signature not reading or the short circuit?

 

Begin here to see how to ask questions: https://www.avrfreaks.net/forum/...

 

Jim

 

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

But i think I broke it/the STK when i attach a stepmotor to the Atmega

What does your motor driver circuit look like (what chips or transistors)? you could feedback high voltage spikkes that damaged things.

Do things return to normal with all of that disconnected (assume no , you prob already tried that)

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you for the replies

ki0bk wrote:

Fix what, the signature not reading or the short circuit?

The short curcuit is already removed, i removed the step motor and the corresponding driver.

 

avrcandies wrote:

But i think I broke it/the STK when i attach a stepmotor to the Atmega

What does your motor driver circuit look like (what chips or transistors)? you could feedback high voltage spikkes that damaged things.

Do things return to normal with all of that disconnected (assume no , you prob already tried that)

 

I already reomved the motor driver curcuit, so the problem appears when only using STK500, Atmega8 and attached LEDS PORTB.

 

What I would to 'fix' is to enable programming of my Atmega again, which most likely corresponds to the read signature.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I would try a new atmega if you can not read its signature then your stk500 is broken!

 

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ki0bk wrote:

I would try a new atmega if you can not read its signature then your stk500 is broken!

 

 

Yeah, new Atmega is not changing anything. Too bad... in that case I guess i have to throw it away.. Thanks tho

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 The Status Led switched immediately to red (short circuit),

Is it still red with all the motor stuff removed? If green, there is hope

 

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

Last Edited: Thu. Mar 26, 2020 - 11:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

avrcandies wrote:

 The Status Led switched immediately to red (short circuit),

Is it still red with all the motor stuff removed? If green, there is hope

 

 

When starting the STK, the Status LED switches from Red - Orange - Green - Off - Green and stays Green.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you tried using it with Atmel Studio?

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

avrcandies wrote:

Have you tried using it with Atmel Studio?

 

I will try that as soon as I have a windows machine running :) I'll come back, thanks!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No, unfortunately no success with AVR Studio 7 either.. Any ideas what I could further try?

 

I got some detail information, maybe it helps:

And when trying to read the signature, I get:

error read voltage 1.6v is outside selected device operating range 2.7v to 5.5v.

Last Edited: Sat. Apr 4, 2020 - 11:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

error read voltage 1.6v

So is your chip plugged into the correct socket in the STK500? Is it plugged backwards?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The STK500 lets you pick the voltage to the chip...is it possible you just have the adjustment set too low?  I would doubt it would allow you to pick one that is illegal...but never say never...please go check.

 

There is also some little plastic jumper to install for the voltage...if the jumper is removed, you must supply your own voltage to the chip (I believe).  Maybe a jumper fell off & you didn't notice.  Go check  ALL of the little jumpers.

A lack of a proper clock jumper would give some other error.

 

 

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

Last Edited: Sun. Apr 5, 2020 - 03:32 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

avrcandies wrote:

The STK500 lets you pick the voltage to the chip...is it possible you just have the adjustment set too low?  I would doubt it would allow you to pick one that is illegal...but never say never...please go check.

 

wow! I assumed, it is only possible to READ this value, which was always reported as 1.6v. But thanks to your hint, I saw that it is also possible to write it. So i set it to 5V, and voila, the signature was read properly and programming STK worked!

Also, it works again with avrude.

 

Thank you so much :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The STK500 was really a nice setup...I wish they would have continued with some upgrades (I don't have or like the stk600).  I still find is useful, for its simplicity.

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

paul2244 wrote:
the signature was read properly and programming STK worked!

 

Excellent!

 

Now please mark the solution - see Tip #5 in my signature (below)

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1


paul2244 wrote:
I assumed, it is only possible to READ this value,

 

 

Reading the manual rather than assumption is often the better course of action cheeky