XMEGA E

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

Does anyone have information about this device? I've seen it in ASF docs, but can not find any other information about it.

Is it a future version? Any links to this device?
Any product specs? Any timeframes? any samples?

I'm assuming it's a bit smaller (peripherals, memory) than the D series

Thx

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

Quote:

Is it a future version? Any links to this device?
Any product specs? Any timeframes? any samples?

Search in this forum there was another thread discussing it (*) with a link to a leaked copy of the early datasheet on a Russian website. Clearly it's "on the cusp".
Quote:

I'm assuming it's a bit smaller

The main selling point seems to be 32 pins so, yes, it's smaller.

(*) I think it was the "Xmega wish list" thread in fact.

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

Rumors are for 1st quarter of 2013 release, so we are 1/3 of the way into the 1st quarter. :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I read somewhere that E has configurable logic inside.

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

Quote:
E has configurable logic inside

Clearly "fuses" on Tinies, Megas, and Xmegas count as configurable logic inside. :wink:

That said, the latest version of Xmegas include a USB module. Adding additional features/modules as the series is further expanded would not be a surprise.

JC

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

Quote:

has configurable logic inside

You mean CPLD/FPGA? First I've heard of that part of the rumour.

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

Quote:

First I've heard of that part of the rumour.

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

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

Speculation is fun but quite pointless until the official release. Let's just hope it's in Q1. Then you can start speculating what will really be inside...

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

My point was I was hoping to keep the same family of chips, but was hoping for something "smaller" than the D series. For this app, only needed 1 serial, 16 io pins, rtc (accuracy is not a big issue )and about 4-8k of memory and a bit of reduced price.

I was hoping for the same family of chips as there is some code from other projects with the xmega. I will likely just design around the d series and change if the chip is released earlier (and fits the need better).

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

Ordering AVnetexpress I got delivery confirmation for end of october... I believe Q1 will be a nice dream. I saw this device electronica Munich 2012 too. If somebody have pinout I could start development :-(

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

Quote:
8k of memory and a bit of reduced price.
There are 3 E5 chips, 8K, 16K and 32K.

No idea about the price for the 32 pin device, I would hope it to be cheaper than, say, the Xmega16A4U-AU ($2.86) or the ATxmega16D4-AU ($2.39)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

wow so Avnet at least aknowledges the chip unlike Digikey :-)

Xmega8E5-AU $1.31
Xmega16E5-AU $1.52
Xmega32E5-AU $1.83

We want them NOW!! :lol:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

to me, chip price is only part of the equation. board space which translates to packing are also concerns. small is good, smaller is better.

I guess I should stop using the 1206 size smd devices but prototyping with smaller gets beyond my eyes . :)

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

Feb. 6, 2013

How about that, Mouser now lists several E5's:

ATXmega8E5-AU $1.04, 26 Weeks lead time
ATXmega8E5-M4U $1.04, 26 Weeks lead time
ATXmega8E5-MU $1.04, 26 Weeks lead time

ATXmega16E5-AU $1.21, 26 Weeks lead time

A step closer.

JC

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

Holatron mentioned:

Quote:
I read somewhere that E has configurable logic inside.

Disclaimer: I don't program in C, or use ASF.

The Release Notes for ASF 3.5.0 state that the XmegaE is now included in ASF, and that there is now a new Demo for the XCL Module, (programable logic module).

JC

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

Atmel is already inviting people to their Tech Online Seminars regarding XMEGA E, yet nothing about E family can be found on their website.

That's what I found when I tried to find out what these chips are:
http://www.ineltek.com/de/news/news_Atmel_XMEGA_E.php

Engineering design triangle:
Fast, cheap, good. Choose 2 of the above

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

I see there is a webinar on March 13th. I would assume there would be a formal product announce along with more details (data sheet?) before that date.

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

Wow. I want it !!!
Aside from the major selling-point, the custom logic, I also saw that USART continues to work in sleep mode. This is exactly what I'd like the XMegas had, and now it happens.

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

How odd, to see what look like Atmel press releases from 3rd parties, and references in Atmel documents, for a part that Atmel does not seem to have announced themselves.

