Suppress Boot messages

Wilberforce
Posts: 8
Joined: Sun Apr 02, 2017 4:50 am

Suppress Boot messages

Postby Wilberforce » Thu Apr 13, 2017 4:59 am

Hi, how can these boot messages be suppressed?

Code: Select all

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:2488
load:0x40078000,len:7088
load:0x40080000,len:252
entry 0x40080034
E (45) boot: ota data partition invalid, falling back to factory
I (1358) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1359) heap_alloc_caps: At 3FFCC990 len 00013670 (77 KiB): DRAM
I (1368) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM
I (1390) heap_alloc_caps: At 4009CA04 len 000035FC (13 KiB): IRAM
I (1411) cpu_start: Pro cpu up.
I (1422) cpu_start: Single core mode
I (1435) cpu_start: Pro cpu start user code
I (1495) cpu_start: Starting scheduler on PRO CPU.
WARNING: Free heap size: 151328
I (1555) wifi: wifi firmware version: c604573
I (1555) wifi: config NVS flash: enabled
I (1555) wifi: config nano formating: disabled
I (1563) wifi: Init dynamic tx buffer num: 32
I (1563) wifi: wifi driver task: 3ffd56f8, prio:23, stack:3584
I (1568) wifi: Init static rx buffer num: 10
I (1572) wifi: Init dynamic rx buffer num: 0
I (1576) wifi: Init rx ampdu len mblock:7
I (1580) wifi: Init lldesc rx ampdu entry mblock:4
I (1585) wifi: wifi power manager task: 0x3ffdaab4 prio: 21 stack: 2560

There was a reference here:
viewtopic.php?t=299#p1306

but that would then turn off all printf output?

Thanks

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: Suppress Boot messages

Postby WiFive » Thu Apr 13, 2017 7:21 am

You can set the log levels to none and use efuse to turn off ROM output.

ESP_igrr
Posts: 2067
Joined: Tue Dec 01, 2015 8:37 am

Re: Suppress Boot messages

Postby ESP_igrr » Thu Apr 13, 2017 8:55 am

Bootstrapping GPIO15 to ground will also disable initial output from the ROM bootloader.

Wilberforce
Posts: 8
Joined: Sun Apr 02, 2017 4:50 am

Re: Suppress Boot messages

Postby Wilberforce » Thu Apr 13, 2017 11:41 pm

WiFive wrote:You can set the log levels to none and use efuse to turn off ROM output.
How do youdo this? It sounds like this is on a per board basis and can it be undone?

So there is no way to do this in firmware?

Ideally I want to suppress bootloader output, but allow informational debug output.

Wilberforce
Posts: 8
Joined: Sun Apr 02, 2017 4:50 am

Re: Suppress Boot messages

Postby Wilberforce » Thu Apr 13, 2017 11:50 pm

ESP_igrr wrote:Bootstrapping GPIO15 to ground will also disable initial output from the ROM bootloader.
This does not appear to work for me. I have read GP015 state and it is ready zero with my jumper, but has no affect on boot.

ESP_igrr
Posts: 2067
Joined: Tue Dec 01, 2015 8:37 am

Re: Suppress Boot messages

Postby ESP_igrr » Fri Apr 14, 2017 2:42 am

Could you please paste the output you get with GPIO15 is connected to ground? Thanks.

Wilberforce
Posts: 8
Joined: Sun Apr 02, 2017 4:50 am

Re: Suppress Boot messages

Postby Wilberforce » Sat Apr 15, 2017 10:40 pm

ESP_igrr wrote:Could you please paste the output you get with GPIO15 is connected to ground? Thanks.
Ok - there is a difference!

With GPIO15 grounded:

Code: Select all

