AT Firmware does not build when using Bluedroid for ESP32-C6 about esp-at HOT 3 CLOSED

Direct support from Espressif received.
ESP32-C6 should only be built with NimBLE - BT SIG listing identified to allow use of the NimBLE stack.

from esp-at.

I have managed to progress the build by changing the following:
Component Config -> Bluetooth -> Host = Bluedroid
Component Config -> Bluetooth -> Bluedroid Options -> Include blufi function = enabled
Component Config -> Bluetooth -> Bluedroid Options -> Enable Peripheral Preferred Connection Parameters characteristic in GAP service = enabled
Component Config -> Bluetooth -> Bluedroid Options -> Enable BLE 4.2 features = enabled

The build is now failing at the linker step trying to link nimble functions even though it is disabled, see:
idf_py_stdout_output_115646.log

sdkconfig:
sdkconfig.txt

from esp-at.

@JHedgesBartec Hello!
You cannot modify the default Bluetooth protocol stack. This is because the core code in libesp32c6_at_core.a already uses the default protocol stack. Switching the protocol stack would result in some symbols not being found during the linking phase.

Could you please provide more details about why you need to change it, maybe we can give some suggestions.

from esp-at.