Avoiding ESP_EARLY_LOG after code startup

davdav
Posts: 148
Joined: Thu Nov 17, 2016 2:33 pm

Avoiding ESP_EARLY_LOG after code startup

Postby davdav » Fri Jan 11, 2019 10:59 am

Hi,

In my sdkconfig file I have the following settings for LOG management

Code: Select all

CONFIG_LOG_BOOTLOADER_LEVEL_NONE=y
CONFIG_LOG_DEFAULT_LEVEL_DEBUG=y
Bootloader LOG is disabled and LOG level for application is set to DEBUG.

The very first operation I do on my "app_main" is

Code: Select all

esp_log_level_set("*", ESP_LOG_NONE);
in order to disable all the log (I could enable later via a command on uart if needed for debugging on field). However at start-up

Code: Select all

ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:824
load:0x40078000,len:8304
ho 0 tail 12 room 4
load:0x40080000,len:5188
entry 0x40080270
I (448) cpu_start: Pro cpu up.
I (448) cpu_start: Starting app cpu, entry point is 0x4008129c
I (433) cpu_start: App cpu up.
I (449) heap_init: Initializing. RAM available for dynamic allocation:
D (454) heap_init: New heap initialised at 0x3ffaff10
I (459) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
D (465) heap_init: New heap initialised at 0x3ffcd9c0
I (469) heap_init: At 3FFCD9C0 len 00012640 (73 KiB): DRAM
I (474) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (480) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
D (486) heap_init: New heap initialised at 0x4009802c
I (490) heap_init: At 4009802C len 00007FD4 (31 KiB): IRAM
I (495) cpu_start: Pro cpu start user code
D (506) clk: RTC_SLOW_CLK calibration value: 3372518
D (68) intr_alloc: Connected src 46 to int 2 (cpu 0)
D (69) intr_alloc: Connected src 57 to int 3 (cpu 0)
D (69) intr_alloc: Connected src 24 to int 9 (cpu 0)
I (73) esp_core_dump: Init core dump to UART
I (77) 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 (98) heap_init: New heap initialised at 0x3ffe0440
D (103) heap_init: New heap initialised at 0x3ffe4350
D (107) intr_alloc: Connected src 16 to int 12 (cpu 0)
D (207) intr_alloc: Connected src 34 to int 13 (cpu 0)
D (209) intr_alloc: Connected src 37 to int 17 (cpu 0)
The very first part is from ROM code and I know it is managed by strapping fine..The second part from "cpu_start: Pro cpu up" is generated by ESP_EARLY_LOGx instruction which seems to assume CONFIG_LOG_DEFAULT_LEVEL_DEBUG level and not CONFIG_LOG_BOOTLOADER_LEVEL_NONE configuration.

I'm using ESP-IDF v3.1.2 ed13041.

How can I avoid this initial logs (obviously mantaining CONFIG_LOG_DEFAULT_LEVEL_DEBUG =y)?


Thanks

Return to “ESP32 IDF”

Who is online

Users browsing this forum: No registered users and 22 guests