Signatures of the xtiny series and AS7 simulator bug

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

I want my STK2UPDI project to be able to talk to avrdude, so I need to write part definitions (avrdude.conf) for the xtiny series.

I realized I'll eventually need the signatures for all the chips in this family, but the only physical chips I have are tiny 817 (from xplained mini), tiny 1614 (that I'm using as target) and tiny 1616.

 

The signatures are 3 bytes starting at linear address 0x1100. So from my physical chips I have:

tiny817:    0x1E 0x93 0x20
tiny1614:   0x1E 0x94 0x22
tiny1616:   (can't read atm, need to mount in an adapter)

 

So I thought: "Well, I'll start a thread and see if the guys can get me the rest of the signatures", but then I realized I could get them in the simulator, and that's how I found a bug, the signatures in the simulator appear as a 3x 16 bit array instead of a 3 byte array, for example, the 1614 signature is:

1e 00 94 00 22 00

 

Nothing serious, but I'll leave the note here in case someone at Atmochip wants to correct it.

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

ATtiny417:      0x1E9220  data sheet

 

ATtiny1616:    0x1E9421  read using Atmel-ICE in AS7

 

 

EDIT:  The device signatures are listed in the complete data sheet for the parts, search for "Signature Bytes".

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

Last Edited: Wed. Dec 13, 2017 - 11:50 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks. Yes, normally the signatures are listed in the datasheet, but for the xtiny series that doesn't seem to be the case, at least the ones I checked.

But with the transition to Microchip, there are so many versions of the datasheets around I can't be sure.

 

edit: anyway, I already have all the signatures from the simulator (even the ones that don't really exist), but it's always better to confirm with real hardware.

 

tiny212     0x1E    0x91    0x21
tiny214     0x1E    0x91    0x20
tiny412     0x1E    0x92    0x23
tiny414     0x1E    0x92    0x22
tiny416     0x1E    0x92    0x21
tiny417     0x1E    0x92    0x20
tiny814     0x1E    0x93    0x22
tiny816     0x1E    0x93    0x21
tiny817     0x1E    0x93    0x20
tiny1614    0x1E    0x94    0x22
tiny1616    0x1E    0x94    0x21
tiny1617    0x1E    0x94    0x20

 

Last Edited: Thu. Dec 14, 2017 - 12:23 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Add the ATtiny32xx series to the ones that don't really exist, though they should. ;)  Microchip|Atmel are you following this?

 

Note that the end of the signatures for the 3214 and 3217 are not following the pattern in your list as they are swapped, signatures are from the simulator.  Is this another bug in AS7 or are these device signatures really going to be different?

 

ATtiny3214:    0x1E9520

ATtiny3216:    0x1E9521

ATtiny3217:    0x1E9522

 

 

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

Yes, the signatures are correct, and yes the tiny321x breaks the pattern. Probably a slip somewhere when they where sharing out the signatures.

 

Thanks for the 16bit bug. I'll look into it.

 

-Jan Egil