JMGross,thank you for the atention that you gave for my problem with interrupt, I don't finish my work yet, but I really had problems with the configuration of my IDE, I'm using eclipse and solve some problems and now I think it is working properly. I have others questions but first, I will to formulate better and I will send after to mspgcclist.
2009/5/27 <[email protected]> > Send Mspgcc-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mspgcc-users digest..." > > > Today's Topics: > > 1. Re: Memory Address Allowcation (Sergey A. Borshch) > 2. Re: TI executable .txt file format. (Chris Liechti) > 3. Re: Memory Address Allowcation (Anthony L) > 4. msp430-gdbproxy and 54XX (Dmitry Zuikov) > 5. Re: Struct size (JMGross) > 6. Re: TI executable .txt file format. (Andy Warner) > 7. Problem with interrupt (Daniel Flor) > 8. Re: Problem with interrupt (JMGross) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 21 May 2009 11:38:40 +0300 > From: "Sergey A. Borshch" <[email protected]> > Subject: Re: [Mspgcc-users] Memory Address Allowcation > To: "GCC for MSP430 - http://mspgcc.sf.net"; > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1251; format=flowed > > Anthony L wrote: > > I want to set the storage location for this struct at memory address > 0x0021. > > Ive been told that in IAR this is done with the @ symbol. Is there a > simmilar way of doing this in mspgcc? > Take a look at header files in msp430/include/msp430: > > struct adc10_t adc10 asm("0x01B0"); > > > -- > Regards, > Sergey A. Borshch mailto: [email protected] > SB ELDI ltd. Riga, Latvia > > > > ------------------------------ > > Message: 2 > Date: Thu, 21 May 2009 14:06:44 +0200 > From: Chris Liechti <[email protected]> > Subject: Re: [Mspgcc-users] TI executable .txt file format. > To: "GCC for MSP430 - http://mspgcc.sf.net"; > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Andy Warner schrieb: > > I am planning to write some python scripts to process > > pre-built msp430 firmware images, to manipulate > > default values in fixed locations in flash and write > > new .txt files out. > [...] > > Alternatively, does anyone know of python code that > > can read/write the TI .txt format ? > > msp430-jtag and -bsl and the ihex2titext tools all use this code to read > and write: > > > http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/python/mspgcc/memory.py?revision=1.4&view=markup > > it supports reading ELF, ihex and TI-text and can write ihex and TI-text > > the setup.py here http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/python/ > allows to install that python module, so that you can simply import > "mspgcc" in your tools :-) > > chris > > > > ------------------------------ > > Message: 3 > Date: Fri, 22 May 2009 02:02:38 +0000 > From: Anthony L <[email protected]> > Subject: Re: [Mspgcc-users] Memory Address Allowcation > To: <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="Windows-1252" > > > Thank you, > > I will take a look at the header files. Your example did the trick. > > Anthony > > > > Date: Thu, 21 May 2009 11:38:40 +0300 > > From: [email protected] > > To: [email protected] > > Subject: Re: [Mspgcc-users] Memory Address Allowcation > > > > Anthony L wrote: > > > I want to set the storage location for this struct at memory address > 0x0021. > > > Ive been told that in IAR this is done with the @ symbol. Is there a > simmilar way of doing this in mspgcc? > > Take a look at header files in msp430/include/msp430: > > > > struct adc10_t adc10 asm("0x01B0"); > > > > > > -- > > Regards, > > Sergey A. Borshch mailto: [email protected] > > SB ELDI ltd. Riga, Latvia > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. > Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp asthey present alongside digital heavyweights like > Barbarian > > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > > _______________________________________________ > > Mspgcc-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > _________________________________________________________________ > Drag n? drop?Get easy photo sharing with Windows Live? Photos. > > http://www.microsoft.com/windows/windowslive/products/photos.aspx > > ------------------------------ > > Message: 4 > Date: Mon, 25 May 2009 12:25:12 +0400 > From: Dmitry Zuikov <[email protected]> > Subject: [Mspgcc-users] msp430-gdbproxy and 54XX > To: "GCC for MSP430 - http://mspgcc.sf.net"; > <[email protected]> > Message-ID: <1243239912.6601.21.ca...@x200> > Content-Type: text/plain > > Hi, > > Does anybody tried to use MSP-FET430UIF, msp430-gdbproxy and 54XX (we > use 5418 MCU). > > I tried to use gdbproxy with 2418 before, the windows version works well > with it under wine. However, it does not work with 5418 even with > msp430.dll and hil.dll from the latets IAR (I checked it out, IAR works > ok with the MCU). > > Is there any way to use the 54XX MCUs with msp430-gcc ? > > There are some companies around, that make the patched msp430-gdbproxy > avalaible for downloading, how do they make it work? Do they have some > support from TI or what? > > > > --- > Regards, > Dmitry > > > > > ------------------------------ > > Message: 5 > Date: Mon, 25 May 2009 17:09:45 +0200 > From: "JMGross" <[email protected]> > Subject: Re: [Mspgcc-users] Struct size > To: "MSPGCC mailing list," <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="ISO-8859-1" > > > It not only makes access inefficient, it can also cause more trouble, > especially if you use arrays of structs. > The compiler might then generate word-access to aligned fields (if aligned > inside the original struct) which point to an odd address (since the struct > now might have an odd length). > This results in every second struct in the array being accessed wrong > without notice (the processor just ignores the LSB in word operations, while > the compiler 'thinks' everything is well when doing word access to odd > adresses) > > I had a lot of trouble with this when working with stacked data packages > which are transmitted from MSP to ATmega and X86 systems. I ended up storing > everything in byte elements (INT and LONG stored in char[x] > fields and read/set with macros). > > JMGross > > ----- Urspr?ngliche Nachricht ----- > Von: Sergey A. Borshch > An: GCC for MSP430 - http://mspgcc.sf.net > Gesendet am: 19.Mai.2009 00:42:11 > Betreff: Re: [Mspgcc-users] Struct size > > [email protected] wrote: > > Thank you for the tip. > > I found the (quite easy) solution: > > > > -fpack-struct solves the problem. > But it makes access to multi-byte fields inefficient (byte-by-byte). > > > > > ------------------------------ > > Message: 6 > Date: Tue, 26 May 2009 15:26:43 -0500 > From: Andy Warner <[email protected]> > Subject: Re: [Mspgcc-users] TI executable .txt file format. > To: "GCC for MSP430 - http://mspgcc.sf.net"; > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On Thu, May 21, 2009 at 7:06 AM, Chris Liechti <[email protected]> wrote: > > Andy Warner schrieb: > >> I am planning to write some python scripts to process > >> pre-built msp430 firmware images, to manipulate > >> default values in fixed locations in flash and write > >> new .txt files out. > > [...] > >> Alternatively, does anyone know of python code that > >> can read/write the TI .txt format ? > > > > msp430-jtag and -bsl and the ihex2titext tools all use this code to read > > and write: > > > > > http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/python/mspgcc/memory.py?revision=1.4&view=markup > > > > it supports reading ELF, ihex and TI-text and can write ihex and TI-text > > > > the setup.py here > http://mspgcc.cvs.sourceforge.net/viewvc/mspgcc/python/ > > allows to install that python module, so that you can simply import > > "mspgcc" in your tools :-) > > Thanks for the pointer, I got my first batch of scripts working over the > weekend, and it's working just like downtown. > > Next step, integration with the Elprotronic DLL interface to their > programmers. > -- > Andy > > > > ------------------------------ > > Message: 7 > Date: Tue, 26 May 2009 20:22:41 -0300 > From: Daniel Flor <[email protected]> > Subject: [Mspgcc-users] Problem with interrupt > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > Hello, > I don't undertanding the problem, I put the follow routines of interrupt: > > / / Stopping by the burst of counting timerA > *interrupt (TA0IV_) trata_timer( void )* > {...} > > / / Function that handles ineterrup??o by USART1 > *interrupt ( U1IE ) trataIntUSART1( void )* > {...} > > And appears the following warning for both: > Description Resource Path Location Type > *?interrupt? attribute directive ignored* Estufa_20-05-09.c > Diamantina_20-05-2009 391 C/C++ Problem > > I typed the following includes:* > **#define __MSP430__ > #include <msp430x16x.h> > #include <signal.h> > #include <io.h> > #include <math.h> > #include <sys/ieeefp.h>** > *I typed the first and last lines because I had a problem with Endianness. > > There was 3 other warnings that happened: > > escription Resource Path Location Type > *Error launching external scanner info generator > (/opt/msp430/bin/msp430-gcc > -mmcu=msp430x169 -E -P -v -dD > > /home/daniel/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) > * Diamantina_20-05-2009 -1 C/C++ Problem > > Description Resource Path Location Type > /*opt/msp430/msp430/include/math.h conflicting types for built-in function > ?cabs?* Diamantina_20-05-2009 112 C/C++ Problem > > Description Resource Path Location Type > /*opt/msp430/msp430/include/math.h conflicting types for built-in function > ?cabsf?* Diamantina_20-05-2009 190 C/C++ Problem > > > *I don't understanding these warnings. There is something about the > includes > that I typed? > Could someone helpe me?* > > Thank you > Daniel. > > > ------------------------------ > > Message: 8 > Date: Wed, 27 May 2009 17:45:24 +0200 > From: "JMGross" <[email protected]> > Subject: Re: [Mspgcc-users] Problem with interrupt > To: "MSPGCC mailing list," <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="ISO-8859-1" > > Hi! > > I've never seen this style (!) of warnings/errors while working with > MSPGCC. > So there are several possible reasons: > > 1) you are not using MSPGCC as the actual compiler in your IDE. The msp430 > header files are for use with mspgcc only. (unlikely, as there should be > more errors then) > 2) your IDE is postprocessing the compiler messages, transforming them into > something that seems to lose some meaning (likely) > 3) you're using a bad makefile (likely) > 4) your path settings are wrong (likely) > (3+4 are exchangeable if it comes to header include paths) > > The message "Error launching external scanner info generator > (/opt/msp430/bin/msp430-gcc -mmcu=msp430x169 -E -P -v -dD > /home/daniel/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c)" > seems to indicate that msp430-gcc cannot be executed > Or (if it is only the result of a compiler run failing with the other two > messages) indicates that you're including the wrong include files. > > The compiler/environment should be set up to use NONE of the normal include > files used for normal C++ compilations. Set your IDE/makefile up to use ONLY > the msp430 include files and any files you manually > created local to your project. > > in 'signal.h' the interrupt keyword is defined as a macro. > #define interrupt(x) void __attribute__((interrupt (x))) > Note the missing space between the keyword and the brackets. It makes a > difference. You MUST remove the space in your code so the macro is detected > and expanded. Else it is treated as an attribute keyword > which has no meaning outside an attribute definition, making your function > a plain vanilla function with an ignore warning. > > In any case, using U1IE as interrupt vector is nonsense. U1IE refers to the > interrupt enable register in which the interrupt enable flags for TX and RX > need to be set if an interrupt is wanted. U1IE resolves to IE2 (on > other devices it might be on IE1) which is defined as "volatile unsigned > char IE2 asm(#0x0001)". Same for TA0IV_. You're surely never get the desired > result if your functions address is stored into the interrupt enable > register (enablign random interrupts) - if the flash tool can place it > there at all, as it is outside flash area. > > The proper interrupt vector definition would be > > interrupt(UART1RX_VECTOR) uart1rx_handler(void){ > > and don't forget to add > > U1IE |= URXIE1; > > to enable the Uart1 Rx interrupt (and then enable global interrupts in > general) > > Usage of TA0IV is a bit more complex. The interrupt vector for timera0 is > TIMERA0_VECTOR and for timera1 is TIMERA1_VECTOR. TA0IV_ makes only sense in > TIMERA1_VECTOR, as it indicates the number of the > highest-priority interrupt that happened, except(!) for the timera0 > interrupt which has its own independent vector and is not covered by TA0IV_ > > Most of this is covered in the proper MSP 1x device family document from > TI. > > JMGross > > > ----- Urspr?ngliche Nachricht ----- > Von: Daniel Flor > An: [email protected] > Gesendet am: 27 Mai 2009 01:22:41 > Betreff: [Mspgcc-users] Problem with interrupt > > Hello, > I don't undertanding the problem, I put the follow routines of interrupt: > > / / Stopping by the burst of counting timerA > *interrupt (TA0IV_) trata_timer( void )* > {...} > > / / Function that handles ineterrup??o by USART1 > *interrupt ( U1IE ) trataIntUSART1( void )* > {...} > > And appears the following warning for both: > Description Resource Path Location Type > *?interrupt? attribute directive ignored* Estufa_20-05-09.c > Diamantina_20-05-2009 391 C/C++ Problem > > I typed the following includes:* > **#define __MSP430__ > #include <msp430x16x.h> > #include <signal.h> > #include <io.h> > #include <math.h> > #include <sys/ieeefp.h>** > *I typed the first and last lines because I had a problem with Endianness. > > There was 3 other warnings that happened: > > escription Resource Path Location Type > *Error launching external scanner info generator > (/opt/msp430/bin/msp430-gcc > -mmcu=msp430x169 -E -P -v -dD > > /home/daniel/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) > * Diamantina_20-05-2009 -1 C/C++ Problem > > Description Resource Path Location Type > /*opt/msp430/msp430/include/math.h conflicting types for built-in function > ?cabs?* Diamantina_20-05-2009 112 C/C++ Problem > > Description Resource Path Location Type > /*opt/msp430/msp430/include/math.h conflicting types for built-in function > ?cabsf?* Diamantina_20-05-2009 190 C/C++ Problem > > > > > > ------------------------------ > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > > ------------------------------ > > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > End of Mspgcc-users Digest, Vol 36, Issue 8 > ******************************************* >
