I am trying to get the Msp430-gcc toolchain to work on ubuntu 12.04. i've tried installing from the repos, and from source but the same problem persists.
The problem is that the option "-mmcu" is ignored. "msp430-gcc -target-help" says :
"-mmcu= select microcontroller type (ignored)"
This of course leads to the correct header file not being included and the linker not finding the correct memory.x file. How can i fix this?
Tommi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The line you're quoting should be in a section labeled MSP430 as-specific options. What it's telling you is that -mmcu isn't meaningful to the assembler; msp430-gcc has already taken it and used material from the msp430mcu package (which you must install) to convert it to a collection of -mcpu/-mmpy/other flags that are passed to the appropriate tool for processing.
Two things you need to do: ensure msp430mcu is installed, and pass the same -mmcu flag to gcc when compiling as you pass to it when linking. (And do use msp430-gcc for linking rather than invoking msp430-ld directly.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-05-21
Thank you for your reply. As it turns out, i used wrong -mmcu parameters as my instructions were for an older version of mspgcc. Also, all manuals say that the console prints out a list of availabla MCU's if the given -mmcu is not supported. Mine does not, is there any other way to find out supported MCU's than to view the contents of the MCU header folder?
thank you for your time
tommi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the only source of mcu information is the msp430mcu package. There are nearly 400 mcus now, so keeping the list inside the individual tools is not feasible. However, all MCUs are the canonical name for the MCU as specified by TI, so if you know your chip you know the mcu flag to provide. The genericized MCUs like msp430x16x are no longer supported.
The manual is unfortunately quite out of date. Someday somebody might fund an update.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone!
I am trying to get the Msp430-gcc toolchain to work on ubuntu 12.04. i've tried installing from the repos, and from source but the same problem persists.
The problem is that the option "-mmcu" is ignored. "msp430-gcc -target-help" says :
"-mmcu= select microcontroller type (ignored)"
This of course leads to the correct header file not being included and the linker not finding the correct memory.x file. How can i fix this?
Tommi
The line you're quoting should be in a section labeled MSP430 as-specific options. What it's telling you is that -mmcu isn't meaningful to the assembler; msp430-gcc has already taken it and used material from the msp430mcu package (which you must install) to convert it to a collection of -mcpu/-mmpy/other flags that are passed to the appropriate tool for processing.
Two things you need to do: ensure msp430mcu is installed, and pass the same -mmcu flag to gcc when compiling as you pass to it when linking. (And do use msp430-gcc for linking rather than invoking msp430-ld directly.)
Thank you for your reply. As it turns out, i used wrong -mmcu parameters as my instructions were for an older version of mspgcc. Also, all manuals say that the console prints out a list of availabla MCU's if the given -mmcu is not supported. Mine does not, is there any other way to find out supported MCU's than to view the contents of the MCU header folder?
thank you for your time
tommi
No, the only source of mcu information is the msp430mcu package. There are nearly 400 mcus now, so keeping the list inside the individual tools is not feasible. However, all MCUs are the canonical name for the MCU as specified by TI, so if you know your chip you know the mcu flag to provide. The genericized MCUs like msp430x16x are no longer supported.
The manual is unfortunately quite out of date. Someday somebody might fund an update.