Build nrf connect SDK samples for Thingy:91 nRF52840

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øyvind — Mon, 11 Dec 2023 15:18:52 GMT

Hi,

[quote user="dno"] It has been opened without much progress for more than two months.[/quote]

Yes, this is true due to the Thingy:91 being a prototyping platform for the nRF9160. Currently, the connectivity bridge is the official supported "ble" sample that controls the USB connectivity, which runs on the nRF52840 as a board control. The application also provides an option of adding the Bluetooth® functionality by making use of the Nordic UART Service (NUS).

I assume you have looked at the LTE Sensor Gateway sample as well? Note that this sample is designed for the nRF9160DK.

[quote user="dno"]any update on this issue?[/quote]

You could try adding the following to nrf/boards/arm/thingy91_nrf52840/Kconfig.defconfig

config BT_CTLR
    default BT

This allows you to build the sample with thingy91_nrf52840 at least.

Kind regards,
Øyvind

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Fri, 08 Dec 2023 23:41:39 GMT

Hi, any update on this issue? It has been opened without much progress for more than two months. Appreciate if you can get back asap. Thanks.

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øyvind — Thu, 30 Nov 2023 14:00:39 GMT

Hello, sorry for the late reply. I have been assigned your ticket while my colleague Øivind is currently out of the office. I will need to read through the ticket and get an overview of the case. Will get back to you within Tuesday or Wednesday. Sorry for the inconvenience.

Kind regards,
Øyvind

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Wed, 29 Nov 2023 02:38:54 GMT

Hi Nordic Support Engineer,

Any update to share?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Sun, 19 Nov 2023 04:10:09 GMT

Hi Oivind, have you managed to find out the technical info from the Thingy91 developers?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Tue, 14 Nov 2023 23:33:44 GMT

Hi Oivind, any update and technical tips to share?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Tue, 07 Nov 2023 14:55:24 GMT

Hi, any update to share?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Fri, 03 Nov 2023 16:06:14 GMT

My intended use case: Using the nRF52840 in Thingy91 to connect with other BLE devices via BLE connection, using various profiles. The BLE devices which control some sensors will transmit selected data to the Thingy91's nRF52840. In addition, certain crucial data processed by Thingy91's nRF52840 will be passed on to Thingy91's nRF9160 via UART for uploading to Cloud.

In nRF Connect SDK, I only managed to find one nrf BLE example that can be built for Thing91's nRF52840, i.e. connectivity_bridge application.
None of the sample projects in nrf/samples/bluetooth supports Thingy91's nRF52840 even though quite a number of the BLE samples do support nRF52840 DK.
It seems to me, with some device tree and/or KConfig changes (primarily in the UART and button/LED configuration), the BLE samples that support nRF52840 should be able to be built for and run in Thingy91's nRF52840. Not sure why changing the board in build configuration from nrf52840 DK to thingy91_nrf52840 could result in so many build errors.

The BLE functionality in connectivity_bridge app is very limited (only support NUS), it will be helpful if Nordic can provide other BLE samples that can run in Thingy91-nRF52840.
Please help to find out from Thingy developers exactly what changes are needed in order to build those BLE samples (which support nRF52840 SDK) for Thingy91-nRF52840. Thank you.

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øivind — Fri, 03 Nov 2023 14:22:15 GMT

Hi again, I have not found a way around this yet. More details about your use case will be useful when I contact the thingy91 developers about this. Why do you need a standalone bluetooth application on the thingy91_nrf52840? What apllication are you planning to run on the thingy91_nrf9160?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øivind — Thu, 02 Nov 2023 15:08:57 GMT

Oh, so sorry. I misunderstood. That was for thingy91_nrf9160_ns. I don't really think the thingy91_nrf52840 is designed for stand-alone applications, but I will see if it is possible to get around that. I will update you tomorrow.

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Thu, 02 Nov 2023 05:27:59 GMT

Hi,
Thanks for your reply. I tried out the changes you described but I am still encountered some build errors and not able to get a successful build for the central_bas sample project. I have yet to try the changes in central_and_peripheral_hr project.

Can you help to elaborate in detail where you made the changes (e.g. which project, which files and etc)?
It will be great if you can share the whole modified sample project which you managed to build for thingy91_nrf52840, if possible.

I was trying to build for thing91_nrf52840 with the following configuration:

NCS SDK version: v2.4.2
Sample: nrf\samples\bluetooth\central_bas

Create a new build configuration (build_1) with
Board: thingy91_nrf52840
Input files:
- Configuration: proj.conf
- Overlay: thing91_nrf52840.overlay

