esp-idf/components/bootloader/subproject/main/ld/esp32/bootloader.rom.ld

PROVIDE ( ets_update_cpu_frequency = 0x40008550 ); /* Updates g_ticks_per_us on the current CPU only; not on the other core */
PROVIDE ( MD5Final = 0x4005db1c );
PROVIDE ( MD5Init = 0x4005da7c );
PROVIDE ( MD5Update = 0x4005da9c );

/* bootloader will use following functions from xtensa hal library */
xthal_get_ccount = 0x4000c050;
xthal_get_ccompare = 0x4000c078;
xthal_set_ccompare = 0x4000c058;
bootloader: export ets_update_cpu_frequency 2017-01-08 14:08:24 -05:00			`PROVIDE ( ets_update_cpu_frequency = 0x40008550 ); /* Updates g_ticks_per_us on the current CPU only; not on the other core */`
esp32: remove ROM functions redefined in IDF from LD script In some cases, linker could choose to use ROM functions instead of the ones defined in IDF. For functions used in ROM stub table, this would lead to infinite recursion when the corresponding function was called from ROM. For crypto functions, some of these were modified in IDF, and incompatible with ROM counterparts. 2018-09-26 08:46:15 -04:00			`PROVIDE ( MD5Final = 0x4005db1c );`
			`PROVIDE ( MD5Init = 0x4005da7c );`
			`PROVIDE ( MD5Update = 0x4005da9c );`
misc adjustment of esp32 component 2019-03-26 04:30:43 -04:00
			`/* bootloader will use following functions from xtensa hal library */`
			`xthal_get_ccount = 0x4000c050;`
			`xthal_get_ccompare = 0x4000c078;`
			`xthal_set_ccompare = 0x4000c058;`