CONFIG_FLASH_MAP was assigned the value y, but got the value n. Missing dependencies: FLASH_HAS_DRIVER_ENABLED

[robbsadler]

I have the following settings in my prj.conf:

# Enable the BLE stack with GATT Client configuration
CONFIG_BT=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y

# Enable BLE scan
CONFIG_BT_SCAN=y
CONFIG_BT_SCAN_FILTER_ENABLE=y
CONFIG_BT_SCAN_SHORT_NAME_CNT=1
CONFIG_BT_GATT_DM=y

# Enable bonding
CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y

# Config logger
CONFIG_LOG=y

and getting the error 

CONFIG_FLASH_MAP was assigned the value y, but got the value n. Missing dependencies:
FLASH_HAS_DRIVER_ENABLED

My understanding is that FLASH_HAS_DRIVER_ENABLED is not set directly, but by inclusion of some config that assures that flash drivers will be included.

I have the same flash setting in another project and it is working...

Using v2.8 SDK and Toolchain.

Running on nRF52840.

Your input is greatly appreciated!

[Edvin]

DevZone is a bit flaky sometimes. Perhaps it works now if you try again.

I tried to add the above at the end of prj.conf in the NCS v2.8.0\nrf\samples\bluetooth\peripheral_uart (but I couldn't remove what was already there, because that would cause it to fail due to undefined references to e.g. buttons or UART). 

It built without any errors/warnings.

What sample were you using? Is it possible to zip the application folder of the sample you were using, and upload it here? (let us hope DevZone behaves this time). Also, what build command are you using? It is possible to copy it if you are using VS Code by right clicking the build folder in the "Applications" menu.

Best regards,

Edvin

[robbsadler]

It was the bluetooth central sample: zephyr/samples/bluetooth/central. I created it and then added the prj.conf lines and that should repro for you (unless my install is not right somehow).

[Edvin]

Hello,

I tried the zephyr\samples\bluetooth\central sample now, and it built without issues (also with your prj.conf file). 

I got your build log from Marvin (I understand you spoke to him as well).

I noticed that it says:

--domain bt_central_test at the end of the build command. Do you know why that is there? I have not seen it before. I assume bt_central_test is the name of the application folder (because it told me "valid domains are: central", which is the name of my application folder. 

Have you tried deleting the build folder and generate it again?

Have you tried building from command line using the build command: "west build -b nrf52840dk/nrf52840 -d build"

If it still doesn't work, I suspect an SDK/toolchain setup issue. How did you set up your SDK and Toolchain?

Best regards,

Edvin

[robbsadler]

I had created a brand new application named "bt_central_test" thus the name at the end of the build command. And thus with the new application the build folder was not there prior to that.

It could be my toolchain or SDKs are the issue. I installed then using the nrf Connect extension in VS Code. I have reinstalled them before. 

I will try the command line to see if anything different results.

Thanks!

[robbsadler]

I agree it must be toolchain. I tested on my laptop and the build was successful. I had figured I had a configuration incorrect, thus the ticket. Thanks for your help!

[robbsadler]

Weird thing - the build was successful, but I had the warning "CONFIG_UART_CONSOLE was assigned the value y, but got the value n. Missing dependencies:
SERIAL_HAS_DRIVER" on my laptop show up in the "Problems" tab, but the log didn't show any warnings. It has a fresh install of the toolchain and SDK. (2.8).

I'm going to drop this issue for now, and circle back if it a problem on the code I move over into my main development project from this central sample.

Thanks again!

[Edvin]

I tend to ignore the "problems" tab. This is because the warnings/problems there are usually not real. I believe it struggles to understand the application context. So I would say that it is absolutely best to rely on the information in the build log. If the build log says that the "CONFIGU_UART_CONSOLE was assigned the value y, but got the value n. Missing dependencies: ...", then it is real, and something you need to look into. 

Best regards,

Edvin