> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On > Behalf Of Bradley Jarvis > Sent: Monday, May 23, 2011 10:46 PM > To: Joerg Wunsch; Bradley Jarvis; [email protected] > Subject: [avr-libc-dev] [patch #7464] Fix iom168p.h to be compatible > withiom168.h > > Follow-up Comment #3, patch #7464 (project avr-libc): > > Ok then, I did not realise that iom186p.h is auto generated. My problem is > that I have a board that started development life with an atmega168 on it, > since it is now hard to get it has been replaced with the atmega168p (and > there is also a atmega168v) I have updated to the newer chip. There are > several differences with names between the iom168.h and iom168p.h that > have > caused re-compilation problems. One was the vector names, I though that > SIG_ > were the newer ones not the ones that have been replaced, no problems I > can > update my code for this to work.
I took a look at our current documentation for interrupt names: http://www.nongnu.org/avr-libc/user-manual/group__avr__interrupts.html Section "Choosing the vector: Interrupt vector names". It describes the two different naming systems, but you're right, it doesn't seem to explicitly say that the "SIG_" names are deprecated. Joerg, we will need to change that. > There is a problem however with the port > bit > names though. iom168.h (or iomx8.h) names them PA0 PB0 etc, iom168p.h > names > them PORTA0 PORTB0 etc. and neither file have the other definition. > > Maybe a better fix then for this instance is to add the PORTA0, PORTB0 etc > #defines to the iomx8.h file. I can make this change and update the patch > files to add the PORTxx #define if you want. Take a look at <avr/portpins.h>. This header is automatically included when you include <avr/io.h> Eric _______________________________________________ AVR-libc-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
