XMEGA

Go To Last Post
440 posts / 0 new

Pages

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

It's in this thread, John: http://www.avrfreaks.net/index.p...

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

Thanks Kevin. Did you use the EVENT system of the Xmega (does not look like)...or can you have a go at that? It's about the only interesting bit about the Xmega. (Start of Xmega vs Mega/Tiny war :evil: )

I guess you should be able to use the event/dma to pump things out of the lookup table and into the dac.

Or did I get it all wrong? If I did then no Xmega appeal at all. :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

John, the posted code does not use the event system. However, I entertained the idea of using the event system to limited the number of DACs to 1M/s or less (as per the datasheet). Currently, the code is outputting 3.5M/s but the output looks great on the scope.

To use the event system, I considered an audio synthesizer that outputs at 44.1kHz. One connects a timer which triggers an event every 1 microsecond. That event triggers the pending DAC as well as triggers an interrupt. The ISR computes the next value to output to the DAC and stores in the DACs buffer where it awaits the next event. This way, one gets a completely stable 44.1kHz DAC output without worrying about jitter in interrupt latency.

I'm a big fan of XMegas (especially their cost being lower than most larger Mega). But, I suppose I just like AVRs -- I really like Tinys and Megas, too!

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

I have exchanged emails with Digikey on the reason why Xmegas are not listed on the Digikey UK site. The story is :

Digikey cannot export Xmegas because they don't have the proper export license for them. Consequently they only list them on the US website.

:x :evil: :x :x :x (couldn't think of any words)

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

So much for the highly vaunted advantages of 'free trade'. Seems that you could get a Norski product quicker in the UK than in the US anyway. Where is the fab? Any Canuck distribs getting them? Will they ship to the UK?

Imagecraft compiler user

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

Quote:
Where is the fab?

Likely it is in the US.

Quote:
Any Canuck distribs getting them?

Digikey Canada has them listed.

Regards,
Steve A.

The Board helps those that help themselves.

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

I thought the AVR fabs were in France - or perhaps I just dreamt that? I know that Atmel had a fab in the North East of England that closed down last year but I don't think it was making AVRs.

EDIT: Actually http://www.secinfo.com/dScj2.u3q... has the phrase

Quote:
Streamline manufacturing strategy

Retain low-cost fab in Colorado for Microcontroller business


So maybe they are being made in the clean air of Colorado?

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

Some more information about Atmel fabs and what is going on inside Atmel. Must been some rough times at Atmel:

http://www.eetimes.com/news/semi...

Stealing Proteus doesn't make you an engineer.

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

In recent times I have bought AVR's made in USA & Mega's made in South Korea. They seem to use fabs worldwide which is why a bit of consolidation is in progress.

I suspect the more important issue is where they were developed. At one time it was Norway but I suspect this may have moved to the US.

However, the real issue must be availability outside North America. This may be a simple failure of Digikey to get its act together getting export licences. In which case the best course of action is for us to keep nagging them till they sort it out.

Until then those of us, outside North America, whos use is to small for direct purchase from Atmel have a problem.

Trevor

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

Sorry, double post. See below!

Last Edited: Thu. Sep 4, 2008 - 11:55 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

As far as I know your options are JTAGICEmkII (later models), STK600 or AVR One.
Cliff

Hi Cliff,

how can I know if I have a 'later model' of the JTAGICEmkII? I have got problems to connect to my Xmega128A1...

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

I think it says in the Studio helpfile but the good news is that there's now an SP1 for 4.14 that adds X support (PDI) to the much cheaper AVRISPmkII

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

OK, I found it. I have to make an adapter first. The online help told me that I have an old JTAGice.:cry:

But will I be able to debug with the AVRISPmkII?

What about the AVRONE? Are there any experiences with it? Does it work with the AVRStudio or do I have to switch to AVRStudio32? Does it REALLY support the XMEGA:?:

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

Quote:
But will I be able to debug with the AVRISPmkII?

The AVRISPmkII does not have on chip debugging capabilities.

Quote:
What about the AVRONE? Are there any experiences with it? Does it work with the AVRStudio or do I have to switch to AVRStudio32? Does it REALLY support the XMEGA:?:

I don't believe that it currently supports the XMEGA or AVR Studio, but support should be added in the future.

Regards,
Steve A.

The Board helps those that help themselves.

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

YES! I've got my XMEGA running! :D

My problem was that I had an old JTAGICEmkII. Somewhere hidden in the AVR-Studio Online Help you can find the information that the serial number must be B000.. or higher. My old JTAGICEmkII had A000...

PDI with the AVRISPmkII still does not work with my hardware. I have to doublecheck the connections. If I get it working I will inform you.

(I am using AVR Studio 4.14 Build 603)

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

PDI with the AVRISPmkII works now, too. I did a mistake with the PDI connection.
@Koshchi: You are right. You can only program (not debug) with the AVRISPmkII. Although I expected this I wonder if the PDI is only for programming? Or can I use PDI together with the JTAGICEmkII to debug?

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

PDI = Programming and Debugging Interface. Works for both programming and debugging :-)

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

