Bluetooth peripheral sample doesn't work on esp32

[mwerschy]

Describe the bug
The device does not show up in scans (e.g. in LightBlue) when running the bluetooth peripheral sample after #80404.

Board: FireBeetle ESP32-E V1.0
Chip revision: v3.0

To Reproduce

• Build and flash the bluetooth/peripheral sample.
• Zephyr Peripheral Sample device does not show up when scanning bluetooth devices.

Expected behavior

Bluetooth peripheral can be scanned.

Impact

Blocks upgrade to Zephyr 4.0.

Logs and console output

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:0x3ffe8000,len:10668
ho 0 tail 12 room 4
load:0x40078000,len:5968
load:0x400a0000,len:37336
entry 0x400a2ee8
I (36) boot: MCUboot 2nd stage bootloader
I (36) boot: compile time Mar  3 2025 10:54:33
W (37) boot: Unicore bootloader
I (37) spi_flash: detected chip: generic
I (41) spi_flash: flash io: dio
I (43) boot: chip revision: v3.0
I (46) boot.esp32: SPI Speed      : 40MHz
I (50) boot.esp32: SPI Mode       : DIO
I (54) boot.esp32: SPI Flash Size : 4MB
I (57) boot: Enabling RNG early entropy source...
I (93) spi_flash: flash io: dio
[esp32] [INF] Image index: 0, Swap type: none
[esp32] [INF] Loading image 0 - slot 0 from flash, area id: 1
[esp32] [INF] Application start=40090238h
[esp32] [INF] DRAM segment: paddr=000351e4h, vaddr=3ffbdb60h, size=020ach (  8364) load
[esp32] [INF] IRAM segment: paddr=00020040h, vaddr=40080000h, size=151a4h ( 86436) load
I (125) boot: DROM segment: paddr=00040000h, vaddr=3f400000h, size=07124h ( 28964) map
I (125) boot: IROM segment: paddr=00050000h, vaddr=400d0000h, size=33940h (211264) map

I (165) heap_runtime: ESP heap runtime init at 0x3ffc8a80 size 93 kB.

I (165) spi_flash: detected chip: generic
I (165) spi_flash: flash io: dio
*** Booting Zephyr OS build (tainted) v3.7.0-5544-g5678512fe830 ***
[00:00:00.177,000] <0x1b>[0m<inf> fs_nvs: 8 Sectors of 4096 bytes<0x1b>[0m
[00:00:00.177,000] <0x1b>[0m<inf> fs_nvs: alloc wra: 0, f88<0x1b>[0m
[00:00:00.177,000] <0x1b>[0m<inf> fs_nvs: data wra: 0, 7c<0x1b>[0m
[00:00:00.178,000] <0x1b>[0m<inf> esp32_bt_adapter: BT controller compile version [241c96c]<0x1b>[0m
[00:00:00.558,000] <0x1b>[0m<inf> bt_hci_core: No ID address. App must call settings_load()<0x1b>[0m
Bluetooth initialized
[00:00:00.560,000] <0x1b>[0m<inf> bt_hci_core: Identity: 08:3A:F2:3B:59:94 (public)<0x1b>[0m
[00:00:00.560,000] <0x1b>[0m<inf> bt_hci_core: HCI: version 4.2 (0x08) revision 0x030e, manufacturer 0x0060<0x1b>[0m
[00:00:00.560,000] <0x1b>[0m<inf> bt_hci_core: LMP: version 4.2 (0x08) subver 0x030e<0x1b>[0m
Advertising successfully started
Indicate VND attr 0x3f400068 (UUID 12345678-1234-5678-1234-56789abcdef1)

Environment:

• OS: Linux
• Toolchain: Zephyr SDK 0.17.0
• Last good commit: 45fbc31a3f0065f0c5a54ab3cf8cd2d38afdc8a3
• First bad commit: 5678512fe830422c1d909f73cad9db3e8a0d0d19

[sylvioalves]

@mwerschy Have you tested in latest main?

[mwerschy]

Yeah the issue occurs there too.

[sylvioalves]

I have just tested here and it worked using nrfconnect app. Let me try out another board later.
Have you run west blobs fetch hal_espressif in order to pull latest RF libraries as well?

[sylvioalves]

Ok, I was able to reproduce on chip rev v3.1.

[mwerschy]

Yes blobs are up to date. I tested with the firebeetle and a custom rev v3.1 board just now on c7a19da8ca1abefa8eac41e704e7c678af0282a9 (latest as of writing) and can still reproduce.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[mwerschy]

Still broken as of e96bf44d934.