From 4741682c50a2324a0e2ac9fc743aaf1382502c84 Mon Sep 17 00:00:00 2001 From: Erhan Kurubas Date: Tue, 23 Nov 2021 21:18:42 +0100 Subject: [PATCH] startup: timer_early_init before calling esp_apptrace_tmo_init --- components/esp_system/startup.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/components/esp_system/startup.c b/components/esp_system/startup.c index f159a4028c..67c5acae42 100644 --- a/components/esp_system/startup.c +++ b/components/esp_system/startup.c @@ -237,6 +237,12 @@ static void do_core_init(void) app CPU, and when that is not up yet, the memory will be inaccessible and heap_caps_init may fail initializing it properly. */ heap_caps_init(); + + // When apptrace module is enabled, there will be SEGGER_SYSVIEW calls in the newlib init. + // SEGGER_SYSVIEW relies on apptrace module + // apptrace module uses esp_timer_get_time to determine timeout conditions. + // esp_timer early initialization is required for esp_timer_get_time to work. + esp_timer_early_init(); esp_newlib_init(); if (g_spiram_ok) { @@ -263,10 +269,6 @@ static void do_core_init(void) esp_brownout_init(); #endif - // esp_timer early initialization is required for esp_timer_get_time to work. - // This needs to happen before VFS initialization, since some USB_SERIAL_JTAG VFS driver uses - // esp_timer_get_time to determine timeout conditions. - esp_timer_early_init(); esp_newlib_time_init(); #if CONFIG_VFS_SUPPORT_IO