Read device does not match the selected device

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

Hi,

I am trying to program the ATtiny10 I am getting the error message:

Unable to enter programming mode. The read device ID does not match the selected device or any other supported device. Please verify device selection, interface settings, target power and connections to the target device. 

I am pretty sure that the connections are fine. The ATtiny I am using is actually called ATTINY10-TSHR but I have selected ATtiny10 (can't see any other options for ATtiny10). Could this be the reason? Any other suggestions I could try? I am using Atmel studio 7.

Thanks very much for your time and help

 

 

karl

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

1) is the target powered?  (AVR programmers do not normally supply target power)

2) is anything else connected to the programming pins? 

3) is there a cap on the reset line?  There should not be.

 

What programmer are you using?   Does it support TPI?

 

Jim

 

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

This is the programmer I am using. 

1.) I am sure the power comes from the programmer. The jumper is in position.

2.) nothing else

3.) No capacitor

I am plugged into the TPI port on the programmer and have connect up the programmer as per this image. I have checked and there is continuity between the relevant pins on the ATtiny10 and those going into the TPI port of the programmer. I have tried two different ATtiny10s and get the same result. Wondering if the programmer is working correctly.

What do you reckon? 

 

 

 

karl

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

vcc = 5 v?  Data sheet says tpi programming requires 5 volts.

Can you post a picture of your setup, bread board or pcb?

Jim

 

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

If you have multimeter then just check at tiny10 vcc pin if it get powered correctly. Also the ground wire get connected or not.
.
MG

I don't know why I'm still doing this hobby

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

It might help a bit to post the complete log output of your programmer.

Are there any other error messages?

 

I've also had a look at:

paul@dualcore ~ $ scite /etc/avrdude.conf &

And the only references to ATTINY is:

#define ATTINY10    0x10  /* the _old_ one that never existed! */
#------------------------------------------------------------
# ATtiny10
#------------------------------------------------------------

part parent "t9"
    id		= "t10";
    desc	= "ATtiny10";
    signature	= 0x1e 0x90 0x03;
;

There is no string "THSR" in that file, but to be sure of any differences you should check the datasheets.

Paul van der Hoeven.
Bunch of old projects with AVR's:
http://www.hoevendesign.com

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

Thanks. I managed to get it working. I found that my programmer had a loose connection internally.  

As an experiment I have taken the Hex file that is generated from the arduino blink program and tried to run it on a few Attinys.  It works fine on the ATtiny85 but does not run on the ATtiny10. Seen as it is just Hex why would it work on one and not the other? 

karl

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

Absolutely correct. They are different inside. You MUST recompile it. Even going from a Mega88 to Mega168, which are part of the same "family", needs recompile.

 

Jim 

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

volmo wrote:
Seen as it is just Hex why would it work on one and not the other? 

What inside the .Hex is determine how your MCU works so every .Hex is device specific.

If you think you can use it to any MCU so what's the need of various device type. Just randomly pick one and it will "magically" know what you want it to do?

 

 

 

 

MG

I don't know why I'm still doing this hobby