Re: msp430x1612 header
Peter Bigot <[email protected]> Fri, 31 Mar 2017 06:18:19 -0500
| Newsgroups | gmane.comp.hardware.texas-instruments.msp430.gcc.user |
|---|---|
| Message-ID | <CAPOJ94OZYD=wutM7o5JisA8YyaR8PiiUNp94ekAgCsGmpqq6tg@mail.gmail.com> |
--===============5963449478836092990== Content-Type: multipart/alternative; boundary=94eb2c1bf47082d34f054c04f7d7 --94eb2c1bf47082d34f054c04f7d7 Content-Type: text/plain; charset=UTF-8 The x variants were an early attempt to simplify identifying processors where part number variation did not affect the compiler, at a time when the MSP430 product line was quite limited. Introduction of additional processor families broke those assumptions, particularly in the need to vary the addresses and presence of different peripherals. In 2013 when I last updated msp430mcu (may not have been released) there were north of 450 distinct chip IDs that affected code generation or peripheral address. The generic ID originally spelled msp430x16x covered six of them. Peter On Thu, Mar 30, 2017 at 8:11 PM, Norrathep Rattanavipanon <[email protected]> wrote: > Thanks I just found out that I need to include periph.x. Just curious is > there any difference for x1612 vs f1612 in terms of hardware configuration? > Or is x1612 just renamed to f1612? > > On Thu, Mar 30, 2017 at 4:51 PM, David W. Schultz < > [email protected]> wrote: > > > On 03/30/2017 06:38 PM, Norrathep Rattanavipanon wrote: > > > Thank you so much for your help, David. Now it compiles perfectly past > > > that point but I run into another issue (I'm not sure if this is the > > > right place to post please let me know if its not): > > > > > > /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot represent > > > machine `msp:110' > > > > > > > There should be a linker script available as well in the same location. > > If you have given the compiler the path to that directory it should find > > it. > > > > -I /usr/ti/gcc/include > > > > Is what I use. > > > > TI moved a lot of information, like device register addresses, from the > > .h files into the linker scripts some time ago. You should use the > > provided linker scripts and they will resolve symbols like WDTCTL. > > > > -- > > David W. Schultz > > http://home.earthlink.net/~david.schultz > > "Life without stock is barely worth living..." - Anthony Bourdain > > > > ------------------------------------------------------------ > > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Mspgcc-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > > > > -- > Norrathep (Oak) Rattanavipanon > M.S. in Computer Science > University of California - Irvine > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > --94eb2c1bf47082d34f054c04f7d7-- --===============5963449478836092990== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot --===============5963449478836092990== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users --===============5963449478836092990==--