Hi Bernie, we integrated the USB peripherals. Please try our new patch under
http://www.innoventis.de/downloads/mspgcc/ and give us feedback. By the way: What kind of driver do you use at PC side for the USB communication? Best regards -------- Original-Nachricht -------- > Datum: Fri, 20 Nov 2009 20:31:48 +1300 > Von: Bernard Mentink <[email protected]> > An: "GCC for MSP430 - http://mspgcc.sf.net"; > <[email protected]> > Betreff: Re: [Mspgcc-users] msp430x5529 support > On Thu, Nov 19, 2009 at 7:54 AM, Gerald Lutter > <[email protected]>wrote: > > > Hi Bernie, > > > > > 1. I notice some MACROS around each header file > > > entry. Are these for the linker so it knows the > > > address of each peripheral? If so, can you tell > > > me how to use them. > > > > Yes, they are used to set the addresses but not for the linker it's for > the > > compiler and the assembler. The linker itself compared to the > CC-Essentials > > Toolchain does not know anything about the SFR locations. For details > take > > a > > look at my post on the mailinglist: "Complete Support for msp430x54xx > > devices inside msp430-libc" from 2009/08/20 11:55. > > > > > 2. After adding the header file and adding the > > > details to msp430x55x9-new...., can I just > > > recompile with the script with mspgcclibc=1? > > > > No because the directory will be cleaned every time you start the > script. > > The script itself stops after adding the current patches to msp430-libc. > > You > > have to press <ENTER> to proceed. At this point you can apply your > changes > > to the library. After finishing your work just press Enter and your > changes > > will be part of your version of the library. > > > > Before continuing the build by pressing <ENTER> I recommend to create a > > patch of your version because if anything goes wrong during compile you > can > > continue your work by just adding your patch to the current version of > the > > library. > > > > Best regards > > Gerald > > > > > Hi Gerald, > > I am having trouble including the files. I put the new > MSP430x55x9_newversion.h into the directory build/msp430libc/include and > the new file USB.h into build/msp430libc/include/msp430new when the > msp430-libc compile was at the ENTER stage, and then let it complete. > > My output had the new USB.h file, but still had the > old MSP430x55x9_newversion.h, it was obviously getting overwritten. > > Can you please explain where to put the files when at the ENTER part of > the > compile. > Maybe I have to use a different name? But then how do I stop the old > ...._newversion.h being included as well. > > Also is it sufficient to in the script just enable the libc compile, with > the others set to "0". > > Thanks, > Bernie -- Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.! http://portal.gmx.net/de/go/dsl02
