AVRdude + USBasp + Attiny10 = partial success exactly once? What happened?

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

I made a very simple breakout board for an Attiny10 to play around with it.  It includes a standard 10-pin ISP connection, except (as per various online tutorials) MISO and MOSI are connected via a resistor and MOSI is not directly connected to the chip (TPI programming doesn't use it).  Attached is the schematic.

 

I have an USBASP programmer handy, so I go to use that.  I understand that there's some evilness going on regarding which versions of AVRDUDE support TPI... I didn't get that far.  Here's my issue... on the FIRST test, I got the following mostly-positive result:

 

> avrdude.exe -p t10 -c usbasp -U flash:r:flash.bin:r

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude.exe: Error: usbasp programmer does not support TPI
avr_read(): error reading address 0x0000
    read operation not supported for memory "signature"
avrdude.exe: error reading signature data for part "ATtiny10", rc=-2
avrdude.exe: error reading signature data, rc=-1

avrdude.exe done.  Thank you.

OK, so fine I don't have the avrdude version right OR my usbasp doesn't have the latest firmware... whatever... the point is, a connection was made and it attempted the read.

 

But SINCE that very first read, now all I get is:

 

>avrdude.exe -p t10 -c usbasp -U flash:r:flash.bin:r

avrdude.exe: error: program enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
             Double check connections and try again, or use -F to override
             this check.

avrdude.exe done.  Thank you.

The connections are hardwired and I've changed nothing.  The two attempts were literally seconds apart. 

 

Did I somehow fry my Attiny10 on that first attempt?!?!  Or fuse brick it??

What now?

 

Thanks.

Attachment(s): 

Last Edited: Thu. Apr 6, 2017 - 12:04 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hmm... OK, so I ran the same test about 20 times in a row and every 9 to 11 it seems to "work" (ie. I get the same message as the first).  So now I'm really confused.  Perhaps it really is a connection problem.  I'll hit everything with the iron again.

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

AFIK, Chinese firmware does not support TPI.
The original Germam firmware did not support TPI.
I think that the German 2011 firmware does support TPI. But it uses a different pinout to the AVRISP-2
.
So you need a modern avrdude and compatible firmware in the USBASP.
.
David.

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

Yes, I'm aware of all that.  My USBasp is a custom build of my own design using the latest (2011) firmware... not a cheapo Chinese thing.

 

I read that it is heavily dependent on the version of AVRdude and perhaps "modern" doesn't work.  I'm using 6.3 but I read somewhere I may have to degrade to a specific 5.11.1 variant.  I'm not sure, but that's not really the issue at this point.  it is the connection that is weird.

 

I've gone over the soldering and it is solid, so now I'm really confused why it is intermittently connecting.

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

Attached is the schematic.

Where?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

js wrote:

Attached is the schematic.

Where?

 

Hmm.  I must have typed that an then forgot to actually do it.  I'll edit/add shortly.  Sorry about that.

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

Turned out to be a sketchy wire is all.  *dumb*

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

s_mack yourself. wink

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

indeed   lol