I'm going to go with "no".
Why is that? Is it because its a new line of chips?
I only spent a few minutes with the datasheet so I could easily be wrong. It looks like the basic architecture is very similar or even identical (RISC; 32 registers; very similar instruction set) to the AVR. That's the good news.
However, all the peripherals (timers, ADC, etcetera) appear to be different. The essence of most Arduino libraries is to provide a simplified interface to a peripheral. If the peripherals are different the library will be different; meaning the library will have to be rewritten. That's the bad news.
How to start off developing these to arduino compatible form?
From my experience porting to ATtiny processors...
is always first. digitalWrite
is always second. digitalRead
is always third. millis
is always fourth. With those four functions you have the ability to perform crude debugging. If possible, Serial
• Porting the Arduino API is a creative endeavor. You need to be prepared for a long-term commitment. There will be fits and starts as your brain works out how to solve a problem.
• Porting the Arduino API is an intimate endeavor. You need to have the hardware in one hand and the datasheet in the other. I keep a notebook where I can write down ideas and snippets of useful information.
• Porting the Arduino API is an incremental endeavor. Steal. Whenever possible, "steal" something that works. That is one of the biggest advantages open-source has over closed-source. Leverage that advantage.
• Ensure the toolset is ready. I believe the Arduino IDE ships with a compiler for the XMega processors. Make certain. Google will very likely be able to answer.
• Get the hardware.
You may want to spend some time with Google performing general searches. For example, this looks helpful...http://blog.omegacs.net/2010/06/26/getting-started-with-xmega-differences-from-atmega-part-1/