For people in this newsgroup that has been wondering...


Key features
* ATmegaAVR core (just higher frequency)
* 1.6V-3.6V operation
* Flash (max 384 kB)/SRAM/EEPROM
* 32 Mhz operation (max 32 MIPS)
* 44/64/100 pin package
The pinout allows a design to use 44,64 and 100 pin concentric pads
with S/W compatability. Pin multiplexing will be identical for
all I/O ports, Larger devices will have extra ports, not different
ports.
* 12 bit 2 Ms ADC/1 Ms DAC
* 4 level interrupts
* 4 channel double buffered DMA
* Advanced timers for Motor control
* Fancy new event system
* 2 uA in sleep w Brownout protection and 32 kHz osc.
* 100 nA in deepest sleep mode
* External bus in larger devices with SRAM/SDRAM support

First parts are available now in sample qty.

Press release
http://www.atmel.com/dyn/corporate/v...C_NAME=Product

Datasheet
http://www.atmel.com/dyn/products/pr...N=ATxmega128A1


--
Best Regards,
Ulf Samuelsson
This is intended to be my personal opinion which may,
or may not be shared by my employer Atmel Nordic AB

On Feb 28, 12:28 am, "Ulf Samuelsson" <u...@a-t-m-e-l.com> wrote:
Only thing missing is a LCD segment driver. Otherwise, we would jump
right into it.

linnix <me@linnix.info-for.us> writes:

And an extra 24 bits of register width... And a Von Neumann
architecture.

--

John Devereux

John Devereux wrote:
It's fair enough that it's an 8-bit architecture, but they could have
put a little effort into fixing the most glaring design flaws of the
cpu. Why not drop the fmul* instructions that almost never get used,
along with the rcall opcodes (I guess they are used by Forth systems,
but I can't see they are much use to a C compiler), and add some of the
features that would have made a real difference to the cpu power for C
programming? Adding an X+q mode comparable to the Y+q and Z+q, and
making R24:R25 a forth pointer register would be a big help. Support
for (SP+q) addressing would be a benefit, although it would not be too
important if it there was more if a forth pointer with W+q addressing
modes existed. A method of atomically accessing the 16-bit stack
pointer would be useful, however.

As for making it entirely von Neumann, I think that's a bit too big a
change - but it would have been perfectly possible to make the flash
accessible in the data space as well (in the same way as the eeprom is
now mapped into the data space). You'd need 24-bit pointers to access
it, but it would still be a very useful feature.

It's also missing a CAN controller, and the SDRAM setup is a bit odd (it
should be possible to get an 8-bit SDRAM bus using only three ports).

Apart from that, it looks a very nice chip, which we will probably find
use for. Maybe I can use it to drive my QVGA screen...

On Feb 28, 9:53 am, David Brown
<david.br...@hesbynett.removethisbit.no> wrote:
Adding to the AVR wish list. Having access to the SPI engine from the
CPU would be nice. There are many features of the uC available to
external SPI access, but impossible to do internally. For examples:
fuses and lock bits, flash and eeprom.

Ulf Samuelsson wrote:
Missing in these devices is any mention of LIN support ?

(but they do have a truckload of serial ports, and
Quadrature counting, Ulf left of his list..)

Peripherals is where all the action is these days.

-jg

linnix wrote:
You mean the programming interface ?
flash and eeprom are surely available ?

Fuses ? - a good uC should be able to READ the fuse status, but
IAP programming them is a different call: Higher risk, and lower
security ?

-jg

On Feb 28, 10:39 am, Jim Granville <no.s...@designtools.maps.co.nz>
wrote:
No more riskier than being able to reprogram the flash. They can have
a very complicated sequence to change the fuses/locks.

On Feb 28, 12:22*pm, linnix <m...@linnix.info-for.us> wrote:

Atmel introduced the SAM7L series a few days ago, which is low power
and has an LCD segment driver, but meager SRAM (always something!)

http://www.atmel.com/dyn/corporate/v...M7L_2_26..html

On Feb 28, 11:00 am, steve <bungalow_st...@yahoo.com> wrote:
But it does not come in 44 pins. We are small people working on small
projects, so smaller chip is better. We need 16K flash, 4 A2D and
12x4 or 8x8 segmented LCD.

linnix wrote:

A 44 pin device with LCD drive would be a very unusual animal ?.

You might be better off with 2 chips, a 'uC of your choice',
and a LCD driver chip ?.

On the subject of the AT91SAM7L - anyone seen a price on the
Eval Kit - that has a nice looking LCD ?

-jg

On Feb 28, 2:23*pm, linnix <m...@linnix.info-for.us> wrote:
I think only microchip makes small 28 and 44 pin LCD devices that are
close to what you need

http://www.microchip.com/stellent/id...ram=en 022838

On Feb 28, 12:11 pm, steve <bungalow_st...@yahoo.com> wrote:
Yes, I think the 16F913 w/ 28 pin QFN is what I need. Unfortunately,
I have to learn pic now.

On Feb 28, 3:33*pm, linnix <m...@linnix.info-for.us> wrote:
you have my sympathies

is your "small" constraint more size or price? you can use any old
micro to drive an segmented LCD, but requires external parts (cheaper
but bigger)

On Feb 28, 12:44 pm, steve <bungalow_st...@yahoo.com> wrote:
Both. I guess more for price than size.

Yes, it is in the drawing board as well. We need an external charge
pump and regulator to constant 3V from 2V to 6V battery range.
Luminary Micro ARM Cortex M3 is also possible.

"David Brown" <david.brown@hesbynett.removethisbit.no> skrev i meddelandet
news:47c6f520$0$15000$8404b019@news.wineasy.se...
Which of course require a new compiler...
The decision was made to not change the CPU core.

The AVR core supports 16 MB dataspace and 8 MB instruction space.
I think that if the code was mapped to the upper 8 MB of the dataspace
there would be no conflicts.
Again, such a change would probably affect the compilers,
which was undesirable.

I assume that the fancy stuff will come in future chips.

--
Best Regards,
Ulf Samuelsson
This is intended to be my personal opinion which may,
or may not be shared by my employer Atmel Nordic AB

I think that you might be able to create a simple LCD controller with the
X-Mega DMA controllers, timers and the event handling.

--
Best Regards,
Ulf Samuelsson
This is intended to be my personal opinion which may,
or may not be shared by my employer Atmel Nordic AB

On Feb 28, 1:23 pm, "Ulf Samuelsson" <u...@a-t-m-e-l.com> wrote:
Yes, as long as we can set the outputs at 3V, regardless of battery
voltage.

"linnix" <me@linnix.info-for.us> skrev i meddelandet
news:30e2fb0a-53b2-429d-80b7-15b040def232@x30g2000hsd.googlegroups.com...
You have a PLL with 4 x CPU clock (128 MHz) connected to
a timer, so It may be possible (didn't check) that you
can do a switch regulator for some of the I/O pins.

--
Best Regards,
Ulf Samuelsson
This is intended to be my personal opinion which may,
or may not be shared by my employer Atmel Nordic AB

On Feb 28, 2:15 pm, "Ulf Samuelsson" <u...@a-t-m-e-l.com> wrote:
Yes, the external oscillator, booster and regulator will be assisted
by uC software. It will be a combinations of transistors, diodes,
resistors, capacitors and mutual inductors. Actually, we already have
the circuit in the production device, but they are not yet populated
and activated. We just want to make sure there is enough space for
it. The power circuit is on a separate circuit board, so no space
limitations there. However, the uC must fit inside the 0.8" width of
the LCD glass. It is very tight with the 64 pins MLF.