完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
烧写v4.0.1中examplesbluetoothesp_ble_meshble_mesh_nodeonoff_client例子,menuconfig配已了CONFIG_BLE_MESH_ESP_WROVER,烧写完成后可以正常运行,然后经过几次断电(usb连pc供电)后,不断出现以下错误,尝试idf.py flash重烧,还是出现同样错误,使用idf.py erase再idf.py flash,也是同样错误。
目前手上三块板子有一块出现了这种问题,刚买三天。 请问如何解决,谢谢! ts Jun 8 2016 00:22:57 rst:0xc (SW_CPU_RESET),boot:0x13 (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:6864 ho 0 tail 12 room 4 load:0x40078000,len:14076 load:0x40080400,len:4304 entry 0x400806e8 I (75) boot: Chip Revision: 1 I (75) boot_comm: chip revision: 1, min. bootloader chip revision: 0 I (41) boot: ESP-IDF v4.0.1-dirty 2nd stage bootloader I (41) boot: compile time 15:49:12 I (41) boot: Enabling RNG early entropy source... I (47) boot: SPI Speed : 40MHz I (51) boot: SPI Mode : DIO I (55) boot: SPI Flash Size : 2MB I (59) boot: Partition Table: I (62) boot: ## Label Usage Type ST Offset Length I (70) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (77) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (85) boot: 2 factory factory app 00 00 00010000 00100000 I (92) boot: End of partition table I (96) boot_comm: chip revision: 1, min. application chip revision: 0 I (103) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x2bfe0 (180192) map I (177) esp_image: segment 1: paddr=0x0003c008 vaddr=0x3ffbdb60 size=0x03c0c ( 15372) load I (183) esp_image: segment 2: paddr=0x0003fc1c vaddr=0x40080000 size=0x003f4 ( 1012) load I (184) esp_image: segment 3: paddr=0x00040018 vaddr=0x400d0018 size=0xa059c (656796) map I (427) esp_image: segment 4: paddr=0x000e05bc vaddr=0x400803f4 size=0x0000c ( 12) load I (428) esp_image: segment 5: paddr=0x000e05d0 vaddr=0x40080400 size=0x12c00 ( 76800) load I (478) boot: Loaded app from partition at offset 0x10000 I (478) boot: Disabling RNG early entropy source... I (479) cpu_start: Pro cpu up. I (482) cpu_start: Application information: I (487) cpu_start: Project name: onoff_client I (493) cpu_start: App version: v4.0.1-dirty I (498) cpu_start: Compile time: Jun 22 2020 15:48:25 I (504) cpu_start: ELF file SHA256: 727a686671428cc0... I (510) cpu_start: ESP-IDF: v4.0.1-dirty I (515) cpu_start: Starting app cpu, entry point is 0x400812b4 I (501) cpu_start: App cpu up. I (526) heap_init: Initializing. RAM available for dynamic allocation: I (533) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM I (539) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM I (545) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM I (551) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM I (557) heap_init: At 3FFCC550 len 00013AB0 (78 KiB): DRAM I (563) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (570) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (576) heap_init: At 40093000 len 0000D000 (52 KiB): IRAM I (582) cpu_start: Pro cpu start user code I (601) spi_flash: detected chip: generic I (601) spi_flash: flash io: dio W (601) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (612) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (623) onoff_client: Initializing... use esp timer !!! I (633) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3 I (653) BTDM_INIT: BT controller compile version [c1cbe45] I (653) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE W (663) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration |
|
相关推荐
1个回答
|
|
以下是一些建议来解决这个问题:
1. 检查电源:确保您的板子在断电后能够正常供电。如果可能,请尝试使用不同的电源适配器或USB线。 2. 检查烧录设置:在menuconfig中,确保您已经选择了正确的烧录选项,例如烧录速度、烧录大小等。 3. 检查固件版本:您提到使用的是v4.0.1版本,可以尝试升级到最新版本的ESP-IDF,以获取可能的修复和改进。 4. 检查硬件:检查您的板子是否有任何损坏或焊接问题。如果可能,请尝试使用另一块板子进行测试。 5. 检查示例代码:确保您使用的示例代码是正确的,没有错误或遗漏。您可以尝试烧录其他示例程序,看看问题是否仍然存在。 6. 重置板子:尝试对板子进行硬件重置,例如通过按住FLASH按钮,然后给板子供电。 7. 检查错误日志:您提供的错误日志显示了SW_CPU_RESET和SPI_FAST_FLASH_BOOT,这可能表明板子在尝试烧录时遇到了问题。检查您的烧录工具和设置,确保它们与板子兼容。 |
|
|
|
只有小组成员才能发言,加入小组>>
509浏览 6评论
426浏览 5评论
有没有办法在不使用混杂模式的情况下实现Wifi驱动程序接收缓冲区访问中断呢?
404浏览 5评论
406浏览 4评论
378浏览 4评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-10-21 16:54 , Processed in 0.760838 second(s), Total 81, Slave 63 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号