ATxmega256A3BU on Xplained board--chip revision?

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

I'm planning to get a XMEGA-A3BU Xplained board to do some prototype/proof-of-concept work on an upcoming app.

Does anyone know what silicon revision of the A3BU is likely to be on the Xplained board? As the critical part of the app is ADC work, it wouldn't be much use to me if the chip is rev. D or earlier--

Quote:
39.1.3 rev. D
"¢ ADC unsigned mode non-functional
"¢ ADC increased noise when using internal 1.0V reference at low temperature
"¢...

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

Wonder if there's any kind of correlation between the LOTNUM's in this and the rev?

typedef struct NVM_PROD_SIGNATURES_struct
{
    register8_t RCOSC2M;  /* RCOSC 2MHz Calibration Value */
    register8_t reserved_0x01;
    register8_t RCOSC32K;  /* RCOSC 32kHz Calibration Value */
    register8_t RCOSC32M;  /* RCOSC 32MHz Calibration Value */
    register8_t reserved_0x04;
    register8_t reserved_0x05;
    register8_t reserved_0x06;
    register8_t reserved_0x07;
    register8_t LOTNUM0;  /* Lot Number Byte 0, ASCII */
    register8_t LOTNUM1;  /* Lot Number Byte 1, ASCII */
    register8_t LOTNUM2;  /* Lot Number Byte 2, ASCII */
    register8_t LOTNUM3;  /* Lot Number Byte 3, ASCII */
    register8_t LOTNUM4;  /* Lot Number Byte 4, ASCII */
    register8_t LOTNUM5;  /* Lot Number Byte 5, ASCII */
    register8_t reserved_0x0E;
    register8_t reserved_0x0F;
    register8_t WAFNUM;  /* Wafer Number */
    register8_t reserved_0x11;
    register8_t COORDX0;  /* Wafer Coordinate X Byte 0 */
    register8_t COORDX1;  /* Wafer Coordinate X Byte 1 */
    register8_t COORDY0;  /* Wafer Coordinate Y Byte 0 */
    register8_t COORDY1;  /* Wafer Coordinate Y Byte 1 */
    register8_t reserved_0x16;
    register8_t reserved_0x17;
    register8_t reserved_0x18;
    register8_t reserved_0x19;
    register8_t reserved_0x1A;
    register8_t reserved_0x1B;
    register8_t reserved_0x1C;
    register8_t reserved_0x1D;
    register8_t reserved_0x1E;
    register8_t reserved_0x1F;
    register8_t ADCACAL0;  /* ADCA Calibration Byte 0 */
    register8_t ADCACAL1;  /* ADCA Calibration Byte 1 */
    register8_t reserved_0x22;
    register8_t reserved_0x23;
    register8_t ADCBCAL0;  /* ADCB Calibration Byte 0 */
    register8_t ADCBCAL1;  /* ADCB Calibration Byte 1 */
    register8_t reserved_0x26;
    register8_t reserved_0x27;
    register8_t reserved_0x28;
    register8_t reserved_0x29;
    register8_t reserved_0x2A;
    register8_t reserved_0x2B;
    register8_t reserved_0x2C;
    register8_t reserved_0x2D;
    register8_t TEMPSENSE0;  /* Temperature Sensor Calibration Byte 0 */
    register8_t TEMPSENSE1;  /* Temperature Sensor Calibration Byte 0 */
    register8_t DACAOFFCAL;  /* DACA Calibration Byte 0 */
    register8_t DACAGAINCAL;  /* DACA Calibration Byte 1 */
    register8_t DACBOFFCAL;  /* DACB Calibration Byte 0 */
    register8_t DACBGAINCAL;  /* DACB Calibration Byte 1 */
    register8_t reserved_0x34;
    register8_t reserved_0x35;
    register8_t reserved_0x36;
    register8_t reserved_0x37;
    register8_t reserved_0x38;
    register8_t reserved_0x39;
    register8_t reserved_0x3A;
    register8_t reserved_0x3B;
    register8_t reserved_0x3C;
    register8_t reserved_0x3D;
    register8_t reserved_0x3E;
} NVM_PROD_SIGNATURES_t;

Note the comment in this:

https://www.avrfreaks.net/index.p...

He seems to be saying that an alternative to reading the rev from the chip (because it's underneath the soldered item) is by somehow analysing the signature row info.

EDIT, sorry, no he's talking about this:

/* MCU Control */
typedef struct MCU_struct
{
    register8_t DEVID0;  /* Device ID byte 0 */
    register8_t DEVID1;  /* Device ID byte 1 */
    register8_t DEVID2;  /* Device ID byte 2 */
    register8_t REVID;  /* Revision ID */
    register8_t JTAGUID;  /* JTAG User ID */
    register8_t reserved_0x05;
    register8_t MCUCR;  /* MCU Control */
    register8_t reserved_0x07;
    register8_t EVSYSLOCK;  /* Event System Lock */
    register8_t AWEXLOCK;  /* AWEX Lock */
    register8_t reserved_0x0A;
    register8_t reserved_0x0B;
} MCU_t;

Add 'A' onto the REVID and you have your revision letter.

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

Yahbut, I'm trying to determine whether it is worth getting the board. It won't help me much to do proof-of-concept ADC work--if the ADC isn't working up to par.

So I'm hoping a 'Freak has gotten one of the beasties recently and can shed some light. Either by the read-the-chip method, and/or date code, and/or ???.

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

MCU.REVID is 6 on my XMEGA-A3BU Xplained board, which would be rev. G. I bought it about two months ago from Mouser. The datecode (i guess) on the XMEGA is 1143.

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

Quote:

MCU.REVID is 6 on my XMEGA-A3BU Xplained board, which would be rev. G. I bought it about two months ago from Mouser. The datecode (i guess) on the XMEGA is 1143.

Thanks much. I'll go ahead and order one and take a chance. ;)

I've managed to avoid Xmega so far. Regular readers may know that initially I was very excited but the long wait to real silicon and the long errata list when chips were available was too discouraging.

But I have to get into the new decade/century/millennium sometime, and a new app is better suited to Xmega than AVR8.

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

snigelen wrote:
MCU.REVID is 6 on my XMEGA-A3BU Xplained board, which would be rev. G. I bought it about two months ago from Mouser. The datecode (i guess) on the XMEGA is 1143.
Have you tested the ADC system, to verify that it's not buggy anymore ?

1) Studio 4.18 build 716 (SP3)
2) WinAvr 20100110
3) PN, all on Doze XP... For Now
A) Avr Dragon ver. 1
B) Avr MKII ISP, 2009 model
C) MKII JTAGICE ver. 1

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

No, I haven't had time for that yet. Maybe someday... ;-).