Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-23 Thread JMGross
-users] mspgcc4 usci.h error in definition of UCBxCTL0/1 Will these patches being going into GCC cvs? BTW, other than these minor header file issues I haven't had any major issues with mspgcc4 on msp430F5437. One small thing that snagged me...I had my interrupt routines in a file by themselves

Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-23 Thread Anthony Asterisk
, none of the code is linked, but if, all of the code gets linked. JMGross - Ursprüngliche Nachricht - Von: Anthony Asterisk An: mspgcc-us...@lists.sourcefor... Gesendet am: 17 Mrz 2010 21:08:26 Betreff: Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1 Will these patches

Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-17 Thread Anthony Asterisk
Will these patches being going into GCC cvs? BTW, other than these minor header file issues I haven't had any major issues with mspgcc4 on msp430F5437. One small thing that snagged me...I had my interrupt routines in a file by themselves. Since the interrupts were not called from any other

Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-17 Thread Peter Bigot
Project GNU is not involved with maintaining any of the msp430-libc variants. The changes have been integrated into the msp430-libc I maintain, and should be part of the next mspgcc4 release. I don't think what you describe is quite normal for interrupt handling. If the function declaration has

[Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-16 Thread Anthony Asterisk
I found an error in the usci.h modification for the 5xxx series. The definitions for UCBxCTL0/1 are swapped. The UCAxCTL are ok. Here are the versions of the file I'm using: * 2009-11-20 - modifications by J.M.Gross msp...@grossibaer.de * - split definitions for 8/11port and 2/4 USCI CPUs *

Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-16 Thread Peter Bigot
Thanks; I'd fixed the issue for UCA, but neglected to do the same for UCB, and wasn't using that header by the time I validated UCB functionality. I'll fix usci.h in my variant msp430-libc, but you may be better off using usci_5xx.h, which gives up on trying to support everything in one file,

Re: [Mspgcc-users] mspgcc4 usci.h error in definition of UCBxCTL0/1

2010-03-16 Thread JMGross
Hi Anthony, you're right. TI has messed-up the port register names (or the positions). The first versions of the documentation listed them all in the wrong order, later revisions corrected this for the UCAxCTLy but still had them wrong for the UCBxCTLy. This was when this header file was last