Strange behaviour on init of BLE/nimBLE

Fredckx
Posts: 17
Joined: Mon Mar 29, 2021 8:55 pm

Strange behaviour on init of BLE/nimBLE

Postby Fredckx » Tue Nov 30, 2021 9:11 pm

I have a problem with initializing a BLE/nimBLE controller. I use an ESP32 (Heltec LORA32 V2) and ESP-IDF 4.2 in the command line.

When I try to initialize a nimBLE controller with esp_bt_controller_init(&bt_cfg)) I see the following messages in my monitor screen:

I (1631) BTDM_INIT: BT controller compile version [3723d5b]
D (1637) BTDM_INIT: .data initialise [0x3ffae6e0] <== [0x4000d890]
D (1643) BTDM_INIT: .bss initialise [0x3ffb0000] - [0x3ffb09a8]
D (1649) BTDM_INIT: .bss initialise [0x3ffb09a8] - [0x3ffb1ddc]
D (1655) BTDM_INIT: .bss initialise [0x3ffb1ddc] - [0x3ffb2730]
D (1661) BTDM_INIT: .bss initialise [0x3ffb8000] - [0x3ffb9a20]
D (1667) BTDM_INIT: .bss initialise [0x3ffbdb28] - [0x3ffbdb5c]

After this, the system reboots without further notice.

During booting I see messages like:

D (671) memory_layout: Reserved memory range 0x40080000 - 0x4009c1c4
0x40080000: _WindowOverflow4 at C:/Users/Fred/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1730

D (677) memory_layout: Building list of available memory regions:
V (684) memory_layout: Examining memory region 0x3ffae000 - 0x3ffb0000
V (690) memory_layout: Start of region 0x3ffae000 - 0x3ffb0000 overlaps reserved 0x3ffae000 - 0x3ffae6e0
V (700) memory_layout: Start of region 0x3ffae6e0 - 0x3ffb0000 overlaps reserved 0x3ffae6e0 - 0x3ffaff10
D (709) memory_layout: Available memory region 0x3ffaff10 - 0x3ffb0000
V (716) memory_layout: Examining memory region 0x3ffb0000 - 0x3ffb8000
V (722) memory_layout: Start of region 0x3ffb0000 - 0x3ffb8000 overlaps reserved 0x3ffb0000 - 0x3ffb6388
D (732) memory_layout: Available memory region 0x3ffb6388 - 0x3ffb8000
V (739) memory_layout: Examining memory region 0x3ffb8000 - 0x3ffc0000
V (745) memory_layout: Start of region 0x3ffb8000 - 0x3ffc0000 overlaps reserved 0x3ffb8000 - 0x3ffb9a20
V (755) memory_layout: Region 0x3ffb9a20 - 0x3ffc0000 contains reserved 0x3ffbdb28 - 0x3ffbdb5c
D (764) memory_layout: Available memory region 0x3ffb9a20 - 0x3ffbdb28
V (770) memory_layout: Examining memory region 0x3ffbdb5c - 0x3ffc0000
V (777) memory_layout: End of region 0x3ffbdb5c - 0x3ffc0000 overlaps reserved 0x3ffbdb60 - 0x3ffc96e0
V (786) memory_layout: Examining memory region 0x3ffc0000 - 0x3ffc2000
V (793) memory_layout: Region 0x3ffc0000 - 0x3ffc2000 inside of reserved 0x3ffbdb60 - 0x3ffc96e0
V (802) memory_layout: Examining memory region 0x3ffc2000 - 0x3ffc4000
V (808) memory_layout: Region 0x3ffc2000 - 0x3ffc4000 inside of reserved 0x3ffbdb60 - 0x3ffc96e0
V (817) memory_layout: Examining memory region 0x3ffc4000 - 0x3ffc6000
V (824) memory_layout: Region 0x3ffc4000 - 0x3ffc6000 inside of reserved 0x3ffbdb60 - 0x3ffc96e0
V (832) memory_layout: Examining memory region 0x3ffc6000 - 0x3ffc8000
V (839) memory_layout: Region 0x3ffc6000 - 0x3ffc8000 inside of reserved 0x3ffbdb60 - 0x3ffc96e0
V (848) memory_layout: Examining memory region 0x3ffc8000 - 0x3ffca000
V (854) memory_layout: Start of region 0x3ffc8000 - 0x3ffca000 overlaps reserved 0x3ffbdb60 - 0x3ffc96e0
D (864) memory_layout: Available memory region 0x3ffc96e0 - 0x3ffca000
V (871) memory_layout: Examining memory region 0x3ffca000 - 0x3ffcc000


As part of the regions are the same as those listed by the BTDM_INIT messages, I thought that the clue could be in these overlapping memory regions. Is that true? What can I do to find the origin of failure of initialization ofthe nimBLE controller?

Thanks

Who is online

Users browsing this forum: Baidu [Spider] and 126 guests