Do you suppose that Atmel is getting more careful about mentioning overly optimistic ship dates? ("Volume shipments in Jan '13"", according to the document at Ineltek. heh.)

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

By analyzing Atmel device introductions of late vis-a-vis availability, I suggest to heed Mouser indications of avaialbility in fall '13.

Consider SAM4L: announced in Sep 12 claiming samples in Oct 12 and mass production in Nov 12.
As of today, no samples are in sight, and Mouser still indicates 5 months lead time.

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

Svuppe wrote:
Wow. I want it !!!
Aside from the major selling-point, the custom logic, I also saw that USART continues to work in sleep mode. This is exactly what I'd like the XMegas had, and now it happens.

Can you elaborate? It would seem that there would be no way to generate the USART clock when the peripheral clock is stopped, or do you just mean in idle mode?

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

mojo-chan wrote:
Can you elaborate?

Not really. I just read it in the link above:

Quote:
AVR XMEGA E devices can stay in sleep mode and use only 180nA while the brown-out detection, watchdog, real-time counter, I/O pin change interrupts, I2C address match logic, and USART can continue operation.

I did wonder about the clock afterwards, and I have no idea how they would pull this one off.

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

Surely it's just saying that start bit activity on the RXD is enough to wake it from sleep? I doubt it can actually receive data in sleep but up to now if you have wanted an AVR to wake on UART activity you have had to cross wire RXD to INT0 or similar (and there can be issues about getting awake quick enough to the receive the first frame).

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

Perhaps it is running from the 32kHz oscillator? Energy Micro's EFM32 processors have a perihperal that does this, and still allows communication at 9600 baud in the deeper sleep modes.

Of course this is all idle speculation. Once the datasheet is released we'll all know for certain.

Jeff Nichols

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

Personally I don't care if it receives the first byte while in sleep, or just wakes up at the start bit. If it can receive the first byte, I will be happy.
They also say it can wake up on 5 µs, but how precise is the baudrate generation then? I don't believe it has enough time to sync to an external reference (32.768 kHz).

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

Should be "Wake up on USART/UART start of frame without dataloss".

--
Follow me on the birdsite @AndreasMCUguy

I work at Atmel, but I try my best not to add marketing fluff in this forum.Hopefully I succeed. Views are my own and does not represent Atmel --

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

Quote:

They also say it can wake up on 5 µs, but how precise is the baudrate generation then? I don't believe it has enough time to sync to an external reference (32.768 kHz).

From the pirate information:

Sleep Modes/Wakeup Sources:
"USART start of frame" in PowerSave, Standby, and Extended Standby with a note for PowerSave "Only from internal 8MHz oscillator in low power mode".

Quote:
8.3.3 Power-save mode
Power-save mode is identical to power down, with two exceptions. If the real-time counter (RTC) is enabled, it will keep running during sleep, and the device can also wake up from either an RTC overflow or compare match interrupt.

If the UART start frame detector is enabled, the device can also wake-up from any UART interrupt, including start frame interrupt. The internal 8MHz in low power mode must be used to wake-up the device from UART interrupts.

Quote:
8.3.4 Standby mode
[...and...]
8.3.5 Extended standby mode
...
If the UART start frame detector is enabled, the device can also wake-up from any UART interrupt, including start frame interrupt.

Quote:
20.9.4 Start frame detection
The start frame detection is supported in UART mode only and takes place only if the system is in deeper sleep modes.

The UART start frame detector can wake up the system from power save, standby or extended standby sleep modes when a start bit is detected. In power save mode, the internal 8MHz oscillator in low power mode must be used as clock source, but in standby or extended standby modes it can operate with any clock source.

When a high-to-low transition is detected on RxDn, the oscillator is powered up and the UART clock is enabled. After start-up, the rest of the data frame can be received, provided that the baud rate is slow enough in relation to the oscillator start-up time.

Start-up time of the oscillators varies with supply voltage and temperature. For details on oscillator start-up time characteristics, refer to device datasheet.

If a false start bit is detected and if the system has not been waken-up by another source, the oscillator will be automatically powered-off and the UART waits for the next transition.

The UART start frame detection works in asynchronous mode only. It is enabled by writing the Start Frame Detection bit (SFDEN) in “CTRLB – Control register B” on page 280”. If the start bit is detected, the UART Start Interrupt Flag (RXSIF) bit is set.

In active and idle sleep modes, the asynchronous detection is automatically disabled. In power down sleep mode, the asynchronous detector is enabled, but the internal oscillator is never powered. In such case, it is highly recommended to disable the start detector before going in power down sleep mode.

The UART receive complete flag and UART start interrupt flag share the same interrupt line, but each has its dedicated interrupt settings. The Table 20-5 shows the USART start frame detection modes, depending of interrupt setting.
...

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.

Last Edited: Mon. Feb 25, 2013 - 05:04 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Did I dream it but doesn't the very recent tiny1634 also have this feature?

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

Quote:

Did I dream it but doesn't the very recent tiny1634 also have this feature?


Indeed, it has "wake on start bit". Let's check that description...

Sleep modes table is roughly similar/corresponding.

USART description:

Quote:
16.9.4 Start Frame Detection
The USART start frame detector can wake up the MCU from Power-down, Standby or ADC Noise Reduction sleep mode when it detects a start bit.
When a high-to-low transition is detected on RxDn, the internal 8 MHz oscillator is powered up and the USART clock is enabled. After start-up the rest of the data frame can be received, provided that the baud rate is slow enough in relation to the internal 8 MHz oscillator start-up time.
Start-up time of the internal 8 MHz oscillator varies with supply voltage and temperature.

The USART start frame detection works both in asynchronous and synchronous modes. It is enabled by writning the Start Frame Detection Enable bit (SFDEn). If the USART Start InterruptEnable (RXSIE) bit is set, the USART Receive Start Interrupt is generated immediately when start is detected.

When using the feature without start interrupt, the start detection logic activates the internal 8MHz oscillator and the USART clock while the frame is being received, only. Other clocks remain stopped until the Receive Complete Interrupt wakes up the MCU.

The maximum baud rate in synchronous mode depends on the sleep mode the device is woken up from, as follows:
• Idle or ADC Noise Reduction sleep mode: system clock frequency divided by four.
• Standby or Power-down: 500 kbps.

The maximum baud rate in asynchronous mode depends on the sleep mode the device is woken up from, as follows:
• Idle sleep mode: the same as in active mode.
• Other sleep modes: see Table 16-4 and Table 16-5.
...

Hmmm--pretty clever for a Monday, Cliff-- intersperse "dreaming" with "wakeup sources" ... ;)

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

So it is just a slightly faster way of waking up the micro and enabling the USART without any code, helping it to catch the first byte of the transmission. Currently RX0 is on pin 2 of the port so that it can wake with an async interrupt, but then your code has to enable the USART which typically takes too long to get the first byte unless the baud rate is ridiculous. Nice.

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

Quote:

Feb. 6, 2013

How about that, Mouser now lists several E5's:

ATXmega8E5-AU $1.04, 26 Weeks lead time
...
A step closer.


Avnet sez 12 week lead time on the '8E5. But check the '16E5:

Quote:
Lead Time: 143 Week
Factory Lead Time
:twisted:

