我用贵公司的芯片ESP32-WROVER-B模组,用的esp-idf V3.X版本,一切正常,后因有些例程只有V4.x上才有,我就 git checkout 成了 esp-idf V4.X版,build,烧录下载,引导提示过程均一切正常,但是执行到例程Main部分后出现
E (484) Client: bluetooth_init initialize controller failed
E (484) Client: esp32_bluetooth_init failed (err 258)
蓝牙初始化失败?
后来我发现在V4.X下,4.0 - 4.3,所有的,只要关于BLE的例程,都会出现这个错误,这是怎么回事呢?
ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
Last edited by xiang8000 on Wed May 20, 2020 7:51 am, edited 1 time in total.
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
启动代码如下,错误在最后两行,对应的出错代码为:
I (31) boot: ESP-IDF v4.2-dev-1054-g7d0f1536e-dirty 2nd stage bootloader
I (31) boot: compile time 10:13:53
I (31) boot: chip revision: 1
I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (32) boot.esp32: SPI Speed : 40MHz
I (33) boot.esp32: SPI Mode : DIO
I (34) boot.esp32: SPI Flash Size : 4MB
I (34) boot: Enabling RNG early entropy source...
I (35) boot: Partition Table:
I (35) boot: ## Label Usage Type ST Offset Length
I (36) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (37) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (38) boot: 2 factory factory app 00 00 00010000 00100000
I (39) boot: End of partition table
I (39) boot_comm: chip revision: 1, min. application chip revision: 0
I (40) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x2e84c (190540) map
I (114) esp_image: segment 1: paddr=0x0003e874 vaddr=0x3ffbdb60 size=0x017a4 ( 6052) load
I (117) esp_image: segment 2: paddr=0x00040020 vaddr=0x400d0020 size=0xa5ec8 (679624) map
0x400d0020: _stext at ??:?
I (376) esp_image: segment 3: paddr=0x000e5ef0 vaddr=0x3ffbf304 size=0x025bc ( 9660) load
I (380) esp_image: segment 4: paddr=0x000e84b4 vaddr=0x40080000 size=0x00404 ( 1028) load
0x40080000: _WindowOverflow4 at /home/xiang/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730
I (381) esp_image: segment 5: paddr=0x000e88c0 vaddr=0x40080404 size=0x131f0 ( 78320) load
I (426) boot: Loaded app from partition at offset 0x10000
I (426) boot: Disabling RNG early entropy source...
I (426) cpu_start: Pro cpu up.
I (426) cpu_start: Application information:
I (427) cpu_start: Project name: vendor_client
I (428) cpu_start: App version: v4.2-dev-1054-g7d0f1536e-dirty
I (428) cpu_start: Compile time: Apr 22 2020 10:13:38
I (429) cpu_start: ELF file SHA256: 705cd9ffced62fe2...
I (430) cpu_start: ESP-IDF: v4.2-dev-1054-g7d0f1536e-dirty
I (431) cpu_start: Starting app cpu, entry point is 0x400814dc
0x400814dc: call_start_cpu1 at /home/xiang/esp-idf/components/esp32/cpu_start.c:277
I (0) cpu_start: App cpu up.
I (433) heap_init: Initializing. RAM available for dynamic allocation:
I (433) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (434) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (435) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (435) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
I (436) heap_init: At 3FFCC1B8 len 00013E48 (79 KiB): DRAM
I (437) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (438) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (438) heap_init: At 400935F4 len 0000CA0C (50 KiB): IRAM
I (439) cpu_start: Pro cpu start user code
I (450) spi_flash: detected chip: generic
I (450) spi_flash: flash io: dio
I (450) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (452) Client: Initializing...
use esp timer !!!
I (482) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
E (482) Client: bluetooth_init initialize controller failed
E (482) Client: esp32_bluetooth_init failed (err 258)
I (31) boot: ESP-IDF v4.2-dev-1054-g7d0f1536e-dirty 2nd stage bootloader
I (31) boot: compile time 10:13:53
I (31) boot: chip revision: 1
I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (32) boot.esp32: SPI Speed : 40MHz
I (33) boot.esp32: SPI Mode : DIO
I (34) boot.esp32: SPI Flash Size : 4MB
I (34) boot: Enabling RNG early entropy source...
I (35) boot: Partition Table:
I (35) boot: ## Label Usage Type ST Offset Length
I (36) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (37) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (38) boot: 2 factory factory app 00 00 00010000 00100000
I (39) boot: End of partition table
I (39) boot_comm: chip revision: 1, min. application chip revision: 0
I (40) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x2e84c (190540) map
I (114) esp_image: segment 1: paddr=0x0003e874 vaddr=0x3ffbdb60 size=0x017a4 ( 6052) load
I (117) esp_image: segment 2: paddr=0x00040020 vaddr=0x400d0020 size=0xa5ec8 (679624) map
0x400d0020: _stext at ??:?
I (376) esp_image: segment 3: paddr=0x000e5ef0 vaddr=0x3ffbf304 size=0x025bc ( 9660) load
I (380) esp_image: segment 4: paddr=0x000e84b4 vaddr=0x40080000 size=0x00404 ( 1028) load
0x40080000: _WindowOverflow4 at /home/xiang/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730
I (381) esp_image: segment 5: paddr=0x000e88c0 vaddr=0x40080404 size=0x131f0 ( 78320) load
I (426) boot: Loaded app from partition at offset 0x10000
I (426) boot: Disabling RNG early entropy source...
I (426) cpu_start: Pro cpu up.
I (426) cpu_start: Application information:
I (427) cpu_start: Project name: vendor_client
I (428) cpu_start: App version: v4.2-dev-1054-g7d0f1536e-dirty
I (428) cpu_start: Compile time: Apr 22 2020 10:13:38
I (429) cpu_start: ELF file SHA256: 705cd9ffced62fe2...
I (430) cpu_start: ESP-IDF: v4.2-dev-1054-g7d0f1536e-dirty
I (431) cpu_start: Starting app cpu, entry point is 0x400814dc
0x400814dc: call_start_cpu1 at /home/xiang/esp-idf/components/esp32/cpu_start.c:277
I (0) cpu_start: App cpu up.
I (433) heap_init: Initializing. RAM available for dynamic allocation:
I (433) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (434) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (435) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (435) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
I (436) heap_init: At 3FFCC1B8 len 00013E48 (79 KiB): DRAM
I (437) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (438) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (438) heap_init: At 400935F4 len 0000CA0C (50 KiB): IRAM
I (439) cpu_start: Pro cpu start user code
I (450) spi_flash: detected chip: generic
I (450) spi_flash: flash io: dio
I (450) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (452) Client: Initializing...
use esp timer !!!
I (482) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
E (482) Client: bluetooth_init initialize controller failed
E (482) Client: esp32_bluetooth_init failed (err 258)
-
- Posts: 8
- Joined: Wed Apr 22, 2020 3:09 am
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
您好,我测试了4.0分支的 BLE_SPP_ERVER,没能复现您说的问题
请问是必现吗? 您有没有修改 menuconfig 里面的配置? 或者修改了部分代码
还请您提供更详细的信息:
1. ESP-IDF 的准确 commit;
2. 能够复显的 example 名字
3. 是否有改动(比如 menuconfig 代码 等等),如有,也请一并提供
请问是必现吗? 您有没有修改 menuconfig 里面的配置? 或者修改了部分代码
还请您提供更详细的信息:
1. ESP-IDF 的准确 commit;
2. 能够复显的 example 名字
3. 是否有改动(比如 menuconfig 代码 等等),如有,也请一并提供
-
- Posts: 8
- Joined: Wed Apr 22, 2020 3:09 am
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
从log来看,应该不是完全的 example, 可以提供下复现代码吗xiang8000 wrote: ↑Wed Apr 22, 2020 2:37 am启动代码如下,错误在最后两行,对应的出错代码为:
I (31) boot: ESP-IDF v4.2-dev-1054-g7d0f1536e-dirty 2nd stage bootloader
I (31) boot: compile time 10:13:53
I (31) boot: chip revision: 1
I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (32) boot.esp32: SPI Speed : 40MHz
I (33) boot.esp32: SPI Mode : DIO
I (34) boot.esp32: SPI Flash Size : 4MB
I (34) boot: Enabling RNG early entropy source...
I (35) boot: Partition Table:
I (35) boot: ## Label Usage Type ST Offset Length
I (36) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (37) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (38) boot: 2 factory factory app 00 00 00010000 00100000
I (39) boot: End of partition table
I (39) boot_comm: chip revision: 1, min. application chip revision: 0
I (40) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x2e84c (190540) map
I (114) esp_image: segment 1: paddr=0x0003e874 vaddr=0x3ffbdb60 size=0x017a4 ( 6052) load
I (117) esp_image: segment 2: paddr=0x00040020 vaddr=0x400d0020 size=0xa5ec8 (679624) map
0x400d0020: _stext at ??:?
I (376) esp_image: segment 3: paddr=0x000e5ef0 vaddr=0x3ffbf304 size=0x025bc ( 9660) load
I (380) esp_image: segment 4: paddr=0x000e84b4 vaddr=0x40080000 size=0x00404 ( 1028) load
0x40080000: _WindowOverflow4 at /home/xiang/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730
I (381) esp_image: segment 5: paddr=0x000e88c0 vaddr=0x40080404 size=0x131f0 ( 78320) load
I (426) boot: Loaded app from partition at offset 0x10000
I (426) boot: Disabling RNG early entropy source...
I (426) cpu_start: Pro cpu up.
I (426) cpu_start: Application information:
I (427) cpu_start: Project name: vendor_client
I (428) cpu_start: App version: v4.2-dev-1054-g7d0f1536e-dirty
I (428) cpu_start: Compile time: Apr 22 2020 10:13:38
I (429) cpu_start: ELF file SHA256: 705cd9ffced62fe2...
I (430) cpu_start: ESP-IDF: v4.2-dev-1054-g7d0f1536e-dirty
I (431) cpu_start: Starting app cpu, entry point is 0x400814dc
0x400814dc: call_start_cpu1 at /home/xiang/esp-idf/components/esp32/cpu_start.c:277
I (0) cpu_start: App cpu up.
I (433) heap_init: Initializing. RAM available for dynamic allocation:
I (433) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (434) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (435) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (435) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
I (436) heap_init: At 3FFCC1B8 len 00013E48 (79 KiB): DRAM
I (437) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (438) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (438) heap_init: At 400935F4 len 0000CA0C (50 KiB): IRAM
I (439) cpu_start: Pro cpu start user code
I (450) spi_flash: detected chip: generic
I (450) spi_flash: flash io: dio
I (450) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (452) Client: Initializing...
use esp timer !!!
I (482) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
E (482) Client: bluetooth_init initialize controller failed
E (482) Client: esp32_bluetooth_init failed (err 258)
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
没有更改过menuconfig中的配置,用的ESP-WROVER-KIT开发板,具体操作步骤如下:
1:下载 git clone -b v4.1-beta1 --recursive https://github.com/espressif/esp-idf.git
2:切换分支 git checkout remotes/origin/release/v4.2
3:运行了./install.sh 和 . ./exprot.sh,因为以前一直在用esp-idf V3.0,所以这两条语句基本没改变什么配置
4:进入/esp-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_vendor_model/vendor_client/例程,编译后就如上所诉,ble初始化出错。
5:我换了其他的/esp-idf/examples/bluetooth/例程,均有此错误,蓝牙初始化不过,但我git checkout 回V3.x版本就又正常了,蓝牙初始化和使用一切正常,搞不明白了……(感谢您的回复)
1:下载 git clone -b v4.1-beta1 --recursive https://github.com/espressif/esp-idf.git
2:切换分支 git checkout remotes/origin/release/v4.2
3:运行了./install.sh 和 . ./exprot.sh,因为以前一直在用esp-idf V3.0,所以这两条语句基本没改变什么配置
4:进入/esp-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_vendor_model/vendor_client/例程,编译后就如上所诉,ble初始化出错。
5:我换了其他的/esp-idf/examples/bluetooth/例程,均有此错误,蓝牙初始化不过,但我git checkout 回V3.x版本就又正常了,蓝牙初始化和使用一切正常,搞不明白了……(感谢您的回复)
-
- Posts: 8
- Joined: Wed Apr 22, 2020 3:09 am
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
我这里没能复现这个 issues
建议如下:
1. 检查下 submodule 有没有更新
2. 模组烧录固件之前,先完全擦除 flash 一次
3. 提供下你编译的 bin 文件和 sdkconfig
建议如下:
1. 检查下 submodule 有没有更新
2. 模组烧录固件之前,先完全擦除 flash 一次
3. 提供下你编译的 bin 文件和 sdkconfig
Re: ESP32-WROVER-B模组使用EPS-IDF V4.X模块出错??大佬们看看这是怎么回事
submodule 检查过,没其它的更新了
另下载前也做了flash完全清除,下载后依然如此,试了2块ESP-WROVER-KIT开发板均如此
这是附上的编译出来的bin和sdkconfig文件,对您给予的帮助再次表示感谢
另下载前也做了flash完全清除,下载后依然如此,试了2块ESP-WROVER-KIT开发板均如此
这是附上的编译出来的bin和sdkconfig文件,对您给予的帮助再次表示感谢
- Attachments
-
- vendor_client.rar
- (495.74 KiB) Downloaded 1013 times
-
- sdkconfig.rar
- (9.58 KiB) Downloaded 1059 times
Who is online
Users browsing this forum: No registered users and 111 guests