;31mE (9) boot: ota data partition invalid, falling back to factorym
;32mI (1322) heap_alloc_caps: Initializing. RAM available for dynamic allocation:m
;32mI (1323) heap_alloc_caps: At 3FFCC990 len 00013670 (77 KiB): DRAMm
;32mI (1333) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAMm
;32mI (1354) heap_alloc_caps: At 4009CA04 len 000035FC (13 KiB): IRAMm
;32mI (1375) cpu_start: Pro cpu up.m
;32mI (1387) cpu_start: Single core modem
;32mI (1400) cpu_start: Pro cpu start user codem
;32mI (1459) cpu_start: Starting scheduler on PRO CPU.m
WARNING: Free heap size: 151328
I (1520) wifi: wifi firmware version: c604573
I (1520) wifi: config NVS flash: enabled
I (1520) wifi: config nano formating: disabled
I (1528) wifi: Init dynamic tx buffer num: 32
I (1528) wifi: wifi driver task: 3ffd56f8, prio:23, stack:3584
I (1533) wifi: Init static rx buffer num: 10
I (1537) wifi: Init dynamic rx buffer num: 0
I (1541) wifi: Init rx ampdu len mblock:7
I (1545) wifi: Init lldesc rx ampdu entry mblock:4
I (1550) wifi: wifi power manager task: 0x3ffdaab4 prio: 21 stack: 2560
I (1557) wifi: wifi timer task: 3ffdbb5c, prio:22, stack:3584
;32mI (1577) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0m
I (1577) wifi: mode : sta (24:0a:c4:00:2f:90) + softAP (24:0a:c4:00:2f:91)
with GPO15 floating:

Code: Select all

ets Jun  8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:2488
load:0x40078000,len:7088
load:0x40080000,len:252
entry 0x40080034
;31mE (45) boot: ota data partition invalid, falling back to factorym
;32mI (1358) heap_alloc_caps: Initializing. RAM available for dynamic allocation:m
;32mI (1358) heap_alloc_caps: At 3FFCC990 len 00013670 (77 KiB): DRAMm
;32mI (1368) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAMm
;32mI (1389) heap_alloc_caps: At 4009CA04 len 000035FC (13 KiB): IRAMm
;32mI (1410) cpu_start: Pro cpu up.m
;32mI (1422) cpu_start: Single core modem
;32mI (1435) cpu_start: Pro cpu start user codem
;32mI (1495) cpu_start: Starting scheduler on PRO CPU.m
WARNING: Free heap size: 151328
I (1555) wifi: wifi firmware version: c604573
I (1555) wifi: config NVS flash: enabled
I (1555) wifi: config nano formating: disabled
I (1563) wifi: Init dynamic tx buffer num: 32
I (1563) wifi: wifi driver task: 3ffd56f8, prio:23, stack:3584
I (1568) wifi: Init static rx buffer num: 10
I (1572) wifi: Init dynamic rx buffer num: 0
I (1576) wifi: Init rx ampdu len mblock:7
I (1580) wifi: Init lldesc rx ampdu entry mblock:4
I (1585) wifi: wifi power manager task: 0x3ffdaab4 prio: 21 stack: 2560
I (1592) wifi: wifi timer task: 3ffdbb5c, prio:22, stack:3584
;32mI (1612) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0m
I (1613) wifi: mode : sta (24:0a:c4:00:2f:90) + softAP (24:0a:c4:00:2f:91)

So this part is suppressed:
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:2488
load:0x40078000,len:7088
load:0x40080000,len:252
entry 0x40080034

ESP_igrr
Posts: 2067
Joined: Tue Dec 01, 2015 8:37 am

Re: Suppress Boot messages

Postby ESP_igrr » Sun Apr 16, 2017 2:46 am

Remaining part comes from the second stage bootloader and the application. You can configure logging level for bootloader in Bootloader config in menuconfig, and for the application — under Component config, Logging.

wevets
Posts: 112
Joined: Sat Mar 09, 2019 2:56 am

Re: Suppress Boot messages

Postby wevets » Wed Dec 04, 2019 5:48 am

I had the same problem, the need to suppress boot messages to the terminal. I've found the complete solution. It consists of 3 steps.

1. As mentioned in earlier posts (> 2.5 years ago), strap GPIO15 to ground.

In "make menuconfig"

2. Bootloader config -> Bootloader log verbosity -> (no output)

3. Component config -> Log output -> Default log verbosity (no output)

Not doing any of these steps enables a different set of boot messages. For instance, not strapping GPIO15 to ground enables messages on reboot from deep sleep. The others enable different sets of boot messages.

design4
Posts: 6
Joined: Tue May 18, 2021 2:49 am

Re: Suppress Boot messages

Postby design4 » Tue May 18, 2021 2:54 am

Hi genius,

Im using ESP8266 freertos sdk. I have done three step to suppress boot msg but Im still unable to suppress fully boot msg. Below is the msg that printed at baudrate 74880.
ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x60000014, len 8, room 16
tail 8
Thanks in advanced

Who is online

Users browsing this forum: Baidu [Spider] and 131 guests