From the grapevine it appears that the E series might be "sampling". However, it is again disappointing that Atmel product announcement again/still appears to be pure smoke. I'm still sour on the original Xmega, the "available now", the overlong wait for parts, and the ugliness of the errata list. This latest episode, on the E-size that is suited for real MICROcontroller apps, does not remove the sour taste.

I suppose I need to put all that aside and actually jump into an Xmega app. So far I've resisted.

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

Look what I found in Google's cache:
http://webcache.googleuserconten...

Quote:
Mar 13,2013

Atmel AVR XMEGA E Microcontrollers

This webinar introduces the new Atmel® AVR® XMEGA® E series. You’ll learn about key product features, including the new enhancements to the analog peripherals and the new digital innovations. You’ll also find out which applications are suited for development with the AVR XMEGA E devices. In addition, you’ll gain insight into how the XMEGA E compares with competitive devices.

Details and Registration

Webinar Microcontrollers

Unfortunately -- it seems to now be vapour. Sigh.

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

Quote:

From the grapevine it appears that the E series might be "sampling".
That seems likely as there are at least two contributors here, that I know of, that are already working with them ;-)

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

theusch wrote:
However, it is again disappointing that Atmel product announcement again/still appears to be pure smoke. I'm still sour on the original Xmega, the "available now", the overlong wait for parts, and the ugliness of the errata list.

Do I understand correctly that you're angry at Atmel because they released the XMegas before they were ready and you're also angry at Atmel because they're keeping mum and not releasing the E chips before they're ready?

From my perspective it looks like they learned their lesson and are doing things correctly.

Jeff Nichols

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

Quote:
That seems likely as there are at least two contributors here,
Poor sods....
Quote:
it seems to now be vapour
Are you referring to the chips or the webminar?

The webminar info for the E5 (and some more) was sent out as part of the Atmel newsletter a few weeks back. I hope it is still going ahead, it's not for just ANY webminar that I make time, in fact this would be one of maybe 2 in my lifetime.

I have purchased some cushions to spread around my chair just in case I fall asleep and fall off it. :shock:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I think the Xmegas are great chips, but they certainly got off to a poor start with their delayed availability after their announcement, and the numerous ADC issues.

Its worth noting that most of the errata have been cleaned up in the Ver II chips, (the ones with the internal USB module).

I suspect Atmel is being more careful in their roll-out of the E-series, having hopefully learned their lessons last time.

I think the E series will be, functionally, the XTinies, with many of the Xmega's features, but in a smaller package, and with a few more new features, such as the programmable logic mentioned above.

I'm looking forward to its release, and hopefully to ZBasic's and Bascom's furture support for the chip!

JC

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

Quote:

Do I understand correctly that you're angry at Atmel because they released the XMegas before they were ready and you're also angry at Atmel because they're keeping mum and not releasing the E chips before they're ready?

Whoa--back up the truck beep beep beep...

Have you looked at the link earlier? What part of that is not a "release"? What does the release say?

"Atmel introduces the AVR XMEGA E Series MCU "
"Samples 13-November Volume Shipments January 2013"

That's what >>I'm<< talking about. The same old dance.

And there is a difference between disappointment and "anger".

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

Quote:
What part of that is not a "release"?

Seriously? It's not on Atmel's web site, or in the press. It's a "leak", not a "release."

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

Quote:

Seriously? It's not on Atmel's web site, or in the press. It's a "leak", not a "release."


Seriously? The Webinar announcement >>on Atmel's Web site<< is all leaked? Links to it from distributor Web sites are "leaks"? The link above from Ineltek -- "Ineltek awarded Atmel`s Distributor of the Year 2010 Europe." -- is all leak?

If all of the above is true, then it is some kind of subliminal plot by Atmel to keep my interest.

Quote:

Quote:
it seems to now be vapour
Are you referring to the chips or the webminar?

The webminar info for the E5 (and some more) was sent out as part of the Atmel newsletter a few weeks back. I hope it is still going ahead, it's not for just ANY webminar that I make time, in fact this would be one of maybe 2 in my lifetime.


The Webinar announcement on Atmel's site, as indicated by the cache link, can no longer be found. The links from major US distributor sites are also dead or have disappeared. I can only assume that it was postponed or cancelled.

Quote:

That seems likely as there are at least two contributors here, that I know of, that are already working with them Wink


I knew that. I'm just tired of the smoke and/or way-late. Having your distributor-of-the-year out flogging the product because of a sales bulletin touting Jan shipments -- peeves me greatly. Just say "sampling soon" or "sampling now" -- if >>actually<< doing it.

westfw is hammering at me pretty well. Do you want me to dig out the official Atmel Xmega announcements with the "available immediately" in them?

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

Quote:
"sampling now" -- if >>actually<< doing it.
Well "sampling now" may be possible, I guess, if you are nice to someone in Atmel sales, who knows he may even be reading this thread and may want to prove you wrong. :wink:

It has happened in the past.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I remember getting excited when SAM3 first appeared thinking "at last Cortex from Atmel" and it was true that for quite a while you could get the SAM3 Xplained board but that was the only way to access the chips. In fact I remember reading of someone who bought boards to lift the chips. It does seem to be a trend to run a few engineering sample wafers then use those to make eval boards even though production quantities of a chip are many months away.

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

Being around the block for some time, announcements of new parts are many times geared toward the quarterly financial analysts meeting, relaying confidence that production is humming along and revenues are coming in "real soon now". When analysts start to get impatient after a couple of quarters, then a new part, the best ever, comes along with unchecked "excitement" at corporate.

