RIOT/boards/msb-430-common/Makefile.include

## the cpu to build for
export CPU = msp430fxyz
export MCU = msp430f1612

# toolchain config
export PREFIX = msp430-
export CC = $(PREFIX)gcc
export AR = $(PREFIX)ar
export CFLAGS += -Wstrict-prototypes -gdwarf-2 -Os -Wall -mmcu=$(MCU)
export ASFLAGS += -mmcu=$(MCU) --defsym $(MCU)=1 --gdwarf-2
export AS = $(PREFIX)as
export LINK = $(PREFIX)gcc
export SIZE = $(PREFIX)size
export OBJCOPY = $(PREFIX)objcopy
export LINKFLAGS += -mmcu=$(MCU) -lgcc
TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm

export FLASHER ?= mspdebug
export PORT ?= /dev/ttyUSB0
export PROGRAMMER ?= olimex
export MSPDEBUGFLAGS += -j $(PROGRAMMER)
ifeq ($(strip $(PROGRAMMER)),uif)
	export MSPDEBUGFLAGS += -d $(PORT)
endif
export DEBUGSERVER = $(FLASHER)
export DEBUGSERVER_FLAGS = $(MSPDEBUGFLAGS) gdb
export DEBUGGER = $(PREFIX)gdb
export DEBUGGER_FLAGS = --tui --ex="target remote localhost:2000" --ex "monitor reset halt" --ex load -ex "monitor reset halt"  $(ELFFILE)
export TERMFLAGS += -p "$(PORT)"

export FFLAGS = $(MSPDEBUGFLAGS) "prog $(HEXFILE)"

export USEMODULE += msp430_common
export INCLUDES += -I$(RIOTCPU)/msp430-common/include/ -I$(RIOTBOARD)/msb-430-common/include -I$(RIOTBOARD)/msb-430-common/drivers/include
export OFLAGS = -O ihex

export UNDEF += $(BINDIR)msp430_common/startup.o
* renamed makefiles to Makefile * included a more convenient approach to organize Makefiles 2013-03-10 16:50:50 +01:00			`## the cpu to build for`
cpu: msp430: renamed msp430x16x to msp430fxyz 2014-12-01 17:32:29 +01:00			`export CPU = msp430fxyz`
* changed MCU name to adapt to current msp430-gcc version 2013-04-01 00:00:42 +02:00			`export MCU = msp430f1612`
* renamed makefiles to Makefile * included a more convenient approach to organize Makefiles 2013-03-10 16:50:50 +01:00
			`# toolchain config`
muting compiler and binutils optionally Instead of muting all compiler and other binutils output by default, introduce a variable to make this behaviour configurable. 2014-01-03 19:00:41 +01:00			`export PREFIX = msp430-`
			`export CC = $(PREFIX)gcc`
			`export AR = $(PREFIX)ar`
Do not mandate input language An application might want to use C11 features. The user would assume that setting `CFLAGS=-std=gnu11` in the Makefile would work. It does not since the board's Makefile.include shadows the `-std` flag. This patch removes the `-std=gnu99` from the various Makefile.includes, and sets the flag in the common Makefile.include of RIOT instead. If an `-std` flag was provided by an earlier Makefile (the application, the board, or the CPU [whilst only the former one should]), then no additional flag is set. It is first tested if the supplied compiler understands `-std=gnu99`, then `-std=c99`. 2014-02-12 17:32:34 +01:00			`export CFLAGS += -Wstrict-prototypes -gdwarf-2 -Os -Wall -mmcu=$(MCU)`
* renamed makefiles to Makefile * included a more convenient approach to organize Makefiles 2013-03-10 16:50:50 +01:00			`export ASFLAGS += -mmcu=$(MCU) --defsym $(MCU)=1 --gdwarf-2`
			`export AS = $(PREFIX)as`
			`export LINK = $(PREFIX)gcc`
			`export SIZE = $(PREFIX)size`
			`export OBJCOPY = $(PREFIX)objcopy`
