Page 1 of 1

Bootstrap pin - MTDO

Posted: Thu Sep 05, 2019 1:27 am
by Seungwhan
Hi,
So I shorted the MTDO pin(GPIO15) and I still get the boot log like these.
Wasn't the pin to disable these logs?
What could possibly gone wrong?
Thanks for your comments.

------------
I (12) boot: ESP-IDF v3.2.2-dirty 2nd stage bootloader
I (12) boot: compile time 16:57:47
I (12) boot: Enabling RNG early entropy source...
I (16) boot: SPI Speed : 40MHz
I (20) boot: SPI Mode : DIO
I (24) boot: SPI Flash Size : 8MB
I (28) boot: Partition Table:
I (31) boot: ## Label Usage Type ST Offset Length
I (39) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (46) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (54) boot: 2 factory factory app 00 00 00010000 00100000
I (61) boot: End of partition table
I (65) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x08848 ( 34888) map
I (86) esp_image: segment 1: paddr=0x00018870 vaddr=0x3ffb0000 size=0x01eb0 ( 7856) load
I (90) esp_image: segment 2: paddr=0x0001a728 vaddr=0x40080000 size=0x00400 ( 1024) load
I (95) esp_image: segment 3: paddr=0x0001ab30 vaddr=0x40080400 size=0x054e0 ( 21728) load
I (112) esp_image: segment 4: paddr=0x00020018 vaddr=0x400d0018 size=0x127b8 ( 75704) map
I (139) esp_image: segment 5: paddr=0x000327d8 vaddr=0x400858e0 size=0x03ca4 ( 15524) load
I (151) boot: Loaded app from partition at offset 0x10000
I (151) boot: Disabling RNG early entropy source...
I (152) cpu_start: Pro cpu up.
I (155) cpu_start: Starting app cpu, entry point is 0x40080e94
I (0) cpu_start: App cpu up.
I (166) heap_init: Initializing. RAM available for dynamic allocation:
I (173) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (179) heap_init: At 3FFB2EF8 len 0002D108 (180 KiB): DRAM
I (185) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (191) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (198) heap_init: At 40089584 len 00016A7C (90 KiB): IRAM
I (204) cpu_start: Pro cpu start user code
I (222) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
----------------------------

Re: Bootstrap pin - MTDO

Posted: Thu Sep 05, 2019 1:52 am
by WiFive
I (12) boot: ESP-IDF v3.2.2-dirty 2nd stage bootloader
Try menuconfig

Re: Bootstrap pin - MTDO

Posted: Thu Sep 05, 2019 4:29 pm
by Seungwhan
Thanks for the reply.
OK, so I figured it out all and posting the result here for future reference.


ets Jun 8 2016 00:22:57 <--------------- Start of ROM Bootloader log. Can be disabled by MTDO pin.

rst:0x1 (POWERON_RESET),boot:0x17 (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:6200
load:0x40078000,len:10180
load:0x40080400,len:6660
entry 0x40080764
I (28) boot: ESP-IDF v3.2.2-dirty 2nd stage bootloader <---- Start of 2nd Stage Bootloader. Can be disabled by LOG_BOOTLOADER_LEVEL_NONE.
I (28) boot: compile time 16:57:47
I (29) boot: Enabling RNG early entropy source...
I (33) boot: SPI Speed : 40MHz
I (38) boot: SPI Mode : DIO
I (42) boot: SPI Flash Size : 8MB
I (46) boot: Partition Table:
I (49) boot: ## Label Usage Type ST Offset Length
I (57) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (64) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (71) boot: 2 factory factory app 00 00 00010000 00100000
I (79) boot: End of partition table
I (83) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x08848 ( 34888) map
I (104) esp_image: segment 1: paddr=0x00018870 vaddr=0x3ffb0000 size=0x01eb0 ( 7856) load
I (108) esp_image: segment 2: paddr=0x0001a728 vaddr=0x40080000 size=0x00400 ( 1024) load
I (112) esp_image: segment 3: paddr=0x0001ab30 vaddr=0x40080400 size=0x054e0 ( 21728) load
I (130) esp_image: segment 4: paddr=0x00020018 vaddr=0x400d0018 size=0x127b8 ( 75704) map
I (157) esp_image: segment 5: paddr=0x000327d8 vaddr=0x400858e0 size=0x03ca4 ( 15524) load
I (169) boot: Loaded app from partition at offset 0x10000
I (169) boot: Disabling RNG early entropy source...
I (170) cpu_start: Pro cpu up. <---------- Start of Kernel(or FreeRTOS) message. Can be disabled by LOG_DEFAULT_LEVEL_NONE.
I (173) cpu_start: Starting app cpu, entry point is 0x40080e94
I (0) cpu_start: App cpu up.
I (184) heap_init: Initializing. RAM available for dynamic allocation:
I (191) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (197) heap_init: At 3FFB2EF8 len 0002D108 (180 KiB): DRAM
I (203) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (209) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (216) heap_init: At 40089584 len 00016A7C (90 KiB): IRAM
I (222) cpu_start: Pro cpu start user code
I (240) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.