I've been informed via the bug list that this [mspgcc-Bugs-3484369] will be fixed in the next release of the MCU headers. Though Peter did not say, I assume that the solution will be to ensure that:
#define TIMERA0_VECTOR TIMER0_A0_VECTOR is present in all the header files. This is partially implemented already and solves both the old program and the different device flavors of the problem. Have Fun! Reg --- On Mon, 2/6/12, JMGross <msp...@grossibaer.de> wrote: > From: JMGross <msp...@grossibaer.de> > Subject: Re: [Mspgcc-users] TIMERA0_VECTOR vs TIMER0_A0_VECTOR > To: "MSPGCC mailing list," <mspgcc-users@lists.sourceforge.net> > Date: Monday, February 6, 2012, 7:57 AM > > Hi Reginald, > > the first MSPs did only have one timer of the A type. > So there were TIMERA0_VECTOR and TIMERA1_VECTOR for the two > vectors belonging to the TimerA. > Later devices were equipped with more than one TimerA module > (up to three). > The old notation then became ambiguous (one could think the > two are one vector for TimerA0 and one for TimerA1. > Personally, I had preferred a notation like TIMERAx_VECTORy, > or (less desireable, but compliant with other vector > names) TIMERAx_y_VECTOR. > But well, someone decided to name them TIMERx_Ay_VECTOR. > (x being the index of the timer, y of the vector for this > timer) > > Since there is much old demo code still around, and often > the code runs on devices with more > than one TimerA without further change, the old vector names > have been mapped to > the new notation for Timer A0. > > P.s.: the notation to describe a timer in the datasheet as > TimerAx, where x is the number of CCR units, > adds to the confusion. > > ----- Ursprüngliche Nachricht ----- > Von: Reginald Beardsley > An: mspgcc-users@lists.sourceforge.net > Gesendet am: 04 Feb 2012 03:36:08 > Betreff: [Mspgcc-users] TIMERA0_VECTOR vs TIMER0_A0_VECTOR > > I discovered today when compiling a small program for the > 2331 that comes w/ the LaunchPad on a 2553 that the > TIMERA0_VECTOR on the 2331 > needed to be changed to TIMER0_A0_VECTOR to compile for the > 2553. > > Scanning all the device headers showed that for some parts > TIMERA0_VECTOR is redefined to TIMER0_A0_VECTOR. > > Is there a valid reason for the variance? I can't see > any, but there may be something I'm not aware of. > > I'd like to be able to compile code for any part that had > the requisite facility w/o having to fiddle w/ gratuitous > changes in names. So fixing this > is worth my time if it means the problem goes away. > Who maintains the device headers? I wasn't able to > find any specifics. > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft > developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, > CSS3, MVC3, > Metro Style Apps, more. Free future releases when you > subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
