[问答]

用ESP32的纯芯片设计的电路板，不断复位的原因？

问答对人有帮助，内容完整，我也想知道答案 0 我们的硬件工程师设计了一款PCBA实现项目功能，需要将一些数据保存到外置flash, 我在调试的时候发现只要初始化了华邦的SPI flash的片选引脚，MCU就会不断的重启（所有看门狗都已经关闭），不初始化这个引脚就不会重启，导致flash无法使用，搞不懂时什么原因？ entry 0x40080678 I (54) boot: ESP-IDF v4.3.1-dirty 2nd stage bootloader I (54) boot: compile time 17:30:11 I (54) boot: chip revision: 3 I (58) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (74) boot.esp32: SPI Speed : 40MHz I (74) boot.esp32: SPI Mode : DIO I (74) boot.esp32: SPI Flash Size : 4MB W (79) boot.esp32: PRO CPU has been reset by WDT. W (84) boot.esp32: WDT reset info: PRO CPU PC=0x400803c0 0x400803c0: _DoubleExceptionVector at D:/ESP32_GIT/components/freertos/port/xtensa/xtensa_vectors.S:455 W (90) boot.esp32: WDT reset info: APP CPU PC=0x400e6202 (waiti mode) 0x400e6202: esp_pm_impl_waiti at D:/ESP32_GIT/components/esp_pm/pm_impl.c:829 I (97) boot: Enabling RNG early entropy source... I (103) boot: Partition Table: I (106) boot: ## Label Usage Type ST Offset Length I (114) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (121) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (129) boot: 2 factory factory app 00 00 00010000 00100000 I (136) boot: End of partition table I (141) boot_comm: chip revision: 3, min. application chip revision: 0 I (148) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=08dd4h ( 36308) map I (170) esp_image: segment 1: paddr=00018dfc vaddr=3ffb0000 size=029bch ( 10684) load I (174) esp_image: segment 2: paddr=0001b7c0 vaddr=40080000 size=04858h ( 18520) load I (183) esp_image: segment 3: paddr=00020020 vaddr=400d0020 size=167d4h ( 92116) map I (217) esp_image: segment 4: paddr=000367fc vaddr=40084858 size=07d44h ( 32068) load I (231) esp_image: segment 5: paddr=0003e548 vaddr=50000000 size=00010h ( 16) load I (237) boot: Loaded app from partition at offset 0x10000 I (237) boot: Disabling RNG early entropy source... I (251) cpu_start: Pro cpu up. I (251) cpu_start: Starting app cpu, entry point is 0x400810a0 0x400810a0: call_start_cpu1 at D:/ESP32_GIT/components/esp_system/port/cpu_start.c:141 I (0) cpu_start: App cpu up. I (265) cpu_start: Pro cpu start user code I (265) cpu_start: cpu freq: 160000000 I (265) cpu_start: Application information: I (270) cpu_start: Project name: play_mp3_pwm_or_dac I (276) cpu_start: App version: v2.3-99-g107e8c3-dirty I (282) cpu_start: Compile time: Jul 11 2022 10:32:05 I (288) cpu_start: ELF file SHA256: 0853114b73ceec0c... I (294) cpu_start: ESP-IDF: v4.3.1-dirty I (300) heap_init: Initializing. RAM available for dynamic allocation: I (307) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (313) heap_init: At 3FFB32E8 len 0002CD18 (179 KiB): DRAM I (319) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (325) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (332) heap_init: At 4008C59C len 00013A64 (78 KiB): IRAM I (339) spi_flash: detected chip: winbond I (343) spi_flash: flash io: dio I (348) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU.entry 0x40080678 I (54) boot: ESP-IDF v4.3.1-dirty 2nd stage bootloader I (54) boot: compile time 17:30:11 I (54) boot: chip revision: 3 I (58) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (74) boot.esp32: SPI Speed : 40MHz I (74) boot.esp32: SPI Mode : DIO I (74) boot.esp32: SPI Flash Size : 4MB W (79) boot.esp32: PRO CPU has been reset by WDT. W (84) boot.esp32: WDT reset info: PRO CPU PC=0x400803c0 0x400803c0: _DoubleExceptionVector at D:/ESP32_GIT/components/freertos/port/xtensa/xtensa_vectors.S:455 W (90) boot.esp32: WDT reset info: APP CPU PC=0x400e6202 (waiti mode) 0x400e6202: esp_pm_impl_waiti at D:/ESP32_GIT/components/esp_pm/pm_impl.c:829 I (97) boot: Enabling RNG early entropy source... I (103) boot: Partition Table: I (106) boot: ## Label Usage Type ST Offset Length I (114) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (121) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (129) boot: 2 factory factory app 00 00 00010000 00100000 I (136) boot: End of partition table I (141) boot_comm: chip revision: 3, min. application chip revision: 0 I (148) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=08dd4h ( 36308) map I (170) esp_image: segment 1: paddr=00018dfc vaddr=3ffb0000 size=029bch ( 10684) load I (174) esp_image: segment 2: paddr=0001b7c0 vaddr=40080000 size=04858h ( 18520) load I (183) esp_image: segment 3: paddr=00020020 vaddr=400d0020 size=167d4h ( 92116) map I (217) esp_image: segment 4: paddr=000367fc vaddr=40084858 size=07d44h ( 32068) load I (231) esp_image: segment 5: paddr=0003e548 vaddr=50000000 size=00010h ( 16) load I (237) boot: Loaded app from partition at offset 0x10000 I (237) boot: Disabling RNG early entropy source... I (251) cpu_start: Pro cpu up. I (251) cpu_start: Starting app cpu, entry point is 0x400810a0 0x400810a0: call_start_cpu1 at D:/ESP32_GIT/components/esp_system/port/cpu_start.c:141 I (0) cpu_start: App cpu up. I (265) cpu_start: Pro cpu start user code I (265) cpu_start: cpu freq: 160000000 I (265) cpu_start: Application information: I (270) cpu_start: Project name: play_mp3_pwm_or_dac I (276) cpu_start: App version: v2.3-99-g107e8c3-dirty I (282) cpu_start: Compile time: Jul 11 2022 10:32:05 I (288) cpu_start: ELF file SHA256: 0853114b73ceec0c... I (294) cpu_start: ESP-IDF: v4.3.1-dirty I (300) heap_init: Initializing. RAM available for dynamic allocation: I (307) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (313) heap_init: At 3FFB32E8 len 0002CD18 (179 KiB): DRAM I (319) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (325) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (332) heap_init: At 4008C59C len 00013A64 (78 KiB): IRAM I (339) spi_flash: detected chip: winbond I (343) spi_flash: flash io: dio I (348) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. 0 本主题由 Harmony技术专家于 2024-6-14 15:39 审核通过
2024-6-14 06:34:18　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 38 个回答。邀请回答 hgimtk 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答 723662364d 该类别下有 27 个回答。邀请回答 overheat 该类别下有 27 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答安德森大该类别下有 27 个回答。邀请回答 xwgc888 该类别下有 27 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答举报 jsqueh 相关推荐 • 用ESP32的纯芯片设计的电路板不断复位是什么原因？ 232 • ESP32为什么没有显示电路板的引脚号？ 265 • 用ESP32的纯芯片设计的电路板，MCU不断重启的原因？ 652 • 用ESP32-S2FN4R2芯片设计出来的板焊上ESP32-S2FN4R2后烧录不了的原因？ 238 • ESP32 C3FN4检测不到芯片是怎么回事？ 306 • ESP32-WROOM-32U不断重启的原因？ 187 • esp32-s2r2芯片无法下载是什么原因导致的？ 284 • 为什么ESP32开发模块需要不断按下启动按钮才能启动程序呢？ 242 • ESP32始终以下载模式启动是怎么回事？ 362 • 如何管理电路板和通过电路板连接的外部RGB LED灯条的电源需求？ 421 1个回答

