Hi Bernie, changing addresses inside the assembler section does not change the symbol for your C-Code. This is because the assembler Section of the header is only available if you use assembler. But I think you are using C-Code therefore your changes will have no effect. By the way, the assembler section of msp430x55x9_newversion.h is generated automatically during the build of the library out of msp430x55x9_template.header (this file does only exist before you build the msp430-libc after applying our patch).
But now to your actual question: if tOutputEndPointDescriptorBlock is of type OutputEndDescriptorType then you have to define your tOutputEndPointDescriptorBlock as pointer: volatile OutputEndDescriptorType *tOutputEndDescriptorBlock = (volatile OutputEndDescriptorType *)&USBOEPCNF_1; you are now able to configure your component using this code tOutputEndDiscriptorBlock-><any field inside your struct> = <any value you need>; Best regards, Gerald -----Ursprüngliche Nachricht----- Von: Bernard Mentink [mailto:[email protected]] Gesendet: Donnerstag, 3. Dezember 2009 07:51 An: GCC for MSP430 - http://mspgcc.sf.net Betreff: Re: [Mspgcc-users] msp430x5529 support On Wed, Dec 2, 2009 at 8:16 PM, Bernard Mentink <[email protected]> wrote: > > > On Wed, Dec 2, 2009 at 8:11 AM, Gerald Lutter > <[email protected]>wrote: > >> Hi Bernie, >> >> here is an example: >> your code: tOutputEndPointDescriptorBlock = 0x2388; >> our code: USBOEPCNF_1 >> >> Best regards, >> Gerald >> >> > > Hi again Gerald, I am still having trouble with this. Rather than replacing all the instances of tOutputEndPointDescriptorBlock with USBOEPCNF_1 in the USB stack, I put tOutputEndPointDescriptorBlock = 0x2388 into msp430xx55x9_newversion.h in the __ASSEMBLER__ section ....(just as a quick hack) but I am still getting errors on any code referencing that symbol by the linker (well I think it's the linker ..) Any advise most welcome. I am not familiar with how mspgcc allows symbol address to be assigned. Cheers, Bernie