But presumably not with an AVRISPmkII ? (that is it'll be PI not PDI)

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

clawson wrote:
But presumably not with an AVRISPmkII ? (that is it'll be PI not PDI)

Correct. If you start a debug project with the AVR Studio it does only offer Dragon, JTAGICEmkII and so on but not AVRISPmkII. Only if you connect to target for programming the AVR Studio offers AVRISPmkII. And if you have the AVR Studio 4.14 Build 603 then you can program a XMEGA with your AVRISPmkII.

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

ce wrote:
Somewhere hidden in the AVR-Studio Online Help you can find the information that the serial number must be B000.. or higher.

Nice, the sticker on mine says B0000031BA. This is the first time I've had it out of the box. I bought this lead contaminated one at half price from Arrow because I couldn't pass up a bargain. :)

If I ever get an Xmega, I'll put on my hazmat suit and fire it up. :)

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

ce wrote:
...And if you have the AVR Studio 4.14 Build 603 then you can program a XMEGA with your AVRISPmkII.

According to Atmel's AVRStudio web-site, version 4.14 Build 589 is the latest version. Where did you come by build 603?

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

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

Regards,
Steve A.

The Board helps those that help themselves.

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

Thanks for the link, Steve.

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

Koshchi wrote:
Possibly here: http://www.atmel.no/beta_ware/
I found two download links for "AVR Studio 4.14 Service pack 1". One is for 'AS414SP1.exe' and the other for 'AVRStudio4SP1Setup.exe' is a broken link.

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

To get AVR Studio 4.14 Build 603 you have to download and install AS414SP1.exe.
Follow this link:
http://www.atmel.no/beta_ware/

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

I have looked high and low for documentation on the pinout of a programming header to hook an AVRISP MKII to an XMEGA chip. Even a very switched on local distributor couldn't find any documentation. Does anyone have a schematic ?

regards
bugwhiskers

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

Quote:
Does anyone have a schematic ?
The only thing I can find is the one on page 308 of the Xmega A specs. I have not seen any physical pinout. Perhpas it may be somewhere hidden with the new service pack help files??

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

bugwhiskers wrote:
Does anyone have a schematic ?
If you open the help of AVR Studio 4.14 Build 603 then you have to choose 'AVR Tools User Guide'. Then click on 'User Guide' for AVRISP mkII. In chapter 2.5 'Target Interface' you will find the pinout for the PDI interface. Just connect it to RESET/PDI_CLK (pin 90 at XMEGA A1, TQFP) and PDI_DATA (pin 91 at XMEGA A1, TQFP) to your XMEGA.

It works fine (programming only)!

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

...and don't forget VCC and GND??

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:
...and don't forget VCC and GND??
Yes, of course!

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

Correction, PIN 89 is PDI_DATA and PIN 90 is PDI_CLOCK.

AVRISP MKII HEADER TO XMEGA PDI

PIN1 --> PDI_DATA, TQFP100 PIN 89
PIN2 --> VCC (MAX 3.6V)
PIN3 --> NO CONNECTION
PIN4 --> NO CONNECTION
PIN5 --> PDI_CLOCK, TQFP100 PIN 90
PIN6 --> GND

regards
bugwhiskers

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

Quote:
My problem was that I had an old JTAGICEmkII. Somewhere hidden in the AVR-Studio Online Help you can find the information that the serial number must be B000.. or higher. My old JTAGICEmkII had A000...

In order to use PDI yes, but you can use JTAG instead if i understand correctly.

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

kris10an wrote:
Quote:
My problem was that I had an old JTAGICEmkII. Somewhere hidden in the AVR-Studio Online Help you can find the information that the serial number must be B000.. or higher. My old JTAGICEmkII had A000...

In order to use PDI yes, but you can use JTAG instead if i understand correctly.

No, with my old JTAGICEmkII (serial: A000...) I was not able to connect to the XMEGA at all (no JTAG and no PDI). Exchanging the old JTAGICEmkII with a new one worked.

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

Did Atmel exchange the JTAGICEMkII for you?

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

I was wondering, could an XMega drive a WQVGA display in 24-bit parallel RGB mode(DCLK 11.1 MHz), or 8-bit serial RGB mode(DCLK 33.3MHz)? Or will I need a 32-bit microcontroller anyway? It's to interface with a HX5116-A AMOLED chip driver.

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

Well I don't see how a 32MHz processor could do a 33.3MHz pixel clock. I'd have thought you'd need something a bit faster, even with the DMA that's available.

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

I'd say you need a display controller for that.

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

kmr wrote:
Did Atmel exchange the JTAGICEMkII for you?
I did not ask, because I needed a second one anyway.

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

Trevor_G wrote:
I have exchanged emails with Digikey on the reason why Xmegas are not listed on the Digikey UK site. The story is :

Digikey cannot export Xmegas because they don't have the proper export license for them. Consequently they only list them on the US website.

:x :evil: :x :x :x (couldn't think of any words)


Now, that is quite interesting. Perhaps DigiKey isn't "caught up" on the Xmega yet because they have received no stock. Or contact Nu Horizons -- ;) -- as the Sept. 11 Webinar says "No export restrictions from USA" in both the text and in the presentation.
http://www.nuhorizons.com/xpress...

Lee

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 situation with Digikey has moved on. A few weeks ago Xmegas were added to the UK website but you could not place an order due to export restrictions! I contacted them again and was told there was no prospect of the export licence being obtained. Last week the Xmegas were removed from the UK website again.

To a certian extent this is academic because Digikey have yet to receive supplies of any Xmegas. They are listed as "8/28/2008 - Delivery Date Past Due". I will contact them again when I see they have some stock.

Trevor

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

Does that mean that if someone in the US buys a few, sticks them in an envelope and sends them to someone in Europe they are guilty of treason or something? Crikey!

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

Trevor--as I mentioned, the very new Atmel presentation makes a point of no export restrictions. If I were you I would contact Atmel to get a definitive answer. Let us know.

Re stocking levels: If you have been following Xmega threads and Xmega documents, the only known spottings in the wild have been of 128A1 Engineering Samples (E.S.) silicon rev G which have a sizable errata list. While many distis have listings of the first/announced models, none will have stock on this date.

Someone (Carl?) said they were promised 64A1 samples, but no-one has come back and posted having anything but 128A1 rev. G in their sweaty palm. Anyone?

Lee

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 good news: New datasheet revs have been posted on the Atmel site for A1, A3, A4.

The bad news: The only errata list is the one posted previously, for '128A1 rev. G.

Lee

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

ce wrote:
And if you have the AVR Studio 4.14 Build 603 then you can program a XMEGA with your AVRISPmkII.

Hmm.. I have been reading the AVR Tools User Guide.

The AVRISP mkII supported devices:
ATxmega128A1
ATxmega64A1

The JTAGICE mkII supported devices:
ATXMEGA128A1

My problem is that I want to program the ATxmega16A4. Do anyone know if this is posible?
Funny they don't have the tools ready.

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

Quote:
My problem is that I want to program the ATxmega16A4.

You have samples then?

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

Side note: Given the uncertainties in "available now", note the Atmel marketing twist on this. Something to the effect of "All Xmegas are the same, so you can develop on any model and then change to the model of your choice for production." ;)

Lee

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

clawson wrote:
Quote:
My problem is that I want to program the ATxmega16A4.
You have samples then?
No need for samples before we know if we can use the xmega16 in our project or not.

My supplier at EBV have placed the order for a few thousand units, starting with 5 samples. Hopefully I will get the confirm tomorrow.
But after reading this topic, I wonder if it's not that easy after all..
Maybe I will have to knock at Atmels door next time I'm back in Trondheim.

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

But my point was that there's no point Atmel adding 16A4 support to the AVRISPmkII or JTAGICEmkII support in Studio until someone in this world actually has the silicon in the hands. The fact is that about 4-5 weeks ago Atmel issued SP1 for Studio 4.14 with the intention, amongst other things, of adding the 64/128 support to the AVRISPmkII because they know some folks out in the wide world now have samples.

In fact it's a pretty strong indicator that samples of a device are about to ship if a Service Pack or new version of Studio is shipped. So keep an eye out for the next issue of Studio software.

But like Lee says, a supposed joy of Xmega is that you can develop on any device then size-reduce to the small ones when (if?) they eventually become available.

So you might as well get some 128A1 samples and start developing with those and (as you've seen) build 603 now has the ICE/ISP support for these.

As someone who was talking to Atmel about using a variant of the 16A4 in industrial quantities let's just say I have a bit of an insight ;)

Last Edited: Wed. Sep 24, 2008 - 03:41 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

IIRC, there were some AN from Atmel supporting your statement, Lee.

I couldn't find the exact one (it was something like Programming Style for XMegas), but this one could help to understand this twist: http://www.atmel.com/dyn/resourc...

Have fun.

Guillem.
"Common sense is the least common of the senses" Anonymous.

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

Clawson, thanks for your quick reply.

But I still got one problem... I want to use the xmega16A4 (44 pins). I can't use xmega64A1 or 128A1 for development since they have a 100 pins package.

I will post a follow-up after talking to EBV tomorrow, hopefully getting delivery dates for 16A4,32A4,64A4 or 128A4 samples. Probably am I too optimistic..

Plan B is to go back on the original design and use the ATmega64. But it would be a lot easier with the xmega Crypto Engine.

Pages