I receievd today a newsletter note from Atmel saying jubilantly that samples of SAM4L can now be ordered (a reminder: samples availability were promised for Oct 2013). So I checked it out. Yes, now Atmel lists the parts in the "Samples" ordering section - an improvement from last month - but when I placed 2 different SAM4L in my basket and proceeded to checkout, the system responded with "0" in stock - expected delivery in Aug 2013...

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

So does anyone have an update on the availability of the xmega e series ?

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

....or an update if the E5 Webminar is still going ahead tomorrow? I tried to click on the email I had about it but nothing happens. :(

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Were the webminar to happen I would most likely miss it! :(

Feeding into the "world clock": (times from the Atmel newsletter)
Wednesday, 13 March 2013 4:00 pm GMT (London time) results in 3:00 AM EDT Thursday, 14 March 2013 in Sydney
Wednesday, 13 March 2013 8:00 am PST (Los Angeles but says PDT) results in 2:00 AM EDT Thursday, 14 March 2013 in Sydney
Wednesday, 13 March 2013 11:00 am EST (New York but says EDT) results in 2:00 AM EDT Thursday, 14 March 2013 in Sydney

However there are 4 EST time zones including Eastern Australia for Sydney and Brisbane, that would result in the seminar being held on Wednesday, 13 March 2013 11:00 am EST :roll:

...all hypothetical of course...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

And I guess this puts the nail in the coffin :cry:

Very disappointed but not unexpected...back to plan A now.

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Need poetic adaptation to this by our great story tellers http://www.storyarts.org/library...

Something along the lines

Quote:
There once was a sales executive who was bored as he sat on the hillside watching the village sheep. To amuse himself he took a great breath and sang out, "XmegaE5! XmegaE5! The XmegaE5 are being released!"

The 'freaks came running up the hill to help the sales executive launch the XmegaE5 away. But when they arrived at the top of the hill, they found no XmegaE5. The sales executive laughed at the sight of their angry faces.

"Don't cry 'XmegaE5', sales executive ," said the 'freaks, "when there's no XmegaE5!" They went grumbling back down the hill.

etc. etc.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I guess their approach is slightly better than giving you a hunk of silicon with a few wires that doesn't work.

It would be nice to know if it is "just around the corner" or just "around the bend" or "just around the curvature of the earth" or some time frame.

Would also love to have a bit on the pin out and datasheet.

I'm sure in the next year or two I'll look back the frustration will have ebbed - or is replaced with some other item that is just about ready to be release.

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

Quote:

and datasheet.

Header files already in AS6 reveal a lot. Also there is some suport in ASF 3.7.2. For example if I search "drivers" having selected atxmega32e5 there is example code there and if I look at "XCL" there's even a "quick start guide" which links to this page:

http://asf.atmel.com/docs/3.7.2/...

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

Looks like there is another webinar scheduled for the xmega e series.

Apr 17th.

http://www.atmel.com/design-supp...

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

Quote:
Apr 17th.
Are you sure the 7 is really there?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

took me a while, but funny.

yes the link is still active and hopefully it isn't an April fools joke.

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

I could use one of these today instead of a Tiny. So frustrating, but not unexpected for Atmel. They seem to do very slow, soft roll outs and it takes distributors literally years to get the parts in. At least Farnell don't try to charge you £8 for an XMEGA any more, but still...

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

for those who have an interest in the E series, it seems the data sheets are now available from Atmel

http://www.atmel.com/products/mi... (bottom of page)

find chips does not show any vendor with stock. There is a seminar next week, but not sure if it is a demo of a real device or just a slide show of what's coming.

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

I have been looking at the Atmel website every week for this.

However even though the datasheets are now available a search for Xmega32E5 brings up NOTHING one needs to search for ATXmega32E5 for anything to come up. :( :cry: :roll:

Yep, great search facility! Must be employing the same people who messed up the NXP LPCware website.

Edit Quick link to datasheets http://www.atmel.com/devices/ATX...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Nice looking parts. 32 Pin xmegas :)
Price indicators are good.

Some drawbacks:

* Not 5V operation, & not even 5V tolerant ?!
(contrast Microchip have just released 5V PIC24, Infineon's new XMC1000 is 1.8-5.5v)

* No USB version mentioned yet ?
(Smallest xmega USB is currently 44 pins, but I guess the LS-SW-USB solution would coast along in xmega-E ? )

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

Quote:
Not 5V operation
None of the Xmega are 5V
Quote:
No USB version mentioned yet
As I hate USB I won't lose any sleep over that. :)

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:
None of the Xmega are 5V

True, but all of the Std AVR-8 are fully 5V capable, as are all the newest AT89LP series, and some AVR-32 are 5V tolerant, as are SAM7S series, SAM7X series, SAM7A3.

Just a little surprising to see a small general use uC released in 2013, that is not even 5V tolerant on the pins.

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

A single in-line resistor makes it 5V tolerant.

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

Couldn't find specs for temperature accuracy/stability of internal oscillators.

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

gdhospers wrote:
Couldn't find specs for temperature accuracy/stability of internal oscillators.

See the good graphs in section
37.10 Oscillator Characteristics

I cannot see worst case table values, but the graphs are probably more useful.
They even include the Calibrate step sizes.

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

Probably a bit early still....
http://www.atmel.com/tools/XMEGA...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Who-me wrote:
gdhospers wrote:
Couldn't find specs for temperature accuracy/stability of internal oscillators.

See the good graphs in section
37.10 Oscillator Characteristics

I cannot see worst case table values, but the graphs are probably more useful.
They even include the Calibrate step sizes.

That is not in the Xmega-E manual.
I found this in the "Preliminary" section.

This looks far better :D then in other Xmega's where the curve keeps going down if you move from room temperature towards lower temperatures.

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

There is still no 10-12-14 bit hardware SPI... :-(

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

?? SPI is 8 bits in all the micros I have worked with for the past 30+ years.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

And speak of the devil an Atmel webminar reminder just popped in for the Xmega E5 webminar, bad news for me it's at 1AM the 18th.
It better be worth me getting up at that time, the coffee machine may go into meltdown. :lol:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Quote:

SPI is 8 bits in all the micros I have worked with for the past 30+ years.

Not tried ARM yet? For example NXP's 8bit killer has 1 to 16 bit SPI. Even SAM3 has 8 to 16 bit length, same in STM32.

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

excuse my ignorance sir clawson :) no sarcasm intended. what is the new NXP's 8bit killer

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

I agree, variable length SPI would be very handy. Even if it was only 1-8 bits you could then easily do say 12 bits in two transactions. These days we are seeing more and more devices with SPI-ish serial interfaces that have odd numbers of bits.

If anyone is interested I managed to make an XMEGA do a kind-of 12 bit SPI bodged so that it would work with DMA.

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

Quote:

what is the new NXP's 8bit killer

LPC 800

Currently my favourite MCU I think.

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

Quote:

Quote:

what is the new NXP's 8bit killer

LPC 800

Currently my favourite MCU I think.


Certainly it would have more processing power than an AVR8 at the same price range (about $1 qty. 100).

Perhaps it is just my mindset--besides a fast comms bridge I can't think of apps that would excite me for "microcontroller" work. No ADC? Almost all of our real AVR8 apps use a channel or two, and sometimes many channels.

Is there a family document that describes this "multi rate timer" with more than one paragraph? Input capture? PWM? Timer-as-counter?

Anyway, we digress. As discussed throughout the thread, the Xmega E series addresses adding life to the AVR8 line, now to the 32-pin Mega88 size. Whether there will be models down to 8-pin? I don't know. [In most of our AVR8 apps, space isn't critical -- e.g. between TSOP8 and TQFP32.

Similarly in modest volumes a model that might be $1.23 vs. $0.98 isn't critical.

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

Might be a nicer chip, might be faster, might be easier to use, and might be an 8 bit kill BUT - suffers the same issue the Atxmega64a4u, 128a4u, e series and some others. The only thing you can buy is a promise. there are no any chips available.

I'm kinda new to the world of micro controllers and thought for this current project which started out very simple, I would use a D4 series (small and did not need usb). well added some functionality and needed a usb so went to the a4u series (44 pin) thinking, well, if my app gets more complex I will just use the atxmega32a4u.

My app just crossed over the 18k mark and want to add some additional functions and thought I better plan using the atxmega64a4u - great plan, but no chips. Same with the 128a4u - no chips :-(. Some marginally good news. I requested some samples from Atmel. Was backlogged till yesterday. Just got notice of shipment. Maybe they did a large production run and mouser of digikey will get some.

Lesson learned - don't design a project around a promise. I would love to use the E Series on a small project, but will not even consider it till I see distributors with stock.

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

I have used SPI with chips requiring a number other than 8 bits like 17 and 35 bits, you just send more zero bits than required as they usually lock further clocks out or may have to bit bang 1 bit.

Of course any hardwre helps.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Many TFT LCD controllers have 9-bit SPI mode. Very useful, because it don’t need RS control signal. It will be nice to have the SPI with possibility to send a preprogrammed number of dummy bytes. Very useful when interfacing with dataFLASH memories, where read sequence needs to send 1-1056 dummy bytes. And what is very important to me – the possibility of clocking any interface (SPI, USART) using CLKPER4, or at least CLKPER2. Another nice feature will be 4-bit SD-card interface.

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

About 6.5 hours to zero count and blast off, I'll probably sleep through the excitment. :lol:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

At least with the XMEGA line they are all fairly closely pin and software compatible. What we have done is prototype with say a 128A3U and once we know what the final product and code will look like downsize to the smallest/cheapest possible part and make minor code adjustments.

The E series is a bit trickier because of the new pinout, but I am currently working on a simple control/battery charging system with a 128D3. It isn't a cheap product so the extra 50p cost is irrelevant, but later on the same code will easily port over the to E series in other devices.

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

As good as it got here. :cry: Trying for the past 20 minutes and the only thing I can get is a new slide everytime try and relog in.

At least it's happening. And I wish myself a very good night...what's left of it.

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Hey JS try again and you can watch it. Let me know if you are inspired :)

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

It doesn't work at all in Chrome, I had to switch to Internet Explorer.

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

I watched the replay of this. pretty much like the reading from the docs.

I very much like the power consumption numbers.

The questions about availability were answered with a great deal of vagueness, so still not sure if I would design around this yet.

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

Quote:

The questions about availability were answered with a great deal of vagueness,

LOL...lessee--you started the thread four months ago.

FindChips still only gets the same hits at Avnet and Mouser...

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

Quote:
Let me know if you are inspired
I have been inspired since November last year. :wink:

I guess now we can let the bag out of the cat....and reveal that some of us here have had sample chips of the A version for a while and have played with them.

I was one of the fortunate ones to receive a Xmega E5 Xplain board mid December when someone at Atmel wanted to prove me wrong about the availability of the chip :-) so I have designed a product around the Xmega E5 and today I should get my second prototype PCB.

A nice surprise this morning when DHL delivered a couple of the new Rev B Xmega32E5 which I will put on my new board as soon as it arrives today. Thanks to the people involved.

Someone else has a breakout board already running (the guilty party may step forward now) :-) I have also designed a smaller breakout board but haven't had the change of getting it made yet, maybe in the next couple of weeks.

Is EVERYONE EXCITED YET?!! The August delivery date seems reasoanble.

My prediction for the Xmega E5 family is that it will overtake the Mega168 family for the hobbiest as well of course being a nice chip for many applications.

The slogan for the E5 family "Enough X to drive you crazy, not enough to lead you to suicide". :mrgreen:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Fri. Apr 19, 2013 - 09:48 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Someone else has a breakout board already running

Oh man. I wouldn't have carefully erased the Xmega E5 label on the PCB just a day or two ago if I'd know you were going to announce your work with the E5 today.

As the official Atmel Data Sheets are available on the Atmel web site I guess that counts as an official declaration of their existance.

My Xmega32E5 breakout PCB can be seen in the Thread about using solder paste, Found Here .

And, as John stated above, I think this will become a very popular chip.

JC

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

As I have a few small boards getting made for something else I'm adding a couple of the E5 breakout boards to see if they work.

Trying a new (for me) PCB company which seems very reasonable with price and delivery times when it comes to prototypes, see how we go.

Atmel's marketing will be very exited by our contributions and send us lots of money. :lol:

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:

My prediction for the Xmega E5 family is that it will overtake the Mega168 family for the hobbiest as well of course being a nice chip for many applications.

The XMega E5 is nice, but the lack of wide supply means it can never displace all Mega168.
Your prediction will have to wait, until Atmel release a wide-supply Xmega.

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

Of course, like anything else. Maybe 6 months to a year.

By looking at some of the applications shown in the slides (ie cordless drills) I think that the average person may have to wait a bit longer than those manufacturers.

It was the same when Arduino hogged all the Mega168/328 available when they first came out.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

hehe, oops I should have been clearer.

Even after chip-supply issues are resolved, there will remain the Supply-voltage limitations on the xMega.
A Mega168 can operate to 5.5V and directly drive grunty Logic level FETS, for example.
Not so the XMega (yet).

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

Quote:

My prediction for the Xmega E5 family is that it will overtake the Mega168 family for the hobbiest

You mean they are going to be doing them in DIP packages?!? Cool.

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

clawson wrote:
Quote:

My prediction for the Xmega E5 family is that it will overtake the Mega168 family for the hobbiest

You mean they are going to be doing them in DIP packages?!? Cool.

Now THAT would be awsome.

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

They still have the problem no 5V!

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

sparrow2 wrote:
They still have the problem no 5V!

5V and DIP (or PLCC) and I'll immediatelly start redrawing some of our boards.

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

Quote:

Is EVERYONE EXITED YET?!!

That's a rather interesting Freudian slip. Was the word supposed to be "excited" perhaps?

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

XMEGA chips can interface just fine with 5V stuff, all you need is some basic level translation. Often a current limiting resistor is enough, especially for hobbyists.

I'd love to see a DIP version too but won't be holding my breath. Prototyping is getting harder and these days you pretty much have to go direct to PCB very early and then buy yourself some kind of oven to attach all the interesting parts that only come in pin-less packages :(

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

By the way, was the webinar worth watching? I was hoping I could just browse the slides but it doesn't seem to be possible.

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

I guess one can convert these things to DIP with:

those are $0.80 here:

http://www.futurlec.com/SMD_Adap...

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

clawson wrote:
I guess one can convert these things to DIP with:

those are $0.80 here:

http://www.futurlec.com/SMD_Adap...

And how much with an XMEGA E5 and pins mounted on it (price per 300)?

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

Quote:

And how much with an XMEGA E5 and pins mounted on it (price per 300)?

Priceless. :twisted: [E5s are made of unobtanium.]

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

theusch wrote:
Quote:

And how much with an XMEGA E5 and pins mounted on it (price per 300)?

Priceless. :twisted: [E5s are made of unobtanium.]

:D ah, the octarine element

my question was actually how much it would cost to put a 32 pin component on that PCB + pins. nice to be able to buy a certain PCB at 0.8$ but that is not the total cost.

It'll probably be cheaper to build a complete SMD PCB and outsource SMD soldering. TH we can do ourselves at low volumes. So a DIP package for this XMEGA is interesting due to the low production volume of the product.

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

Quote:

but that is not the total cost.

It is in my back bedroom. I don't need more than one - I'm a "hobbyist". I'm not great at SMD soldering (or any soldering for that matter) but I think I could have a fair crack at a 32 pin device.

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

clawson wrote:
Quote:

but that is not the total cost.

It is in my back bedroom. I don't need more than one - I'm a "hobbyist". I'm not great at SMD soldering (or any soldering for that matter) but I think I could have a fair crack at a 32 pin device.

I tried once. Damn difficult to do. I've wasted 3 prototypes and 4 hours in some small rework :D. TQFP pins are very close to each other.

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

Let's face it guys (and I did about 10 years ago extremely reluctantly) you need to use SMD devices if you want to use modern stuff.

Companies do not make money from hobbiest but from consumer stuff which needs to be smaller and smaller.

I would love to see the E5 in a PDIP package like other devices but would love to see them even more in a socketable PLCC package which is extermely unlikely.

I have designed a simple 28 pin 0.6" spacing breakout board which will mount on a 28 pin socket, I should get a few in about a week I hope. But that was just for fun. Soon breakout boards will be available everywhere like it happens with everything else not easily usable by hobbiest.

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Quote:
was the webinar worth watching?
I was up at 1am :cry: but could not log on until after the webminar was finished and posted.

It is only about 30 minutes long and availbale on demand now from the training page of the Atmel site.

One of the thing I had missed was the fact that the bootloader flash is ADDITIONAL to the user flash, so the 8E5 has in fact a 10K flash device while the 16E5 is 20K and the 32E5 is 36K.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I wrote above

Quote:
DHL delivered a couple of the new Rev B Xmega32E5
But the chip still shows up as rev A in the progammer and the "undocumented features" present in the older chips are still there in the new chip :roll: (different markings on the chip) I tink I have been flimflammed..... :lol:

I'll email Atmel with details for an explanations.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

And for the unbelievers that the chip really exist. :-) (the rest of the board is top secret :wink: )

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Quote:

And for the unbelievers that the chip really exist

Hmmm--to this old bit-pusher, it could be an ATtiny48... :twisted:

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

But it isn't, it's a Xmega32E5. :wink:

Not the greatest photographer in the world I know. Not very happy with the quality of the silk screen on the board either, the 2nd time they have messed things up.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Very Nice!

Hand assembled or machine assembled?

The parts look pretty small and pretty precisely oriented to be done by hand, but maybe you are just that good at it!

JC

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

Hand assembled....with one semibad eye. (floaters)

Quote:
but maybe you are just that good at it!
What can I say. :lol:

Too early for machine assembly, may still need to do some small mods to the board once I get some prospective clients feedback.

How is your "problem" coming along? Got flashing LEDs yet?

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:
..But the chip still shows up as rev A in the progammer and the "undocumented features" present in the older chips are still there in the new chip ....

What do the marking underneath say ?
Should have a Die ID and a Die revision letter ?

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

Quote:
How is your "problem" coming along? Got flashing LEDs yet?

Short answer: "No".

I can do lots, but not yet Interrupt driven.

I think my Dragon is flaky. I tried to learn about debugging in Studio 6 and sometimes I can read the Xmega's Signature, sometimes I can't. Once or twice I thought I was debugging, but things locked up... My AVR ISP mkII always connects flawlessly, but it isn't a debugger, and I don't have a JTAG device.

I think I have the Vector Table correct, in the def.dat file, but I don't think the (Bascom) compiler is routing the interrupts to the correct vector address. I'm sure this is my mistake, I just haven't tracked it down, yet. To be fair, Bascom doesn't officially support the E series yet.

Blinking in the Main Loop, running the LCD, and as of this evening running the 7-Segment display all work. I had to simulate Interrupts in the Main Loop to trigger the 7-Segment LED Driver, however.

This test project was going to be a GPS clock to drive the 7-Segment display, but its tough to do an Interrupt Driven Ring Buffered USART when you are having Interrupt difficulties. I haven't used a 7-Seg LED display in many years, but thought it would be a good test of the new chip to write a driver for it.

The 7-Seg is so bright the LCD display doesn't show up well in the photo, but they both look good on the real hardware.

I'll tell you, however, some days I really think I ought to trade in my O'scope for some golf clubs!

JC

Attachment(s): 

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

Quote:
I think I have the Vector Table correct, in the def.dat file
Unless you have changed it from the one you sent me before it is not correct.

You still had the TCC0 vectors in there and the new vectors for TTC4 and TCC5 were all the way on top of the table away from where they should be.

The Dragon seems to work well with the E5, I'm switching between it and the JTAG Mk3 when I think something is fishy...but it is still fishy with the Mk3 :-) let's wait until AS6.1 full gets released before complaining too much. Shouldn't be too far away.

Quote:
What do the marking underneath say ?
T47 Philippines.

The top markings:

The new chip has the following markings:
Xmega32E5-UES
1312B PH
A3U1146-1

The older chip and the chip on the Xplain board have the following markings:
Xmega32E5-U
1240A PH
2X1036-3

The programmer still shows them both as Revision A. I have emailed Atmel about this.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I solder TQFP parts from time to time, including the XMEGAs. The 0.8mm pitch ones are fine, 0.5mm could be tricky.

I was working on a break-out board for the 64 pin parts but might switch to the 32 pin ones now. As well as the usual caps and an inductor for AVCC I think an LM4040 2.048V reference would be handy. Maybe squeeze a micro USB socket on as well.

One nice thing about adapter boards is that if you solder the pins in "upside down" so they poke up it is easy to get probes on to them.

Maybe someone (me? nah) should do a little Kickstarter project or something to do a run of DIP converter PCBs with the smaller MLF package parts professionally soldered on.

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

Quote:

The new chip has the following markings:
Xmega32E5-UES
1312B PH
A3U1146-1

The older chip and the chip on the Xplain board have the following markings:
Xmega32E5-U
1240A PH
2X1036-3


Back when I was your age :twisted: the letter at the end of the second line on an AVR indicated the die revision. But there has been a lot since then, including the fab outsourcing.

From a traditional point of view, it looks like date codes of Week 40, 2012 and Week 12, 2013 so the "new" chip appears ... newer.

The new chip has an ES -- I'd guess Engineering Sample.

The letter after the date code -- A, B -- could be the die rev? It would seem to correspond to the Errata section of the datasheet.

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

Quote:
the second line on an AVR indicated the die revision
OK but the programmer tells me Revision A, maybe I don't understand what the programmer is saying. :-)

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

If the original silicon was not publicly sampled and was revised, the public silicon will probably have a revision A monkier as well. Your top-markings seem to indicate it's physically revision B silicon.

- Dean :twisted:

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

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

Since XMEGA chips have a separate revision byte in the signature row I doubt that the programmer would be reading it wrong, so chances are Atmel forgot to increment it in this revision :-)

The rev. C change list will be:

- Fixed incorrect chip revision byte

Speaking of which, I wonder if they fixed the bug with reading back the signature row values with EEPROM power saving enabled.

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

Quote:

Since XMEGA chips have a separate revision byte in the signature row I doubt that the programmer would be reading it wrong, so chances are Atmel forgot to increment it in this revision

There's a difference when the device hasn't been released; if it's an internal-only version the silicon revision might not be incremented when the device goes public, so that the first shipped silicon is revision A to prevent customer confusion (not very well in this case, since some non-final silicon got into John's hands :P).