make: don't overwrite LINKFLAGS Fix the boards' Makefiles were a potentially set LINKFLAGS variable were overwritten. 2014-10-17 22:39:45 +02:00			`export LINKFLAGS += -mmcu=$(MCU) -lgcc`
pyterm: renamed pyterm.py to pyterm 2014-07-31 19:42:06 +02:00			`TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm`
improve programmer handling in msb-430-common 2013-12-19 12:02:23 +01:00
make: clean msb-430-common Makefile.include set default values with `?=` automatically add `PORT` for `PROGRAMMER == uif` 2014-03-20 21:55:13 +01:00			`export FLASHER ?= mspdebug`
			`export PORT ?= /dev/ttyUSB0`
			`export PROGRAMMER ?= olimex`
make: msb-430 boards: added debug and debugserver targets 2014-08-05 13:43:58 +02:00			`export MSPDEBUGFLAGS += -j $(PROGRAMMER)`
make: clean msb-430-common Makefile.include set default values with `?=` automatically add `PORT` for `PROGRAMMER == uif` 2014-03-20 21:55:13 +01:00			`ifeq ($(strip $(PROGRAMMER)),uif)`
make: msb-430 boards: added debug and debugserver targets 2014-08-05 13:43:58 +02:00			`export MSPDEBUGFLAGS += -d $(PORT)`
* renamed makefiles to Makefile * included a more convenient approach to organize Makefiles 2013-03-10 16:50:50 +01:00			`endif`
make: msb-430 boards: added debug and debugserver targets 2014-08-05 13:43:58 +02:00			`export DEBUGSERVER = $(FLASHER)`
			`export DEBUGSERVER_FLAGS = $(MSPDEBUGFLAGS) gdb`
			`export DEBUGGER = $(PREFIX)gdb`
			`export DEBUGGER_FLAGS = --tui --ex="target remote localhost:2000" --ex "monitor reset halt" --ex load -ex "monitor reset halt" $(ELFFILE)`
make: Fix TERMFLAGS Sometimes boards/*/Makefile.include (e. g. in case of the msba2) gets included twice somehow, leading the TERMFLAG to be set twice and faulty. This fixes that. 2014-08-10 05:20:57 +02:00			`export TERMFLAGS += -p "$(PORT)"`
improve programmer handling in msb-430-common 2013-12-19 12:02:23 +01:00
make: msb-430 boards: added debug and debugserver targets 2014-08-05 13:43:58 +02:00			`export FFLAGS = $(MSPDEBUGFLAGS) "prog $(HEXFILE)"`
* fixed flasher flags for MSB-A2 * added required include for msb-430-common 2013-04-09 11:25:04 +02:00
remove trailing whitespace and newlines 2014-02-11 18:15:43 +01:00			`export USEMODULE += msp430_common`
make: couple include path and -I This is necessary if includes have to be filtered, such as in native to throw out RIOTs posix includes which interfere with system includes. 2014-02-27 08:14:33 +01:00			`export INCLUDES += -I$(RIOTCPU)/msp430-common/include/ -I$(RIOTBOARD)/msb-430-common/include -I$(RIOTBOARD)/msb-430-common/drivers/include`
added objcopy flags to makefiles for all platforms 2013-10-11 15:07:53 +02:00			`export OFLAGS = -O ihex`
Use subfolders in bin dir Creating all object files in one directory is bound to produce name clashes. RIOT developers may take care to use unique file names, but external packages surely don't. With this change all the objects of a module (e.g. `shell`) will be created in `bin/$(BOARD)/$(MODULE)`. I compared the final linker command before and after the change. The `.o` files (e.g. `startup.o`, `syscall.o` ...) are included in the same order. Neglecting the changed path name where the `.o` files reside, the linker command stays exactly the same. A major problem could be third party boards, because the location of the `startup.o` needs to the specified now in `boards/$(BOARD)/Makefile.include`, e.g. ```Makefile export UNDEF += $(BINDIR)msp430_common/startup.o ``` 2014-02-15 12:31:43 +01:00
			`export UNDEF += $(BINDIR)msp430_common/startup.o`