[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-libc-dev] [bug #5799] error(?) in iom162.h

From: nobody
Subject: [avr-libc-dev] [bug #5799] error(?) in iom162.h
Date: Fri, 17 Oct 2003 16:12:31 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1

=================== BUG #5799: LATEST MODIFICATIONS ==================

Changes by: Theodore A. Roth <address@hidden>
Date: Fri 10/17/03 at 13:12 (US/Pacific)

            What     | Removed                   | Added
          Resolution | None                      | Fixed
              Status | Open                      | Closed

------------------ Additional Follow-up Comments ----------------------------
I've this on HEAD and 1.0 branch.    

The PORTxn changes are really a separate issue and are being handled.

=================== BUG #5799: FULL BUG SNAPSHOT ===================

Submitted by: None                    Project: AVR C Runtime Library        
Submitted on: Tue 10/07/03 at 23:58
Category:  Header                     Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  troth                   Originator Email:  address@hidden     
Status:  Closed                       

Summary:  error(?) in iom162.h

Original Submission:  In definitions for UCSR0A: bit 2 is defined as PE0, this 
should be UPE0. In definitions for UCSR1A: bit 2 is defined as PE1, this should 
be UPE1. This according to datasheet for Atmega162(V) rev: 2513E-AVR-09/03

I guess this is the reson why PORTE bits are defined as PORTE0, PORTE1.... 
instead of PE0, PE1.. as would be normal.

I am usign WinAVR-20030913

Follow-up Comments

Date: Fri 10/17/03 at 13:12         By: troth
I've this on HEAD and 1.0 branch.    

The PORTxn changes are really a separate issue and are being handled.

Date: Fri 10/17/03 at 10:49         By: troth
The 09/02 version of the datasheet still has UPEn. I see no mention of PEn in 
the UCSRnA register summary. I'm going to simply replace PEn with UPEn instead 
of adding UPEn and making PEn an alias.

Now the PORTE part brings up another issue. The usage is not consistant in this 
header file. All other port pins are defined like PAn while PORTE is PORTEn. 
The datasheet register summary shows them all as PORTxn. I'd prefer to just 
have all the headers use Pxn regardless of what the datasheets say, but that 
doesn't seem to be the concensus of the developers.

CC list is empty

No files currently attached

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]