- Dean

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

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

Apparently there will be an updated Studio "part pack" for rev B released shortly, so we wait until then. :-)

Everything is working pretty well though even if I have to do a bit of contortionism with the timers (as Dean may remember among millions of other things he needs to remember) possibly due to incorrect Studio files or me not understanding how the "new" timers are supposed to work.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Perhaps someone can enlighten me as to how the new EDMA data match feature works.

The XMEGA E manual states that it will end the EDMA transfer when data matches. The data to be matched is placed in the memory address register, which suggests that the memory address register is not being used to actually store the data in SRAM. Is that a fair assumption?

I was thinking about using this feature for receiving data from a GPS module. It sends sentences over a USART that start with a $ sign and end with a newline (\n) character. Ideally the EDMA controller could trigger when the $ character arrives and automatically end the transaction when the newline arrives and generate an interrupt. Is that sort of thing possible?

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

The above E5 breakout board built. https://www.avrfreaks.net/index.p...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I think you accidentally a word :-)

Looks good though. How does it work?

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

Ha, looks like I accidentally a word too :-)

I should have asked "how well does it work?"

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

Haven't tried it yet, I have been busy dismantling my test jig and figure out what I did 20 years ago! :roll:

I put the test jig diagram in a safe spot so I wouldn't lose it..I know I did....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Well it works, just hacked some code from another project to generate a sine wave and it's sineing.

