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 add
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 <
david.schu...@earthlink.net> wrote:
> On 03/30/2017 06:38 PM,
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/../../../../m
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'
I put the followi
On 03/30/2017 04:43 PM, Norrathep Rattanavipanon wrote:
> Hello,
>
> I have an old code that compiles with " msp430-gcc -mmcu=msp430x1612 ...".
> However, I'm very new and dont have any prior experience in msp430 so I
> tried to compile it but it said "warning unable to identify and include MCU
>
