ESP32 Forum

Posted: **Wed Oct 31, 2018 10:33 am**

Hi,

I have setup on sdkconfig file a DEBUG level for logs in my application.

The first thing I do on my program is

esp_log_level_set("*", ESP_LOG_NONE);

to stop logging. However I got

Code: Select all

I (416) cpu_start: Pro cpu up.
I (416) cpu_start: Starting app cpu, entry point is 0x40081290
I (402) cpu_start: App cpu up.
I (417) heap_init: Initializing. RAM available for dynamic allocation:
D (422) heap_init: New heap initialised at 0x3ffaff10
I (427) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
D (432) heap_init: New heap initialised at 0x3ffcdc08
I (437) heap_init: At 3FFCDC08 len 000123F8 (72 KiB): DRAM
I (442) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (448) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
D (454) heap_init: New heap initialised at 0x40097a84
I (458) heap_init: At 40097A84 len 0000857C (33 KiB): IRAM
I (463) cpu_start: Pro cpu start user code
D (474) clk: RTC_SLOW_CLK calibration value: 3170752
D (36) intr_alloc: Connected src 46 to int 2 (cpu 0)
D (37) intr_alloc: Connected src 57 to int 3 (cpu 0)
D (37) intr_alloc: Connected src 24 to int 9 (cpu 0)
I (41) esp_core_dump: Init core dump to UART
I (45) cpu_start: Starting scheduler on PRO CPU.
D (0) intr_alloc: Connected src 25 to int 2 (cpu 1)
I (4) cpu_start: Starting scheduler on APP CPU.
D (66) heap_init: New heap initialised at 0x3ffe0440
D (71) heap_init: New heap initialised at 0x3ffe4350
D (75) intr_alloc: Connected src 16 to int 12 (cpu 0)
D (159) intr_alloc: Connected src 34 to int 13 (cpu 0)
D (160) intr_alloc: Connected src 35 to int 17 (cpu 0)

Those are generated by "cpu_start.c" and other code which are run by ESP32 before calling main program. How can I disable those "ESP_EARLY_LOGx" logs?

Thanks

Posted: **Wed Oct 31, 2018 12:50 pm**

Unfortunately, I think the only way to disable ESP_EARLY_LOGx calls are to lower your log level in sdkconfig. However this will mean that the rest of your application will also be restricted to the sdkconfig level or below as esp_log_level_set() can only lower the log level and not raise it.

Posted: **Wed Oct 31, 2018 2:11 pm**

Hello @ESP_Dazz,

I will change the calls "ESP_LOGD" to "ESP_LOGW" in my application and setup a WARNING level in sdkconfig even if it's a pity to lost informations for debugging.

Otherwise, I could modify cpu_start.c (and other files which call that function before main() is started) and remove the ESP_EARLY_LOGx. Is it correct?

Thanks

Posted: **Wed Oct 31, 2018 10:46 pm**

Im not sure, but did you try to change this option in menuconfig:

Code: Select all

 Bootloader log verbosity (Info)

Posted: **Thu Nov 01, 2018 12:12 am**

chegewara wrote:Im not sure, but did you try to change this option in menuconfig:
Code: Select all
 Bootloader log verbosity (Info) 

These lines are logged by the app during its early startup code, after control is handed over from the bootloader binary. So the bootloader log level won't change it, unfortunately.

ESP32 Forum

Avoid Early LOG "Pro cpu up" "App cpu up"

Avoid Early LOG "Pro cpu up" "App cpu up"

Re: Avoid Early LOG "Pro cpu up" "App cpu up"

Re: Avoid Early LOG "Pro cpu up" "App cpu up"

Re: Avoid Early LOG "Pro cpu up" "App cpu up"

Re: Avoid Early LOG "Pro cpu up" "App cpu up"