Skip to content

fix(nimble): Enable legacy VHCI support #311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lucasssvaz
Copy link
Member

Description

This pull request adds support for legacy VHCI (Virtual Host Controller Interface) mode in the NimBLE Bluetooth stack across multiple ESP32 platform configuration files. The main change is the enabling of the CONFIG_BT_NIMBLE_LEGACY_VHCI_ENABLE option, which may improve compatibility with legacy Bluetooth controller interfaces.

Related

Fixes espressif/arduino-esp32#11716

@lucasssvaz lucasssvaz requested a review from me-no-dev August 13, 2025 12:07
@lucasssvaz lucasssvaz self-assigned this Aug 13, 2025
@lyusupov
Copy link

lyusupov commented Aug 23, 2025

@lucasssvaz

Not sure that this commit f6c9202
gives positive effect necessary.

For instance, there are still no VHCI symbols for C5 in artifacts section of the Actions build :
https://github.com/espressif/esp32-arduino-lib-builder/actions/runs/16936720969

image


$ pwd
/tmp/tools/esp32-arduino-libs/esp32c5/lib
$ nm libbt.a | grep -e esp_vhci -e nimble
         U nimble_port_get_dflt_eventq
nm: bt_hci_log.c.obj: no symbols
nm: ble_log_spi_out.c.obj: no symbols
nm: esp_ble_mesh_generic_model_api.c.obj: no symbols
nm: esp_ble_mesh_lighting_model_api.c.obj: no symbols
nm: esp_ble_mesh_sensor_model_api.c.obj: no symbols
nm: esp_ble_mesh_time_scene_model_api.c.obj: no symbols
nm: btc_ble_mesh_ble.c.obj: no symbols
nm: btc_ble_mesh_generic_model.c.obj: no symbols
nm: btc_ble_mesh_lighting_model.c.obj: no symbols
nm: btc_ble_mesh_sensor_model.c.obj: no symbols
nm: btc_ble_mesh_time_scene_model.c.obj: no symbols
nm: ecc_platform_specific.c.obj: no symbols
nm: settings_nvs.c.obj: no symbols
nm: settings_uid.c.obj: no symbols
nm: settings.c.obj: no symbols
nm: ble_adv.c.obj: no symbols
nm: cfg_cli.c.obj: no symbols
nm: fast_prov.c.obj: no symbols
nm: friend.c.obj: no symbols
nm: health_cli.c.obj: no symbols
nm: lpn.c.obj: no symbols
nm: prov_node.c.obj: no symbols
nm: prov_pvnr.c.obj: no symbols
nm: proxy_client.c.obj: no symbols
nm: proxy_server.c.obj: no symbols
nm: pvnr_mgmt.c.obj: no symbols
nm: test.c.obj: no symbols
nm: generic_client.c.obj: no symbols
nm: lighting_client.c.obj: no symbols
nm: sensor_client.c.obj: no symbols
nm: time_scene_client.c.obj: no symbols
nm: generic_server.c.obj: no symbols
nm: lighting_server.c.obj: no symbols
nm: sensor_server.c.obj: no symbols
nm: server_common.c.obj: no symbols
nm: state_binding.c.obj: no symbols
nm: state_transition.c.obj: no symbols
nm: time_scene_server.c.obj: no symbols
nm: esp_ble_mesh_agg_model_api.c.obj: no symbols
nm: esp_ble_mesh_brc_model_api.c.obj: no symbols
nm: esp_ble_mesh_df_model_api.c.obj: no symbols
nm: esp_ble_mesh_lcd_model_api.c.obj: no symbols
nm: esp_ble_mesh_odp_model_api.c.obj: no symbols
nm: esp_ble_mesh_prb_model_api.c.obj: no symbols
nm: esp_ble_mesh_rpr_model_api.c.obj: no symbols
nm: esp_ble_mesh_sar_model_api.c.obj: no symbols
nm: esp_ble_mesh_srpl_model_api.c.obj: no symbols
nm: esp_ble_mesh_mbt_model_api.c.obj: no symbols
nm: btc_ble_mesh_agg_model.c.obj: no symbols
nm: btc_ble_mesh_brc_model.c.obj: no symbols
nm: btc_ble_mesh_df_model.c.obj: no symbols
nm: btc_ble_mesh_lcd_model.c.obj: no symbols
nm: btc_ble_mesh_mbt_model.c.obj: no symbols
nm: btc_ble_mesh_odp_model.c.obj: no symbols
nm: btc_ble_mesh_prb_model.c.obj: no symbols
nm: btc_ble_mesh_rpr_model.c.obj: no symbols
nm: btc_ble_mesh_sar_model.c.obj: no symbols
nm: btc_ble_mesh_srpl_model.c.obj: no symbols
hci_driver_nimble.c.obj:
nm: transport.c.obj: no symbols
nm: ble_svc_hid.c.obj: no symbols
nm: ble_svc_cte.c.obj: no symbols
nm: ble_hs_shutdown.c.obj: no symbols
         U nimble_port_get_dflt_eventq
         U nimble_port_get_dflt_eventq
nm: ble_hs_periodic_sync.c.obj: no symbols
nm: ble_ead.c.obj: no symbols
nm: ble_aes_ccm.c.obj: no symbols
nm: ble_l2cap_coc.c.obj: no symbols
nm: ble_hs_resolv.c.obj: no symbols
nm: ble_store_ram.c.obj: no symbols
nm: ble_store_nvs.c.obj: no symbols
nm: ble_gattc_cache.c.obj: no symbols
nm: ble_gattc_cache_conn.c.obj: no symbols
nm: ble_eatt.c.obj: no symbols
nimble_port.c.obj:
00000000 T esp_nimble_deinit
00000000 T esp_nimble_init
00000000 T nimble_port_deinit
00000000 T nimble_port_get_dflt_eventq
00000000 T nimble_port_init
00000000 T nimble_port_run
00000000 T nimble_port_stop
00000000 t nimble_port_stop_cb
nimble_port_freertos.c.obj:
00000000 T esp_nimble_disable
00000000 T esp_nimble_enable
00000000 T nimble_port_freertos_deinit
00000000 T nimble_port_freertos_init

@lucasssvaz
Copy link
Member Author

@lyusupov Indeed, you are right. From what I see these VHCI functions depend only on CONFIG_BT_CONTROLLER_ENABLED and CONFIG_BT_LE_HCI_INTERFACE_USE_RAM which we already have. They shouldn't depend on any stack settings. I will investigate.

@lucasssvaz lucasssvaz marked this pull request as draft August 23, 2025 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ArduinoBLE fails to build on H2 and C6 using v3.3.0 release
2 participants