From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.182.22.133 with SMTP id d5mr9607906obf.27.1395058654716;
        Mon, 17 Mar 2014 05:17:34 -0700 (PDT)
X-Received: by 10.182.28.129 with SMTP id b1mr361obh.37.1395058654419; Mon, 17
 Mar 2014 05:17:34 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!ur14no8866795igb.0!news-out.google.com!gi6ni236igc.0!nntp.google.com!ur14no8866794igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 17 Mar 2014 05:17:33 -0700 (PDT)
In-Reply-To: <2528b8c4-93a8-4fb8-a6a5-192493d5d616@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=192.109.190.88;
 posting-account=mOyWBQoAAAD7S-NBmMUOr9hRClcL0vqR
NNTP-Posting-Host: 192.109.190.88
References: <2528b8c4-93a8-4fb8-a6a5-192493d5d616@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <01818147-3406-414e-8481-7dc875ef213c@googlegroups.com>
Subject: Re: Interrupt-driven Usart not working in Ada, but in C working, why?
From: rrr.eee.27@gmail.com
Injection-Date: Mon, 17 Mar 2014 12:17:34 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: news.eternal-september.org comp.lang.ada:18827
Date: 2014-03-17T05:17:33-07:00
List-Id: <comp.lang.ada>

On Sunday, March 16, 2014 9:37:45 PM UTC+1, Rego, P. wrote:
> I am trying to use interrupt-driven Usart on an Atmel AVR ATmega2560 chip. 

AVR-Ada has both polled and interrupt driven UART packages. Both work at least on atmega328. I never tried ATmega2560.

As far as I remember one of the two versions exhibited a bug in the FSF-gnat of the time (gcc-4.5 or gcc-4.6). It was fixed in a later gcc release (4.7.1?).  You also might try a more recent gcc version.

Rolf