At least I know that 1 pin is working along with the PDI pins. :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I really can't wait to have a play with one now. Unfortunately it usually takes the UK a loooong time to get any stock.

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

How are the ADC's performing?

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

The ADC seems to work well. I haven't yet carried out a very strict test (or calibration) but I'm happy enough with it's performance for my application to lead me to remove the external 12 bit ADC I fitted as back up in the first prototype.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Have you tried the oversampling functionality? I'm very interested in that and what the noise is.

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

I believe the Rev. A E series has two Errata, (silicon bugs), regarding the ADC averaging feature.

Of interest, neither is still listed in the Rev. B chip's Errata list.

It should, therefore, work as per the data sheets.

JC

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

But js told us he had "rev A"...

Quote:

I wrote above
Quote:
DHL delivered a couple of the new Rev B Xmega32E5
But the chip still shows up as rev A in the progammer and the "undocumented features" present in the older chips are still there in the new chip Rolling Eyes (different markings on the chip) I tink I have been flimflammed..... Laughing

I'll email Atmel with details for an explanations.

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

The code I had before (non E5) does multipe ADC reads and average them so I haven't tried the oversampling (too busy with other things).

There also seems to be some automatic interrupt which can be set when the ADC value reaches some point which could simplify things but again I'm playing safe for now and use what I know has worked before.

