RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
ae4d505154
RIOT/makefiles/tools/avrdude.inc.mk

41 lines
1.6 KiB
Makefile
Raw Normal View History

makefiles: factor out avrdude configuration Allows to use avrdude as a flashing tool in any context (e.g. not dependent on arduino or atmega) though it only works (AFAIK) on atmega, but I thought it's better to have it here as we have other flashing tools.
2018-05-14 19:27:10 +02:00
FLASHER = avrdude
Makefile*: Allow multiple external board dirs - Add the new EXTERNAL_BOARD_DIRS variable that can contain a space separated list of folders containing external boards - Introduce $(BOARDDIR) as shortcut for $(BOARDSDIR)/$(BOARD) - Map the existing BOARDSDIR to the new approach - If BOARDSDIR is provided by the user, it will be added to EXTERNAL_BOARD_DIRS for backward compatibility. (And a warning is issued to encourage users migrating to EXTRA_BOARDS.) - BOARDSDIR is updated after the board is found to "$(BOARDDIR)/..". - Useful for `include $(BOARDSDIR)/common/external_common/Makefile.dep` - Provides backward compatibility
2020-04-14 15:23:23 +02:00
DIST_PATH = $(BOARDDIR)/dist
dist: De-duplicated AVR debug config & scripts Use common debug.sh, debug_srv.sh and gdb.conf for all AVR boards.
2019-03-27 13:45:25 +01:00
AVARICE_PATH = $(RIOTTOOLS)/avarice
makefiles: factor out avrdude configuration Allows to use avrdude as a flashing tool in any context (e.g. not dependent on arduino or atmega) though it only works (AFAIK) on atmega, but I thought it's better to have it here as we have other flashing tools.
2018-05-14 19:27:10 +02:00
DEBUGSERVER_PORT = 4242
dist: De-duplicated AVR debug config & scripts Use common debug.sh, debug_srv.sh and gdb.conf for all AVR boards.
2019-03-27 13:45:25 +01:00
DEBUGSERVER = $(AVARICE_PATH)/debug_srv.sh
makefiles/tools/avrdude: Improved debug handling - Choose correct debug protocol for ATmega328P (which supports debugWIRE instead of JTAG) - Allow overwriting debugger device via AVR_DEBUGDEVICE environment variable, default to the Atmel-ICE (least expensive, supports most AVR devices)
2019-03-27 15:59:29 +01:00
# Allow choosing debugger hardware via AVR_DEBUGDEVICE, default to Atmel ICE,
# which is compatible to all AVR devices and since the AVR Dragon is no longer
# produced, the least expensive option
AVR_DEBUGDEVICE ?= --edbg
AVR_DEBUGINTERFACE ?= usb
ifneq (,$(filter $(CPU),atmega328p))
# Use debugWIRE as protocol for debugging (ATmega328P does not support JTAG)
DEBUGPROTO := -w
else
# Use JTAG as protocol for debugging
DEBUGPROTO := -j $(AVR_DEBUGINTERFACE)
endif
DEBUGSERVER_FLAGS = "$(AVR_DEBUGDEVICE) $(DEBUGPROTO) :$(DEBUGSERVER_PORT)"
dist: De-duplicated AVR debug config & scripts Use common debug.sh, debug_srv.sh and gdb.conf for all AVR boards.
2019-03-27 13:45:25 +01:00
DEBUGGER_FLAGS = "-x $(AVARICE_PATH)/gdb.conf $(ELFFILE)"
DEBUGGER = "$(AVARICE_PATH)/debug.sh" $(DEBUGSERVER_FLAGS) $(AVARICE_PATH) $(DEBUGSERVER_PORT)
makefiles: factor out avrdude configuration Allows to use avrdude as a flashing tool in any context (e.g. not dependent on arduino or atmega) though it only works (AFAIK) on atmega, but I thought it's better to have it here as we have other flashing tools.
2018-05-14 19:27:10 +02:00
makefiles/tools: Automatically set avrdude target The CPU variable in the boards Makefile.include file already contains the target CPU, so there is no reason to provide it in each board again as avrdude flag. This commit automatically sets the avrdude target from the CPU variable and removes the unneeded flags.
2019-02-20 21:59:06 +01:00
PROGRAMMER_FLAGS = -p $(subst atmega,m,$(CPU))
makefiles/tools: fix avrdude with ICSP programmers Currently the flag "-P ${PORT}" is added to avrdude regardless of the programmer used. But this flag should only be set for programmers that operate over a serial port - e.g. like the various Arduino bootloaders. This commit changes the behaviour so that the "-P flag" is only set for only of the default programmers of the various AVR boards supported by RIOT. This allows to use ICSP programmers (e.g. like the usbtiny) like this: make BOARD=arduino-uno PROGRAMMER=usbtiny
2019-02-20 21:40:40 +01:00
# Set flasher port only for programmers that require it
board: add support for arduino-leonardo
2017-07-03 19:23:28 +02:00
ifneq (,$(filter $(PROGRAMMER),arduino avr109 buspirate stk500v1 stk500v2 wiring))
makefiles/tools: fix avrdude with ICSP programmers Currently the flag "-P ${PORT}" is added to avrdude regardless of the programmer used. But this flag should only be set for programmers that operate over a serial port - e.g. like the various Arduino bootloaders. This commit changes the behaviour so that the "-P flag" is only set for only of the default programmers of the various AVR boards supported by RIOT. This allows to use ICSP programmers (e.g. like the usbtiny) like this: make BOARD=arduino-uno PROGRAMMER=usbtiny
2019-02-20 21:40:40 +01:00
# make the flasher port configurable (e.g. with atmelice the port is usb)
# defaults to terminal's serial port if not configured
makefiles/tools/avrdude.inc.mk: migrate to use PROG_DEV - Move serial.inc.mk in mega-xplained/Makefile.include after PROG_DEV so PROG_DEV can still default to PORT - Add deprecation warning for arduino-leonardo and mega-xplained
2019-10-15 14:16:44 +02:00
PROGRAMMER_FLAGS += -P $(PROG_DEV)
makefiles/tools: fix avrdude with ICSP programmers Currently the flag "-P ${PORT}" is added to avrdude regardless of the programmer used. But this flag should only be set for programmers that operate over a serial port - e.g. like the various Arduino bootloaders. This commit changes the behaviour so that the "-P flag" is only set for only of the default programmers of the various AVR boards supported by RIOT. This allows to use ICSP programmers (e.g. like the usbtiny) like this: make BOARD=arduino-uno PROGRAMMER=usbtiny
2019-02-20 21:40:40 +01:00
endif
PROGRAMMER_FLAGS += $(FFLAGS_EXTRA)
makefiles: factor out avrdude configuration Allows to use avrdude as a flashing tool in any context (e.g. not dependent on arduino or atmega) though it only works (AFAIK) on atmega, but I thought it's better to have it here as we have other flashing tools.
2018-05-14 19:27:10 +02:00
# don't force to flash HEXFILE, but set it as default
FLASHFILE ?= $(HEXFILE)
tools/avrdude.inc.mk: use FLASHFILE variable Update to use FLASHFILE as file to be flashed on the board.
2018-12-19 19:12:54 +01:00
FFLAGS += -c $(PROGRAMMER) $(PROGRAMMER_FLAGS) -U flash:w:$(FLASHFILE)
tools/avrdude: Fix `make reset` with bootloader The generic approach of calling avrdude to perform a reset with `make reset` does also work on board with a bootloader, but only if no other process is also accessing the serial (e.g. via `make term`). `make test` first accesses the serial and then performs `make reset` to not miss any output on the serial. This however blocks when `make reset` also wants to access that serial. As workaround, `make reset` is no only provided if the ATmega device is not programmed via bootloader. Normally, those boards reset anyway upon `make term`, which allows `make test` to work normally again.
2019-11-25 14:39:25 +01:00
ifeq (,$(filter $(PROGRAMMER),arduino avr109 stk500v1 stk500v2 wiring))
# Use avrdude to trigger a reset, if programming is not done via UART and a
# bootloader.
RESET ?= $(FLASHER) -c $(PROGRAMMER) $(PROGRAMMER_FLAGS)
endif
Copy Permalink