完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
最近学习用ESP32, 想试试蓝牙组网。ESP-IDFexamplesbluetoothbluedroidbleblufi 在eclipse环境编译,下载到开发板;在华为P40 Pro上安装EspBluFi,运行后能够配对蓝牙设备,但是EspBluFi上显示:
Connected FC:F5:C4:3C:4C:42 Discover service failed Disconnected FC:F5:C4:3C:4C:42 开发板的串口终端显示: ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_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:0x3fff0030,len:4 load:0x3fff0034,len:6872 load:0x40078000,len:13072 ho 0 tail 12 room 4 load:0x40080400,len:3896 entry 0x40080688 I (31) boot: ESP-IDF v4.1-dirty 2nd stage bootloader I (31) boot: compile time 14:38:49 I (31) boot: chip revision: 3 I (34) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (41) boot.esp32: SPI Speed : 40MHz I (46) boot.esp32: SPI Mode : DIO I (51) boot.esp32: SPI Flash Size : 2MB I (55) boot: Enabling RNG early entropy source... I (60) boot: Partition Table: I (64) boot: ## Label Usage Type ST Offset Length I (71) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (79) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (86) boot: 2 factory factory app 00 00 00010000 00100000 I (94) boot: End of partition table I (98) boot_comm: chip revision: 3, min. application chip revision: 0 I (105) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x24964 (149860) map I (171) esp_image: segment 1: paddr=0x0003498c vaddr=0x3ffbdb60 size=0x03fc4 ( 16324) load I (178) esp_image: segment 2: paddr=0x00038958 vaddr=0x40080000 size=0x00404 ( 1028) load I (179) esp_image: segment 3: paddr=0x00038d64 vaddr=0x40080404 size=0x072b4 ( 29364) load I (200) esp_image: segment 4: paddr=0x00040020 vaddr=0x400d0020 size=0xa89ac (690604) map I (463) esp_image: segment 5: paddr=0x000e89d4 vaddr=0x400876b8 size=0x15040 ( 86080) load I (515) boot: Loaded app from partition at offset 0x10000 I (516) boot: Disabling RNG early entropy source... I (516) cpu_start: Pro cpu up. I (520) cpu_start: Application information: I (524) cpu_start: Project name: blufi_demo I (530) cpu_start: App version: 1 I (534) cpu_start: Compile time: Oct 8 2020 14:38:23 I (540) cpu_start: ELF file SHA256: 734af5f98b12f6eb... I (546) cpu_start: ESP-IDF: v4.1-dirty I (551) cpu_start: Starting app cpu, entry point is 0x400812dc I (0) cpu_start: App cpu up. I (562) heap_init: Initializing. RAM available for dynamic allocation: I (569) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM I (575) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM I (581) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM I (587) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM I (593) heap_init: At 3FFCC550 len 00013AB0 (78 KiB): DRAM I (599) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (606) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (612) heap_init: At 4009C6F8 len 00003908 (14 KiB): IRAM I (618) cpu_start: Pro cpu start user code I (636) spi_flash: detected chip: generic I (637) spi_flash: flash io: dio W (637) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (648) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (753) wifi:wifi driver task: 3ffd0a34, prio:23, stack:6656, core=0 I (753) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (753) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (783) wifi:wifi firmware version: 3ea4c76 I (783) wifi:config NVS flash: enabled I (783) wifi:config nano formating: disabled I (783) wifi:Init dynamic tx buffer num: 32 I (793) wifi:Init data frame dynamic rx buffer num: 32 I (793) wifi:Init management frame dynamic rx buffer num: 32 I (803) wifi:Init management short buffer num: 32 I (803) wifi:Init static rx buffer size: 1600 I (803) wifi:Init static rx buffer num: 10 I (813) wifi:Init dynamic rx buffer num: 32 I (903) phy: phy_version: 4180, cb3948e, Sep 12 2019, 16:39:13, 0, 0 I (903) wifi:mode : sta (fc:f5:c4:3c:4c:40) I (913) BTDM_INIT: BT controller compile version [219866f] I (913) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (1243) BLUFI_EXAMPLE: BD ADDR: fc:f5:c4:3c:4c:42 I (1253) BLUFI_EXAMPLE: BLUFI VERSION 0102 I (1253) BLUFI_EXAMPLE: BLUFI init finish I (21333) BLUFI_EXAMPLE: BLUFI ble connect I (22533) BLUFI_EXAMPLE: BLUFI ble disconnect I (1692123) BLUFI_EXAMPLE: BLUFI ble connect I (1693313) BLUFI_EXAMPLE: BLUFI ble disconnect I (1705773) BLUFI_EXAMPLE: BLUFI ble connect I (1707013) BLUFI_EXAMPLE: BLUFI ble disconnect 哪位高手给指点一下,问题出在哪里?演示程序没有做任何修改,配置也没有做修改。 |
|
相关推荐
1个回答
|
|
在这种情况下,我们可以通过以下几个步骤来诊断问题:
1. 检查ESP-IDF版本:确保你使用的ESP-IDF版本与示例代码兼容。如果不兼容,尝试更新或降级ESP-IDF。 2. 检查蓝牙配置:检查示例代码中的蓝牙配置是否正确。例如,确保蓝牙设备名称、服务UUID等设置正确。 3. 检查EspBluFi应用程序:确保EspBluFi应用程序是最新版本,并且与ESP32设备兼容。如果可能,请尝试使用其他蓝牙扫描应用程序来排除EspBluFi的问题。 4. 检查开发板硬件:确保ESP32_DevKitC_V4开发板没有硬件问题。检查电源、连接线等是否正常。 5. 检查串口终端输出:从串口终端输出来看,设备已经成功启动并进入SPI快速闪存模式。但是,没有关于蓝牙发现服务失败的详细信息。这可能是由于蓝牙服务未正确注册或服务UUID不正确。 6. 检查ESP32日志输出:在ESP-IDF中启用更详细的日志输出,以便更好地了解问题所在。你可以在`menuconfig`中设置日志级别,然后重新编译并上传代码。 7. 检查代码:检查示例代码,确保没有错误或遗漏。如果可能,请尝试使用其他蓝牙示例代码,以排除代码问题。 8. 搜索相关问题:在ESP-IDF的GitHub问题跟踪器或其他社区论坛上搜索类似问题,看看是否有其他人遇到相同的问题,并找到解决方案。 通过以上步骤,你应该能够找到导致蓝牙发现服务失败的原因,并采取相应的解决措施。 |
|
|
|
只有小组成员才能发言,加入小组>>
474浏览 6评论
398浏览 5评论
有没有办法在不使用混杂模式的情况下实现Wifi驱动程序接收缓冲区访问中断呢?
378浏览 5评论
384浏览 4评论
354浏览 4评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-9-29 07:13 , Processed in 0.737223 second(s), Total 78, Slave 62 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号