ESP32-WROOM-32D模组反复重启，显示Rebooting...，这是怎么回事

[xxkj2010]

ESP32-WROOM-32D模组，上传bootloader.bin到 0x1000，partition-table.bin到 0x8000，hello_world.bin到 0x10000之后，总是反复打印以下信息，请大家帮助分析一下，是哪个地方出错了。
Rebooting...
[0;32mI (12) boot: ESP-IDF v4.4 2nd stage bootloader[0m
[0;32mI (12) boot: compile time 20:52:46[0m
[0;32mI (12) boot: chip revision: 1[0m
[0;32mI (14) boot_comm: chip revision: 1, min. bootloader chip revision: 0[0m
[0;32mI (21) boot.esp32: SPI Speed : 40MHz[0m
[0;32mI (25) boot.esp32: SPI Mode : DIO[0m
[0;32mI (30) boot.esp32: SPI Flash Size : 4MB[0m
[0;32mI (35) boot: Enabling RNG early entropy source...[0m
[0;32mI (40) boot: Partition Table:[0m
[0;32mI (44) boot: ## Label Usage Type ST Offset Length[0m
[0;32mI (51) boot: 0 nvs WiFi data 01 02 00009000 00006000[0m
[0;32mI (58) boot: 1 phy_init RF data 01 01 0000f000 00001000[0m
[0;32mI (66) boot: 2 factory factory app 00 00 00010000 00100000[0m
[0;32mI (73) boot: End of partition table[0m
[0;32mI (77) boot_comm: chip revision: 1, min. application chip revision: 0[0m
[0;32mI (84) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=07b64h ( 31588) map[0m
[0;32mI (104) esp_image: segment 1: paddr=00017b8c vaddr=3ffb0000 size=02360h ( 9056) load[0m
[0;32mI (108) esp_image: segment 2: paddr=00019ef4 vaddr=40080000 size=06124h ( 24868) load[0m
[0;32mI (122) esp_image: segment 3: paddr=00020020 vaddr=400d0020 size=14fc4h ( 85956) map[0m
[0;32mI (154) esp_image: segment 4: paddr=00034fec vaddr=40086124 size=05040h ( 20544) load[0m
[0;32mI (162) esp_image: segment 5: paddr=0003a034 vaddr=50000000 size=00010h ( 16) load[0m
[0;32mI (168) boot: Loaded app from partition at offset 0x10000[0m
[0;32mI (168) boot: Disabling RNG early entropy source...[0m
[0;32mI (185) cpu_start: Pro cpu up.[0m
[0;31mE (185) cpu_start: Running on single core variant of a chip, but app is built with multi-core support.[0m
[0;31mE (187) cpu_start: Check that CONFIG_FREERTOS_UNICORE is enabled in menuconfig[0m

abort() was called at PC 0x400d0d3c on core 0


Backtrace:0x4008181e:0x3ffe3b600x40085051:0x3ffe3b80 0x40089e56:0x3ffe3ba0 0x400d0d3c:0x3ffe3c10 0x40081101:0x3ffe3c40 0x400794d4:0x3ffe3c80 |<-CORRUPTED




ELF file SHA256: d40a0c5809e257fc