[问答]

在esp32开发板上测试blufi例程，一直循环打印这两条log，wifi无法连接是什么原因导致？

问答对人有帮助，内容完整，我也想知道答案 0 在esp32开发板上测试blufi例程，发现在ble成功连接后，通过手机发送完ssid和password后，一直循环打印这两条log，wifi无法连接，不知道是什么原因导致？未对例程做任何修改。 E (60049) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (60049) BT_BTC: btc_blufi_send_encap wait to send blufi custom data 下面为开机的log: I (29) boot: ESP-IDF v4.2-dirty 2nd stage bootloader I (29) boot: compile time 15:40:07 I (29) boot: chip revision: 1 I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0 I (39) boot.esp32: SPI Speed : 40MHz I (44) boot.esp32: SPI Mode : DIO I (48) boot.esp32: SPI Flash Size : 2MB I (53) boot: Enabling RNG early entropy source... I (58) boot: Partition Table: I (62) boot: ## Label Usage Type ST Offset Length I (69) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (76) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (84) boot: 2 factory factory app 00 00 00010000 00100000 I (91) 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=0x2453c (148796) map I (168) esp_image: segment 1: paddr=0x00034564 vaddr=0x3ffbdb60 size=0x03f78 ( 16248) load I (175) esp_image: segment 2: paddr=0x000384e4 vaddr=0x40080000 size=0x00404 ( 1028) load 0x40080000: _WindowOverflow4 at C:/Users/liny/Desktop/esp-idf-2/components/freertos/xtensa/xtensa_vectors.S:1730 I (176) esp_image: segment 3: paddr=0x000388f0 vaddr=0x40080404 size=0x07728 ( 30504) load I (198) esp_image: segment 4: paddr=0x00040020 vaddr=0x400d0020 size=0xa9248 (692808) map 0x400d0020: _stext at ??:? I (462) esp_image: segment 5: paddr=0x000e9270 vaddr=0x40087b2c size=0x15e64 ( 89700) load 0x40087b2c: r_lld_pdu_rx_handler at ??:? I (517) boot: Loaded app from partition at offset 0x10000 I (517) boot: Disabling RNG early entropy source... I (518) cpu_start: Pro cpu up. I (521) cpu_start: Application information: I (526) cpu_start: Project name: blufi_demo I (531) cpu_start: App version: v4.2-dirty I (536) cpu_start: Compile time: May 18 2021 10:01:43 I (542) cpu_start: ELF file SHA256: d2501fc46410de51... I (548) cpu_start: ESP-IDF: v4.2-dirty I (554) cpu_start: Starting app cpu, entry point is 0x400818d4 0x400818d4: call_start_cpu1 at C:/Users/liny/Desktop/esp-idf-2/components/esp32/cpu_start.c:287 I (0) cpu_start: App cpu up. I (564) heap_init: Initializing. RAM available for dynamic allocation: I (571) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM I (577) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM I (583) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM I (589) heap_init: At 3FFCB280 len 00014D80 (83 KiB): DRAM I (595) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (602) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (608) heap_init: At 4009D990 len 00002670 (9 KiB): IRAM I (614) cpu_start: Pro cpu start user code I (633) spi_flash: detected chip: generic I (633) spi_flash: flash io: dio W (633) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (644) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (750) wifi:wifi driver task: 3ffcf6a0, prio:23, stack:6656, core=0 I (750) system_api: Base MAC address is not set I (750) system_api: read default base MAC address from EFUSE I (770) wifi:wifi firmware version: 1865b55 I (770) wifi:wifi certification version: v7.0 I (770) wifi:config NVS flash: enabled I (770) wifi:config nano formating: disabled I (780) wifi:Init data frame dynamic rx buffer num: 32 I (780) wifi:Init management frame dynamic rx buffer num: 32 I (790) wifi:Init management short buffer num: 32 I (790) wifi:Init dynamic tx buffer num: 32 I (800) wifi:Init static rx buffer size: 1600 I (800) wifi:Init static rx buffer num: 10 I (800) wifi:Init dynamic rx buffer num: 32 I (810) wifi_init: rx ba win: 6 I (810) wifi_init: tcpip mbox: 32 I (820) wifi_init: udp mbox: 6 I (820) wifi_init: tcp mbox: 6 I (820) wifi_init: tcp tx win: 5744 I (830) wifi_init: tcp rx win: 5744 I (830) wifi_init: tcp mss: 1440 I (840) wifi_init: WiFi IRAM OP enabled I (840) wifi_init: WiFi RX IRAM OP enabled I (930) phy: phy_version: 4500, 0cd6843, Sep 17 2020, 15:37:07, 0, 0 I (940) wifi:mode : sta (08:3a:f2:ac:1b:e8) I (940) BTDM_INIT: BT controller compile version [3723d5b] I (1280) BLUFI_EXAMPLE: BD ADDR: 08:3a:f2:ac:1b:ea I (1280) BLUFI_EXAMPLE: BLUFI VERSION 0102 I (1280) BLUFI_EXAMPLE: BLUFI init finish I (350810) BLUFI_EXAMPLE: BLUFI ble connect E (354550) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354550) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354560) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354560) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354580) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354580) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354590) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354590) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354600) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354600) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354620) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354620) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354630) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354630) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354650) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354650) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354660) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354660) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354670) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354670) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354690) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354690) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354700) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354700) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354720) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354720) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354730) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354730) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354740) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354740) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354760) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354760) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354770) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354770) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354790) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354790) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354800) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354800) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354820) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354820) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354830) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354830) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354840) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354840) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354860) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354860) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354870) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354870) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354890) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354890) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354900) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354900) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354910) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354910) BT_BTC: btc_blufi_send_encap wait to send blufi custom data E (354930) BT_L2CAP: l2ble_update_att_acl_pkt_num not found p_tcb W (354930) BT_BTC: btc_blufi_send_encap wait to send blufi custom data 0 本主题由 Harmony技术专家于 2024-6-22 15:06 审核通过
2024-6-21 15:44:03　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × hgimtk 该类别下有 38 个回答。邀请回答 wang21cj 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答 overheat 该类别下有 27 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答安德森大该类别下有 27 个回答。邀请回答 xwgc888 该类别下有 27 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答 h1654155143.8331 该类别下有 27 个回答。邀请回答举报梁宏满相关推荐 • ESP32C2（8684）BLUFI例程不通是什么原因造成的？ 114 • ESP32C2（8684）BLUFI例程不通的原因？ 138 • 求助，ESP32C2（8684）BLUFI例程不通的原因？ 104 • esp8684-DevKitM-1 BLUFI例程不通的原因？ 99 • Lyrat_mini-v1.2开发板烧录VoIP.bin后无法连接到FreePBX的原因？如何解决？ 160 • 求助，ESP32C2（8684）BLUFI例程不通怎么处理？ 141 • 将BLE与ESP32连接时，导致与任何Android应用程序的BLE连接失败的原因？ 215 • 测试ESP-IDF ESP32C6，创建线程调用recvform接收数据发现一直被阻塞，如何解决？ 254 • 将BLE与ESP32连接失败的原因？ 504 • esp32-s2r2芯片无法下载是什么原因导致的？ 268 1个回答