=============================================================================
I appended the configs changes you mentioned to the proj.conf as shown below.

Modified proj.conf's content:
------------------------------

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_SMP=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_GATT_DM=y
CONFIG_HEAP_MEM_POOL_SIZE=1024
CONFIG_BT_BAS_CLIENT=y

CONFIG_BT_SCAN=y
CONFIG_BT_SCAN_FILTER_ENABLE=y
CONFIG_BT_SCAN_UUID_CNT=1
CONFIG_BT_PRIVACY=y

CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

CONFIG_DK_LIBRARY=y

# Appended the following changes as advised by Oivind:
CONFIG_NRF_SW_LPUART=y
CONFIG_NRF_SW_LPUART_INT_DRIVEN=y

CONFIG_UART_1_ASYNC=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n
CONFIG_UART_1_NRF_HW_ASYNC=y
CONFIG_UART_1_NRF_HW_ASYNC_TIMER=2

CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_TFM_LOG_LEVEL_SILENCE=y

------------------------------------------------------------------
6 problems were flagged out after making the changes, listed below:
1. CONFIG_UART_1_ASYNC was assigned the value y, but got the value n. Missing dependencies:
UART_1_NRF_UARTE
2. CONFIG_UART_1_INTERRUPT_DRIVEN was assigned the value n, but got the value n. Missing dependencies:
UART_1_NRF_UARTE
3. CONFIG_UART_1_NRF_HW_ASYNC was assigned the value y, but got the value n. Missing dependencies:
UART_1_ASYNC && UART_1_NRF_UARTE
4. CONFIG_UART_1_NRF_HW_ASYNC_TIMER couldn't be set. Missing dependencies:
UART_1_NRF_HW_ASYNC && UART_1_NRF_UARTE
5. CONFIG_LOG_BACKEND_RTT was assigned the value y, but got the value n. Missing dependencies:
!LOG_MODE_MINIMAL
6. CONFIG_TFM_LOG_LEVEL_SILENCE was assigned the value y, but got the value n. Missing dependencies:
BUILD_WITH_TFM || (BUILD_WITH_TFM && 0)

=============================================================================
I filled up the newly created thing91_nrf52840.overlay file with the devicetree changes you mentioned as shown below:

// To get started, press Ctrl+Space to bring up the completion menu and view the available nodes.

// You can also use the buttons in the sidebar to perform actions on nodes.
// Actions currently available include:

// * Enabling / disabling the node
// * Adding the bus to a bus
// * Removing the node
// * Connecting ADC channels

// For more help, browse the DeviceTree documentation at docs.zephyrproject.org/.../index.html
// You can also visit the nRF DeviceTree extension documentation at nrfconnect.github.io/.../nrfdevicetree.html

/ {
chosen {
zephyr,bt-uart=&lpuart;
};
};

&uart1 {
current-speed = <1000000>;
status = "okay";
/delete-property/ hw-flow-control;

pinctrl-0 = <&uart1_default_alt>;
pinctrl-1 = <&uart1_sleep_alt>;
pinctrl-names = "default", "sleep";
lpuart: nrf-sw-lpuart {
compatible = "nordic,nrf-sw-lpuart";
status = "okay";
req-pin = <24>;
rdy-pin = <25>;
};
};

&gpiote {
interrupts = <49 NRF_DEFAULT_IRQ_PRIORITY>;
};

&uart0 {
status = "disabled";
};

&pinctrl {
uart1_default_alt: uart1_default_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 0, 22)>,
<NRF_PSEL(UART_RX, 0, 23)>;
};
};

uart1_sleep_alt: uart1_sleep_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 0, 22)>,
<NRF_PSEL(UART_RX, 0, 23)>;
low-power-enable;
};
};
};

-----------------------------------------
2 problems were noticed in the thing91_nrf52840.overlay file:

hw-flow-control --> Unknown property
low-power-enable --> Property not mentioned in "nordic,nrf-pinctrl:child:child"

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øivind — Wed, 01 Nov 2023 15:42:43 GMT

Hi, I am able to build the samples with these changes to the devicetree and configs:

/ {
	chosen {
		zephyr,bt-uart=&lpuart;
	};
};

&uart1 {
	current-speed = <1000000>;
	status = "okay";
	/delete-property/ hw-flow-control;

	pinctrl-0 = <&uart1_default_alt>;
	pinctrl-1 = <&uart1_sleep_alt>;
	pinctrl-names = "default", "sleep";
	lpuart: nrf-sw-lpuart {
		compatible = "nordic,nrf-sw-lpuart";
		status = "okay";
		req-pin = <24>;
		rdy-pin = <25>;
	};
};