答案对人有帮助，有参考价值 0 根据您提供的信息，您的ESP32电路板在初始化华邦SPI Flash的片选引脚时不断重启。这个问题可能有以下几个原因： 1. 电源问题：确保SPI Flash的电源稳定，电压在规定的范围内。不稳定的电源可能导致MCU不断重启。 2. 引脚连接问题：检查SPI Flash的片选引脚是否正确连接到ESP32。错误的连接可能导致信号不稳定，从而引发重启。 3. SPI通信问题：检查SPI通信设置，包括时钟速率、数据传输模式等。不匹配的设置可能导致通信错误，进而引发重启。 4. 硬件冲突：检查电路板上是否有其他硬件设备与SPI Flash共享资源，如共享SPI总线。硬件冲突可能导致MCU不断重启。 5. 软件问题：检查您的代码，确保SPI Flash的初始化和操作是正确的。错误的代码可能导致MCU在执行过程中不断重启。 6. 固件/软件版本问题：您提到的ESP-IDF版本是4.3.1-dirty，这可能表示您的固件或软件版本存在问题。尝试更新到最新的稳定版本，看看问题是否得到解决。 7. 硬件故障：如果以上方法都无法解决问题，可能是ESP32或SPI Flash本身存在硬件故障。尝试更换MCU或Flash，看看问题是否仍然存在。建议您按照上述步骤逐一排查问题，找到导致ESP32不断重启的原因，并进行相应的修复。

2024-6-14 16:57:28 评论举报叹久