Dear All,

I guess a lot of you are using the AVR range of devices, so hope the answer 
to my question below will seem straightforward.

The hardware engineers on my team wish to use the ATmega64 in a design we're 
working on. I'm the software engineer. The design relies on having 2 UARTs 
and and an SPI bus available simultaneously. On paper, this processor seems 
to provide this. However, I'm concerned that some of these functions may be 
multiplexed, i.e. can only have 2 UARTs and no SPI, or 1 UART and SPI 
present.

The data sheets are a little vague on this. Can anyone shed some light on 
this?

Very many thanks in anticipation!

Kind regards,

Clive Wilson 

"Anon" <a...@nowhere.invalid> wrote in message
news:9...@giganews.com...
> Dear All,
>
> I guess a lot of you are using the AVR range of devices, so hope the
answer
> to my question below will seem straightforward.
>
> The hardware engineers on my team wish to use the ATmega64 in a design
we're
> working on. I'm the software engineer. The design relies on having 2 UARTs
> and and an SPI bus available simultaneously. On paper, this processor
seems
> to provide this. However, I'm concerned that some of these functions may
be
> multiplexed, i.e. can only have 2 UARTs and no SPI, or 1 UART and SPI
> present.
>
> The data sheets are a little vague on this. Can anyone shed some light on
> this?

Well, a quick glance at the datasheet reveals that RXD0, TXD0, RXD1, TXD1,
MOSI, MISO and SCK all have their own pins. Not much of a problem then...
:-)

Meindert

"Meindert Sprang" <m...@NOcustomSPAMware.nl> wrote in message 
news:1...@corp.supernews.com...
> "Anon" <a...@nowhere.invalid> wrote in message
> news:9...@giganews.com...

<snip>

> Well, a quick glance at the datasheet reveals that RXD0, TXD0, RXD1, TXD1,
> MOSI, MISO and SCK all have their own pins. Not much of a problem then...
> :-)

OK, thanks. After having posted I took another, more careful look, and 
realised I was panicking unnecessarily.

Thanks anyway,

Clive Wilson 

"Anon" <a...@nowhere.invalid> schreef in bericht
news:W...@giganews.com...
>
> "Meindert Sprang" <m...@NOcustomSPAMware.nl> wrote in message
> news:1...@corp.supernews.com...
> > "Anon" <a...@nowhere.invalid> wrote in message
> > news:9...@giganews.com...
>
> <snip>
>
> > Well, a quick glance at the datasheet reveals that RXD0, TXD0, RXD1,
TXD1,
> > MOSI, MISO and SCK all have their own pins. Not much of a problem
then...
> > :-)
>
> OK, thanks. After having posted I took another, more careful look, and
> realised I was panicking unnecessarily.
>
> Thanks anyway,
>
> Clive Wilson
>

Better panic now then when everything has been designed and changing things
is far more costly ;)

Jeroen

In article <42161a28$0$28985$e...@news.xs4all.nl>, n...@none.com 
says...
> 
> "Anon" <a...@nowhere.invalid> schreef in bericht
> news:W...@giganews.com...
> >
> > "Meindert Sprang" <m...@NOcustomSPAMware.nl> wrote in message
> > news:1...@corp.supernews.com...
> > > "Anon" <a...@nowhere.invalid> wrote in message
> > > news:9...@giganews.com...
> >
> > <snip>
> >
> > > Well, a quick glance at the datasheet reveals that RXD0, TXD0, RXD1,
> TXD1,
> > > MOSI, MISO and SCK all have their own pins. Not much of a problem
> then...
> > > :-)
> >
> > OK, thanks. After having posted I took another, more careful look, and
> > realised I was panicking unnecessarily.
> >
>
There are other issues to consider than whether SPI and USART have 
separate pins.   That is true on the MSP430, but internally, both
modes use some common registers.   That can make it difficult
to use both the SPI and USART in anything except polled mode operation.

If you are going to rely on interrupt-driven I/O for the USART, you
may not have the freedom to switch modes between SPI and USART without
risking the loss of incoming USART data.

Mark Borgerson

> > Well, a quick glance at the datasheet reveals that RXD0, TXD0, RXD1,
TXD1,
> > MOSI, MISO and SCK all have their own pins. Not much of a problem
then...
> > :-)
>
> OK, thanks. After having posted I took another, more careful look, and
> realised I was panicking unnecessarily.
>

After everything else fails, read the instructions ;-)
I think this should work fine.

-- 
Best Regards,
Ulf Samuelsson
u...@a-t-m-e-l.com
This message is intended to be my own personal view and it
may or may not be shared by my employer Atmel Nordic AB

Ulf Samuelsson <u...@a-t-m-e-l.com> wrote:

> After everything else fails, read the instructions ;-)

Or, as an acquaintance of mine puts it: "RTFM?  You must be kidding.
Real engineers only refer to documentation if the keyboard-shaped
dents in their forehead become too obvious."

-- 
Hans-Bernhard Broeker (b...@physik.rwth-aachen.de)
Even if all the snow were burnt, ashes would remain.