Xmega wrong Device ID

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

Hello,

last week i got some PCB from our production line which have a xmega16a4 included. When i try to programm the controllers using AVRstudio5.1 i get the device ID 0x1E 0x94 0x42 ->"Unable to enter programming mode. The read device id indicates that the connected device is an ATxmega16D4".
When i switch Avrstudio to xmega16d4 i am able to flash the controller, but the code doesnt work.
The imprint on the controller shows:
Atmel
Xmega16A4
MH1140
KOREA-AB
35957-B
1G8314-1

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

Wow. That would be a problem.

I think you need to contact Atmel Tech Support, AND have the PCB manufacturer contact Atmel Tech Support.

I suspect Atmel will want a couple of the boards/chips to X-Ray.

One can only guess as to whether or not the PCB manufacturer used bogus chips, or whether perhaps some chips made it down the line and were mis-printed, (doubtful).

Somewhat related, in another recent thread it was noted that the naming convention for the chips is a little difficult to understand.

The Xmega 64A4 and 128A4 are no longer in the current Xmega lineup.

Both of their Signature ID Byte Patterns have been reused for the Xmega 64A4U and 128A4U chips.

It would also appear to the casual reader that the Xmega 16A4 and 32A4, both still in the current lineup, have the SAME Signature ID Bytes as the Xmega 16A4U and 32A4U chips. They DON'T appear to have unique Signatures.

I've reviewed the data sheets a couple of times. Perhaps I just need some more sleep, (or more caffeine), and I'm mis-reading the data sheets.

Perhaps there is a typo in the data sheets.

Perhaps the numbering sequences are not as unique as one would expect.

To be fair the programmer (AVRISP mkII, STK600, etc.), doesn't really need to distinguish between the above overlapping models, as they have the same amount of Flash, same Flash Page Size, and the same EEPROM Size. Presumably, also, the system designer/programmer knows which chip the board has, so you write code for USB modules only for those which have one.

Back On Topic, however, I agree the Xmega 16D4 and 16A4 have unique Signature ID Bytes.

JC

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

Uh oh. Please email avr@atmel.com with the full chip markings (both on the top of the chips AND the bottom of the chips) and we'll investigate.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

Somewhat off-topic, but I have been playing around with the UC3B1256 board controller on my XMEGA-A1 Xplained boards and when I tried copying the code from one board to the other, the JTAG ID had multiple bits change. I had to change the device file before I could erase or program it. Erasing the FLASH clears one of the bits, but even so the JTAG ID is significantly different than what the part shipped with. So now I have to edit the device file to erase it, then edit the device file again to program it...

Gamu The Killer Narwhal
Portland, OR, US
_________________
Atmel Studio 6.2
Windows 8.1 Pro
Xplained boards mostly