esp-idf/components/xtensa/component.mk

COMPONENT_ADD_INCLUDEDIRS := include esp32/include

COMPONENT_ADD_LDFLAGS += $(COMPONENT_PATH)/esp32/libxt_hal.a

COMPONENT_ADD_LDFRAGMENTS += linker.lf

COMPONENT_SRCDIRS := . esp32

ifdef IS_BOOTLOADER_BUILD
	COMPONENT_OBJEXCLUDE := xtensa_intr.o xtensa_intr_asm.o
endif
create xtensa component 1. move xtensa specific files out of esp32 component 2. merge xtensa-debug-module component into xtensa 2019-03-25 09:11:53 -04:00			`COMPONENT_ADD_INCLUDEDIRS := include esp32/include`

hal: extract hal component from soc component 2020-08-08 08:15:27 -04:00			`COMPONENT_ADD_LDFLAGS += $(COMPONENT_PATH)/esp32/libxt_hal.a`
misc adjustment of esp32 component 2019-03-26 04:30:43 -04:00
create xtensa component 1. move xtensa specific files out of esp32 component 2. merge xtensa-debug-module component into xtensa 2019-03-25 09:11:53 -04:00			`COMPONENT_ADD_LDFRAGMENTS += linker.lf`

xtensa: add TRAX support for esp32s2 2020-02-19 06:31:54 -05:00			`COMPONENT_SRCDIRS := . esp32`
[system]: Made longjmp save for context switch * Patched longjmp to be context-switch safe longjmp modifies the windowbase and windowstart registers, which isn't safe if a context switch occurs during the modification. After a context switch, windowstart and windowbase will be different, leading to a wrongly set windowstart bit due to longjmp writing it based on the windowbase before the context switch. This corrupts the registers at the next window overflow reaching that wrongly set bit. The solution is to disable interrupts during this code. It is only 6 instructions long, the impact shouldn't be significant. The fix is implemented as a wrapper which replaces the original first instructions of longjmp which are buggy. Then, it jumps back to execute the rest of the original longjmp function. Added a comparably reliable test to the test apps. 2021-04-08 00:16:17 -04:00
			`ifdef IS_BOOTLOADER_BUILD`
			`COMPONENT_OBJEXCLUDE := xtensa_intr.o xtensa_intr_asm.o`
			`endif`