Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
OVMS3-idf/components/esp32/Makefile.projbuild

51 lines
1.8 KiB
Makefile
Raw Normal View History

add PHY init support
2016-11-15 10:36:18 +00:00
ifdef CONFIG_ESP32_PHY_INIT_DATA_IN_PARTITION
PHY_INIT_DATA_OBJ = $(BUILD_DIR_BASE)/phy_init_data.o
PHY_INIT_DATA_BIN = $(BUILD_DIR_BASE)/phy_init_data.bin
# Command to flash PHY init data partition
partition_table: Expanding the space under the bootloader Allows you to move the partition table, it gives more space for the bootloader. Added a new utility - parttool.py. This utility can search for the offset and/or size of the partitions by name and type/subtype. Use for getting APP_OFFSET and PHY_DATA_OFFSET. The linker(esp32.bootloader.ld) made changes that allow you to write a custom bootloader code more. TW14125
2018-04-19 04:42:26 +00:00
PHY_INIT_DATA_FLASH_CMD = $(ESPTOOLPY_SERIAL) write_flash $(PHY_DATA_OFFSET) $(PHY_INIT_DATA_BIN)
ESPTOOL_ALL_FLASH_ARGS += $(PHY_DATA_OFFSET) $(PHY_INIT_DATA_BIN)
phy init data: Read PHY init data partition offset from menuconfig
2016-11-16 01:22:32 +00:00
ESP32_COMPONENT_PATH := $(COMPONENT_PATH)
add PHY init support
2016-11-15 10:36:18 +00:00
$(PHY_INIT_DATA_OBJ): $(ESP32_COMPONENT_PATH)/phy_init_data.h $(BUILD_DIR_BASE)/include/sdkconfig.h
$(summary) CC $(notdir $@)
printf "#include \"phy_init_data.h\"\n" | $(CC) -I $(BUILD_DIR_BASE)/include -I $(ESP32_COMPONENT_PATH) -I $(ESP32_COMPONENT_PATH)/include -c -o $@ -xc -
phy init data: Read PHY init data partition offset from menuconfig
2016-11-16 01:22:32 +00:00
add PHY init support
2016-11-15 10:36:18 +00:00
$(PHY_INIT_DATA_BIN): $(PHY_INIT_DATA_OBJ)
$(summary) BIN $(notdir $@)
phy init data: Read PHY init data partition offset from menuconfig
2016-11-16 01:22:32 +00:00
$(OBJCOPY) -O binary $< $@
add PHY init support
2016-11-15 10:36:18 +00:00
phy init data: Read PHY init data partition offset from menuconfig
2016-11-16 01:22:32 +00:00
phy_init_data: $(PHY_INIT_DATA_BIN)
add PHY init support
2016-11-15 10:36:18 +00:00
phy_init_data-flash: $(BUILD_DIR_BASE)/phy_init_data.bin
@echo "Flashing PHY init data..."
$(PHY_INIT_DATA_FLASH_CMD)
phy_init_data-clean:
rm -f $(PHY_INIT_DATA_BIN) $(PHY_INIT_DATA_OBJ)
phy init data: Read PHY init data partition offset from menuconfig
2016-11-16 01:22:32 +00:00
all: phy_init_data
flash: phy_init_data
add PHY init support
2016-11-15 10:36:18 +00:00
endif # CONFIG_ESP32_PHY_INIT_DATA_IN_PARTITION
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 08:26:35 +00: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
endif
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 14:39:49 +00: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 16:49:38 +00: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 14:39:49 +00: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 22:59:31 +00:00
ESP32_LINKER_SCRIPT_TEMPLATE := $(COMPONENT_PATH)/ld/esp32.project.ld.in
ldgen: fix build issue on make when build dir is a symlink Fixes an issue where build fails if the build directory is a symlink. The issue is caused by the rule target and the final executable dependency not matching. Closes https://github.com/espressif/esp-idf/issues/3626
2019-08-27 02:26:34 +00:00
ESP32_LINKER_SCRIPT_OUTPUT_DIR := $(realpath $(BUILD_DIR_BASE)/esp32)
tools: implement linker script generation
2018-04-18 02:57:45 +00:00
# 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 22:59:31 +00:00
$(eval $(call ldgen_process_template, $(ESP32_LINKER_SCRIPT_TEMPLATE), $(ESP32_LINKER_SCRIPT_OUTPUT_DIR)/esp32.project.ld))
Reference in a new issue Copy permalink