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
630b14b322
RIOT/makefiles/tools/avrdude.inc.mk

51 lines
2.0 KiB
Makefile
Raw Normal View History

makefiles/tools: ensure all FLASHER/DEBUGGER* vars are overridable
2020-11-21 22:31:03 +01: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
makefiles/tools: ensure all FLASHER/DEBUGGER* vars are overridable
2020-11-21 22:31:03 +01:00
DEBUGSERVER ?= $(AVARICE_PATH)/debug_srv.sh
tools/avarice: deduce debugger from AVRDUDE_PROGRAMMER If `AVRDUDE_PROGRAMMER` is already set to a programmer that is also capable of debugging, we can assume that typically the user will want to use the same hardware for debugging. Thus, let `AVR_DEBUGDEVICE` default to the matching hardware.
2022-09-23 13:41:27 +02:00
# Allow choosing debugger hardware via AVR_DEBUGDEVICE. If the
# AVRDUDE_PROGRAMMER however is also capable of debugging, use that by default
ifneq (,$(filter $(AVRDUDE_PROGRAMMER),atmelice xplainedpro xplainedpro_pdi))
AVR_DEBUGDEVICE ?= --edbg
endif
ifneq (,$(filter dragon%,$(AVRDUDE_PROGRAMMER)))
AVR_DEBUGDEVICE ?= --dragon
endif
# Atmel ICE / EDBG is the most sensible fallback
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
AVR_DEBUGDEVICE ?= --edbg
AVR_DEBUGINTERFACE ?= usb
ifneq (,$(filter $(CPU),atmega328p))
# Use debugWIRE as protocol for debugging (ATmega328P does not support JTAG)
DEBUGPROTO := -w
else
makefiles/tools/avrdude: Add xmega cpu conditions The current script don't allow change debug protocol and not allows set proper part name for xmega. This make DEBUGPROTO optional with JTAG as default protocol. It add a filter for atxmega to add proper AVRDUDE_PROGRAMMER_FLAGS. Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
2021-01-02 19:32:51 +01:00
# Use JTAG as protocol for debugging as default
DEBUGPROTO ?= -j $(AVR_DEBUGINTERFACE)
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
endif
makefiles/tools: ensure all FLASHER/DEBUGGER* vars are overridable
2020-11-21 22:31:03 +01:00
DEBUGSERVER_FLAGS ?= "$(AVR_DEBUGDEVICE) $(DEBUGPROTO) :$(DEBUGSERVER_PORT)"
makefiles/tools: define DEBUG_ELFFILE and use it for debugging
2022-05-31 12:39:16 +02:00
DEBUGGER_FLAGS ?= "-x $(AVARICE_PATH)/gdb.conf $(DEBUG_ELFFILE)"
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 = "$(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/avrdude: Add xmega cpu conditions The current script don't allow change debug protocol and not allows set proper part name for xmega. This make DEBUGPROTO optional with JTAG as default protocol. It add a filter for atxmega to add proper AVRDUDE_PROGRAMMER_FLAGS. Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
2021-01-02 19:32:51 +01:00
ifeq (atxmega,$(CPU))
AVRDUDE_PROGRAMMER_FLAGS ?= -p $(subst atxmega,x,$(CPU_MODEL))
else
AVRDUDE_PROGRAMMER_FLAGS = -p $(subst atmega,m,$(CPU))
endif
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
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
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
ifneq (,$(filter $(AVRDUDE_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
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
AVRDUDE_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
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
AVRDUDE_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)
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
FFLAGS += -c $(AVRDUDE_PROGRAMMER) $(AVRDUDE_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
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
ifeq (,$(filter $(AVRDUDE_PROGRAMMER),arduino avr109 stk500v1 stk500v2 wiring))
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
# Use avrdude to trigger a reset, if programming is not done via UART and a
# bootloader.
boards: don't include programmer logic at board level
2020-11-19 18:38:41 +01:00
RESET ?= $(FLASHER) -c $(AVRDUDE_PROGRAMMER) $(AVRDUDE_PROGRAMMER_FLAGS)
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
endif
Copy Permalink