> -----Original Message----- > From: pabi...@gmail.com [mailto:pabi...@gmail.com] On Behalf Of Peter > Bigot > Sent: Tuesday, September 20, 2011 08:12 > To: Alessandro Triglia > Cc: mspgcc-users@lists.sourceforge.net > Subject: Re: [Mspgcc-users] memory.x not found and debugger crashing > > On Mon, Sep 19, 2011 at 1:36 PM, Alessandro Triglia <san...@mclink.it> > wrote: > > > > Oh, that's interesting. You are saying that one needs to invoke the > linker > > through the compiler rather than invoking it directly? > > As Eric suggests, you don't have to do that, but if you choose not to > it's your responsibility to provide msp430-ld all the information that > msp430-gcc would. At this time, only msp430-gcc has the information > necessary to translate the MCU identifier to the three constituent > elements (CPU architecture, MPY availability, interrupt vector > length), and to use those to select the correct msp430-libc library, > libgcc, and C runtime object file (and to add the path that tells the > linker where to find the MCU-specific include files). You can see > what those are by using "-v" on an msp430-gcc link command. > > If you use -mdisable-watchdog, that also affects the libraries that > msp430-ld needs, but needs to go through msp430-gcc to do so. > > The simplest approach is to not use msp430-ld directly.
Thank you. It's very clear now. Alessandro ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