Once I get on top of things and have more time I'll be more adventurous, by then more people should have some chips in their hands so that we can bounce things off each other.

I'm still at a loss believeing that only 2 people in this forum have the E5.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Well I got my own Xplained board on Friday for it, so you're not totally alone now...

- Dean :twisted:

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

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

Well start working on the timer flags issue (or most likely misunderstanding on my part). :wink:

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

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I'm not familiar with ADC's of XMEGA and certainly not of the E version. I've some questions:
* what would be the sample rate in 16 bit mode (1024 times oversampling) on 4 differential + 2 single ended channels (scanning those 6 inputs).
* can this scanning be done by DMA?

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

jan_dc wrote:
* what would be the sample rate in 16 bit mode (1024 times oversampling)

ADC in XMEGA is 12-bit. 1024 times oversampling gives additional 5 bits, as of 1024=2**10 and it gives the squre root of that. So with 1024 times oversampling it would be 17-bit mode.
But it will have large nonlinearity, which is not so depend from oversampling, and the precision will be not much better than in 12 bit mode.

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

maksim wrote:
jan_dc wrote:
* what would be the sample rate in 16 bit mode (1024 times oversampling)

ADC in XMEGA is 12-bit. 1024 times oversampling gives additional 5 bits, as of 1024=2**10 and it gives the squre root of that. So with 1024 times oversampling it would be 17-bit mode.
But it will have large nonlinearity, which is not so depend from oversampling, and the precision will be not much better than in 12 bit mode.

