Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Thread

Re: [AVR-Chat] Prototypitis

Re: [AVR-Chat] Prototypitis

2005-03-01 by John Samperi

Hi David

Here I am chewing my finger nails waiting to hear
the reults of you Prototypitis :-)

I'm about to modify one of my boards currently using a
Motorola HC711 chip over to a M64 (or M128), so I'm interested
in your misfortunes so that I can learn and avoid them,
especially the random Int. on the second UART, which is one
of the reasons I'm changing over because I need 2 UARTS from
time to time (and of course Motorola has lost favor with me lately).


Regards

John Samperi

******************************************************
                         Ampertronics Pty. Ltd.
   11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
          Tel. (02) 9674-6495       Fax (02) 9674-8745
                Email: samperi@ampertronics.com.au
                  Website  http://www.ampertronics.com.au
* Electronic Design   * Custom Products   * Contract Assembly
******************************************************

Re: [AVR-Chat] Prototypitis

2005-03-01 by Dave VanHorn

At 04:23 PM 3/1/2005, John Samperi wrote:

>Hi David
>
>Here I am chewing my finger nails waiting to hear
>the reults of you Prototypitis :-)\

Me too.. I'm just not seeing why the uart should even BE interrupting me 
like this.
It's probably something simple, but according to the registers displayed by 
the ICE, there's no reason for the int.


>I'm about to modify one of my boards currently using a
>Motorola HC711 chip over to a M64 (or M128), so I'm interested
>in your misfortunes so that I can learn and avoid them,
>especially the random Int. on the second UART, which is one
>of the reasons I'm changing over because I need 2 UARTS from
>time to time (and of course Motorola has lost favor with me lately).

"There are AVRs with more uarts.", he said mysteriously...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.