&gpiote {
	interrupts = <49 NRF_DEFAULT_IRQ_PRIORITY>;
};

&uart0 {
	status = "disabled";
};

&pinctrl {
	uart1_default_alt: uart1_default_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 22)>,
				<NRF_PSEL(UART_RX, 0, 23)>;
		};
	};

	uart1_sleep_alt: uart1_sleep_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 22)>,
				<NRF_PSEL(UART_RX, 0, 23)>;
			low-power-enable;
		};
	};
};

CONFIG_NRF_SW_LPUART=y
CONFIG_NRF_SW_LPUART_INT_DRIVEN=y

CONFIG_UART_1_ASYNC=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n
CONFIG_UART_1_NRF_HW_ASYNC=y
CONFIG_UART_1_NRF_HW_ASYNC_TIMER=2

CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_TFM_LOG_LEVEL_SILENCE=y

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Mon, 30 Oct 2023 09:24:58 GMT

Hi Oivind,

Any update to share?

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

deno — Wed, 25 Oct 2023 00:06:52 GMT

Hi,

I encountered build errors when building the following nrf connect SDK samples for thingy91_nrf52840:

1) C:\ncs\v2.4.2\nrf\samples\bluetooth\central_bas

2) C:\ncs\v2.4.2\nrf\samples\bluetooth\central_and_peripheral_hr

Below are the error messages shown:

C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:84:41: error: '__device_dts_ord_DT_CHOSEN_zephyr_bt_uart_ORD' undeclared here (not in a function)
84 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
| ^~~~~~~~~
C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:210:37: note: in expansion of macro 'DEVICE_NAME_GET'
210 | #define DEVICE_DT_NAME_GET(node_id) DEVICE_NAME_GET(Z_DEVICE_DT_DEV_ID(node_id))
| ^~~~~~~~~~~~~~~
C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:227:34: note: in expansion of macro 'DEVICE_DT_NAME_GET'
227 | #define DEVICE_DT_GET(node_id) (&DEVICE_DT_NAME_GET(node_id))
| ^~~~~~~~~~~~~~~~~~
C:\ncs\v2.4.2\zephyr\drivers\bluetooth\hci\h4.c:74:44: note: in expansion of macro 'DEVICE_DT_GET'
74 | static const struct device *const h4_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_bt_uart));
| ^~~~~~~~~~~~~
[161/238] Linking C static library zephyr\subsys\bluetooth\host\libsubsys__bluetooth__host.a
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'c:\ncs\v2.4.2\nrf\samples\bluetooth\central_bas\build_1'

------------------------------------------------

C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:84:41: error: '__device_dts_ord_DT_CHOSEN_zephyr_bt_uart_ORD' undeclared here (not in a function)
84 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
| ^~~~~~~~~
C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:210:37: note: in expansion of macro 'DEVICE_NAME_GET'
210 | #define DEVICE_DT_NAME_GET(node_id) DEVICE_NAME_GET(Z_DEVICE_DT_DEV_ID(node_id))
| ^~~~~~~~~~~~~~~
C:\ncs\v2.4.2\zephyr\include\zephyr\device.h:227:34: note: in expansion of macro 'DEVICE_DT_NAME_GET'
227 | #define DEVICE_DT_GET(node_id) (&DEVICE_DT_NAME_GET(node_id))
| ^~~~~~~~~~~~~~~~~~
C:\ncs\v2.4.2\zephyr\drivers\bluetooth\hci\h4.c:74:44: note: in expansion of macro 'DEVICE_DT_GET'
74 | static const struct device *const h4_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_bt_uart));
| ^~~~~~~~~~~~~
[5/79] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_nrfx.c.obj
[6/79] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/soc_flash_nrf.c.obj
[7/79] Building C object zephyr/drivers/serial/CMakeFiles/drivers__serial.dir/uart_nrfx_uarte.c.obj
[8/79] Building C object zephyr/drivers/pinctrl/CMakeFiles/drivers__pinctrl.dir/pinctrl_nrf.c.obj
[9/79] Building C object zephyr/drivers/timer/CMakeFiles/drivers__timer.dir/nrf_rtc_timer.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'c:\ncs\v2.4.2\nrf\samples\bluetooth\central_and_peripheral_hr\build'

RE: Build nrf connect SDK samples for Thingy:91 nRF52840

Øivind — Tue, 24 Oct 2023 21:21:15 GMT

Hi,

The compatible board list is not exhaustive, so the sample may work without issues on boards not listed.
Could you give me one or more examples of samples which you are having issues with? Then I will look into which changes are necessary for those samples.