oops, I ment 256 times. The 1024 is from the averaging specification. I need about 10 measurements per channel per second at 1.8MHz clock frequency. According to the specifications it should be feasable but I have no idea of the stability of the ADC when it's continuously switching/scanning.

Yes, you're right about the non linearity. I forgot that one.

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

Good afternoon everybody.
I was asked to develop a new project with this uC. I was searching for the first info and I see there's no support for it in avr-gcc. just avr studio have it. and I don't use windows... :P
Do you know how long I should wait for have it supported by avr-gcc on linux?

I can start developing in a virtual machine. no problem with it. But I want to leave it as soon as possible.
thank you for any info you can do.
A

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

It's supposed to work with the latest Atmel toolchain. There is a stand alone version for Windows and one for Linux.

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

Oh! great. So there's an Atmel toolchain on the website? I always used avr-gcc shipped with the distribution. Need to find it :)
Thank you for your reply
Andrea

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

Quote:

So there's an Atmel toolchain on the website?

See this thread:

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

To avoid Atmel's registration rubbish use the links in the post from SprinterSB.

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

Thank you clawson,
I installed it. Need to wait for my new demo uc and socket for stk600 for testing it. :)

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

looks like my samples will be here at the end of august... I asked for them on june 15th... 75 days for 3 samples is not too much?

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

If I try to get production signatures (Xmega16/32 E5 Rev. B) using AvrIsp mkll error message appears "memory read fails at offset 0x35". Other successfully read Registers contain 0. Any ideas why?