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
5a705762ee
RIOT/cpu/esp32/Makefile.include

206 lines
6.7 KiB
Makefile
Raw Normal View History

cpu: add esp32
2018-10-08 12:20:49 +02:00
# check some environment variables first
ifndef ESP32_SDK_DIR
$(info ESP32_SDK_DIR should be defined as /path/to/esp-idf directory)
$(info ESP32_SDK_DIR is set by default to /opt/esp/esp-idf)
export ESP32_SDK_DIR=/opt/esp/esp-idf
endif
# DEFAULT compile configuration
# FLASH_MODE=[ dout | dio | qout | qio ]
# use flash mode dout by default to keep GPIO9 and GPIO10 free for use
export FLASH_MODE ?= dout
# enable GDBSTUP for debugging on exceptions
ifeq ($(ENABLE_GDBSTUB), 1)
USEMODULE += esp_gdbstub
endif
# enable GDB for compilation with debug info
ifeq ($(ENABLE_GDB), 1)
USEMODULE += esp_gdb
endif
# enable modules at command line for testing
ifneq ($(USE_MODULES), )
USEMODULE += $(USE_MODULES)
endif
# SPECIAL module dependencies
# cannot be done in Makefile.dep since Makefile.dep is included too late
cpu/esp32: fixes dependency problem for timer Xtensa newlib version requires pthread_setcancelstate as symbol. Therefore, the module pthread was always used, which in turn requires the module xtimer. The xtimer module, however, uses TIMER_DEV(0). Therefore, tests/timers failed for TIMER_DEV(0).
2018-10-14 13:50:38 +02:00
ifneq (,$(findstring core_thread_flags,$(USEMODULE)))
USEMODULE += pthread
endif
cpu/esp32: workaround for static object init
2019-08-21 22:55:08 +02:00
ifneq (,$(filter cpp,$(FEATURES_USED)))
USEMODULE += esp_cxx
endif
cpu: add esp32
2018-10-08 12:20:49 +02:00
ifneq (,$(filter esp_gdbstub,$(USEMODULE)))
USEMODULE += esp_gdb
endif
ifneq (,$(filter esp_now,$(USEMODULE)))
cpu/esp*: changes to use esp_wifi and esp_now
2019-02-02 14:37:21 +01:00
$(eval GNRC_NETIF_NUMOF=$(shell echo $$(($(GNRC_NETIF_NUMOF)+1))))
cpu: add esp32
2018-10-08 12:20:49 +02:00
USEMODULE += esp_wifi_any
endif
ifneq (,$(filter esp_wifi,$(USEMODULE)))
cpu/esp*: changes to use esp_wifi and esp_now
2019-02-02 14:37:21 +01:00
$(eval GNRC_NETIF_NUMOF=$(shell echo $$(($(GNRC_NETIF_NUMOF)+1))))
cpu: add esp32
2018-10-08 12:20:49 +02:00
USEMODULE += esp_wifi_any
endif
# ESP32 pseudomodules
PSEUDOMODULES += esp_eth_hw
PSEUDOMODULES += esp_gdb
PSEUDOMODULES += esp_gdbstub
PSEUDOMODULES += esp_hw_counter
PSEUDOMODULES += esp_i2c_sw
PSEUDOMODULES += esp_i2c_hw
PSEUDOMODULES += esp_idf_newlib
PSEUDOMODULES += esp_spi_ram
PSEUDOMODULES += esp_spiffs
PSEUDOMODULES += esp_wifi_any
export TARGET_ARCH ?= xtensa-esp32-elf
export ESPTOOL ?= $(ESP32_SDK_DIR)/components/esptool_py/esptool/esptool.py
USEMODULE += esp_idf
USEMODULE += esp_idf_driver
USEMODULE += esp_idf_esp32
USEMODULE += esp_idf_soc
USEMODULE += log
cpu/esp32: use always newlib_syscalls_default Modules newlib and newlib_syscalls_default are now used by default. Conditional compilations for MODULE_NEWLIB_SYSCALLS_DEFAULT as well as alternative code are removed completely.
2019-08-19 14:29:28 +02:00
USEMODULE += newlib
cpu: add esp32
2018-10-08 12:20:49 +02:00
USEMODULE += periph
cpu/esp32: periph submodules enabled by default
2019-04-04 00:22:16 +02:00
USEMODULE += periph_adc_ctrl
USEMODULE += periph_hwrng
USEMODULE += periph_flash
USEMODULE += periph_rtc
USEMODULE += periph_uart
cpu/esp32: module riot_freertos is always required
2019-08-05 14:55:00 +02:00
USEMODULE += riot_freertos
cpu: add esp32
2018-10-08 12:20:49 +02:00
USEMODULE += random
cpu/esp32: use newlib_syscalls_default by default Fix of #11354: Function '_write_r' of ESP32's newlibc does not write the output of function 'write(STDIO_FILENO, ...)' to the UART interface. To fix this problem, module 'newlib_syscalls_default' is now used by default. Function '_write_r' of module 'newlib_syscalls_default' uses 'stdio_write' which in turn uses 'uart_write' if module 'stdio_uart' is used which is now the default case for ESP32.
2019-04-11 16:22:47 +02:00
USEMODULE += stdio_uart
cpu: add esp32
2018-10-08 12:20:49 +02:00
USEMODULE += xtensa
cpu/esp32: move xtensa lib to esp_common
2019-01-27 14:38:27 +01:00
INCLUDES += -I$(RIOTCPU)/esp_common/vendor/
cpu: add esp32
2018-10-08 12:20:49 +02:00
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/esp-idf/include
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/esp-idf/include/esp32
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/esp-idf/include/heap
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/esp-idf/include/spi_flash
INCLUDES += -I$(RIOTCPU)/$(CPU)/vendor/esp-idf/include/tcpip_adapter
INCLUDES += -I$(ESP32_SDK_DIR)/components/
INCLUDES += -I$(ESP32_SDK_DIR)/components/driver/include
INCLUDES += -I$(ESP32_SDK_DIR)/components/esp32/include
INCLUDES += -I$(ESP32_SDK_DIR)/components/heap/include
INCLUDES += -I$(ESP32_SDK_DIR)/components/soc/esp32/include
INCLUDES += -I$(ESP32_SDK_DIR)/components/soc/include
INCLUDES += -I$(RIOTBOARD)/common/$(CPU)/include
INCLUDES += -I$(RIOTCPU)/$(CPU)
CFLAGS += -DSCHED_PRIO_LEVELS=32
CFLAGS += -DSDK_NOT_USED -DCONFIG_FREERTOS_UNICORE=1 -DESP_PLATFORM
CFLAGS += -DLOG_TAG_IN_BRACKETS
CFLAGS += -Wno-unused-parameter -Wformat=0
CFLAGS += -mlongcalls -mtext-section-literals -fstrict-volatile-bitfields
cpu/esp32: fix unknown symbols for unused functions Fixes the problem that the compilation of an applications can throw unknown symbol errors for functions that aren't use at all. Thus, it is possible to remove the warning for unknown symbols and the compilation can abort if there are real unknown symbols.
2019-08-06 07:39:33 +02:00
CFLAGS += -fdata-sections -ffunction-sections -fzero-initialized-in-bss
cpu/arch: blacklist incompatible CFLAGS Blacklist incompatible CFLAGS that are currently "optionally" included in 'cflags.inc.mk'. This prepares for the migration to 'OPTIONAL_CFLAGS'.
2019-08-28 19:43:17 +02:00
OPTIONAL_CFLAGS_BLACKLIST += -Wformat-overflow
OPTIONAL_CFLAGS_BLACKLIST += -Wformat-truncation
toolchain/cflags: enable dwarf compression. Use the -gz option to compress ELF sections containing DWARF information. This saves around 50% of disk space, without any side effects. See https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/Debugging-Options.html#Debugging-Options for more infomation on this option. Some platforms have an outdated toolchain that does not support -gz so the flag is blacklisted there. Even then, the results are quite impressive. I used @cladmi's `buildtest` branch (https://github.com/cladmi/RIOT/tree/wip/du/buildtest) with this change and compiled the `examples/default` application: ``` $ BUILD_IN_DOCKER=1 DOCKER="sudo docker" make -C examples/default buildtest-indocker ``` The size was obtained with: ``` $ find output -name "*.bin.bindirsize" -type f -exec tail -n1 '{}' \; | cut -f 1 | awk '{s+=$1} END {printf "%.0f", s}' ``` Results: - Vanilla: 10328112 KB (~10GB). - with -gz: 4982788 KB (~5GB). This was inspired by #8496.
2019-08-28 18:40:38 +02:00
OPTIONAL_CFLAGS_BLACKLIST += -gz
cpu/arch: blacklist incompatible CFLAGS Blacklist incompatible CFLAGS that are currently "optionally" included in 'cflags.inc.mk'. This prepares for the migration to 'OPTIONAL_CFLAGS'.
2019-08-28 19:43:17 +02:00
cpu: add esp32
2018-10-08 12:20:49 +02:00
ASFLAGS += --longcalls --text-section-literals
cpu/esp32: unconditionally disable thin archives Thin archives also cause a boot loop when using the flash module. To prevent further surprises, disable thin archives unconditionally until the cause for this behaviour is known.
2019-10-01 09:00:56 +02:00
# thin archives trigger a reboot loop - see #12258, #12035, #12346
ARFLAGS = rcs
cpu: add esp32
2018-10-08 12:20:49 +02:00
ifneq ($(CONFIGS),)
CFLAGS += $(CONFIGS)
endif
# if any WiFi interface is used, the number of priority levels has to be 32
ifneq (,$(filter esp_wifi_any,$(USEMODULE)))
CFLAGS += -DSCHED_PRIO_LEVELS=32
endif
ifneq (,$(filter esp_gdb,$(USEMODULE)))
CFLAGS += -Og -ggdb -g3
else
CFLAGS += -Os
endif
ifeq ($(QEMU), 1)
CFLAGS += -DQEMU
endif
# LINKFLAGS += -Wl,--verbose
LINKFLAGS += -L$(ESP32_SDK_DIR)/components/esp32
LINKFLAGS += -L$(ESP32_SDK_DIR)/components/esp32/lib
ifneq (,$(filter esp_wifi_any,$(USEMODULE)))
cpu/esp32: fixes LINKFLAGS in Makfile.include This commit adds the ESP32 vendor libraries for WLAN to the BASELIBS variable. This avoids having to define an additional archive group in the LINKGFLAGS variable which contains these vendor libraries and again RIOT module archive files with the symbols that are refered by these vendor libraries.
2018-11-23 18:04:19 +01:00
BASELIBS += -lcore -lrtc -lnet80211 -lpp -lsmartconfig -lcoexist
BASELIBS += -lwps -lwpa -lwpa2 -lespnow -lmesh -lphy -lstdc++
cpu: add esp32
2018-10-08 12:20:49 +02:00
endif
cpu/esp32: fix pthread_setcancelstate symbol problem When linking an application, symbol pthread_setcancelstate is not known in standard C libraries, even if the pthread module is linked. This is because the pthread module is grouped with all other modules, but not with the default C libraries when they are added to LINK_FLAGS. Therefore, standard C libraries have to be added also to BASELIBS to group them with all other modules.
2019-08-06 07:51:39 +02:00
BASELIBS += -lhal -lg -lc
cpu: add esp32
2018-10-08 12:20:49 +02:00
LINKFLAGS += -L$(RIOTCPU)/$(CPU)/ld/
LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ld/esp32.ld
LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ld/esp32.common.ld
LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ld/esp32.peripherals.ld
LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ld/esp32.rom.ld
LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ld/esp32.rom.nanofmt.ld
cpu/esp32: fix multiple definition of putchar When standard C libraries are added to BASELIBS to group them together with all other modules, there are multiple definitions for the putchar function. The one that is defined writing to the UART as standard output and the one that is provided by the standard C libraries. To solve this symbol conflict, putchar and getchar functions that use the UART as standard output/input are renamed to __wrap_putchar and __wrap_getchar and the linker options are extended by -Wl,-wrap option.
2019-08-06 07:58:10 +02:00
LINKFLAGS += -nostdlib -lgcc -Wl,-gc-sections
cpu/esp32: fix unknown symbols for unused functions Fixes the problem that the compilation of an applications can throw unknown symbol errors for functions that aren't use at all. Thus, it is possible to remove the warning for unknown symbols and the compilation can abort if there are real unknown symbols.
2019-08-06 07:39:33 +02:00
cpu/esp32: workaround for static object init
2019-08-21 22:55:08 +02:00
ifneq (,$(filter esp_cxx,$(USEMODULE)))
UNDEF += $(BINDIR)/esp_cxx/cxa_guard.o
endif
cpu/esp32: use FLASHFILE variable Use ELFFILE as FLASHFILE as all files are created from this one using esptool.
2018-12-19 17:44:09 +01:00
# The ELFFILE is the base one used for flashing
FLASHFILE ?= $(ELFFILE)
cpu: add esp32
2018-10-08 12:20:49 +02:00
# configure preflasher to convert .elf to .bin before flashing
FLASH_MODE ?= dout # FIX configuration, DO NOT CHANGE
FLASH_FREQ = 40m # FIX configuration, DO NOT CHANGE
cpu/esp32: resolve esptool.py warning During the flash step esptool.py gives the following warning: WARNING: Flash size arguments in megabits like '16m' are deprecated. Please use the equivalent size '2MB'. Megabit arguments may be removed in a future release. esptool.py v2.7-dev This patch replaces '16m' with '2MB' to enable future compatibility. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
2019-04-18 09:44:29 +02:00
FLASH_SIZE ?= 2MB
boards/tools: remove exporting PREFLASH/FLASHDEPS PREFLASHER/PREFFLAGS/FLASHDEPS are evaluated by the main Makefile.include. Their value does not need to be exported. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `16 insertions(+), 16 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE` plus the newline that is said to have changed.
2019-05-17 13:52:34 +02:00
PREFLASHER = $(ESPTOOL)
PREFFLAGS = --chip esp32 elf2image
PREFFLAGS += -fm $(FLASH_MODE) -fs $(FLASH_SIZE) -ff $(FLASH_FREQ)
cpu/esp32: use FLASHFILE variable Use ELFFILE as FLASHFILE as all files are created from this one using esptool.
2018-12-19 17:44:09 +01:00
PREFFLAGS += -o $(FLASHFILE).bin $(FLASHFILE);
cpu/common/esp32: use 'awk/printf' instead of 'echo' - replaces 'echo -n' and 'awk' with 'printf' and 'awk' - replaces rest of 'echo' statements with printf
2019-09-24 15:34:54 +02:00
PREFFLAGS += printf "\n" > $(BINDIR)/partitions.csv;
PREFFLAGS += printf "nvs, data, nvs, 0x9000, 0x6000\n" >> $(BINDIR)/partitions.csv;
PREFFLAGS += printf "phy_init, data, phy, 0xf000, 0x1000\n" >> $(BINDIR)/partitions.csv;
PREFFLAGS += printf "factory, app, factory, 0x10000, " >> $(BINDIR)/partitions.csv;
cpu/esp32: use FLASHFILE variable Use ELFFILE as FLASHFILE as all files are created from this one using esptool.
2018-12-19 17:44:09 +01:00
PREFFLAGS += ls -l $(FLASHFILE).bin | awk '{ print $$5 }' >> $(BINDIR)/partitions.csv;
boards/tools: remove exporting PREFLASH/FLASHDEPS PREFLASHER/PREFFLAGS/FLASHDEPS are evaluated by the main Makefile.include. Their value does not need to be exported. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `16 insertions(+), 16 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE` plus the newline that is said to have changed.
2019-05-17 13:52:34 +02:00
cpu/common/esp32: use 'awk/printf' instead of 'echo' - replaces 'echo -n' and 'awk' with 'printf' and 'awk' - replaces rest of 'echo' statements with printf
2019-09-24 15:34:54 +02:00
boards/tools: remove exporting PREFLASH/FLASHDEPS PREFLASHER/PREFFLAGS/FLASHDEPS are evaluated by the main Makefile.include. Their value does not need to be exported. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `16 insertions(+), 16 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE` plus the newline that is said to have changed.
2019-05-17 13:52:34 +02:00
PREFFLAGS += python $(RIOTCPU)/$(CPU)/gen_esp32part.py --disable-sha256sum
PREFFLAGS += --verify $(BINDIR)/partitions.csv $(BINDIR)/partitions.bin
cpu/esp*: append to FLASHDEPS Append to FLASHDEPS instead of overwriting/lazy setting it.
2019-06-05 11:53:00 +02:00
FLASHDEPS += preflash
cpu: add esp32
2018-10-08 12:20:49 +02:00
# flasher configuration
ifeq ($(QEMU), 1)
boards/tools: remove exporting FLASHER/FFLAGS FLASHER and FFLAGS are evaluated by the main Makefile.include or by file included by it. Their value does not need to be exported. This will also prevent evaluating 'PORT' for FFLAGS when not needed. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `84 insertions(+), 84 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE`.
2019-05-17 13:52:34 +02:00
FLASHER = dd
FFLAGS += if=/dev/zero bs=1M count=4 | tr "\\000" "\\377" > tmp.bin && cat tmp.bin |
FFLAGS += head -c $$((0x1000)) |
FFLAGS += cat - $(RIOTCPU)/$(CPU)/bin/bootloader.bin tmp.bin |
FFLAGS += head -c $$((0x8000)) |
FFLAGS += cat - $(BINDIR)/partitions.bin tmp.bin |
FFLAGS += head -c $$((0x10000)) |
cpu/esp32: use FLASHFILE variable Use ELFFILE as FLASHFILE as all files are created from this one using esptool.
2018-12-19 17:44:09 +01:00
FFLAGS += cat - $(FLASHFILE).bin tmp.bin |
boards/tools: remove exporting FLASHER/FFLAGS FLASHER and FFLAGS are evaluated by the main Makefile.include or by file included by it. Their value does not need to be exported. This will also prevent evaluating 'PORT' for FFLAGS when not needed. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `84 insertions(+), 84 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE`.
2019-05-17 13:52:34 +02:00
FFLAGS += head -c $$((0x400000)) > $(BINDIR)/esp32flash.bin && rm tmp.bin &&
FFLAGS += cp $(RIOTCPU)/$(CPU)/bin/rom_0x3ff90000_0x00010000.bin $(BINDIR)/rom1.bin &&
FFLAGS += cp $(RIOTCPU)/$(CPU)/bin/rom_0x40000000_0x000c2000.bin $(BINDIR)/rom.bin
cpu: add esp32
2018-10-08 12:20:49 +02:00
else
export PROGRAMMER_SPEED ?= 460800
boards/tools: remove exporting FLASHER/FFLAGS FLASHER and FFLAGS are evaluated by the main Makefile.include or by file included by it. Their value does not need to be exported. This will also prevent evaluating 'PORT' for FFLAGS when not needed. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `84 insertions(+), 84 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE`.
2019-05-17 13:52:34 +02:00
FLASHER = $(ESPTOOL)
boards: change PORT used for flash/debug/reset to PROG_DEV
2019-10-15 14:29:51 +02:00
FFLAGS += --chip esp32 -p $(PROG_DEV) -b $(PROGRAMMER_SPEED)
boards/tools: remove exporting FLASHER/FFLAGS FLASHER and FFLAGS are evaluated by the main Makefile.include or by file included by it. Their value does not need to be exported. This will also prevent evaluating 'PORT' for FFLAGS when not needed. Testing ------- `git diff --word-diff` only reports `export` being removed. `git show --stat` reports `84 insertions(+), 84 deletions(-)` Which is the same amount as lines that where matching `export[[:blank::]]\+VARIABLE`.
2019-05-17 13:52:34 +02:00
FFLAGS += --before default_reset --after hard_reset write_flash
FFLAGS += -z -fm $(FLASH_MODE) -fs detect -ff $(FLASH_FREQ)
FFLAGS += 0x1000 $(RIOTCPU)/$(CPU)/bin/bootloader.bin
FFLAGS += 0x8000 $(BINDIR)/partitions.bin
cpu/esp32: use FLASHFILE variable Use ELFFILE as FLASHFILE as all files are created from this one using esptool.
2018-12-19 17:44:09 +01:00
FFLAGS += 0x10000 $(FLASHFILE).bin
cpu: add esp32
2018-10-08 12:20:49 +02:00
endif
Copy Permalink