Fatal Error while building peripheral UART example.

[Nabeel Ar]

Hi,

I'm trying to test the peripheral UART example in the nRF connect SDK in the nrf52810 dk. I've built the configurations as prj_minimal.conf as mentioned in the Document. but I'm getting Fatal error uart_async_adapter.h:22:10: fatal error: zephyr/device.h: No such file or directory 22 | #include <zephyr/device.h>.

How can I solve it? Thanks in advance. 

[Turbo J]

You may grabbed an older NRF connect SDK, the include path is correct for 2.2.x and newer.

There was an include path change in the underlying zephyr RTOS.

[Nabeel Ar]

Thanks for the reply.

But I'm using version 2.2.0.

[Naeem Maroof]

Hi Nabeel,

This does not look like issue related to the DK or the project configuration file.

It appears to be the sdk/zephyr path configuration and/or the incorrect installation.

Can you please reinstall the required SDK version through the ToolChain Manager (NRF Connect for Desktop).

In such a case, please first remove the SDK, and then do a fresh install.

You may also update the SDK and update the toolchain.

Additionally, you may like to update the nRF Connect for Desktop app as well.

Regards,

Naeem

[Nabeel Ar]

Hi Naeem, 

I've removed the existing SDK and installed the latest v2.3.0 sdk. Then I created a new application "Peripheral UART" and build the configuration with pjr_minimal.conf because I want it as nrf52810 in my nrf52832 DK. I've flashed the program in my DK but I can't see any LED blinking nor It is advertising. I've opened the serial port and it is continuously printing the "Starting Nordic UART service example" message.

Please help me with it. Thanks in advance. 

[Nabeel Ar]

Hi Naeem Maroof,

Can you please update regarding this?

Thanks in advance.

[Naeem Maroof]

Hi Nabeel,

Good to know that your initial problem is resolved.

You may try to build the same example in an older ncs, for example v2.0.0.

You may also look at known issues in the ncs v2.3.0.

sample not building in v2.3.0

Regards,

Naeem

[Nabeel Ar]

 Hi Naeem Maroof,

Thanks for the reply. As you stated I can find the issue in the known issue section.

If I want to work around where can I find the CONFIG_BT_LL_CHOICE option I can't find such an option in Kconfig.

And what's the difference between CONFIG_BT_LL_SW_SPLIT and CONFIG_BT_LL_SOFTDEVICE options if I want to change them??

Thanks in advance.

[Naeem Maroof]

You can put the following in the project configuration file (prj.conf)

CONFIG_BT_LL_SOFTDEVICE=y

The difference is using "Zephyr software BLE Link Layer" vs using "Softdevice Link Layer".

You can search about these Kconfigs from Kconfig-Reference.

[Nabeel Ar]

Tried it but no help. Still, it's not advertising.

I'll try with an older version of ncs or Is there any similar example to try?