alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
0efdeb202e
esp-idf/components/esp32/Makefile.projbuild

18 lines
755 B
Makefile
Raw Normal View History

Add initial SPI RAM support. This adds support for an ESP-PSRAM32 chip connected to the default flash pins and GPIO 16 and 17. The RAM is mapped to address 0x3F800000, but otherwise ignored by esp-idf as of yet.
2017-07-20 04:26:35 -04:00
# Enable psram cache bug workaround in compiler if selected
ifdef CONFIG_SPIRAM_CACHE_WORKAROUND
CFLAGS+=-mfix-esp32-psram-cache-issue
CXXFLAGS+=-mfix-esp32-psram-cache-issue
esp32: also add -mfix-esp32-psram-cache-issue to LDFLAGS xtensa-esp32-elf-gcc selects among the multilib configurations based on the presence of -mfix-esp32-psram-cache-issue flag. Pass this flag in LDFLAGS so that the correct libraries are linked. Reported in https://github.com/espressif/esp-idf/issues/3624
2019-07-28 01:48:21 -04:00
LDFLAGS+=-mfix-esp32-psram-cache-issue
Add initial SPI RAM support. This adds support for an ESP-PSRAM32 chip connected to the default flash pins and GPIO 16 and 17. The RAM is mapped to address 0x3F800000, but otherwise ignored by esp-idf as of yet.
2017-07-20 04:26:35 -04:00
endif
esp_wifi: fix wrong path of phy_init_data Closes https://github.com/espressif/esp-idf/issues/3482
2019-06-11 23:52:23 -04:00
# Enable dynamic esp_timer overflow value if building unit tests
esp32, mbedtls: check component name when enabling test flags Otherwise flags get enabled even when building tests for other components.
2018-11-19 11:49:38 -05:00
ifneq ("$(filter esp32,$(TEST_COMPONENTS_LIST))","")
esp_timer: reduce overflow value in unit tests This allows testing for race conditions which occur near timer overflow point more effectively.
2018-05-23 10:39:49 -04:00
CPPFLAGS += -DESP_TIMER_DYNAMIC_OVERFLOW_VAL
endif
esp32: Rename esp32.common.ld to esp32.project.ld to avoid build errors when downgrading Linker script generator produces build/esp32/esp32.common.ld from components/esp32/ld/esp32.common.ld.in This works fine until IDF is downgraded to V3.1 which uses components/esp32/ld/esp32.common.ld and doesn't track build/esp32/esp32.common.ld at all. At this point, the linker runs in the build/esp32 directory and "-T esp32.common.ld" picks up the linker script generated .ld file, which causes mis-builds. As reported on forums: https://esp32.com/viewtopic.php?f=13&t=9684&p=40105
2019-03-13 18:59:31 -04:00
ESP32_LINKER_SCRIPT_TEMPLATE := $(COMPONENT_PATH)/ld/esp32.project.ld.in
tools: implement linker script generation
2018-04-17 22:57:45 -04:00
ESP32_LINKER_SCRIPT_OUTPUT_DIR := $(abspath $(BUILD_DIR_BASE)/esp32)
# Target to generate linker script generator from fragments presented by each of
# the components
esp32: Rename esp32.common.ld to esp32.project.ld to avoid build errors when downgrading Linker script generator produces build/esp32/esp32.common.ld from components/esp32/ld/esp32.common.ld.in This works fine until IDF is downgraded to V3.1 which uses components/esp32/ld/esp32.common.ld and doesn't track build/esp32/esp32.common.ld at all. At this point, the linker runs in the build/esp32 directory and "-T esp32.common.ld" picks up the linker script generated .ld file, which causes mis-builds. As reported on forums: https://esp32.com/viewtopic.php?f=13&t=9684&p=40105
2019-03-13 18:59:31 -04:00
$(eval $(call ldgen_process_template, $(ESP32_LINKER_SCRIPT_TEMPLATE), $(ESP32_LINKER_SCRIPT_OUTPUT_DIR)/esp32.project.ld))
Reference in New Issue Copy Permalink