答案对人有帮助，有参考价值 0 以下是一些建议和可能的原因： 1. 确保您的ESP32开发板固件是最新的。您提到的“ESP-IDF v4.2-dirty”可能表示您的固件不是最新的。请尝试更新到最新的稳定版本。 2. 检查您的ESP32开发板的硬件连接是否正常。确保天线连接正确，没有损坏或松动。 3. 检查您的手机是否支持BLE。确保您的手机蓝牙功能正常，并且支持BLE。 4. 检查您的SSID和密码是否正确。确保您输入的SSID和密码与您的WiFi网络匹配。 5. 检查您的WiFi网络是否允许BLE设备连接。有些WiFi网络可能限制了连接的设备类型。 6. 检查ESP32开发板的电源供应是否稳定。不稳定的电源可能会影响WiFi连接。 7. 尝试使用其他BLE设备或手机进行测试，以排除设备兼容性问题。 8. 如果问题仍然存在，您可以尝试查看ESP32开发板的日志，以获取更多关于问题的信息。您提供的日志信息中，"E (60049) BT_L2CAP: l2ble_update_att_acl_pkt_num not found" 和 "W (60049) BT_BTC: btc_blufi_send_encap wait to send blufi custom data" 可能与BLE连接有关，但不一定与WiFi连接问题直接相关。您可以进一步分析这些日志，以确定问题的根本原因。

2024-6-22 15:36:33 评论举报麻酱